<?xml version="1.0" encoding="US-ASCII"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC768 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0768.xml">
<!ENTITY RFC793 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0793.xml">
<!ENTITY RFC2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3688 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY RFC3986 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
<!ENTITY RFC4340 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4340.xml">
<!ENTITY RFC4960 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4960.xml">
<!ENTITY RFC5985 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5985.xml">
<!ENTITY RFC6155 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6155.xml">
<!ENTITY RFC6280 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6280.xml">
]>

<?rfc rfcedstyle="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc toc="yes"?>
<?rfc tocindent="yes"?>

<rfc number="6915" category="std" submissionType="IETF" consensus="yes" ipr="trust200902" updates="6155">
  <front>
    <title abbrev="Flow Identity for HELD"> Flow Identity Extension for
HTTP-Enabled Location Delivery (HELD) </title>

    <author initials="R" surname="Bellis" fullname="Ray Bellis">
      <organization>Nominet UK</organization>
      <address>
        <postal>
          <street>Edmund Halley Road</street>
          <city>Oxford</city>
          <code>OX4 4DQ</code>
          <country>United Kingdom</country>
        </postal>
        <phone>+44 1865 332211</phone>
        <email>ray.bellis@nominet.org.uk</email>
        <uri>http://www.nominet.org.uk/</uri>
      </address>
    </author>


    <date month="April" year="2013"/>
    <area>RAI</area>
    <workgroup>GEOPRIV</workgroup>

    <keyword>HELD</keyword>
    <keyword>Flow</keyword>

