idnits 2.17.1
draft-winterbottom-geopriv-held-identity-extensions-04.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 465.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 476.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 483.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 489.
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
== Line 160 has weird spacing: '...dDevice xmlns...'
== 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 (November 19, 2007) is 6000 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 417, but no explicit
reference was found in the text
== Outdated reference: A later version (-16) exists of
draft-ietf-geopriv-http-location-delivery-03
== Outdated reference: A later version (-10) exists of
draft-ietf-geopriv-l7-lcp-ps-05
** 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-00
-- Obsolete informational reference (is this intentional?): RFC 2434
(Obsoleted by RFC 5226)
Summary: 4 errors (**), 0 flaws (~~), 7 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: May 22, 2008 H. Tschofenig
6 Nokia Siemens Networks
7 November 19, 2007
9 HELD Identity Extensions
10 draft-winterbottom-geopriv-held-identity-extensions-04.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 May 22, 2008.
37 Copyright Notice
39 Copyright (C) The IETF Trust (2007).
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 URIs 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. URI Definitions . . . . . . . . . . . . . . . . . . . . . 6
67 3.1.1. Ethernet MAC URI . . . . . . . . . . . . . . . . . . . 6
68 3.1.2. IP Address URIs . . . . . . . . . . . . . . . . . . . 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 URIs 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 URI or
110 typed-token. A set of URI definitions that can be used to specify
111 these identities is also provided.
113 3.1. URI Definitions
115 The URIs 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 URIs in the following sub-sections are defined using ABNF
126 (augmented Backus-Naur form) described in [RFC2234].
128 3.1.1. Ethernet MAC URI
130 This is the Ethernet hardware address of the device. The ABNF for
131 this URI type is defined as:
133 mac-uri = "mac:" 12*12HEXDIG
135 This type of URI is, for example, used in RFC 4479 [RFC4479]. An
136 example of its use is provided in Figure 5.
138 3.1.2. IP Address URIs
140 This section provides the ABNF for IP version 4 and IP version 6
141 URIs. One application of this URI scheme is described in
142 [I-D.ietf-geopriv-l7-lcp-ps], where an outbound SIP proxy needs to
143 make location requests to a LIS on behalf of a Target because, for
144 some reason, the necessary information was not provided by the
145 Target.
147 ip-uri = "ip:" ipv4 / ipv6
148 ipv4 = "IPv4+" IPv4-Address
149 IPv4-Address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT
150 ipv6 = "IPv6+" hexpart [ ":" IPv4-Address ]
151 hexpart = hexseq / hexseq "::" [ hexseq ] / "::" [ hexseq ]
152 hexseq = hex4 *( ":" hex4)
153 hex4 = 1*4HEXDIG
154 An example of a location request including a URI in this form to
155 identify the Target device is shown in Figure 3.
157
159 geodetic
160
161 ip:IPv4+192.0.2.5
162
163
165 Figure 3: HELD Location Request Using an IP Address
167 Note that the URI types are not case sensitive and the iP:ipv4+
168 192.0.2.5 is still a valid URI.
170 3.2. Schema
172 This section defines a schema that is used to provide Target
173 identifiers in a HELD location request.
175
176
183
185
186
187
188
190
191
192
194
196
197
198
199
201
202
203
205
207
208
209
211
213
214
216
218
220 Figure 4: Schema
222 The schema provided in Figure 4 allows a URI and/or token to be
223 provided so that a Target can identify itself by more than just its
224 IP address. The URI can also include an optional "type" attribute so
225 that URIs that might otherwise look the same can be distinguished
226 based on their usage.
228 For example sip:callee@example.com or sip:callee@example.com
231 When the element is used the "type" attribute is
232 mandatory as it tells the LIS or receiving entity how to interpret
233 the identifier. An IANA registry is established for the central
234 repository for recognized identifier types. The set of initial types
235 is provided in Section 5.3.
237 A HELD location request sent by a device using the schema shown in
238 Figure 4 to provide its identity as a MAC URI would look similar to
239 Figure 5.
241
243 geodetic
244
245 mac:01ab34ef690c
246
247
249 Figure 5: HELD Location Request URI example
251 Similarly a Target identifying itself using its DHCP client
252 identifier (DHCP option 61 in [RFC2132]) in a location request to a
253 LIS would send something similar to Figure 6.
255
257 geodetic
258
259 035552764
260
261
263 Figure 6: HELD Location Request Identifier example
265 4. Security Considerations
267 An operator of a LIS that supports this schema extension needs to
268 ensure that location provided to nodes requesting location in this
269 manner are entitled to the location information being requested. In
270 some circumstances support of this schema extension will be
271 inappropriate and alternative measures will need to be employed.
273 5. IANA Considerations
275 This document registers an XML namespace and schema with IANA in
276 accordance with guidelines in [RFC3688]. It also creates a new
277 registry for device identity types, and stipulates how new types are
278 to be added.
280 5.1. URN Sub-Namespace Registration for
281 urn:ietf:params:xml:ns:geopriv:held:id
283 This section registers a new XML namespace,
284 "urn:ietf:params:xml:ns:geopriv:held:id", as per the guidelines in
285 [RFC3688].
287 URI: urn:ietf:params:xml:ns:geopriv:held:id
289 Registrant Contact: IETF, GEOPRIV working group,
290 (geopriv@ietf.org), James Winterbottom
291 (james.winterbottom@andrew.com).
293 XML:
295 BEGIN
296
297
299
300
301 HELD Device Identity Extensions
302
303
304 Namespace for HELD Device Identity Extensions
305 urn:ietf:params:xml:ns:geopriv:held:id
306 [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
307 with the RFC number for this specification.]]
308 See RFCXXXX.
309
310
311 END
313 5.2. XML Schema Registration
315 This section registers an XML schema as per the guidelines in
316 [RFC3688].
318 URI: urn:ietf:params:xml:schema:geopriv:held:id
320 Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org),
321 James Winterbottom (james.winterbottom@andrew.com).
323 Schema: The XML for this schema can be found as the entirety of
324 Figure 4 of this document.
326 5.3. Identifier 'type' Attribute values
328 This document requests that the IANA create a new registry for
329 identifier 'type' attribute values. These are text strings that
330 clarify how the value identifies the Device. Referring to [RFC2434]
331 this registry operates under the "Expert Review" rule.
333 The following identifier types are registered as part of this memo:
335 o 'dhcpClientId' The DHCP client identifier as defined by DHCP
336 option 61 in [RFC2132]
338 o 'msisdn' The Mobile Station International Subscriber Dial Number.
339 This is an E.164 number made up of 6 to 15 digits
341 o 'imsi' The International Mobile Subscriber identifier. A unique
342 identifier for GSM or UMTS mobile terminal made up of 6 to 15
343 digits that identify the country code, the network code and
344 device.
346 o 'imei' The International Mobile Equipment identifier. This is an
347 electronic serial number for a mobile device and is consists of up
348 to 15 digits
350 o 'min' Mobile Identification Number. A unique equipment identifier
351 assigned to CDMA handsets.
353 o 'mdn' Mobile Dial Number. An E.164 number made up of 6 to 15
354 digits.
356 o 'hostname' The hostname or FQDN of the device.
358 6. Acknowledgements
360 The authors wish to thank the NENA VoIP location working group for
361 their assistance in the definition of the schema used in this
362 document. Special thanks go to Barbara Stark, Guy Caron, Nadine
363 Abbott, Jerome Grenier and Martin Dawson. Thanks also to Bob Sherry
364 for requesting that URI-types be supported which led to the typedURI
365 form.
367 7. References
369 7.1. Normative references
371 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
372 Requirement Levels", BCP 14, RFC 2119, March 1997.
374 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
375 January 2004.
377 [I-D.ietf-geopriv-http-location-delivery]
378 Barnes, M., Winterbottom, J., Thomson, M., and B. Stark,
379 "HTTP Enabled Location Delivery (HELD)",
380 draft-ietf-geopriv-http-location-delivery-03 (work in
381 progress), November 2007.
383 [I-D.ietf-geopriv-l7-lcp-ps]
384 Tschofenig, H. and H. Schulzrinne, "GEOPRIV Layer 7
385 Location Configuration Protocol; Problem Statement and
386 Requirements", draft-ietf-geopriv-l7-lcp-ps-05 (work in
387 progress), September 2007.
389 [RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
390 Specifications: ABNF", RFC 2234, November 1997.
392 7.2. Informative references
394 [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and
395 J. Polk, "Geopriv Requirements", RFC 3693, February 2004.
397 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
398 Extensions", RFC 2132, March 1997.
400 [I-D.thomson-geopriv-held-measurements]
401 Thomson, M. and J. Winterbottom, "Using Device-provided
402 Location Measurements in HELD",
403 draft-thomson-geopriv-held-measurements-00 (work in
404 progress), October 2007.
406 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
407 IANA Considerations Section in RFCs", BCP 26, RFC 2434,
408 October 1998.
410 [LLDP] IEEE, "802.1AB, IEEE Standard for Local and Metropolitan
411 area networks, Station and Media Access Control
412 Connectivity Discovery", June 2005.
414 [RFC3046] Patrick, M., "DHCP Relay Agent Information Option",
415 RFC 3046, January 2001.
417 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers",
418 RFC 3966, December 2004.
420 [RFC4479] Rosenberg, J., "A Data Model for Presence", RFC 4479,
421 July 2006.
423 Authors' Addresses
425 James Winterbottom
426 Andrew Corporation
427 PO Box U40
428 University of Wollongong, NSW 2500
429 AU
431 Email: james.winterbottom@andrew.com
433 Martin Thomson
434 Andrew Corporation
435 PO Box U40
436 University of Wollongong, NSW 2500
437 AU
439 Email: martin.thomson@andrew.com
441 Hannes Tschofenig
442 Nokia Siemens Networks
443 Otto-Hahn-Ring 6
444 Munich, Bavaria 81739
445 Germany
447 Phone: +49 89 636 40390
448 Email: Hannes.Tschofenig@nsn.com
449 URI: http://www.tschofenig.com
451 Full Copyright Statement
453 Copyright (C) The IETF Trust (2007).
455 This document is subject to the rights, licenses and restrictions
456 contained in BCP 78, and except as set forth therein, the authors
457 retain all their rights.
459 This document and the information contained herein are provided on an
460 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
461 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
462 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
463 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
464 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
465 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
467 Intellectual Property
469 The IETF takes no position regarding the validity or scope of any
470 Intellectual Property Rights or other rights that might be claimed to
471 pertain to the implementation or use of the technology described in
472 this document or the extent to which any license under such rights
473 might or might not be available; nor does it represent that it has
474 made any independent effort to identify any such rights. Information
475 on the procedures with respect to rights in RFC documents can be
476 found in BCP 78 and BCP 79.
478 Copies of IPR disclosures made to the IETF Secretariat and any
479 assurances of licenses to be made available, or the result of an
480 attempt made to obtain a general license or permission for the use of
481 such proprietary rights by implementers or users of this
482 specification can be obtained from the IETF on-line IPR repository at
483 http://www.ietf.org/ipr.
485 The IETF invites any interested party to bring to its attention any
486 copyrights, patents or patent applications, or other proprietary
487 rights that may cover technology that may be required to implement
488 this standard. Please address the information to the IETF at
489 ietf-ipr@ietf.org.
491 Acknowledgment
493 Funding for the RFC Editor function is provided by the IETF
494 Administrative Support Activity (IASA).