datatracker.ietf.org
Sign in
Version 5.12.0, 2015-02-26
Report a bug

Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications
RFC 7135

Document type: RFC - Informational (May 2014; No errata)
Was draft-polk-local-emergency-rph-namespace (individual in rai area)
Document stream: IETF
Last updated: 2014-05-15
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 7135 (Informational)
Responsible AD: Robert Sparks
Send notices to: jmpolk@cisco.com, draft-polk-local-emergency-rph-namespace@ietf.org, Brian.Rosen@neustar.biz

Internet Engineering Task Force (IETF)                           J. Polk
Request for Comments: 7135                                 Cisco Systems
Category: Informational                                         May 2014
ISSN: 2070-1721

     Registering a SIP Resource Priority Header Field Namespace for
                     Local Emergency Communications

Abstract

   This document creates the new Session Initiation Protocol (SIP)
   Resource Priority header field namespace 'esnet' and registers this
   namespace with IANA.  The new header field namespace allows for local
   emergency session establishment to a public safety answering point
   (PSAP), between PSAPs, and between a PSAP and first responders and
   their organizations.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7135.

Copyright Notice

   Copyright (c) 2014 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                          Informational                     [Page 1]
RFC 7135                 Emergency RPH Namespace                May 2014

Table of Contents

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

1.  Introduction

   This document creates the new Session Initiation Protocol (SIP)
   Resource Priority header (RPH) field namespace 'esnet' for local
   emergency usage and registers this namespace with IANA.  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 for use on the open public Internet
   because it can be trivially forged.

   Adding an RPH with the 'esnet' namespace can be differentiated from
   the marking of an emergency call using a service URN as defined in
   [RFC5031] in that the RPH specifically requests preferential
   treatment in networks that honor it, while the marking merely
   identifies an emergency call without necessarily affecting resources
   allocated to it.  It is appropriate to use both where applicable.
   RPH with 'esnet' may also be used within public safety networks for
   SIP sessions that are not emergency calls and thus not marked per RFC
   5031.

   This new namespace is included in SIP requests to provide an explicit
   priority indication within controlled environments, such as an IP
   Multimedia Subsystem (IMS) infrastructure or Emergency Services
   network (ESInet) where misuse can be reduced to an acceptable level
   because these types of networks have controls in place.  The function
   facilitates differing treatment of emergency SIP requests according
   to local policy, or more likely, a contractual agreement between the

[include full document text]