<!-- [rfced] FYI, we have used xml2rfc v2 (available from 
http://xml.resource.org) to convert this document to text. 
-->

    <abstract>
      <t> RFC 6155 specifies an extension for the HTTP-Enabled Location Delivery (HELD) protocol,
        allowing the use of an IP address and port number to request a Device location based on an
        individual packet flow. </t>

      <t> 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. </t>

      <t> This document specifies an XML Schema and a URN Sub-Namespace for a Flow Identity Extension
        for HELD to support this requirement.</t>

      <t> This document updates RFC 6155 by deprecating the port number elements specified
        therein.</t>

    </abstract>
  </front>

  <middle>

    <section anchor="intro" title="Introduction">
      <t> Work at the Emergency Location Task Group of NICC Standards Limited (the UK's telecoms
        industry standards body) prompted the addition of port number identifiers in HELD Identity
          <xref target="RFC6155"/> to allow HELD <xref target="RFC5985"/> requests for Devices
        that are behind NAT devices. </t>

      <t> Subsequent analysis has determined that in the presence of particular types of NAT devices,
        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 subsequently the true Device.</t>

      <t> This document specifies an XML Schema and a URN Sub-Namespace for a Flow Identity Extension
        to support this requirement and provides a more generally applicable means of identifying a
        Device based on the parameters of a network flow of which it is an endpoint.</t>

      <t> Since the Location Recipient may not know in advance whether the Device is behind a NAT
        device, the port number elements from Section 3.3 of <xref target="RFC6155"/> are deprecated
        and MUST NOT be used in new client implementations. Note that server implementations of this
        specification may still encounter requests formed by clients that have implemented only
          <xref target="RFC6155"/>, and those requests might contain the deprecated port element.</t>

      <t> For implementation details not specified in this document, please refer to <xref
          target="RFC6155"/> and <xref target="RFC5985"/>.</t>

    </section>

    <section anchor="conventions" title="Conventions Used in This Document">
      <t>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
          <xref target="RFC2119"/>. </t>
      
      <t>The terms "Device" and "Target" are used as defined in <xref target="RFC6280"/>.</t>
    </section>

    <section anchor="usage" title="Usage">
      <t> An example HELD request is shown below:</t>
      <figure>
        <artwork><![CDATA[
<locationRequest xmlns="urn:ietf:params:xml:ns:geopriv:held"
                      responseTime="8">
  <locationType exact="true">geodetic</locationType>
  <flow xmlns="urn:ietf:params:xml:ns:geopriv:held:flow"
    layer4="tcp" layer3="ipv4">
    <src>
      <address>192.0.2.25</address>
      <port>1024</port>
    </src>
    <dst>
      <address>198.51.100.238</address>
      <port>80</port>
    </dst>
  </flow>
</locationRequest>
          ]]></artwork>
      </figure>

      <t> The <![CDATA[<flow>]]> element MUST contain:<list style="symbols">
          <t> a "layer3" attribute with a value of "ipv4" or "ipv6".</t>
          <t> a "layer4" attribute with a value of "udp" <xref target="RFC0768"/>, "tcp" <xref
              target="RFC0793"/>, "sctp" <xref target="RFC4960"/>, "dccp" <xref target="RFC4340"/>,
            or a decimal integer representing any applicable protocol from the IANA Assigned
            Internet Protocol Numbers Registry.</t>
          <t>an <![CDATA[<src>]]> element and a <![CDATA[<dst>]]> element whose child elements
            contain the Layer 3 address (which MUST conform to the relevant "IPv4address" or
            "IPv6address" grammar as defined in <xref target="RFC3986"/>) and the Layer 4 port
            number of each end of the flow.</t>
        </list> and MAY optionally contain:<list style="symbols">
          <t> a "target" attribute with a value of "src" (default) or "dst" to indicate which end of
            the flow corresponds to the Target of the <![CDATA[<locationRequest>]]> with respect to the HELD
            protocol.</t>
        </list>
      </t>

    </section>

    <section anchor="schema" title="XML Schema">
      <figure>
        <artwork><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:geopriv:held:flow"
  xmlns:xs="http://www.w3.org/2001/XMLSchema"
  xmlns:flow="urn:ietf:params:xml:ns:geopriv:held:flow"
  elementFormDefault="qualified">

  <xs:annotation>
    <xs:appinfo
      source="urn:ietf:params:xml:schema:geopriv:held:flow">
      HELD Flow Identity</xs:appinfo>
    <xs:documentation
      source="http://www.rfc-editor.org/rfc/rfc6915.txt">
      This document defines Flow Identity elements for HELD.
    </xs:documentation>
  </xs:annotation>

  <xs:element name="flow" type="flow:flowIdentity"/>

  <xs:complexType name="flowIdentity">
    <xs:sequence>
      <xs:element name="src" type="flow:flowEndpoint"/>
      <xs:element name="dst" type="flow:flowEndpoint"/>
    </xs:sequence>
    <xs:attribute name="target" default="src">
      <xs:simpleType>
        <xs:restriction base="xs:token">
          <xs:pattern value="(src|dst)"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="layer3" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:token">
          <xs:pattern value="(ipv4|ipv6)"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="layer4" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:token">
          <xs:pattern value="(udp|tcp|sctp|dccp|\d+)"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>

  <xs:complexType name="flowEndpoint">
    <xs:all>
      <xs:element name="address">
        <xs:simpleType>
          <xs:restriction base="xs:token"/>
        </xs:simpleType>
      </xs:element>
      <xs:element name="port">
        <xs:simpleType>
          <xs:restriction base="xs:unsignedShort">
            <xs:minInclusive value="1"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:all>
  </xs:complexType>
</xs:schema>

]]></artwork>
      </figure>
    </section>

    <section anchor="iana" title="IANA Considerations">
      <t> </t>

      <section title="URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:held:flow">
        <t> This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:held:flow",
          as per the guidelines in <xref target="RFC3688"/>. </t>

        <t> URI: urn:ietf:params:xml:ns:geopriv:held:flow</t>

        <t> Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), Ray Bellis
          (ray.bellis@nominet.org.uk)</t>

        <t> XML: </t>

        <figure>
          <artwork><![CDATA[
BEGIN
  <?xml version="1.0"?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
    <head>
      <title>HELD Flow Identity Parameters</title>
    </head>
    <body>
      <h1>Namespace for HELD Flow Identity Parameters</h1>
      <h2>urn:ietf:params:xml:ns:geopriv:held:flow</h2>
      <p>See <a href="http://www.rfc-editor.org/rfc/rfc6915.txt">
         RFC 6915</a>.</p>
    </body>
  </html>
END
]]></artwork>
        </figure>

      </section>

      <section title="XML Schema Registration">
        <t> This section registers an XML Schema as per the guidelines in <xref target="RFC3688"
          />.</t>

        <t> URI: urn:ietf:params:xml:ns:geopriv:held:flow</t>

        <t> Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), Ray Bellis
          (ray.bellis@nominet.org.uk)</t>

        <t> Schema: The XML for this schema can be found as the entirety of <xref target="schema"/>
          of this document. </t>
      </section>

    </section>

    <section anchor="privacy" title="Privacy Considerations">

      <t> All of the considerations in <xref target="RFC6155"/> apply to the use of the mechanism
        defined in this document. Like <xref target="RFC6155"/>, this specification assumes that the
        Location Server being queried already has access to the internal state of the network near
        one end of the flow being queried (for instance, access to the bindings in a NAT in the path
        of the flow). Clients making queries using this specification in environments where that
        assumption may not be true should be aware that the request provides information about that
        client's communications that the Location Server would not otherwise be able to discern and
        may represent additional privacy exposure for that client.</t>

    </section>

    <section anchor="security" title="Security Considerations">
      <t> This document introduces no new security considerations beyond those in <xref
          target="RFC6155"/>.</t>
    </section>

    <section anchor="ack" title="Acknowledgements">
      <t> The author wishes to thank the members of the NICC Emergency Location Task Group, the IETF
        GeoPriv Working Group, and the authors of <xref target="RFC6155"/>, from which the text for
        the URN and XML Schema Registrations were derived.</t>
    </section>
  </middle>

  <back>

    <references title="Normative References"> &RFC2119; &RFC3688; &RFC3986; &RFC5985;
      &RFC6155;</references>

    <references title="Informative References"> &RFC768; &RFC793; &RFC4340; &RFC4960; &RFC6280;</references>
  </back>

</rfc>
