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

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 2015-04-05
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ECRIT                                                    J. Winterbottom
Internet-Draft                               Winterb Consulting Services
Updates: RFC6881, RFC5985                                  H. Tschofenig
(if approved)
Intended status: Standards Track                                L. Liess
Expires: October 7, 2015                                Deutsche Telekom
                                                           April 5, 2015

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

Abstract

   In many circumstances public LoST servers or a distributed network of
   forest guides linking public LoST servers is not available.  The
   general ECRIT calling models breakdown without publically accessible
   LoST servers.  Sometimes location servers may have access to
   emergency routing information.  This document defines an extension to
   the HELD protocol so a location request can include a request for
   routing information and allowing the subsequent location response to
   include routing information.

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 October 7, 2015.

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

Winterbottom, et al.     Expires October 7, 2015                [Page 1]
Internet-Draft                HELD Routing                    April 2015

   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.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Mechanism  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   5.  HELD Schema Extension  . . . . . . . . . . . . . . . . . . . .  8
   6.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   7.  Privacy Considerations . . . . . . . . . . . . . . . . . . . . 10
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
     9.1.  URN sub-namespace registration for
           'urn:ietf:params:xml:ns:geopriv:held:ri' . . . . . . . . . 10
     9.2.  XML Schema Registration  . . . . . . . . . . . . . . . . . 11
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 12
     11.2. Informative References . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

Winterbottom, et al.     Expires October 7, 2015                [Page 2]
Internet-Draft                HELD Routing                    April 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 eventuated 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 adding 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