OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

kmip message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [Fwd: Key Encoding Text]

Here's the proposal I mentioned at the f2f.

--- Begin Message ---
Bob, Judy, and Indra,

In the past, some symmetric key systems have had problems when two 
clients chose different ways to load the keys they were given.  For 
example, one decided to load the key it was given in its register as the 
first byte of the OCTET STRING going in the last byte of their register 
and another did as the first byte of their register.  They're obviously 
not going to interoperate.   I know it seems like this ought to be a 
"duh" kind of thing, but I'm afraid it could happen again without saying 
something.  I've drafted the attached text to explain how the bytes in 
the key that is sent correspond to how it needs to be used (for AES and 
DES keys).  I think it needs to go in the spec because I think it's 
normative.  But, I'm not entirely sure where we should put it.  Thoughts?


Proposal for Key Encoding Text.doc

--- End Message ---

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]