idnits 2.17.1 draft-wendt-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 abstract seems to contain references ([ATIS-1000074]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 30, 2017) is 2370 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 229, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'ATIS-1000074' == Outdated reference: A later version (-18) exists of draft-ietf-stir-certificates-14 Summary: 1 error (**), 0 flaws (~~), 3 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: May 3, 2018 MLB@Realtime Communications 6 October 30, 2017 8 PASSporT SHAKEN Extension (SHAKEN) 9 draft-wendt-stir-passport-shaken-01 11 Abstract 13 This document extends PASSporT, a token object that conveys 14 cryptographically-signed information about the participants involved 15 in personal communications, to include information defined as part of 16 the SHAKEN [ATIS-1000074] specification for indicating an attestation 17 level and originating ID. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on May 3, 2018. 36 Copyright Notice 38 Copyright (c) 2017 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 55 3. Overview of 'shaken' PASSporT extension . . . . . . . . . . . 3 56 4. PASSporT 'attest' Claim . . . . . . . . . . . . . . . . . . . 3 57 5. PASSporT 'origid' Claim . . . . . . . . . . . . . . . . . . . 4 58 6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 7. Using 'shaken' in SIP . . . . . . . . . . . . . . . . . . . . 5 60 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 61 8.1. JSON Web Token claims . . . . . . . . . . . . . . . . . . 5 62 8.2. PASSporT Types . . . . . . . . . . . . . . . . . . . . . 6 63 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 64 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 65 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 11.1. Normative References . . . . . . . . . . . . . . . . . . 6 67 11.2. Informative References . . . . . . . . . . . . . . . . . 7 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 70 1. Introduction 72 The SHAKEN specification defines a framework for using STIR protocols 73 including PASSporT [I-D.ietf-stir-passport], RFC4474bis 74 [I-D.ietf-stir-rfc4474bis] and the STIR certificate framework 75 [I-D.ietf-stir-certificates] for implementing the cryptographic 76 validation of an authorized originator of telephone calls using SIP. 77 Because the current telephone network contains both VoIP and TDM/SS7 78 originated traffic, there is many scenarios that need to be accounted 79 for where PASSporT signatures may represent either direct or indirect 80 call origination scenarios. The SHAKEN [ATIS-1000074] specification 81 defines levels of attribution of the origination of the call as well 82 as an origination identifier that can help create a unique 83 association with the origination of calls from various parts of the 84 VoIP or TDM telephone network. This document specifies these 85 indicators as a specified PASSporT extension. 87 2. Terminology 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in [RFC2119]. 93 3. Overview of 'shaken' PASSporT extension 95 The SHAKEN framework is designed to use PASSporT 96 [I-D.ietf-stir-passport] as a method of asserting the telephone 97 number calling identity. In addition to the PASSporT base claims, 98 there are two additional claims that have been defined for the needs 99 of a service provider to signal information beyond just the telephone 100 identity. First, in order to help bridge the transition of the state 101 of the current telephone network which has calls with no 102 authentication and non-SIP [RFC3261] signaling not compatible with 103 the use of PASSporT and Secure Telephone Identity (STI) in general, 104 there is an attestation claim. This provides three levels of 105 attestation, including a full attestation when the service provider 106 can fully attest to the calling identity, a partial attestation, when 107 the service provider originated a telephone call but can not fully 108 attest to the calling identity, and a gateway attestation which is 109 the lowest level of attestation and represents the service provider 110 receiving a call from a non PASSporT or STI supporting telephone 111 gateway. 113 The second claim is a unique origination identifier that should be 114 used by the service provider to identify different sources of 115 telephone calls to support a traceback mechanism that can be used for 116 enforcement and identification of a source of illegitimate calls. 118 The next two sections define these new claims. 120 4. PASSporT 'attest' Claim 122 This indicator allows for both identifying the service provider that 123 is vouching for the call as well as a clearly indicating what 124 information the service provider is attesting to. The 'attest' claim 125 can be one of the following three values, 'A', 'B', or 'C' as defined 126 in [ATIS-1000074]. 128 'A' represents 'Full Attestation' where the signing provider MUST 129 satisfy all of the following conditions: 131 o Is responsible for the origination of the call onto the IP based 132 service provider voice network. 134 o Has a direct authenticated relationship with the customer and can 135 identify the customer. 137 o Has established a verified association with the telephone number 138 used for the call. 140 'B' represents 'Partial Attestation' where the signing provider MUST 141 satisfy all of the following conditions: 143 o Is responsible for the origination of the call onto its IP-based 144 voice network. 146 o Has a direct authenticated relationship with the customer and can 147 identify the customer. 149 o Has NOT established a verified association with the telephone 150 number being used for the call. 152 'C' represents 'Gateway Attestation' where the signing provider MUST 153 satisfy all of the following conditions: 155 o Is the entry point of the call into its VoIP network. 157 o Has no relationship with the initiator of the call (e.g., 158 international gateways) 160 5. PASSporT 'origid' Claim 162 The purpose of the unique origination identifier is to assign an 163 opaque identifier corresponding to the service provider-initiated 164 calls themselves, customers, classes of devices, or other groupings 165 that a service provider might want to use for determining things like 166 reputation or trace back identification of customers or gateways. 167 The value of 'origid' claim is a UUID as defined in [RFC4122]. 168 SHAKEN isn't prescriptive in the exact usage of origid other than the 169 UUID format as a globally unique identifier representing the 170 originator of the call to whatever granularity the PASSporT signer 171 determines is sufficient for the ability to trace the original 172 origination point of the call. There will likely be best practices 173 documents that more precisely guide it's usage in real deployments. 175 6. Example 176 Protected Header 177 { 178 "alg":"ES256", 179 "typ":"passport", 180 "ppt":"shaken", 181 "x5u":"https://cert.example.org/passport.crt" 182 } 183 Payload 184 { 185 "attest":"A" 186 "dest":{"uri":["sip:alice@example.com"]} 187 "iat":"1443208345", 188 "orig":{"tn":"12155551212"}, 189 "origid":"123e4567-e89b-12d3-a456-426655440000" 190 } 192 7. Using 'shaken' in SIP 194 The use of the 'shaken' PASSporT type and the claims 'attest' and 195 'origid' are formally defined in [ATIS-1000074] for usage in SIP 196 [RFC3261] aligned with the use of the identity header defined in 197 [I-D.ietf-stir-rfc4474bis]. The carriage of the 'attest' and 198 'origid' values are in the full PASSporT token included in the 199 identity header as specified in [ATIS-1000074]. 201 8. IANA Considerations 203 8.1. JSON Web Token claims 205 This specification requests that the IANA add two new claims to the 206 JSON Web Token Claims registry as defined in [RFC7519]. 208 Claim Name: "attest" 210 Claim Description: Attestation level as defined in SHAKEN framework 212 Change Controller: IESG 214 Specification Document(s): [RFCThis] 216 Claim Name: "origid" 218 Claim Description: Originating Identifier as defined in SHAKEN 219 framework 221 Change Controller: IESG 223 Specification Document(s): [RFCThis] 225 8.2. PASSporT Types 227 This specification requests that the IANA add a new entry to the 228 PASSporT Types registry for the type "shaken" which is specified in 229 [RFCThis]. 231 9. Security Considerations 233 TBD 235 10. Acknowledgements 237 TBD 239 11. References 241 11.1. Normative References 243 [ATIS-1000074] 244 ATIS/SIP Forum NNI Task Group, "Signature-based Handling 245 of Asserted information using toKENs (SHAKEN)", January 246 2017. 248 [I-D.ietf-stir-certificates] 249 Peterson, J. and S. Turner, "Secure Telephone Identity 250 Credentials: Certificates", draft-ietf-stir- 251 certificates-14 (work in progress), May 2017. 253 [I-D.ietf-stir-passport] 254 Wendt, C. and J. Peterson, "Personal Assertion Token 255 (PASSporT)", draft-ietf-stir-passport-11 (work in 256 progress), February 2017. 258 [I-D.ietf-stir-rfc4474bis] 259 Peterson, J., Jennings, C., Rescorla, E., and C. Wendt, 260 "Authenticated Identity Management in the Session 261 Initiation Protocol (SIP)", draft-ietf-stir-rfc4474bis-16 262 (work in progress), February 2017. 264 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 265 Unique IDentifier (UUID) URN Namespace", RFC 4122, 266 DOI 10.17487/RFC4122, July 2005, 267 . 269 [RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token 270 (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015, 271 . 273 11.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