draft-ietf-geopriv-flow-identity-02.txt   rfc6915.txt 
GEOPRIV R. Bellis Internet Engineering Task Force (IETF) R. Bellis
Internet-Draft Nominet UK Request for Comments: 6915 Nominet UK
Updates: RFC 6155 (if approved) March 1, 2013 Updates: 6155 April 2013
Intended status: Standards Track Category: Standards Track
Expires: September 2, 2013 ISSN: 2070-1721
Flow Identity Extension for HELD Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)
draft-ietf-geopriv-flow-identity-02
Abstract Abstract
RFC 6155 specifies an extension for the HTTP-Enabled Location RFC 6155 specifies an extension for the HTTP-Enabled Location
Delivery (HELD) Protocol allowing the use of an IP address and port Delivery (HELD) protocol, allowing the use of an IP address and port
number to request a Device location based on an individual packet number to request a Device location based on an individual packet
flow. flow.
However, certain kinds of NAT require that identifiers for both ends However, certain kinds of NAT require that identifiers for both ends
of the packet flow must be specified in order to unambiguously of the packet flow must be specified in order to unambiguously
satisfy the location request. satisfy the location request.
This document specifies an XML Schema and URN Sub-Namespace for a This document specifies an XML Schema and a URN Sub-Namespace for a
Flow Identity Extension for HELD to support this requirement. Flow Identity Extension for HELD to support this requirement.
This document updates RFC 6155 by deprecating the port number This document updates RFC 6155 by deprecating the port number
elements specified therein. elements specified therein.
Status of this Memo 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 This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on September 2, 2013. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6915.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions used in this document . . . . . . . . . . . . . . 4 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
5.1. URN Sub-Namespace Registration for 5.1. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:held:flow . . . . . . . . . 8 urn:ietf:params:xml:ns:geopriv:held:flow . . . . . . . . . 6
5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 8 5.2. XML Schema Registration . . . . . . . . . . . . . . . . . 7
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 9 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
9. Notes to the RFC Editor (to be removed) . . . . . . . . . . . 12 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Work at the Emergency Location Task Group of NICC Standards Ltd (the Work at the Emergency Location Task Group of NICC Standards Limited
UK's telecoms industry standards body) prompted the addition of Port (the UK's telecoms industry standards body) prompted the addition of
Number identifiers in HELD Identity [RFC6155] to allow HELD [RFC5985] port number identifiers in HELD Identity [RFC6155] to allow HELD
requests for target Devices that are behind a NAT device. [RFC5985] requests for Devices that are behind NAT devices.
Subsequent analysis has determined that in the presence of particular Subsequent analysis has determined that in the presence of particular
types of NAT device, and in particular Carrier Grade NATs, it is types of NAT devices, and in particular Carrier Grade NATs, it is
necessary to know the complete tuple of (layer 3 protocol, layer 4 necessary to know the complete tuple of (Layer 3 protocol, Layer 4
protocol, source address, source port, destination address, protocol, source address, source port, destination address,
destination port) in order to unambiguously identify a flow, and destination port) in order to unambiguously identify a flow, and
therefore the true target Device. subsequently the true Device.
This document specifies an XML Schema and URN Sub-Namespace for a This document specifies an XML Schema and a URN Sub-Namespace for a
Flow Identity Extension to support this requirement and provides a Flow Identity Extension to support this requirement and provides a
more generally applicable means of identifying a Device based on the more generally applicable means of identifying a Device based on the
parameters of a network flow of which it is an endpoint. parameters of a network flow of which it is an endpoint.
Since the Location Recipient may not know in advance whether the Since the Location Recipient may not know in advance whether the
Target is behind a NAT device the port number elements from Section Device is behind a NAT device, the port number elements from Section
3.3 of [RFC6155] are deprecated and MUST NOT be used in new client 3.3 of [RFC6155] are deprecated and MUST NOT be used in new client
implementations. Note that server implementations of this implementations. Note that server implementations of this
specification may still encounter requests formed by clients that specification may still encounter requests formed by clients that
have implemented only [RFC6155] and those requests might contain the have implemented only [RFC6155], and those requests might contain the
deprecated port element. deprecated port element.
For implementation details not specified in this document please For implementation details not specified in this document, please
refer to [RFC6155] and [RFC5985]. refer to [RFC6155] and [RFC5985].
2. Conventions used in this document 2. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The terms "Device" and "Target" are used as defined in [RFC6280].
3. Usage 3. Usage
An example HELD request is shown below: An example HELD request is shown below:
<locationRequest xmlns="urn:ietf:params:xml:ns:geopriv:held" <locationRequest xmlns="urn:ietf:params:xml:ns:geopriv:held"
responseTime="8"> responseTime="8">
<locationType exact="true">geodetic</locationType> <locationType exact="true">geodetic</locationType>
<flow xmlns="urn:ietf:params:xml:ns:geopriv:held:flow" <flow xmlns="urn:ietf:params:xml:ns:geopriv:held:flow"
layer4="tcp" layer3="ipv4"> layer4="tcp" layer3="ipv4">
<src> <src>
skipping to change at page 5, line 34 skipping to change at page 4, line 34
The <flow> element MUST contain: The <flow> element MUST contain:
o a "layer3" attribute with a value of "ipv4" or "ipv6". o a "layer3" attribute with a value of "ipv4" or "ipv6".
o a "layer4" attribute with a value of "udp" [RFC0768], "tcp" o a "layer4" attribute with a value of "udp" [RFC0768], "tcp"
[RFC0793], "sctp" [RFC4960], "dccp" [RFC4340], or a decimal [RFC0793], "sctp" [RFC4960], "dccp" [RFC4340], or a decimal
integer representing any applicable protocol from the IANA integer representing any applicable protocol from the IANA
Assigned Internet Protocol Numbers Registry. Assigned Internet Protocol Numbers Registry.
o a <src> element and a <dst> element whose child elements contain o an <src> element and a <dst> element whose child elements contain
the layer 3 address (which MUST conform to the relevant the Layer 3 address (which MUST conform to the relevant
"IPv4address" or "IPv6address" grammar as defined in [RFC3986]) "IPv4address" or "IPv6address" grammar as defined in [RFC3986])
and the layer 4 port number of each end of the flow. and the Layer 4 port number of each end of the flow.
and MAY optionally contain: and MAY optionally contain:
o a "target" attribute with a value of "src" (default) or "dst" to o a "target" attribute with a value of "src" (default) or "dst" to
indicate which end of the flow is the Target of the indicate which end of the flow corresponds to the Target of the
<locationRequest> with respect to the HELD protocol. <locationRequest> with respect to the HELD protocol.
4. XML Schema 4. XML Schema
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:geopriv:held:flow" <xs:schema targetNamespace="urn:ietf:params:xml:ns:geopriv:held:flow"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:flow="urn:ietf:params:xml:ns:geopriv:held:flow" xmlns:flow="urn:ietf:params:xml:ns:geopriv:held:flow"
elementFormDefault="qualified"> elementFormDefault="qualified">
<xs:annotation> <xs:annotation>
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:held:flow"> source="urn:ietf:params:xml:schema:geopriv:held:flow">
HELD Flow Identity</xs:appinfo> HELD Flow Identity</xs:appinfo>
<xs:documentation <xs:documentation
source="http://www.rfc-editor.org/rfc/rfcNEW1.txt"> source="http://www.rfc-editor.org/rfc/rfc6915.txt">
This document defines Flow Identity elements for HELD. This document defines Flow Identity elements for HELD.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:element name="flow" type="flow:flowIdentity"/> <xs:element name="flow" type="flow:flowIdentity"/>
<xs:complexType name="flowIdentity"> <xs:complexType name="flowIdentity">
<xs:sequence> <xs:sequence>
<xs:element name="src" type="flow:flowEndpoint"/> <xs:element name="src" type="flow:flowEndpoint"/>
<xs:element name="dst" type="flow:flowEndpoint"/> <xs:element name="dst" type="flow:flowEndpoint"/>
skipping to change at page 8, line 32 skipping to change at page 7, line 17
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>HELD Flow Identity Parameters</title> <title>HELD Flow Identity Parameters</title>
</head> </head>
<body> <body>
<h1>Namespace for HELD Flow Identity Parameters</h1> <h1>Namespace for HELD Flow Identity Parameters</h1>
<h2>urn:ietf:params:xml:ns:geopriv:held:flow</h2> <h2>urn:ietf:params:xml:ns:geopriv:held:flow</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfcNEW1.txt"> <p>See <a href="http://www.rfc-editor.org/rfc/rfc6915.txt">
RFC NEW1</a>.</p> RFC 6915</a>.</p>
</body> </body>
</html> </html>
END END
5.2. XML Schema Registration 5.2. XML Schema Registration
This section registers an XML schema as per the guidelines in This section registers an XML Schema as per the guidelines in
[RFC3688] [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:held:flow URI: urn:ietf:params:xml:ns:geopriv:held:flow
Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org),
Ray Bellis (ray.bellis@nominet.org.uk) Ray Bellis (ray.bellis@nominet.org.uk)
Schema: The XML for this schema can be found as the entirety of Schema: The XML for this schema can be found as the entirety of
Section 4 of this document. Section 4 of this document.
6. Privacy Considerations 6. Privacy Considerations
skipping to change at page 10, line 8 skipping to change at page 8, line 8
the path of the flow). Clients making queries using this the path of the flow). Clients making queries using this
specification in environments where that assumption may not be true specification in environments where that assumption may not be true
should be aware that the request provides information about that should be aware that the request provides information about that
client's communications that the Location Server would not otherwise client's communications that the Location Server would not otherwise
be able to discern and may represent additional privacy exposure for be able to discern and may represent additional privacy exposure for
that client. that client.
7. Security Considerations 7. Security Considerations
This document introduces no new security considerations beyond those This document introduces no new security considerations beyond those
in [RFC6155] in [RFC6155].
8. Acknowledgements 8. Acknowledgements
The author wishes to thank the members of the NICC Emergency Location The author wishes to thank the members of the NICC Emergency Location
Task Group, the IETF GeoPriv Working Group, and the authors of Task Group, the IETF GeoPriv Working Group, and the authors of
[RFC6155], from which the text for the URN and XML Schema [RFC6155], from which the text for the URN and XML Schema
Registrations were derived. Registrations were derived.
9. Notes to the RFC Editor (to be removed) 9. References
References to "NEW1" need to be replaced with this document's final
RFC number.
10. References
10.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66, RFC
RFC 3986, January 2005. 3986, January 2005.
[RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC
RFC 5985, September 2010. 5985, September 2010.
[RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. [RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R.
Barnes, "Use of Device Identity in HTTP-Enabled Location Barnes, "Use of Device Identity in HTTP-Enabled Location
Delivery (HELD)", RFC 6155, March 2011. Delivery (HELD)", RFC 6155, March 2011.
10.2. Informative References 9.2. Informative References
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC
RFC 793, September 1981. 793, September 1981.
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram
Congestion Control Protocol (DCCP)", RFC 4340, March 2006. Congestion Control Protocol (DCCP)", RFC 4340, March 2006.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC
RFC 4960, September 2007. 4960, September 2007.
[RFC6280] Barnes, R., Lepinski, M., Cooper, A., Morris, J.,
Tschofenig, H., and H. Schulzrinne, "An Architecture for
Location and Location Privacy in Internet Applications",
BCP 160, RFC 6280, July 2011.
Author's Address Author's Address
Ray Bellis Ray Bellis
Nominet UK Nominet UK
Edmund Halley Road Edmund Halley Road
Oxford OX4 4DQ Oxford OX4 4DQ
United Kingdom United Kingdom
Phone: +44 1865 332211 Phone: +44 1865 332211
Email: ray.bellis@nominet.org.uk EMail: ray.bellis@nominet.org.uk
URI: http://www.nominet.org.uk/ URI: http://www.nominet.org.uk/
 End of changes. 34 change blocks. 
75 lines changed or deleted 71 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/