draft-ietf-stir-rph-emergency-services-00.txt   draft-ietf-stir-rph-emergency-services-01.txt 
STIR M. Dolly STIR M. Dolly
Internet-Draft AT&T Internet-Draft AT&T
Intended status: Standards Track C. Wendt Intended status: Standards Track C. Wendt
Expires: July 13, 2020 Comcast Expires: September 10, 2020 Comcast
January 10, 2020 March 09, 2020
Assertion Values for a Resource Priority Header Claim in Support of Assertion Values for a Resource Priority Header Claim in Support of
Emergency Services Networks Emergency Services Networks
draft-ietf-stir-rph-emergency-services-00 draft-ietf-stir-rph-emergency-services-01
Abstract Abstract
This document adds new assertion values for a Resource Priority This document adds new assertion values for a Resource Priority
Header ("rph") claim defined in RFC 8443, in support of Emergency Header ("rph") claim defined in RFC 8443, in support of Emergency
Services Networks for emergency call origination and callback. Services Networks for emergency call origination and callback.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 13, 2020. This Internet-Draft will expire on September 10, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 10 skipping to change at page 2, line 10
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. New Assertion Values . . . . . . . . . . . . . . . . . . . . 3 3. New Assertion Values . . . . . . . . . . . . . . . . . . . . 3
3.1. ESorig . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. EScallback . . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4.1. PASSporT Resource Priority Header (rph) Types . . . . . . 4 4.1. PASSporT Resource Priority Header (rph) Types . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
Personal Assertion Token (PASSporT) Extension for Resource Priority Personal Assertion Token (PASSporT) Extension for Resource Priority
Authorization [RFC8443] extended the Personal Assertion Token Authorization [RFC8443] extended the Personal Assertion Token
(PASSporT) specification defined in [RFC8225] to allow the inclusion (PASSporT) specification defined in [RFC8225] to allow the inclusion
of cryptographically signed assertions of authorization for the of cryptographically signed assertions of authorization for the
values populated in the Session Initiation Protocol (SIP) 'Resource- values populated in the Session Initiation Protocol (SIP) 'Resource-
Priority' header field, which is used for communications resource Priority' header field, which is used for communications resource
skipping to change at page 3, line 22 skipping to change at page 3, line 23
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. New Assertion Values 3. New Assertion Values
This specification defines new assertions values for: This specification defines new assertions values for:
* "ESorig": Emergency Services call origination * "ESorig": Emergency Services call origination
* "EScallback": Emergency Services callback. * "EScallback": Emergency Services callback.
3.1. ESorig
When using "ESorig" as the "rph" assertion value, the "orig" claim of
the PASSporT MUST represent the calling party number that initiates
the call to emergency services. The "dest" claim MUST either be a
country or region specific dial string (e.g., "911" for North America
or "112" GSM defined string used in Europe and other countries) or
"urn:service:sos" as defined in TBD, representing the emergency
services destination of the call.
The following is an example of an "rph" claim for SIP 'Resource- The following is an example of an "rph" claim for SIP 'Resource-
Priority' header field with a "ESorig" assertion: Priority' header field with a "ESorig" assertion:
{ {
"orig":{"tn":"CgPN"}, "orig":{"tn":"12155551212"},
"dest":{["tn":"911 or URN-SOS"]}, "dest":{["tn":"urn:service:sos"]},
"iat":1443208345, "iat":1443208345,
"rph":{"ESorig":["esnet,x"]} "rph":{"ESorig":["esnet,x"]}
} }
3.2. EScallback
When using "EScallback" as the "rph" assertion value, the "orig"
claim of the PASSporT MUST represent the emergency network telephone
number. The "dest" claim MUST be the telephone number representing
the original calling party of the emergency service call that is
being called back.
The following is an example of an "rph" claim for SIP 'Resource- The following is an example of an "rph" claim for SIP 'Resource-
Priority' header field with a "ESorig" assertion: Priority' header field with a "EScallback" assertion:
{ {
"orig":{"tn":"EmergNet Num"}, "orig":{"tn":"12155551213"},
"dest":{["tn":"CgPN that originated emergency call"]}, "dest":{["tn":"12155551212"]},
"iat":1443208345, "iat":1443208345,
"rph":{"EScallback":["esnet,x"]} "rph":{"EScallback":["esnet,x"]}
} }
After the header and claims PASSporT objects have been constructed, After the header and claims PASSporT objects have been constructed,
their signature is generated normally per the guidance in [RFC8225] their signature is generated normally per the guidance in [RFC8225]
using the full form of PASSPorT. The credentials (i.e., Certificate) using the full form of PASSPorT. The credentials (i.e., Certificate)
used to create the signature must have authority over the namespace used to create the signature must have authority over the namespace
of the "rph" claim, and there is only one authority per claim. The of the "rph" claim, and there is only one authority per claim. The
authority MUST use its credentials associated with the specific authority MUST use its credentials associated with the specific
skipping to change at page 6, line 10 skipping to change at page 6, line 35
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Authors' Addresses Authors' Addresses
Martin Dolly Martin Dolly
AT&T AT&T
Email: mmd3135@att.com Email: md3135@att.com
Chris Wendt Chris Wendt
Comcast Comcast
Comcast Technology Center Comcast Technology Center
Philadelphia, PA 19103 Philadelphia, PA 19103
USA USA
Email: chris-ietf@chriswendt.net Email: chris-ietf@chriswendt.net
 End of changes. 11 change blocks. 
14 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/