draft-ietf-stir-passport-shaken-06.txt   draft-ietf-stir-passport-shaken-07.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: June 9, 2019 iconectiv Expires: August 4, 2019 iconectiv
December 06, 2018 January 31, 2019
PASSporT SHAKEN Extension (SHAKEN) PASSporT SHAKEN Extension (SHAKEN)
draft-ietf-stir-passport-shaken-06 draft-ietf-stir-passport-shaken-07
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. The extension is defined, corresponding to the in communications. The extension is defined, corresponding to the
SHAKEN specification, to provide both a specific set of levels-of- SHAKEN specification, to provide both a specific set of levels-of-
confidence in the correctness of the originating identity for a SIP confidence in the correctness of the originating identity for a SIP
based Communication Service Provider (CSP) telephone network based Communication Service Provider (CSP) telephone network
originated call as well as an identifier that allows the CSP to originated call as well as an identifier that allows the CSP to
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 June 9, 2019. This Internet-Draft will expire on August 4, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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. Overview of 'shaken' PASSporT extension . . . . . . . . . . . 3 3. Overview of 'shaken' PASSporT extension . . . . . . . . . . . 3
4. PASSporT 'attest' Claim . . . . . . . . . . . . . . . . . . . 4 4. PASSporT 'attest' Claim . . . . . . . . . . . . . . . . . . . 4
5. PASSporT 'origid' Claim . . . . . . . . . . . . . . . . . . . 4 5. PASSporT 'origid' Claim . . . . . . . . . . . . . . . . . . . 4
6. Example "shaken" PASSporT . . . . . . . . . . . . . . . . . . 5 6. Example "shaken" PASSporT . . . . . . . . . . . . . . . . . . 4
7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 5 7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 4
8. Order of Claim Keys . . . . . . . . . . . . . . . . . . . . . 5 8. Order of Claim Keys . . . . . . . . . . . . . . . . . . . . . 4
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations . . . . . . . . . . . . . . . . . . . 5
10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
11.1. JSON Web Token claims . . . . . . . . . . . . . . . . . 7 11.1. JSON Web Token claims . . . . . . . . . . . . . . . . . 6
11.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 7 11.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
13.1. Normative References . . . . . . . . . . . . . . . . . . 7 13.1. Normative References . . . . . . . . . . . . . . . . . . 6
13.2. Informative References . . . . . . . . . . . . . . . . . 8 13.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The Signature-based Handling of Asserted information using toKENs The Signature-based Handling of Asserted information using toKENs
(SHAKEN) [ATIS-1000074] specification defines a framework for using (SHAKEN) [ATIS-1000074] specification defines a framework for using
Secure Telephone Identity Revisited (STIR) protocols including Secure Telephone Identity Revisited (STIR) protocols including
PASSporT [RFC8225], SIP Authenticated Identity Management [RFC8224] PASSporT [RFC8225], SIP Authenticated Identity Management [RFC8224]
and the STIR certificate framework [RFC8226] for implementing the and 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
skipping to change at page 4, line 10 skipping to change at page 4, line 10
The use of the compact form of PASSporT is not specified in this The use of the compact form of PASSporT is not specified in this
document and is not specified for use in SHAKEN [ATIS-1000074]. document and is not specified for use in SHAKEN [ATIS-1000074].
The next two sections define these new claims. The next two sections define these new claims.
4. PASSporT 'attest' Claim 4. PASSporT 'attest' Claim
This indicator allows for both identifying the service provider that This indicator allows for both identifying the service provider that
is vouching for the call as well as clearly indicating what is vouching for the call as well as clearly indicating what
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'. These
in [ATIS-1000074]. values correspond to 'Full Attestation', 'Partial Attestation', and
'Gateway Attestation', respectively. See [ATIS-1000074] for the
'A' represents 'Full Attestation' where the signing provider MUST definitions of these three levels of attestation.
satisfy all of the following conditions:
o Is responsible for the origination of the call onto the IP based
service provider voice network.
o Has a direct authenticated relationship with the initiator of the
call and can identify the customer associated with the initiator.
o Has established a verified association with the calling party
telephone number used for the call.
'B' represents 'Partial Attestation' where the signing provider MUST
satisfy all of the following conditions:
o Is responsible for the origination of the call onto its IP-based
voice network.
o Has a direct authenticated relationship with the initiator of the
call and can identify the customer associated with the initiator.
o Has NOT established a verified association with the calling party
telephone number being used for the call.
'C' represents 'Gateway Attestation' where the signing provider MUST
satisfy all of the following conditions:
o Is the entry point of the call into its VoIP network.
o Has no relationship with the initiator of the call (e.g.,
international gateways)
5. PASSporT 'origid' Claim 5. PASSporT 'origid' Claim
The purpose of the unique origination identifier is to assign an The purpose of the 'origid' claim is described in [ATIS-1000074].
opaque identifier corresponding to the service-provider-initiated
calls themselves, customers, classes of devices, or other groupings
that a service provider might want to use for determining things like
reputation or trace back identification of customers or gateways.
The value of 'origid' claim is a UUID as defined in [RFC4122]. The value of 'origid' claim is a UUID as defined in [RFC4122].
SHAKEN isn't prescriptive in the exact usage of origid other than the
UUID format as a globally unique identifier representing the
originator of the call to whatever granularity the PASSporT signer
determines is sufficient for the ability to trace the original
origination point of the call.
6. Example "shaken" PASSporT 6. Example "shaken" PASSporT
Protected Header Protected Header
{ {
"alg":"ES256", "alg":"ES256",
"typ":"passport", "typ":"passport",
"ppt":"shaken", "ppt":"shaken",
"x5u":"https://cert.example.org/passport.cer" "x5u":"https://cert.example.org/passport.cer"
} }
Payload Payload
{ {
"attest":"A" "attest":"A"
"dest":{"uri":["sip:alice@example.com"]} "dest":{"tn":["12155550131"]}
"iat":"1443208345", "iat":"1443208345",
"orig":{"tn":"12155550121"}, "orig":{"tn":"12155550121"},
"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 field defined [RFC3261] aligned with the use of the identity header field defined
 End of changes. 10 change blocks. 
63 lines changed or deleted 23 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/