One document matched: draft-ietf-geopriv-flow-identity-00.xml

<?xml version="1.0"?>
<?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 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">
]>

<?rfc rfcedstyle="no"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="no"?>
<?rfc iprnotified="yes"?>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocindent="yes"?>

<rfc category="std" ipr="trust200902" updates="RFC 6155">
  <front>
    <title abbrev="Flow Identity for HELD"> Flow Identity Extension for HELD </title>

    <author initials="R.P." 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/>
    <area>RAI</area>
    <workgroup>GEOPRIV</workgroup>
    <keyword>Internet-Draft</keyword>
    <keyword>HELD</keyword>
    <keyword>Flow</keyword>

    <abstract>
      <t> The GEOPRIV Working Group previously specified how to use an IP address and port number to
        request a 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 specifieds a Flow Identity Extension for the HTTP-Enabled Location Delivery
        (HELD) Protocol to support this requirement.</t>

    </abstract>
  </front>

  <middle>

    <section anchor="intro" title="Introduction">
      <t> 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 <xref
          target="RFC6155"/> to allow HELD <xref target="RFC5985"/> requests for target Devices that
        are behind a NAT device. </t>

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

      <t> This document creates an XML Schema and URN Sub-Namespace for a Flow Identity Extension to
        support this requirement.</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>
    </section>

    <section anchor="usage" title="Usage">
      <t> An example HELD request is show 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.168.1.1</address>
      <port>1024</port>
    </src>
    <dst>
      <address>10.0.0.1</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>
        </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 is the Target of the <![CDATA[<locationRequest>]]> with respect to the HELD
            protocol.</t>
        </list>
      </t>

      <t> 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 <xref target="RFC6155"/> are deprecated and
        SHOULD NOT be used.</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/rfcNEW1.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/rfcNEW1.txt">
         RFC NEW1</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> This document introduces no new privacy considerations beyond those in <xref
          target="RFC6155"/></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 EmLoc Working 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>

    <section anchor="notes" title="Notes to the RFC Editor (to be removed)">
      <t> References to "NEW1" need to be replaced with this document's final RFC number.</t>
    </section>

  </middle>

  <back>

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

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

</rfc>