draft-ietf-stir-passport-shaken-03.txt   draft-ietf-stir-passport-shaken-04.txt 
stir C. Wendt STIR C. Wendt
Internet-Draft Comcast Internet-Draft Comcast
Intended status: Standards Track M. Barnes Intended status: Standards Track M. Barnes
Expires: March 24, 2019 iconectiv Expires: April 20, 2019 iconectiv
September 20, 2018 October 17, 2018
PASSporT SHAKEN Extension (SHAKEN) PASSporT SHAKEN Extension (SHAKEN)
draft-ietf-stir-passport-shaken-03 draft-ietf-stir-passport-shaken-04
Abstract Abstract
This document extends PASSporT, which is a token object that conveys This document extends PASSporT, which is a token object that conveys
cryptographically-signed information about the participants involved cryptographically-signed information about the participants involved
in communications, to include information defined as part of the in communications, to include information defined as part of the
SHAKEN specification from ATIS (Alliance for Telecommunications SHAKEN specification from ATIS (Alliance for Telecommunications
Industry Solutions) and the SIP Forum IP-NNI Joint Task Force. These Industry Solutions) and the SIP Forum IP-NNI Joint Task Force. These
extensions provide a level of confidence in the correctness of the extensions provide a level of confidence in the correctness of the
originating identity for a telephone network that has communications originating identity for a telephone network that has communications
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 March 24, 2019. This Internet-Draft will expire on April 20, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Overview of 'shaken' PASSporT extension . . . . . . . . . . . 3 3. Overview of 'shaken' PASSporT extension . . . . . . . . . . . 3
4. PASSporT 'attest' Claim . . . . . . . . . . . . . . . . . . . 3 4. PASSporT 'attest' Claim . . . . . . . . . . . . . . . . . . . 3
5. PASSporT 'origid' Claim . . . . . . . . . . . . . . . . . . . 4 5. PASSporT 'origid' Claim . . . . . . . . . . . . . . . . . . . 4
6. Example "shaken" PASSporT . . . . . . . . . . . . . . . . . . 4 6. Example "shaken" PASSporT . . . . . . . . . . . . . . . . . . 4
7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 5 7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 5
8. Order of Claim Keys . . . . . . . . . . . . . . . . . . . . . 5 8. Order of Claim Keys . . . . . . . . . . . . . . . . . . . . . 5
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 9. Security Considerations . . . . . . . . . . . . . . . . . . . 5
9.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6 10.1. JSON Web Token claims . . . . . . . . . . . . . . . . . 6
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 10.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 6 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . 7 12.1. Normative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 12.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The SHAKEN [ATIS-1000074] specification defines a framework for using The SHAKEN [ATIS-1000074] specification defines a framework for using
STIR protocols including PASSporT [RFC8225], RFC4474bis [RFC8224] and STIR protocols including PASSporT [RFC8225], SIP Authenticated
the STIR certificate framework [RFC8226] for implementing the Identity Management [RFC8224] and the STIR certificate framework
cryptographic validation of an authorized originator of telephone [RFC8226] for implementing the cryptographic validation of an
calls using SIP. Because the current telephone network contains both authorized originator of telephone calls using SIP. Because the
VoIP and TDM/SS7 originated traffic, there are many scenarios that current telephone network contains both VoIP and TDM/SS7 originated
need to be accounted for where PASSporT signatures may represent traffic, there are many scenarios that need to be accounted for where
either direct or indirect call origination scenarios. The SHAKEN PASSporT signatures may represent either direct or indirect call
[ATIS-1000074] specification defines levels of attestation of the origination scenarios. The SHAKEN [ATIS-1000074] specification
origination of the call as well as an origination identifier that can defines levels of attestation of the origination of the call as well
help create a unique association with the origination of calls from as an origination identifier that can help create a unique
various parts of the VoIP or TDM telephone network. This document association with the origination of calls from various parts of the
specifies these indicators as a specified PASSporT extension. VoIP or TDM telephone network. This document specifies these
indicators as a specified PASSporT extension.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Overview of 'shaken' PASSporT extension 3. Overview of 'shaken' PASSporT extension
The SHAKEN framework is designed to use PASSporT [RFC8225] as a The SHAKEN framework is designed to use PASSporT [RFC8225] as a
skipping to change at page 5, line 44 skipping to change at page 5, line 44
o attest o attest
o dest o dest
o iat o iat
o orig o orig
o origid o origid
9. IANA Considerations 9. Security Considerations
9.1. JSON Web Token claims This document defines a new PASSporT [RFC8225] extension. The
considerations related to the security of the PASSporT object itself
are the same as those described in [RFC8225].
[RFC8224] defines how to compare the values of the "dest", "orig" and
"iat" claims against fields in a SIP containing a PASSporT as part of
validating that request. The values of the new "attest" and "origid"
claims added by this extension are not used in such a validation
step. They are not compared to fields in the SIP message. Instead,
they simply carry additional information from the signer to the
consumer of the PASSport. This new information shares the same
integrity protection and non-repudiation properties as the base
claims in the PASSporT.
10. IANA Considerations
10.1. JSON Web Token claims
This specification requests that the IANA add two new claims to the This specification requests that the IANA add two new claims to the
JSON Web Token Claims registry as defined in [RFC7519]. JSON Web Token Claims registry as defined in [RFC7519].
Claim Name: "attest" Claim Name: "attest"
Claim Description: Attestation level as defined in SHAKEN framework Claim Description: Attestation level as defined in SHAKEN framework
Change Controller: IESG Change Controller: IESG
Specification Document(s): [RFCThis] Specification Document(s): [RFCThis]
Claim Name: "origid" Claim Name: "origid"
Claim Description: Originating Identifier as defined in SHAKEN Claim Description: Originating Identifier as defined in SHAKEN
framework framework
skipping to change at page 6, line 19 skipping to change at page 6, line 36
Claim Name: "origid" Claim Name: "origid"
Claim Description: Originating Identifier as defined in SHAKEN Claim Description: Originating Identifier as defined in SHAKEN
framework framework
Change Controller: IESG Change Controller: IESG
Specification Document(s): [RFCThis] Specification Document(s): [RFCThis]
9.2. PASSporT Types 10.2. PASSporT Types
This specification requests that the IANA add a new entry to the This specification requests that the IANA add a new entry to the
PASSporT Types registry for the type "shaken" which is specified in Personal Assertion Token (PASSporT) Extensions registry for the type
[RFCThis]. "shaken" which is specified in [RFCThis].
10. Acknowledgements 11. Acknowledgements
The authors would like to thank those that helped review and The authors would like to thank those that helped review and
contribute to this document including specific contributions from Jon contribute to this document including specific contributions from Jon
Peterson, Russ Housley, and Andrew Jurczak. The authors would like Peterson, Russ Housley, and Andrew Jurczak. The authors would like
acknowledge the work of the ATIS/SIP Forum IP-NNI Task Force to acknowledge the work of the ATIS/SIP Forum IP-NNI Task Force to
develop the concepts behind this document. develop the concepts behind this document.
11. References 12. References
11.1. Normative References 12.1. Normative References
[ATIS-1000074] [ATIS-1000074]
ATIS/SIP Forum NNI Task Group, "Signature-based Handling ATIS/SIP Forum NNI Task Group, "Signature-based Handling
of Asserted information using toKENs (SHAKEN)", January of Asserted information using toKENs (SHAKEN)", January
2017. 2017, <https://access.atis.org/apps/group_public/
download.php/32237/ATIS-1000074.pdf>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005, DOI 10.17487/RFC4122, July 2005,
<https://www.rfc-editor.org/info/rfc4122>. <https://www.rfc-editor.org/info/rfc4122>.
[RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token [RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token
(JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015, (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015,
<https://www.rfc-editor.org/info/rfc7519>. <https://www.rfc-editor.org/info/rfc7519>.
skipping to change at page 7, line 20 skipping to change at page 7, line 39
[RFC8225] Wendt, C. and J. Peterson, "PASSporT: Personal Assertion [RFC8225] Wendt, C. and J. Peterson, "PASSporT: Personal Assertion
Token", RFC 8225, DOI 10.17487/RFC8225, February 2018, Token", RFC 8225, DOI 10.17487/RFC8225, February 2018,
<https://www.rfc-editor.org/info/rfc8225>. <https://www.rfc-editor.org/info/rfc8225>.
[RFC8226] Peterson, J. and S. Turner, "Secure Telephone Identity [RFC8226] Peterson, J. and S. Turner, "Secure Telephone Identity
Credentials: Certificates", RFC 8226, Credentials: Certificates", RFC 8226,
DOI 10.17487/RFC8226, February 2018, DOI 10.17487/RFC8226, February 2018,
<https://www.rfc-editor.org/info/rfc8226>. <https://www.rfc-editor.org/info/rfc8226>.
11.2. Informative References 12.2. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
 End of changes. 16 change blocks. 
35 lines changed or deleted 55 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/