Flow Identity Extension for HELD
draft-ietf-geopriv-flow-identity-00

The information below is for an old version of the document
Document Type Active Internet-Draft (geopriv WG)
Last updated 2013-02-12 (latest revision 2012-09-13)
Replaces draft-bellis-geopriv-flow-identity
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Robert Sparks
IESG note Alissa Cooper (acooper@cdt.org) is the Document Shepherd.
Send notices to geopriv-chairs@tools.ietf.org, draft-ietf-geopriv-flow-identity@tools.ietf.org
GEOPRIV                                                        R. Bellis
Internet-Draft                                                Nominet UK
Updates: RFC 6155 (if approved)                       September 13, 2012
Intended status: Standards Track
Expires: March 17, 2013

                    Flow Identity Extension for HELD
                  draft-ietf-geopriv-flow-identity-00

Abstract

   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.

   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 March 17, 2013.

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 March 17, 2013                 [Page 1]
Internet-Draft           Flow Identity for HELD           September 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.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   9.  Notes to the RFC Editor (to be removed)  . . . . . . . . . . . 12
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 13
     10.2. Informative References . . . . . . . . . . . . . . . . . . 13
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14

Bellis                   Expires March 17, 2013                 [Page 2]
Internet-Draft           Flow Identity for HELD           September 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 March 17, 2013                 [Page 3]
Internet-Draft           Flow Identity for HELD           September 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].

Show full document text