idnits 2.17.1 draft-ietf-stir-passport-shaken-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 05, 2018) is 2237 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCThis' is mentioned on line 230, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'ATIS-1000074' Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 stir C. Wendt 3 Internet-Draft Comcast 4 Intended status: Standards Track M. Barnes 5 Expires: September 6, 2018 MLB@Realtime Communications 6 March 05, 2018 8 PASSporT SHAKEN Extension (SHAKEN) 9 draft-ietf-stir-passport-shaken-01 11 Abstract 13 This document extends PASSporT, which is a token object that conveys 14 cryptographically-signed information about the participants involved 15 in communications, to include information defined as part of the 16 SHAKEN specification from ATIS (Alliance for Telecommunications 17 Industry Solutions) and the SIP Forum IP-NNI Joint Task Force. These 18 extensions provide a level of confidence in the correctness of the 19 originating identity for a telephone network that has communications 20 coming from both STIR participating originating communications as 21 well as communications that does not include STIR information. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on September 6, 2018. 40 Copyright Notice 42 Copyright (c) 2018 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 59 3. Overview of 'shaken' PASSporT extension . . . . . . . . . . . 3 60 4. PASSporT 'attest' Claim . . . . . . . . . . . . . . . . . . . 3 61 5. PASSporT 'origid' Claim . . . . . . . . . . . . . . . . . . . 4 62 6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 5 64 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 65 8.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5 66 8.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6 67 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 68 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 10.1. Normative References . . . . . . . . . . . . . . . . . . 6 70 10.2. Informative References . . . . . . . . . . . . . . . . . 7 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 73 1. Introduction 75 The SHAKEN [ATIS-1000074] specification defines a framework for using 76 STIR protocols including PASSporT [RFC8225], RFC4474bis [RFC8224] and 77 the STIR certificate framework [RFC8226] for implementing the 78 cryptographic validation of an authorized originator of telephone 79 calls using SIP. Because the current telephone network contains both 80 VoIP and TDM/SS7 originated traffic, there are many scenarios that 81 need to be accounted for where PASSporT signatures may represent 82 either direct or indirect call origination scenarios. The SHAKEN 83 [ATIS-1000074] specification defines levels of attestation of the 84 origination of the call as well as an origination identifier that can 85 help create a unique association with the origination of calls from 86 various parts of the VoIP or TDM telephone network. This document 87 specifies these indicators as a specified PASSporT extension. 89 2. Terminology 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in [RFC2119]. 95 3. Overview of 'shaken' PASSporT extension 97 The SHAKEN framework is designed to use PASSporT [RFC8225] as a 98 method of asserting the telephone number calling identity. In 99 addition to the PASSporT base claims, there are two additional claims 100 that have been defined for the needs of a service provider to signal 101 information beyond just the telephone identity. First, in order to 102 help bridge the transition of the state of the current telephone 103 network which has calls with no authentication and non-SIP [RFC3261] 104 signaling not compatible with the use of PASSporT and Secure 105 Telephone Identity (STI) in general, there is an attestation claim. 106 This provides three levels of attestation, including a full 107 attestation when the service provider can fully attest to the calling 108 identity, a partial attestation, when the service provider originated 109 a telephone call but can not fully attest to the calling identity, 110 and a gateway attestation which is the lowest level of attestation 111 and represents the service provider receiving a call from a non 112 PASSporT or STI supporting telephone gateway. 114 The second claim is a unique origination identifier that should be 115 used by the service provider to identify different sources of 116 telephone calls to support a traceback mechanism that can be used for 117 enforcement and identification of a source of illegitimate calls. 119 The next two sections define these new claims. 121 4. PASSporT 'attest' Claim 123 This indicator allows for both identifying the service provider that 124 is vouching for the call as well as clearly indicating what 125 information the service provider is attesting to. The 'attest' claim 126 can be one of the following three values, 'A', 'B', or 'C' as defined 127 in [ATIS-1000074]. 129 'A' represents 'Full Attestation' where the signing provider MUST 130 satisfy all of the following conditions: 132 o Is responsible for the origination of the call onto the IP based 133 service provider voice network. 135 o Has a direct authenticated relationship with the customer and can 136 identify the customer. 138 o Has established a verified association with the telephone number 139 used for the call. 141 'B' represents 'Partial Attestation' where the signing provider MUST 142 satisfy all of the following conditions: 144 o Is responsible for the origination of the call onto its IP-based 145 voice network. 147 o Has a direct authenticated relationship with the customer and can 148 identify the customer. 150 o Has NOT established a verified association with the telephone 151 number being used for the call. 153 'C' represents 'Gateway Attestation' where the signing provider MUST 154 satisfy all of the following conditions: 156 o Is the entry point of the call into its VoIP network. 158 o Has no relationship with the initiator of the call (e.g., 159 international gateways) 161 5. PASSporT 'origid' Claim 163 The purpose of the unique origination identifier is to assign an 164 opaque identifier corresponding to the service provider-initiated 165 calls themselves, customers, classes of devices, or other groupings 166 that a service provider might want to use for determining things like 167 reputation or trace back identification of customers or gateways. 168 The value of 'origid' claim is a UUID as defined in [RFC4122]. 169 SHAKEN isn't prescriptive in the exact usage of origid other than the 170 UUID format as a globally unique identifier representing the 171 originator of the call to whatever granularity the PASSporT signer 172 determines is sufficient for the ability to trace the original 173 origination point of the call. There will likely be best practices 174 documents that more precisely guide it's usage in real deployments. 176 6. Example 177 Protected Header 178 { 179 "alg":"ES256", 180 "typ":"passport", 181 "ppt":"shaken", 182 "x5u":"https://cert.example.org/passport.cer" 183 } 184 Payload 185 { 186 "attest":"A" 187 "dest":{"uri":["sip:alice@example.com"]} 188 "iat":"1443208345", 189 "orig":{"tn":"12155551212"}, 190 "origid":"123e4567-e89b-12d3-a456-426655440000" 191 } 193 7. Using 'shaken' in SIP 195 The use of the 'shaken' PASSporT type and the claims 'attest' and 196 'origid' are formally defined in [ATIS-1000074] for usage in SIP 197 [RFC3261] aligned with the use of the identity header defined in 198 [RFC8224]. The carriage of the 'attest' and 'origid' values are in 199 the full PASSporT token included in the identity header as specified 200 in [ATIS-1000074]. 202 8. IANA Considerations 204 8.1. JSON Web Token claims 206 This specification requests that the IANA add two new claims to the 207 JSON Web Token Claims registry as defined in [RFC7519]. 209 Claim Name: "attest" 211 Claim Description: Attestation level as defined in SHAKEN framework 213 Change Controller: IESG 215 Specification Document(s): [RFCThis] 217 Claim Name: "origid" 219 Claim Description: Originating Identifier as defined in SHAKEN 220 framework 222 Change Controller: IESG 224 Specification Document(s): [RFCThis] 226 8.2. PASSporT Types 228 This specification requests that the IANA add a new entry to the 229 PASSporT Types registry for the type "shaken" which is specified in 230 [RFCThis]. 232 9. Acknowledgements 234 The authors would like to thank those that helped review and 235 contribute to this document including specific contributions from Jon 236 Peterson, Russ Housley, and Andrew Jurczak. The authors would like 237 acknowledge the work of the ATIS/SIP Forum IP-NNI Task Force to 238 develop the concepts behind this document. 240 10. References 242 10.1. Normative References 244 [ATIS-1000074] 245 ATIS/SIP Forum NNI Task Group, "Signature-based Handling 246 of Asserted information using toKENs (SHAKEN)", January 247 2017. 249 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 250 Unique IDentifier (UUID) URN Namespace", RFC 4122, 251 DOI 10.17487/RFC4122, July 2005, 252 . 254 [RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token 255 (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015, 256 . 258 [RFC8224] Peterson, J., Jennings, C., Rescorla, E., and C. Wendt, 259 "Authenticated Identity Management in the Session 260 Initiation Protocol (SIP)", RFC 8224, 261 DOI 10.17487/RFC8224, February 2018, 262 . 264 [RFC8225] Wendt, C. and J. Peterson, "PASSporT: Personal Assertion 265 Token", RFC 8225, DOI 10.17487/RFC8225, February 2018, 266 . 268 [RFC8226] Peterson, J. and S. Turner, "Secure Telephone Identity 269 Credentials: Certificates", RFC 8226, 270 DOI 10.17487/RFC8226, February 2018, 271 . 273 10.2. Informative References 275 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 276 Requirement Levels", BCP 14, RFC 2119, 277 DOI 10.17487/RFC2119, March 1997, 278 . 280 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 281 A., Peterson, J., Sparks, R., Handley, M., and E. 282 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 283 DOI 10.17487/RFC3261, June 2002, 284 . 286 Authors' Addresses 288 Chris Wendt 289 Comcast 290 One Comcast Center 291 Philadelphia, PA 19103 292 USA 294 Email: chris-ietf@chriswendt.net 296 Mary Barnes 297 MLB@Realtime Communications 299 Email: mary.ietf.barnes@gmail.com