draft-ietf-geopriv-flow-identity-00.txt   draft-ietf-geopriv-flow-identity-01.txt 
GEOPRIV R. Bellis GEOPRIV R. Bellis
Internet-Draft Nominet UK Internet-Draft Nominet UK
Updates: RFC 6155 (if approved) September 13, 2012 Updates: RFC 6155 (if approved) February 13, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: March 17, 2013 Expires: August 17, 2013
Flow Identity Extension for HELD Flow Identity Extension for HELD
draft-ietf-geopriv-flow-identity-00 draft-ietf-geopriv-flow-identity-01
Abstract Abstract
The GEOPRIV Working Group previously specified how to use an IP RFC 6155 specifies an extension for the HTTP-Enabled Location
address and port number to request a location based on an individual Delivery (HELD) Protocol allowing the use of an IP address and port
packet flow. number to request a Device location based on an individual packet
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 specifieds a Flow Identity Extension for the HTTP- This document specifies an XML Schema and URN Sub-Namespace for a
Enabled Location Delivery (HELD) Protocol to support this Flow Identity Extension for HELD to support this requirement.
requirement.
This document updates RFC 6155 by deprecating the port number
elements specified therein.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 17, 2013. This Internet-Draft will expire on August 17, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
skipping to change at page 3, line 7 skipping to change at page 3, line 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
9. Notes to the RFC Editor (to be removed) . . . . . . . . . . . 12 9. Notes to the RFC Editor (to be removed) . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Work at the Emergency Location Working Group of NICC Standards Ltd Work at the Emergency Location Task Group of NICC Standards Ltd (the
(the UK's telecoms standards body) prompted the addition of Port UK's telecoms industry standards body) prompted the addition of Port
Number identifiers in HELD Identity [RFC6155] to allow HELD [RFC5985] Number identifiers in HELD Identity [RFC6155] to allow HELD [RFC5985]
requests for target Devices that are behind a NAT device. requests for target Devices that are behind a NAT device.
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 device, 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. therefore the true target Device.
This document creates an XML Schema and URN Sub-Namespace for a Flow This document specifies an XML Schema and URN Sub-Namespace for a
Identity Extension to support this requirement. Flow Identity Extension to support this requirement.
Since the Location Recipient may not know in advance whether the
Target is behind a NAT device the port number elements from Section
3.3 of [RFC6155] are deprecated and MUST NOT be used. This document
provides a more generally applicable means of identifying a Device
based on the parameters of a network flow of which it is an endpoint.
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].
3. Usage 3. Usage
An example HELD request is show 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>
<address>192.168.1.1</address> <address>192.168.1.1</address>
<port>1024</port> <port>1024</port>
</src> </src>
skipping to change at page 5, line 40 skipping to change at page 6, line 5
[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.
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 is the Target of the
<locationRequest> with respect to the HELD protocol. <locationRequest> with respect to the HELD protocol.
Since the Location Recipient may not know in advance whether the
Target is behind a NAT the port number elements from Section 3.3 of
[RFC6155] are deprecated and SHOULD NOT be used.
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
skipping to change at page 11, line 7 skipping to change at page 11, line 7
This document introduces no new privacy considerations beyond those This document introduces no new privacy considerations beyond those
in [RFC6155] in [RFC6155]
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 EmLoc Working The author wishes to thank the members of the NICC Emergency Location
Group, the IETF GeoPriv Working Group, and the authors of [RFC6155], Task Group, the IETF GeoPriv Working Group, and the authors of
from which the text for the URN and XML Schema Registrations were [RFC6155], from which the text for the URN and XML Schema
derived. Registrations were derived.
9. Notes to the RFC Editor (to be removed) 9. Notes to the RFC Editor (to be removed)
References to "NEW1" need to be replaced with this document's final References to "NEW1" need to be replaced with this document's final
RFC number. RFC number.
10. References 10. References
10.1. Normative References 10.1. Normative References
 End of changes. 13 change blocks. 
25 lines changed or deleted 30 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/