Re: Proposed Up/Down protocol description

[Robert Loomans <robertl@apnic.net>]

>> (BTW, do we *mean* g(SKI), ie, g(SHA1(public key)), or do we really just
>> want to put in the hex of SKI, ie, SHA1(public key), instead? The only
>> interesting thing about g(SKI) was that it's filesystem/URL safe.)
> 
> SKI = sha1(public key) in my lexicon
> 
> so g(ski) is g(sha1(public key))

I know.

I'm asking about representation. Do we really need the g()?

The ski is a 128-bit binary string

eg, printf("%x, ski) => e2b306c8e2e8af09413c432e246c2cdc34e26949

g(ski) == base64url(ski) == base64url(sha1(public key))

eg, g(ski) => 4rMGyOLorwlBPEMuJGws3DTiaUk

I don't care which we use: they are just different encodings of the
binary data.

I just don't believe that we need the g() function to be part of this
protocol... and if that's the case, I would prefer to drop it.

Rob

-- 
Robert Loomans                                 Email:  robertl@apnic.net
Programmer/Analyst, APNIC                      Phone:    +61 7 3858 3100
http://www.apnic.net                             Fax:    +61 7 3858 3199

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature