idnits 2.17.1 draft-bellis-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. -- The draft header indicates that this document updates RFC6155, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 14, 2012) is 4358 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- 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 (==), 4 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) May 14, 2012 5 Intended status: Informational 6 Expires: November 15, 2012 8 Flow Identity Extension for HELD 9 draft-bellis-geopriv-flow-identity-01 11 Abstract 13 Identity Extensions using an IP address and port number to request a 14 location based on an individual packet flow have been previously 15 specified by the GEOPRIV Working Group. 17 However certain kinds of NAT require that identifiers for both ends 18 of the packet flow must be specified in order to unambiguously 19 satisfy the location request. 21 This document specifieds a Flow Identity Extension for the HTTP- 22 Enabled Location Delivery (HELD) Protocol to support this 23 requirement. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on November 15, 2012. 42 Copyright Notice 44 Copyright (c) 2012 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Conventions used in this document . . . . . . . . . . . . . . 4 61 3. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 64 5.1. URN Sub-Namespace Registration for 65 urn:ietf:params:xml:ns:geopriv:held:flow . . . . . . . . . 8 66 5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 8 67 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 9 68 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 69 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 70 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 71 8.2. Informative References . . . . . . . . . . . . . . . . . . 11 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 74 1. Introduction 76 Work at the Emergency Location Working Group of NICC Standards Ltd 77 (the UK's telecoms standards body) prompted the addition of Port 78 Number identifiers in HELD Identity [RFC6155] to allow HELD [RFC5985] 79 requests for target Devices that are behind a NAT device. 81 Subsequent analysis has determined that in the presence of particular 82 types of NAT device, and in particular Carrier Grade NATs, it is 83 necessary to know the complete tuple of (layer 3 protocol, layer 4 84 protocol, source address, source port, destination address, 85 destination port) in order to unambiguously identify a flow, and 86 therefore the true target Device. 88 This document creates an XML Schema and URN Sub-Namespace for a Flow 89 Identity Extension to support this requirement. 91 2. Conventions used in this document 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in [RFC2119]. 97 3. Usage 99 An example HELD request is show below: 101 103 geodetic 104 106 107
192.168.1.1
108 1024 109 110 111
10.0.0.1
112 80 113 114 115 117 The element MUST contain: 119 o a "layer3" attribute with a value of "ipv4" or "ipv6". 121 o a "layer4" attribute with a value of "udp" [RFC0768], "tcp" 122 [RFC0793], "sctp" [RFC4960], "dccp" [RFC4340], or a decimal 123 integer representing any applicable protocol from the IANA 124 Assigned Internet Protocol Numbers Registry. 126 and MAY optionally contain: 128 o a "target" attribute with a value of "src" (default) or "dst" to 129 indicate which end of the flow is the "target" of the 130 with respect to the HELD protocol. 132 4. XML Schema 134 135 140 141 143 HELD Flow Identity 144 146 This document defines Flow Identity elements for HELD. 147 148 150 152 153 154 155 156 157 158 159 160 161 162 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 197 5. IANA Considerations 199 5.1. URN Sub-Namespace Registration for 200 urn:ietf:params:xml:ns:geopriv:held:flow 202 This section registers a new XML namespace, 203 "urn:ietf:params:xml:ns:geopriv:held:flow", as per the guidelines in 204 [RFC3688]. 206 URI: urn:ietf:params:xml:ns:geopriv:held:flow 208 Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), 209 Ray Bellis (ray.bellis@nominet.org.uk) 211 XML: 213 BEGIN 214 215 217 218 219 HELD Flow Identity Parameters 220 221 222

Namespace for HELD Flow Identity Parameters

223

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

224

See 225 RFC NEW1.

226 227 228 END 230 5.2. XML Schema Registration 232 This section registers an XML schema as per the guidelines in 233 [RFC3688] 235 URI: urn:ietf:params:xml:ns:geopriv:held:flow 237 Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), 238 Ray Bellis (ray.bellis@nominet.org.uk) 240 Schema: The XML for this schema can be found as the entirety of 241 Section 4 of this document. 243 6. Privacy Considerations 245 This document introduces no new privacy considerations beyond those 246 in [RFC6155] 248 7. Security Considerations 250 This document introduces no new security considerations beyond those 251 in [RFC6155] 253 8. References 255 8.1. Normative References 257 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 258 Requirement Levels", BCP 14, RFC 2119, March 1997. 260 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 261 January 2004. 263 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", 264 RFC 5985, September 2010. 266 [RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. 267 Barnes, "Use of Device Identity in HTTP-Enabled Location 268 Delivery (HELD)", RFC 6155, March 2011. 270 8.2. Informative References 272 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 273 August 1980. 275 [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, 276 RFC 793, September 1981. 278 [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram 279 Congestion Control Protocol (DCCP)", RFC 4340, March 2006. 281 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 282 RFC 4960, September 2007. 284 Author's Address 286 Ray Bellis 287 Nominet UK 288 Edmund Halley Road 289 Oxford OX4 4DQ 290 United Kingdom 292 Phone: +44 1865 332211 293 Email: ray.bellis@nominet.org.uk 294 URI: http://www.nominet.org.uk/