Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000236806D
Original Publication Date: 2014-May-01
Included in the Prior Art Database: 2014-May-16
Document File: 18 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Polk: AUTHOR

Abstract

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 13% of the total text.

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