idnits 2.17.1 draft-winterbottom-geopriv-held-identity-extensions-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 471. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 482. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 489. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 495. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Too long document name: The document name (without revision number), 'draft-winterbottom-geopriv-held-identity-extensions', is 51 characters long, but may be at most 50 characters Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 30, 2008) is 5810 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3966' is defined on line 423, but no explicit reference was found in the text == Outdated reference: A later version (-16) exists of draft-ietf-geopriv-http-location-delivery-07 == Outdated reference: A later version (-10) exists of draft-ietf-geopriv-l7-lcp-ps-07 ** Downref: Normative reference to an Informational draft: draft-ietf-geopriv-l7-lcp-ps (ref. 'I-D.ietf-geopriv-l7-lcp-ps') ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) == Outdated reference: A later version (-06) exists of draft-thomson-geopriv-held-measurements-02 -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 4 errors (**), 0 flaws (~~), 6 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Geopriv J. Winterbottom 3 Internet-Draft M. Thomson 4 Intended status: Standards Track Andrew Corporation 5 Expires: December 1, 2008 H. Tschofenig 6 Nokia Siemens Networks 7 May 30, 2008 9 HELD Identity Extensions 10 draft-winterbottom-geopriv-held-identity-extensions-05.txt 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on December 1, 2008. 37 Copyright Notice 39 Copyright (C) The IETF Trust (2008). 41 Abstract 43 When a Location Information Server receives a request for location 44 information (using the locationRequest message), described in the 45 base HTTP Enabled Location Delivery (HELD) specification, it uses the 46 source IP address of arriving message as a pointer to the location 47 determination process. This is appropriate in many environments. 48 However, when an entity acting on behalf of the Target would like to 49 request location information then the source IP address of the 50 request will lead to wrong results. In other cases the IP address is 51 not the only identifier that serves as an input to the location 52 determination procedure. 54 This document extends the HELD protocol to allow the location request 55 message to carry additional identifiers assisting the location 56 determination process. It defines a set of URNs for Target 57 identifiers and an XML containment schema. As such, this extension 58 is used in conjunction with HELD to provide Target identification. 59 Examples and usage in HELD message syntax are provided. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 3. Identity Extension Details . . . . . . . . . . . . . . . . . . 6 66 3.1. URN Definitions . . . . . . . . . . . . . . . . . . . . . 6 67 3.1.1. Ethernet MAC URN . . . . . . . . . . . . . . . . . . . 6 68 3.1.2. IP Address URNs . . . . . . . . . . . . . . . . . . . 6 69 3.2. Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 7 70 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 71 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 72 5.1. URN Sub-Namespace Registration for 73 urn:ietf:params:xml:ns:geopriv:held:id . . . . . . . . . . 11 74 5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 11 75 5.3. Identifier 'type' Attribute values . . . . . . . . . . . . 12 76 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 77 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 78 7.1. Normative references . . . . . . . . . . . . . . . . . . . 14 79 7.2. Informative references . . . . . . . . . . . . . . . . . . 14 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 81 Intellectual Property and Copyright Statements . . . . . . . . . . 17 83 1. Introduction 85 Location Configuration Protocols, such as HELD 86 [I-D.ietf-geopriv-http-location-delivery], need to identify a Target 87 in order to determine its location. The base HELD specification only 88 provides Target identity through the IP address of the requesting 89 Target, while [I-D.ietf-geopriv-l7-lcp-ps] provides examples of where 90 this may be insufficient. This memo defines a set of URNs and a 91 containment schema that allows the entity requesting location 92 information to indicate a Target identifier beyond the source IP 93 address of the request. 95 2. Terminology 97 This document reuses the term Target, as defined in [RFC3693]. 99 This document uses the term Location Information Server, LIS as 100 described in [I-D.ietf-geopriv-l7-lcp-ps]. 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in [RFC2119]. 106 3. Identity Extension Details 108 This section defines the details of the schema extension for HELD to 109 support the inclusion of a Target identity in the form of a URN or 110 typed-token. A set of URN definitions that can be used to specify 111 these identities is also provided. 113 3.1. URN Definitions 115 The URNs defined in this section are designed to identify a Target; 116 they do not identify measurements or sighting data associated with a 117 Target, such as the switch and port information to which the Target 118 is attached. This information may, for example, be acquired using 119 DHCP relay information [RFC3046] or LLDP [LLDP]. Device measurements 120 and sighting data are described in 121 [I-D.thomson-geopriv-held-measurements]. The identity provided may 122 be transitory, such as an IP address that is leased from a DHCP 123 server pool. 125 The URNs in the following sub-sections are defined using ABNF 126 (augmented Backus-Naur form) described in [RFC2234]. 128 3.1.1. Ethernet MAC URN 130 This is the Ethernet hardware address of the device, and is defined 131 as per the IEEE 802 specifications. The ABNF for this URN type is 132 defined as: 134 mac-uri = "mac:" 2*2HEXDIG 5*5macdig 135 macdig = "-" 2*2HEXDIG 137 This type of URN is, for example, used in RFC 4479 [RFC4479]. An 138 example of its use is provided in Figure 5. 140 3.1.2. IP Address URNs 142 This section provides the ABNF for IP version 4 and IP version 6 143 URNs. One application of this URN scheme is described in 144 [I-D.ietf-geopriv-l7-lcp-ps], where an outbound SIP proxy needs to 145 make location requests to a LIS on behalf of a Target because, for 146 some reason, the necessary information was not provided by the 147 Target. 149 ip-uri = "ip:" ipv4 / ipv6 150 ipv4 = "IPv4+" IPv4-Address 151 IPv4-Address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT 152 ipv6 = "IPv6+" hexpart [ ":" IPv4-Address ] 153 hexpart = hexseq / hexseq "::" [ hexseq ] / "::" [ hexseq ] 154 hexseq = hex4 *( ":" hex4) 155 hex4 = 1*4HEXDIG 157 An example of a location request including a URN in this form to 158 identify the Target device is shown in Figure 3. 160 162 geodetic 163 164 ip:IPv4+192.0.2.5 165 166 168 Figure 3: HELD Location Request Using an IP Address 170 Note that the URN types are not case sensitive and the iP:ipv4+ 171 192.0.2.5 is still a valid URN. 173 3.2. Schema 175 This section defines a schema that is used to provide Target 176 identifiers in a HELD location request. 178 179 186 188 189 190 191 193 194 195 197 199 200 201 202 204 205 206 208 210 211 212 214 216 217 219 221 223 Figure 4: Schema 225 The schema provided in Figure 4 allows a URI and/or token to be 226 provided so that a Target can identify itself by more than just its 227 IP address. The URI can also include an optional "type" attribute so 228 that URIs that might otherwise look the same can be distinguished 229 based on their usage. 231 For example sip:callee@example.com or sip:callee@example.com 234 When the element is used the "type" attribute is 235 mandatory as it tells the LIS or receiving entity how to interpret 236 the identifier. An IANA registry is established for the central 237 repository for recognized identifier types. The set of initial types 238 is provided in Section 5.3. 240 A HELD location request sent by a device using the schema shown in 241 Figure 4 to provide its identity as a MAC URI would look similar to 242 Figure 5. 244 246 geodetic 247 248 mac:01-ab-34-ef-69-0c 249 250 252 Figure 5: HELD Location Request URI example 254 Similarly a Target identifying itself using its DHCP client 255 identifier (DHCP option 61 in [RFC2132]) in a location request to a 256 LIS would send something similar to Figure 6. 258 260 geodetic 261 262 035552764 263 264 266 Figure 6: HELD Location Request Identifier example 268 4. Security Considerations 270 An operator of a LIS that supports this schema extension needs to 271 ensure that location provided to nodes requesting location in this 272 manner are entitled to the location information being requested. In 273 some circumstances support of this schema extension will be 274 inappropriate and alternative measures will need to be employed. 276 5. IANA Considerations 278 This document registers an XML namespace and schema with IANA in 279 accordance with guidelines in [RFC3688]. It also creates a new 280 registry for device identity types, and stipulates how new types are 281 to be added. 283 5.1. URN Sub-Namespace Registration for 284 urn:ietf:params:xml:ns:geopriv:held:id 286 This section registers a new XML namespace, 287 "urn:ietf:params:xml:ns:geopriv:held:id", as per the guidelines in 288 [RFC3688]. 290 URI: urn:ietf:params:xml:ns:geopriv:held:id 292 Registrant Contact: IETF, GEOPRIV working group, 293 (geopriv@ietf.org), James Winterbottom 294 (james.winterbottom@andrew.com). 296 XML: 298 BEGIN 299 300 302 303 304 HELD Device Identity Extensions 305 306 307

