RE: [Geopriv] I-DACTION:draft-ietf-geopriv-http-location-delivery-00.txt

From: Winterbottom, James ^lt;James.Winterbottom@andrew.com>
Date: Fri Jun 08 2007 - 19:39:58 EDT

Hi Henning, I have no concerns about changing the message codes. I am not sure that I see too many issues with the options extension, though as you point out, adding attributes and using their namespace for qualifying them is the norm within XML. I find it hard to believe that you can't see how the identity extensions aren't provided. Please look at http://tools.ietf.org/html/draft-winterbottom-geopriv-held-identity-exte nsions-01 It has after all only be presented a couple of time now. This is as opposed to something proprietary like Cisco Discovery Protocolas RELO suggests. Cheers James > -----Original Message----- > From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] > Sent: Saturday, 9 June 2007 6:26 AM > To: GEOPRIV > Subject: Re: [Geopriv] I-DACTION:draft-ietf-geopriv-http-location- > delivery-00.txt > > We should probably revisit some of the discussions we've had for > LoST, which have led us to abandon the concept of status codes in > favor of "real" XML. I won't repeat the arguments (Andy can chime > in...), but the basic idea was that this makes debugging and > validation easier and seems much more in the spirit of XML. Using > codes that are almost, but not quite, the same as HTTP (or SIP) seems > to be an invitation for confusion or creative extensions where HTTP > codes are "borrowed". > > I'm also unconvinced that creating a non-namespace extensions > mechanism (options) is a good idea. Either we use XML and its tools > or we make up our own protocol, but a hybrid seems dubious > architecturally. IANA can register namespaces, too. > > The editor may want to take a look at the identity mechanisms in > RELO. It is currently not clear how entities are identified and how > this is extensible. > > Henning > > _______________________________________________ > Geopriv mailing list > Geopriv@ietf.org > https://www1.ietf.org/mailman/listinfo/geopriv ------------------------------------------------------------------------------------------------ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any unauthorized use of this email is prohibited. ------------------------------------------------------------------------------------------------ [mf2]

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv
Received on Fri, 8 Jun 2007 18:39:58 -0500

This archive was generated by hypermail 2.1.8 : Fri Jun 08 2007 - 19:40:10 EDT