draft-ietf-stir-passport-shaken-02.txt   draft-ietf-stir-passport-shaken-03.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 20, 2018 iconectiv Expires: March 24, 2019 iconectiv
March 19, 2018 September 20, 2018
PASSporT SHAKEN Extension (SHAKEN) PASSporT SHAKEN Extension (SHAKEN)
draft-ietf-stir-passport-shaken-02 draft-ietf-stir-passport-shaken-03
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 20, 2018. This Internet-Draft will expire on March 24, 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 17 skipping to change at page 2, line 17
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 . . . . . . . . . . . . . . . . . . . . . . . . . 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 "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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
9.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5 9.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5
9.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6 9.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 6 11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 7 11.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
skipping to change at page 3, line 29 skipping to change at page 3, line 29
a telephone call but can not fully attest to the calling identity, a telephone call but can not fully attest to the calling identity,
and a gateway attestation which is the lowest level of attestation and a gateway attestation which is the lowest level of attestation
and represents the service provider receiving a call from a non and represents the service provider receiving a call from a non
PASSporT or STI supporting telephone gateway. PASSporT or STI supporting telephone 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 use of the compact form of PASSporT is not specified in this
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' as defined
in [ATIS-1000074]. in [ATIS-1000074].
skipping to change at page 4, line 37 skipping to change at page 4, line 40
that a service provider might want to use for determining things like that a service provider might want to use for determining things like
reputation or trace back identification of customers or gateways. 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 SHAKEN isn't prescriptive in the exact usage of origid other than the
UUID format as a globally unique identifier representing the UUID format as a globally unique identifier representing the
originator of the call to whatever granularity the PASSporT signer originator of the call to whatever granularity the PASSporT signer
determines is sufficient for the ability to trace the original determines is sufficient for the ability to trace the original
origination point of the call. There will likely be best practices origination point of the call. There will likely be best practices
documents that more precisely guide it's usage in real deployments. documents that more precisely guide it's usage in real deployments.
6. Example 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"
skipping to change at page 5, line 30 skipping to change at page 5, line 30
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]. [RFC8224].
8. Order of Claim Keys 8. Order of Claim Keys
The order of the claim keys MUST follow the rules of [RFC8225] The order of the claim keys MUST follow the rules of [RFC8225]
Section 9 and be in lexixgraphic order. Therefore, the claim keys Section 9; the claim keys MUST appear in lexicographic order.
MUST appear in the PASSporT Payload in the following order, Therefore, the claim keys discussed in this document appear in the
PASSporT Payload in the following order,
o attest o attest
o dest o dest
o iat o iat
o orig o orig
o origid o origid
 End of changes. 7 change blocks. 
8 lines changed or deleted 12 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/