RE: [Geopriv] New ID creating DHCP LbyR URI delivery Option

From: Winterbottom, James ^lt;James.Winterbottom@andrew.com>
Date: Mon May 14 2007 - 19:39:44 EDT

Hi James, An interesting draft given some of the debates that we have had in the past.. ;) That aside, I have several concerns with this draft. The first is that this does not seem to me to be talking about a reference for LCP, but rather a generic LbyR mechanism, that is it is providing a reference for third parties to dereference. It is unclear to me, what the relationship is between the DHCP server, and thing that is providing location, is the DHCP server being opened up to the general Internet for querying, or is the DHCP server being turned into an application server of some kind? A formal specification describing how the DHCP gets this information, and what it sets in the LIS needs to be defined, for much the same reasons that DHCP updates DNS records. My next concern, is that there is no support or mechanism of any kind for the end-point to specify to the LIS (or whatever the DHCP is getting/setting its information in) what options to set in the resulting PIDF-LO, or indeed who is allowed to access the information. This is not talked about at all in the security section and really needs to be discussed. My final first cut concern is that there is no reference made to the location by reference requirements document, or discussion on how this proposal meets those requirements. Cheers James > -----Original Message----- > From: James M. Polk [mailto:jmpolk@cisco.com] > Sent: Tuesday, 15 May 2007 7:56 AM > To: geopriv@ietf.org > Subject: [Geopriv] New ID creating DHCP LbyR URI delivery Option > > Geopriv WG > > Here is the announcement of a new and real simple ID that creates and > IANA registers a DHCP Option for delivering a Location-by-Reference > (LbyR) URI to an endsystem. > > + I believe we want this LbyR value to be all inclusive, meaning not > break up the Option by having separate DHCP fields for each URI > parameter and/or header parameter another protocol, such as SIP, > might use. This allows for a simple single value Option in DHCP, and > only one length field - for the whole option. I believe the > characters within the URI will provide any delineation necessary, > such as the ' < ', ' > ', and ' ; ' signs used in the ABNF of SIP > header structure. Does anyone disagree with this? > > + What I don't know is if this Option should identify which type of > URI is present (sip, sips, pres...). Anyone have thoughts on make > this an explicit field in the Option (where the URI will already > indicate this)? > > + I'm also not sure if this Option should identify UTF-16, and > therefore also UTF-8, characters as a separate Option field. Any > opinions on this? I could add a "Reserved" field of a byte or two > just for these types of extensions in the future, whenever they are > wanted or needed. Thoughts? > > + I currently state in this ID that > > "LbyR URIs SHOULD NOT reveal identity information of the > user of the device, > since DHCP is a cleartext delivery protocol." > > Should this "SHOULD NOT" be a "MUST NOT"? I know we don't want > identity info in this, but is that need strong enough to be a MUST > NOT strength here in DHCP? > > + Additional comments are appreciated. > > James > > > >A New Internet-Draft is available from the on-line Internet-Drafts > >directories. > > > > Title : Dynamic Host Configuration Protocol > > (DHCP) Option for a Location-by-Reference (LbyR) Uniform Resource > > Identifier (URI) > > Author(s) : J. Polk > > Filename : draft-polk-geopriv-dhcp-lbyr-uri-option-00.txt > > Pages : 7 > > Date : 2007-5-14 > > > > This document creates a Dynamic Host Configuration Protocol (DHCP) > > Option for the Location-by-Reference (LbyR) Uniform Resource > > Identifier (URI) of an endpoint. For example, an endpoint can be a > > Session Initiation Protocol (SIP) User Agent Client (UAC), i.e., a > > phone. This LbyR URI can be included in a UA's messages to inform > > other nodes of that UA's geographic location, once the URI is > > dereferenced by a Location Recipient. > > > >A URL for this Internet-Draft is: > >http://www.ietf.org/internet-drafts/draft-polk-geopriv-dhcp-lbyr-uri- > option-00.txt > > > >_______________________________________________ > >I-D-Announce mailing list > >I-D-Announce@ietf.org > >https://www1.ietf.org/mailman/listinfo/i-d-announce > > _______________________________________________ > 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 Mon, 14 May 2007 18:39:44 -0500

This archive was generated by hypermail 2.1.8 : Mon May 14 2007 - 19:39:54 EDT