idnits 2.17.1 draft-ietf-geopriv-flow-identity-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 13, 2013) is 4089 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) -- Obsolete informational reference (is this intentional?): RFC 793 (Obsoleted by RFC 9293) -- Obsolete informational reference (is this intentional?): RFC 4960 (Obsoleted by RFC 9260) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 GEOPRIV R. Bellis 3 Internet-Draft Nominet UK 4 Updates: RFC 6155 (if approved) February 13, 2013 5 Intended status: Standards Track 6 Expires: August 17, 2013 8 Flow Identity Extension for HELD 9 draft-ietf-geopriv-flow-identity-01 11 Abstract 13 RFC 6155 specifies an extension for the HTTP-Enabled Location 14 Delivery (HELD) Protocol allowing the use of an IP address and port 15 number to request a Device location based on an individual packet 16 flow. 18 However, certain kinds of NAT require that identifiers for both ends 19 of the packet flow must be specified in order to unambiguously 20 satisfy the location request. 22 This document specifies an XML Schema and URN Sub-Namespace for a 23 Flow Identity Extension for HELD to support this requirement. 25 This document updates RFC 6155 by deprecating the port number 26 elements specified therein. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on August 17, 2013. 45 Copyright Notice 47 Copyright (c) 2013 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Conventions used in this document . . . . . . . . . . . . . . 4 64 3. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 67 5.1. URN Sub-Namespace Registration for 68 urn:ietf:params:xml:ns:geopriv:held:flow . . . . . . . . . 8 69 5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 8 70 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 9 71 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 72 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 73 9. Notes to the RFC Editor (to be removed) . . . . . . . . . . . 12 74 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 75 10.1. Normative References . . . . . . . . . . . . . . . . . . . 13 76 10.2. Informative References . . . . . . . . . . . . . . . . . . 13 77 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 79 1. Introduction 81 Work at the Emergency Location Task Group of NICC Standards Ltd (the 82 UK's telecoms industry standards body) prompted the addition of Port 83 Number identifiers in HELD Identity [RFC6155] to allow HELD [RFC5985] 84 requests for target Devices that are behind a NAT device. 86 Subsequent analysis has determined that in the presence of particular 87 types of NAT device, and in particular Carrier Grade NATs, it is 88 necessary to know the complete tuple of (layer 3 protocol, layer 4 89 protocol, source address, source port, destination address, 90 destination port) in order to unambiguously identify a flow, and 91 therefore the true target Device. 93 This document specifies an XML Schema and URN Sub-Namespace for a 94 Flow Identity Extension to support this requirement. 96 Since the Location Recipient may not know in advance whether the 97 Target is behind a NAT device the port number elements from Section 98 3.3 of [RFC6155] are deprecated and MUST NOT be used. This document 99 provides a more generally applicable means of identifying a Device 100 based on the parameters of a network flow of which it is an endpoint. 102 2. Conventions used in this document 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 106 document are to be interpreted as described in [RFC2119]. 108 3. Usage 110 An example HELD request is shown below: 112 114 geodetic 115 117 118
192.168.1.1
119 1024 120 121 122
10.0.0.1
123 80 124 125 126 128 The element MUST contain: 130 o a "layer3" attribute with a value of "ipv4" or "ipv6". 132 o a "layer4" attribute with a value of "udp" [RFC0768], "tcp" 133 [RFC0793], "sctp" [RFC4960], "dccp" [RFC4340], or a decimal 134 integer representing any applicable protocol from the IANA 135 Assigned Internet Protocol Numbers Registry. 137 and MAY optionally contain: 139 o a "target" attribute with a value of "src" (default) or "dst" to 140 indicate which end of the flow is the Target of the 141 with respect to the HELD protocol. 143 4. XML Schema 145 146 151 152 154 HELD Flow Identity 155 157 This document defines Flow Identity elements for HELD. 158 159 161 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 208 5. IANA Considerations 210 5.1. URN Sub-Namespace Registration for 211 urn:ietf:params:xml:ns:geopriv:held:flow 213 This section registers a new XML namespace, 214 "urn:ietf:params:xml:ns:geopriv:held:flow", as per the guidelines in 215 [RFC3688]. 217 URI: urn:ietf:params:xml:ns:geopriv:held:flow 219 Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), 220 Ray Bellis (ray.bellis@nominet.org.uk) 222 XML: 224 BEGIN 225 226 228 229 230 HELD Flow Identity Parameters 231 232 233

Namespace for HELD Flow Identity Parameters

234

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

235

See 236 RFC NEW1.

237 238 239 END 241 5.2. XML Schema Registration 243 This section registers an XML schema as per the guidelines in 244 [RFC3688] 246 URI: urn:ietf:params:xml:ns:geopriv:held:flow 248 Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), 249 Ray Bellis (ray.bellis@nominet.org.uk) 251 Schema: The XML for this schema can be found as the entirety of 252 Section 4 of this document. 254 6. Privacy Considerations 256 This document introduces no new privacy considerations beyond those 257 in [RFC6155] 259 7. Security Considerations 261 This document introduces no new security considerations beyond those 262 in [RFC6155] 264 8. Acknowledgements 266 The author wishes to thank the members of the NICC Emergency Location 267 Task Group, the IETF GeoPriv Working Group, and the authors of 268 [RFC6155], from which the text for the URN and XML Schema 269 Registrations were derived. 271 9. Notes to the RFC Editor (to be removed) 273 References to "NEW1" need to be replaced with this document's final 274 RFC number. 276 10. References 278 10.1. Normative References 280 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 281 Requirement Levels", BCP 14, RFC 2119, March 1997. 283 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 284 January 2004. 286 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", 287 RFC 5985, September 2010. 289 [RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. 290 Barnes, "Use of Device Identity in HTTP-Enabled Location 291 Delivery (HELD)", RFC 6155, March 2011. 293 10.2. Informative References 295 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 296 August 1980. 298 [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, 299 RFC 793, September 1981. 301 [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram 302 Congestion Control Protocol (DCCP)", RFC 4340, March 2006. 304 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 305 RFC 4960, September 2007. 307 Author's Address 309 Ray Bellis 310 Nominet UK 311 Edmund Halley Road 312 Oxford OX4 4DQ 313 United Kingdom 315 Phone: +44 1865 332211 316 Email: ray.bellis@nominet.org.uk 317 URI: http://www.nominet.org.uk/