GEOPRIV R. Bellis Internet-Draft Nominet UK Updates: RFC 6155 (if approved) May 14, 2012 Intended status: Informational Expires: November 15, 2012 Flow Identity Extension for HELD draft-bellis-geopriv-flow-identity-01 Abstract Identity Extensions using an IP address and port number to request a location based on an individual packet flow have been previously specified by the GEOPRIV Working Group. However certain kinds of NAT require that identifiers for both ends of the packet flow must be specified in order to unambiguously satisfy the location request. This document specifieds a Flow Identity Extension for the HTTP- Enabled Location Delivery (HELD) Protocol to support this requirement. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on November 15, 2012. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents Bellis Expires November 15, 2012 [Page 1] Internet-Draft Flow Identity for HELD May 2012 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . 4 3. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:held:flow . . . . . . . . . 8 5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 8 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . . 11 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Bellis Expires November 15, 2012 [Page 2] Internet-Draft Flow Identity for HELD May 2012 1. Introduction Work at the Emergency Location Working Group of NICC Standards Ltd (the UK's telecoms standards body) prompted the addition of Port Number identifiers in HELD Identity [RFC6155] to allow HELD [RFC5985] requests for target Devices that are behind a NAT device. Subsequent analysis has determined that in the presence of particular types of NAT device, and in particular Carrier Grade NATs, it is necessary to know the complete tuple of (layer 3 protocol, layer 4 protocol, source address, source port, destination address, destination port) in order to unambiguously identify a flow, and therefore the true target Device. This document creates an XML Schema and URN Sub-Namespace for a Flow Identity Extension to support this requirement. Bellis Expires November 15, 2012 [Page 3] Internet-Draft Flow Identity for HELD May 2012 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Bellis Expires November 15, 2012 [Page 4] Internet-Draft Flow Identity for HELD May 2012 3. Usage An example HELD request is show below: geodetic
192.168.1.1
1024
10.0.0.1
80
The element MUST contain: o a "layer3" attribute with a value of "ipv4" or "ipv6". o a "layer4" attribute with a value of "udp" [RFC0768], "tcp" [RFC0793], "sctp" [RFC4960], "dccp" [RFC4340], or a decimal integer representing any applicable protocol from the IANA Assigned Internet Protocol Numbers Registry. and MAY optionally contain: o a "target" attribute with a value of "src" (default) or "dst" to indicate which end of the flow is the "target" of the with respect to the HELD protocol. Bellis Expires November 15, 2012 [Page 5] Internet-Draft Flow Identity for HELD May 2012 4. XML Schema HELD Flow Identity This document defines Flow Identity elements for HELD. Bellis Expires November 15, 2012 [Page 6] Internet-Draft Flow Identity for HELD May 2012 Bellis Expires November 15, 2012 [Page 7] Internet-Draft Flow Identity for HELD May 2012 5. IANA Considerations 5.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:held:flow This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:held:flow", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:held:flow Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), Ray Bellis (ray.bellis@nominet.org.uk) XML: BEGIN HELD Flow Identity Parameters

Namespace for HELD Flow Identity Parameters

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

See RFC NEW1.

END 5.2. XML Schema Registration This section registers an XML schema as per the guidelines in [RFC3688] URI: urn:ietf:params:xml:ns:geopriv:held:flow Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), Ray Bellis (ray.bellis@nominet.org.uk) Schema: The XML for this schema can be found as the entirety of Section 4 of this document. Bellis Expires November 15, 2012 [Page 8] Internet-Draft Flow Identity for HELD May 2012 6. Privacy Considerations This document introduces no new privacy considerations beyond those in [RFC6155] Bellis Expires November 15, 2012 [Page 9] Internet-Draft Flow Identity for HELD May 2012 7. Security Considerations This document introduces no new security considerations beyond those in [RFC6155] Bellis Expires November 15, 2012 [Page 10] Internet-Draft Flow Identity for HELD May 2012 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 5985, September 2010. [RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. Barnes, "Use of Device Identity in HTTP-Enabled Location Delivery (HELD)", RFC 6155, March 2011. 8.2. Informative References [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980. [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981. [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram Congestion Control Protocol (DCCP)", RFC 4340, March 2006. [RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, September 2007. Bellis Expires November 15, 2012 [Page 11] Internet-Draft Flow Identity for HELD May 2012 Author's Address Ray Bellis Nominet UK Edmund Halley Road Oxford OX4 4DQ United Kingdom Phone: +44 1865 332211 Email: ray.bellis@nominet.org.uk URI: http://www.nominet.org.uk/ Bellis Expires November 15, 2012 [Page 12]