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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

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


Subject: RE: [uddi-spec] First draft of CR-036 (changes to key hashing) uploaded


Thanks John for this posting. Could you please explain how you arrived to "14 e3 a2 b1 3b d8 4c f5 af a6 0d 14 1b f3 20 76" (i.e. how was it generated, what order is it being represented in?)

Secondly, given the confusion, I think that the text of the CR and the errata needs to be clear that this key needs to put in network byte order. Your CR does not reflect this update to the spec as I think it should.

FYI, please also note that once CR-032 and CR-036 are approved that we'll be in a position to put to vote the WSDL v2 TN. If approved, this TN will be posted before the first v3 errata and thus, we'll need some supporting text on the web page explaining that the keys presented in the TN are those based on a corrected version of the hashing algo. 

Luc Clément 
Microsoft 
Co-chair, OASIS UDDI Spec TC 



-----Original Message-----
From: John Colgrave [mailto:colgrave@hursley.ibm.com] 
Sent: Wednesday, June 18, 2003 09:20
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] First draft of CR-036 (changes to key hashing) uploaded

I have uploaded the first draft of CR-036.

As agreed, I have not changed the table.

I have not updated the reference to the Leach draft as I believe that was incorporated into CR-002.

An updated version of the Leach draft formed the basis of the registration document for a UUID URN Namespace, but that document expired on April 1, 2003.  If you want to look at it anyway, you can find it at http://www.ietf.org/internet-drafts/draft-mealling-uuid-urn-00.txt

There is an online version of the description of the original DCE UUIDs available at http://www.opengroup.org

I ended up regenerating keys for 41 entities, all but one of them tModels.
Of these, only 9 or 10 would not have been affected by the case-folding change so I think we did the right thing is changing the name space ID used in the algorithm.

I think it would be a good idea for someone, ideally with a "little-endian"
implementation, to update it with the new name space ID and the case-folding, and check that they produce the same keys.

John Colgrave
IBM




You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php





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