[cap-talk] Implementing a crypto brand: What are the security requirements?

Mark Miller erights at gmail.com
Fri Mar 23 16:37:03 CDT 2007


On 3/22/07, Kevin Reid <kpreid at mac.com> wrote:
> I have no objection to this renaming if MarkM agrees. However, if I
> were renaming things I would rename the constructor rather than the
> "label".

I do not agree. E's terminology goes back to the Ode, and has not
previously caused any confusion. Changing it now would cause
confusion. To avoid a conflict, Tyler is now looking for another name
for the concept he was calling "Brand".

More generally, I want to caution us from spending too much time
thrashing on differences between E/Pluribus vs Joe-E/Waterken vs
Emily/Dyne. These systems have many similarities, but also many
differences. These differences help us to better explore the design
space. It is inevitable in any such process that the same names get
used across these systems for similar but different concepts. This
creates some confusion, but I don't think there's any better
alternative.

-- 
Text by me above is hereby placed in the public domain

    Cheers,
    --MarkM


More information about the cap-talk mailing list