Namespace for HELD Device Identity Extensions

308

urn:ietf:params:xml:ns:geopriv:held:id

309 [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX 310 with the RFC number for this specification.]] 311

See RFCXXXX.

312 313 314 END 316 5.2. XML Schema Registration 318 This section registers an XML schema as per the guidelines in 319 [RFC3688]. 321 URI: urn:ietf:params:xml:schema:geopriv:held:id 323 Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org), 324 James Winterbottom (james.winterbottom@andrew.com). 326 Schema: The XML for this schema can be found as the entirety of 327 Figure 4 of this document. 329 5.3. Identifier 'type' Attribute values 331 This document requests that the IANA create a new registry for 332 identifier 'type' attribute values. These are text strings that 333 clarify how the value identifies the Device. Referring to [RFC2434] 334 this registry operates under the "Expert Review" rule. 336 The following identifier types are registered as part of this memo: 338 o 'dhcpClientId' The DHCP client identifier as defined by DHCP 339 option 61 in [RFC2132] 341 o 'msisdn' The Mobile Station International Subscriber Dial Number. 342 This is an E.164 number made up of 6 to 15 digits 344 o 'imsi' The International Mobile Subscriber identifier. A unique 345 identifier for GSM or UMTS mobile terminal made up of 6 to 15 346 digits that identify the country code, the network code and 347 device. 349 o 'imei' The International Mobile Equipment identifier. This is an 350 electronic serial number for a mobile device and is consists of up 351 to 15 digits 353 o 'min' Mobile Identification Number. A unique equipment identifier 354 assigned to CDMA handsets. 356 o 'mdn' Mobile Dial Number. An E.164 number made up of 6 to 15 357 digits. 359 o 'hostname' The hostname or FQDN of the device. 361 o 'directoryNumber' The directory number of the device. 363 6. Acknowledgements 365 The authors wish to thank the NENA VoIP location working group for 366 their assistance in the definition of the schema used in this 367 document. Special thanks go to Barbara Stark, Guy Caron, Nadine 368 Abbott, Jerome Grenier and Martin Dawson. Thanks also to Bob Sherry 369 for requesting that URI-types be supported which led to the typedURI 370 form. Thanks to Adam Muhlbauer and Eddy Corbett for providing 371 further corrections. 373 7. References 375 7.1. Normative references 377 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 378 Requirement Levels", BCP 14, RFC 2119, March 1997. 380 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 381 January 2004. 383 [I-D.ietf-geopriv-http-location-delivery] 384 Barnes, M., Winterbottom, J., Thomson, M., and B. Stark, 385 "HTTP Enabled Location Delivery (HELD)", 386 draft-ietf-geopriv-http-location-delivery-07 (work in 387 progress), April 2008. 389 [I-D.ietf-geopriv-l7-lcp-ps] 390 Tschofenig, H. and H. Schulzrinne, "GEOPRIV Layer 7 391 Location Configuration Protocol; Problem Statement and 392 Requirements", draft-ietf-geopriv-l7-lcp-ps-07 (work in 393 progress), March 2008. 395 [RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 396 Specifications: ABNF", RFC 2234, November 1997. 398 7.2. Informative references 400 [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and 401 J. Polk, "Geopriv Requirements", RFC 3693, February 2004. 403 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 404 Extensions", RFC 2132, March 1997. 406 [I-D.thomson-geopriv-held-measurements] 407 Thomson, M. and J. Winterbottom, "Using Device-provided 408 Location-Related Measurements in HELD", 409 draft-thomson-geopriv-held-measurements-02 (work in 410 progress), May 2008. 412 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 413 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 414 October 1998. 416 [LLDP] IEEE, "802.1AB, IEEE Standard for Local and Metropolitan 417 area networks, Station and Media Access Control 418 Connectivity Discovery", June 2005. 420 [RFC3046] Patrick, M., "DHCP Relay Agent Information Option", 421 RFC 3046, January 2001. 423 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", 424 RFC 3966, December 2004. 426 [RFC4479] Rosenberg, J., "A Data Model for Presence", RFC 4479, 427 July 2006. 429 Authors' Addresses 431 James Winterbottom 432 Andrew Corporation 433 PO Box U40 434 University of Wollongong, NSW 2500 435 AU 437 Email: james.winterbottom@andrew.com 439 Martin Thomson 440 Andrew Corporation 441 PO Box U40 442 University of Wollongong, NSW 2500 443 AU 445 Email: martin.thomson@andrew.com 447 Hannes Tschofenig 448 Nokia Siemens Networks 449 Otto-Hahn-Ring 6 450 Munich, Bavaria 81739 451 Germany 453 Phone: +49 89 636 40390 454 Email: Hannes.Tschofenig@nsn.com 455 URI: http://www.tschofenig.com 457 Full Copyright Statement 459 Copyright (C) The IETF Trust (2008). 461 This document is subject to the rights, licenses and restrictions 462 contained in BCP 78, and except as set forth therein, the authors 463 retain all their rights. 465 This document and the information contained herein are provided on an 466 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 467 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 468 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 469 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 470 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 471 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 473 Intellectual Property 475 The IETF takes no position regarding the validity or scope of any 476 Intellectual Property Rights or other rights that might be claimed to 477 pertain to the implementation or use of the technology described in 478 this document or the extent to which any license under such rights 479 might or might not be available; nor does it represent that it has 480 made any independent effort to identify any such rights. Information 481 on the procedures with respect to rights in RFC documents can be 482 found in BCP 78 and BCP 79. 484 Copies of IPR disclosures made to the IETF Secretariat and any 485 assurances of licenses to be made available, or the result of an 486 attempt made to obtain a general license or permission for the use of 487 such proprietary rights by implementers or users of this 488 specification can be obtained from the IETF on-line IPR repository at 489 http://www.ietf.org/ipr. 491 The IETF invites any interested party to bring to its attention any 492 copyrights, patents or patent applications, or other proprietary 493 rights that may cover technology that may be required to implement 494 this standard. Please address the information to the IETF at 495 ietf-ipr@ietf.org. 497 Acknowledgment 499 Funding for the RFC Editor function is provided by the IETF 500 Administrative Support Activity (IASA).