draft-ietf-stir-passport-shaken-00.txt   draft-ietf-stir-passport-shaken-01.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: July 21, 2018 MLB@Realtime Communications Expires: September 6, 2018 MLB@Realtime Communications
January 17, 2018 March 05, 2018
PASSporT SHAKEN Extension (SHAKEN) PASSporT SHAKEN Extension (SHAKEN)
draft-ietf-stir-passport-shaken-00 draft-ietf-stir-passport-shaken-01
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 July 21, 2018. This Internet-Draft will expire on September 6, 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 22 skipping to change at page 2, line 22
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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5 8.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5
8.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6 8.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 6 10.2. Informative References . . . . . . . . . . . . . . . . . 7
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 [I-D.ietf-stir-passport], STIR protocols including PASSporT [RFC8225], RFC4474bis [RFC8224] and
RFC4474bis [I-D.ietf-stir-rfc4474bis] and the STIR certificate the STIR certificate framework [RFC8226] for implementing the
framework [I-D.ietf-stir-certificates] 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
need to be accounted for where PASSporT signatures may represent need to be accounted for where PASSporT signatures may represent
either direct or indirect call origination scenarios. The SHAKEN either direct or indirect call origination scenarios. The SHAKEN
[ATIS-1000074] specification defines levels of attestation of the [ATIS-1000074] specification defines levels of attestation of the
origination of the call as well as an origination identifier that can origination of the call as well as an origination identifier that can
help create a unique association with the origination of calls from help create a unique association with the origination of calls from
various parts of the VoIP or TDM telephone network. This document various parts of the VoIP or TDM telephone network. This document
specifies these indicators as a specified PASSporT extension. 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 The SHAKEN framework is designed to use PASSporT [RFC8225] as a
[I-D.ietf-stir-passport] as a method of asserting the telephone method of asserting the telephone number calling identity. In
number calling identity. In addition to the PASSporT base claims, addition to the PASSporT base claims, there are two additional claims
there are two additional claims that have been defined for the needs that have been defined for the needs of a service provider to signal
of a service provider to signal information beyond just the telephone information beyond just the telephone identity. First, in order to
identity. First, in order to help bridge the transition of the state help bridge the transition of the state of the current telephone
of the current telephone network which has calls with no network which has calls with no authentication and non-SIP [RFC3261]
authentication and non-SIP [RFC3261] signaling not compatible with signaling not compatible with the use of PASSporT and Secure
the use of PASSporT and Secure Telephone Identity (STI) in general, Telephone Identity (STI) in general, there is an attestation claim.
there is an attestation claim. This provides three levels of This provides three levels of attestation, including a full
attestation, including a full attestation when the service provider attestation when the service provider can fully attest to the calling
can fully attest to the calling identity, a partial attestation, when identity, a partial attestation, when the service provider originated
the service provider originated a telephone call but can not fully a telephone call but can not fully attest to the calling identity,
attest to the calling identity, and a gateway attestation which is and a gateway attestation which is the lowest level of attestation
the lowest level of attestation and represents the service provider and represents the service provider receiving a call from a non
receiving a call from a non PASSporT or STI supporting telephone PASSporT or STI supporting telephone gateway.
gateway.
The second claim is a unique origination identifier that should be The second claim is a unique origination identifier that should be
used by the service provider to identify different sources of used by the service provider to identify different sources of
telephone calls to support a traceback mechanism that can be used for telephone calls to support a traceback mechanism that can be used for
enforcement and identification of a source of illegitimate calls. enforcement and identification of a source of illegitimate calls.
The next two sections define these new claims. The next two sections define these new claims.
4. PASSporT 'attest' Claim 4. PASSporT 'attest' 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
[I-D.ietf-stir-rfc4474bis]. The carriage of the 'attest' and [RFC8224]. The carriage of the 'attest' and 'origid' values are in
'origid' values are in the full PASSporT token included in the the full PASSporT token included in the identity header as specified
identity header as specified in [ATIS-1000074]. in [ATIS-1000074].
8. IANA Considerations 8. IANA Considerations
8.1. JSON Web Token claims 8.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"
skipping to change at page 6, line 11 skipping to change at page 6, line 11
Change Controller: IESG Change Controller: IESG
Specification Document(s): [RFCThis] Specification Document(s): [RFCThis]
8.2. PASSporT Types 8.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. Security Considerations 9. Acknowledgements
TBD
10. Acknowledgements
TBD The authors would like to thank those that helped review and
contribute to this document including specific contributions from Jon
Peterson, Russ Housley, and Andrew Jurczak. The authors would like
acknowledge the work of the ATIS/SIP Forum IP-NNI Task Force to
develop the concepts behind this document.
11. References 10. References
11.1. Normative References 10.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.
[I-D.ietf-stir-certificates]
Peterson, J. and S. Turner, "Secure Telephone Identity
Credentials: Certificates", draft-ietf-stir-
certificates-18 (work in progress), December 2017.
[I-D.ietf-stir-passport]
Wendt, C. and J. Peterson, "Personal Assertion Token
(PASSporT)", draft-ietf-stir-passport-11 (work in
progress), February 2017.
[I-D.ietf-stir-rfc4474bis]
Peterson, J., Jennings, C., Rescorla, E., and C. Wendt,
"Authenticated Identity Management in the Session
Initiation Protocol (SIP)", draft-ietf-stir-rfc4474bis-16
(work in progress), February 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>.
[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>.
11.2. Informative References [RFC8224] Peterson, J., Jennings, C., Rescorla, E., and C. Wendt,
"Authenticated Identity Management in the Session
Initiation Protocol (SIP)", RFC 8224,
DOI 10.17487/RFC8224, February 2018,
<https://www.rfc-editor.org/info/rfc8224>.
[RFC8225] Wendt, C. and J. Peterson, "PASSporT: Personal Assertion
Token", RFC 8225, DOI 10.17487/RFC8225, February 2018,
<https://www.rfc-editor.org/info/rfc8225>.
[RFC8226] Peterson, J. and S. Turner, "Secure Telephone Identity
Credentials: Certificates", RFC 8226,
DOI 10.17487/RFC8226, February 2018,
<https://www.rfc-editor.org/info/rfc8226>.
10.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. 13 change blocks. 
57 lines changed or deleted 53 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/