A Routing Request Extension for the HELD Protocol
draft-ietf-ecrit-held-routing-04

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Authors James Winterbottom  , Hannes Tschofenig  , Laura Liess 
Last updated 2016-02-04 (latest revision 2015-12-09)
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Roger Marshall
Shepherd write-up Show (last changed 2015-10-29)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to "Roger Marshall" <rmarshall@telecomsys.com>
IANA IANA review state IANA - Not OK
ECRIT                                                    J. Winterbottom
Internet-Draft                               Winterb Consulting Services
Updates: RFC6881, RFC5985 (if approved)                    H. Tschofenig
Intended status: Standards Track
Expires: June 11, 2016                                          L. Liess
                                                        Deutsche Telekom
                                                        December 9, 2015

           A Routing Request Extension for the HELD Protocol
                  draft-ietf-ecrit-held-routing-04.txt

Abstract

   For cases where location servers have access to emergency routing
   information they are able to return routing information with the
   location information if the location request includes a request for
   the desired routing information.  This document specifies an
   extension to the HELD protocol, updating [RFC5985], to support this
   funciton.

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 June 11, 2016.

Copyright Notice

   Copyright (c) 2015 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
   (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

Winterbottom, et al.      Expires June 11, 2016                 [Page 1]
Internet-Draft                HELD Routing                 December 2015

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  LoST Reuse Considerations . . . . . . . . . . . . . . . .   6
   4.  Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Modification to Phone BCP . . . . . . . . . . . . . . . . . .   7
   6.  HELD Schema Extension . . . . . . . . . . . . . . . . . . . .   8
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     10.1.  URN sub-namespace registration for
            'urn:ietf:params:xml:ns:geopriv:held:ri' . . . . . . . .  13
     10.2.  XML Schema Registration  . . . . . . . . . . . . . . . .  13
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  14
     12.2.  Informative References . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

Winterbottom, et al.      Expires June 11, 2016                 [Page 2]
Internet-Draft                HELD Routing                 December 2015

1.  Introduction

   The general ECRIT calling models described in [RFC6443] and
   [RFC6881]require a local LoST server or network of forest guides in
   order to determine the address of the PSAP in the best position to
   handle a call.  Networks of forest guides have not materialized and
   while PSAPs are moving towards IP networks, LoST server deployment is
   not ubiquitous.  Some regions and countries have expressed reluctance
   to deploy LoST servers making aspects of the current ECRIT
   architecture hard to realize.

   Evolving architectures in Europe to address regulatory requirements,
   such as [M493], couple location and routing information in the access
   network whilst using a softswitch-centric approach to emergency call
   processing.  This document describes an extension to the HELD
   protocol [RFC5985] so that a location information server can provide
   emergency routing information in the absence of a LoST server or
Show full document text