IANA Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications
draft-polk-local-emergency-rph-namespace-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rai area)
Last updated 2012-08-16 (latest revision 2012-07-12)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES. Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Robert Sparks
Send notices to jmpolk@cisco.com, draft-polk-local-emergency-rph-namespace@tools.ietf.org, Brian.Rosen@neustar.biz
Network Working Group                                        James Polk
Internet-Draft                                            Cisco Systems
Expires: January 12, 2013                                 July 12, 2012
Intended Status: Standards Track 

          IANA Registering a SIP Resource Priority Header Field
              Namespace for Local Emergency Communications
               draft-polk-local-emergency-rph-namespace-02

Abstract

   This document creates the new Session Initiation Protocol (SIP) 
   Resource Priority header field namespace "esnet" for local emergency
   usage to a public safety answering point (PSAP), between PSAPs, and 
   between a PSAP and first responders and their organizations, and 
   places this namespace in the IANA registry.

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 January 12, 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
   (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.

Polk                      Expires Jan 12, 2013                 [Page 1]
Internet-Draft SIP Resource-Priority for Local Emergencies    July 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Rules of Usage of the Resource Priority Header  . . . . . . .  3
   3.  "esnet" Namespace Definition  . . . . . . . . . . . . . . . .  5
     3.1   Namespace Definition Rules and Guidelines . . . . . . . .  5
     3.2   The "esnet" Namespace . . . . . . . . . . . . . . . . . .  5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  6
     4.1   IANA Resource-Priority Namespace Registration . . . . . .  6
     4.2   IANA Priority-Value Registrations . . . . . . . . . . . .  6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  7
     7.1   Normative References  . . . . . . . . . . . . . . . . . .  7
     7.2   Informative References  . . . . . . . . . . . . . . . . .  7
       Author's Address  . . . . . . . . . . . . . . . . . . . . . .  8

   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].

1.  Introduction

   This document creates the new Session Initiation Protocol (SIP) 
   Resource Priority header field namespace "esnet" for local emergency
   usage and places this namespace in the IANA registry.  The SIP 
   Resource-Priority header field is defined in RFC 4412 [RFC4412]. 
   The new "esnet" namespace is to be used for inbound calls towards a 
   public safety answering point (PSAP), between PSAPs, and between a 
   PSAP and first responders or their organizations within managed IP 
   networks. This namespace is not envisioned for use on the open 
   public Internet because it can be trivially forged.  

   This new namespace can be included in SIP requests to provide an 
   explicit priority indication within controlled environments, such as
   an IMS infrastructure or Emergency Services network (ESInet) where 
   misuse can be reduced to a minimum because these types of networks 
   have great controls in place.  The function is to facilitate 
   differing treatment of emergency SIP requests according to local 
   policy, or more likely, a contractual agreement between the network 
   organizations.  This indication is used solely to differentiate 
Show full document text