draft-ietf-stir-passport-shaken-01.txt   draft-ietf-stir-passport-shaken-02.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: September 6, 2018 MLB@Realtime Communications Expires: September 20, 2018 iconectiv
March 05, 2018 March 19, 2018
PASSporT SHAKEN Extension (SHAKEN) PASSporT SHAKEN Extension (SHAKEN)
draft-ietf-stir-passport-shaken-01 draft-ietf-stir-passport-shaken-02
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 September 6, 2018. This Internet-Draft will expire on September 20, 2018.
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 19 skipping to change at page 2, line 19
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 5 7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 8. Order of Claim Keys . . . . . . . . . . . . . . . . . . . . . 5
8.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6 9.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 9.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 6 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
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], RFC4474bis [RFC8224] and
the STIR certificate framework [RFC8226] for implementing the the STIR certificate framework [RFC8226] for implementing the
cryptographic validation of an authorized originator of telephone cryptographic validation of an authorized originator of telephone
calls using SIP. Because the current telephone network contains both calls using SIP. Because the current telephone network contains both
VoIP and TDM/SS7 originated traffic, there are many scenarios that VoIP and TDM/SS7 originated traffic, there are many scenarios that
skipping to change at page 3, line 45 skipping to change at page 3, line 45
information the service provider is attesting to. The 'attest' claim information the service provider is attesting to. The 'attest' claim
can be one of the following three values, 'A', 'B', or 'C' as defined can be one of the following three values, 'A', 'B', or 'C' as defined
in [ATIS-1000074]. in [ATIS-1000074].
'A' represents 'Full Attestation' where the signing provider MUST 'A' represents 'Full Attestation' where the signing provider MUST
satisfy all of the following conditions: satisfy all of the following conditions:
o Is responsible for the origination of the call onto the IP based o Is responsible for the origination of the call onto the IP based
service provider voice network. service provider voice network.
o Has a direct authenticated relationship with the customer and can o Has a direct authenticated relationship with the initiator of the
identify the customer. call and can identify the customer associated with the initiator.
o Has established a verified association with the telephone number o Has established a verified association with the calling party
used for the call. telephone number used for the call.
'B' represents 'Partial Attestation' where the signing provider MUST 'B' represents 'Partial Attestation' where the signing provider MUST
satisfy all of the following conditions: satisfy all of the following conditions:
o Is responsible for the origination of the call onto its IP-based o Is responsible for the origination of the call onto its IP-based
voice network. voice network.
o Has a direct authenticated relationship with the customer and can o Has a direct authenticated relationship with the initiator of the
identify the customer. call and can identify the customer associated with the initiator.
o Has NOT established a verified association with the telephone o Has NOT established a verified association with the calling party
number being used for the call. telephone number being used for the call.
'C' represents 'Gateway Attestation' where the signing provider MUST 'C' represents 'Gateway Attestation' where the signing provider MUST
satisfy all of the following conditions: satisfy all of the following conditions:
o Is the entry point of the call into its VoIP network. o Is the entry point of the call into its VoIP network.
o Has no relationship with the initiator of the call (e.g., o Has no relationship with the initiator of the call (e.g.,
international gateways) international gateways)
5. PASSporT 'origid' Claim 5. PASSporT 'origid' Claim
skipping to change at page 5, line 25 skipping to change at page 5, line 25
"iat":"1443208345", "iat":"1443208345",
"orig":{"tn":"12155551212"}, "orig":{"tn":"12155551212"},
"origid":"123e4567-e89b-12d3-a456-426655440000" "origid":"123e4567-e89b-12d3-a456-426655440000"
} }
7. Using 'shaken' in SIP 7. Using 'shaken' in SIP
The use of the 'shaken' PASSporT type and the claims 'attest' and The use of the 'shaken' PASSporT type and the claims 'attest' and
'origid' are formally defined in [ATIS-1000074] for usage in SIP 'origid' are formally defined in [ATIS-1000074] for usage in SIP
[RFC3261] aligned with the use of the identity header defined in [RFC3261] aligned with the use of the identity header defined in
[RFC8224]. The carriage of the 'attest' and 'origid' values are in [RFC8224].
the full PASSporT token included in the identity header as specified
in [ATIS-1000074].
8. IANA Considerations 8. Order of Claim Keys
8.1. JSON Web Token claims The order of the claim keys MUST follow the rules of [RFC8225]
Section 9 and be in lexixgraphic order. Therefore, the claim keys
MUST appear in the PASSporT Payload in the following order,
o attest
o dest
o iat
o orig
o origid
9. IANA Considerations
9.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 5 skipping to change at page 6, line 19
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]
8.2. PASSporT Types 9.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 PASSporT Types registry for the type "shaken" which is specified in
[RFCThis]. [RFCThis].
9. Acknowledgements 10. 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.
10. References 11. References
10.1. Normative References 11.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.
[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>.
skipping to change at page 7, line 5 skipping to change at page 7, line 20
[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>.
10.2. Informative References 11.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,
skipping to change at page 7, line 29 skipping to change at page 7, line 44
Chris Wendt Chris Wendt
Comcast Comcast
One Comcast Center One Comcast Center
Philadelphia, PA 19103 Philadelphia, PA 19103
USA USA
Email: chris-ietf@chriswendt.net Email: chris-ietf@chriswendt.net
Mary Barnes Mary Barnes
MLB@Realtime Communications iconectiv
Email: mary.ietf.barnes@gmail.com Email: mary.ietf.barnes@gmail.com
 End of changes. 18 change blocks. 
31 lines changed or deleted 45 lines changed or added

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