[wsf-dev] 160 bit message id

[Cahill, Conor P]

There's an interesting history in the discussion of the message ID
value. 
 
The current requirement (lines 557-559 of the SOAP Bindings
specification) is:

	Any party that assigns a value to a <wsa:MessageID> header block
MUST ensure that there is negligible probability that that party or any
other party will accidentally assign the same identifier to any other
message

This is not a 160 or 128 bit requirement.
 
I would presume that a 128 bit UUID that included the 48 bits of mac
address of the issuing host would meet that requirement.
 
Conor



________________________________

	From: wsf-dev-bounces at openliberty.org
[mailto:wsf-dev-bounces at openliberty.org] On Behalf Of Asa Hardcastle
	Sent: Monday, April 30, 2007 4:36 PM
	To: wsf-dev at openliberty.org
	Subject: [wsf-dev] 160 bit message id
	
	
	Hi All, 

	Does anyone know the origin of the 160 bit message id
requirement in the <wsa:MessageID> header?  Before I read that line I
was thinking of using a 128 bit UUID.

	thanks,

	asa


	
	

	--
	Asa Hardcastle, Technical Lead, openLiberty
	Tel: +1.413.429.1044 Skype: subsystem7



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openliberty.org/pipermail/wsf-dev/attachments/20070430/f1de3677/attachment.html