idnits 2.17.1 draft-ietf-sipcore-callinfo-rcd-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 18, 2020) is 1227 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) == Outdated reference: A later version (-26) exists of draft-ietf-stir-passport-rcd-08 ** Obsolete normative reference: RFC 2426 (Obsoleted by RFC 6350) ** Downref: Normative reference to an Informational RFC: RFC 3324 ** Obsolete normative reference: RFC 4627 (Obsoleted by RFC 7158, RFC 7159) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Wendt 3 Internet-Draft Comcast 4 Intended status: Standards Track J. Peterson 5 Expires: May 22, 2021 Neustar Inc. 6 November 18, 2020 8 SIP Call-Info Parameters for Rich Call Data 9 draft-ietf-sipcore-callinfo-rcd-01 11 Abstract 13 This document describes a SIP Call-Info header field usage defined to 14 include rich data associated with the identity of the calling party 15 that can be rendered to called party for providing more useful 16 information about the caller or the specific reason for the call. 17 This includes extended comprehensive information about the caller 18 such as what a jCard object can represent for describing the calling 19 party or other call specific information such as describing the 20 reason or intent of the call. The elements defined for this purpose 21 are intended to be extensible to accommodate related information 22 about calls that helps people decide whether to pick up the phone and 23 additionally, with the use of jCard and other elements, to be 24 compatible with the STIR/PASSporT Rich Call Data framework. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on May 22, 2021. 43 Copyright Notice 45 Copyright (c) 2020 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 4. "jcard" Call-Info Token . . . . . . . . . . . . . . . . . . . 4 64 5. 'call-reason' Call-Info Parameter . . . . . . . . . . . . . . 6 65 6. Usage of jCard and property specific usage . . . . . . . . . 7 66 6.1. Identification properties . . . . . . . . . . . . . . . . 7 67 6.1.1. "fn" property . . . . . . . . . . . . . . . . . . . . 8 68 6.1.2. "n" property . . . . . . . . . . . . . . . . . . . . 8 69 6.1.3. "nickname" property . . . . . . . . . . . . . . . . . 8 70 6.1.4. "photo" property . . . . . . . . . . . . . . . . . . 8 71 6.2. Delivery Addressing Properties . . . . . . . . . . . . . 9 72 6.2.1. "adr" property . . . . . . . . . . . . . . . . . . . 9 73 6.3. Communications Properties . . . . . . . . . . . . . . . . 9 74 6.3.1. "tel" property . . . . . . . . . . . . . . . . . . . 9 75 6.3.2. "email" property . . . . . . . . . . . . . . . . . . 9 76 6.3.3. "lang" property . . . . . . . . . . . . . . . . . . . 10 77 6.4. Geographical Properties . . . . . . . . . . . . . . . . . 10 78 6.4.1. "tz" property . . . . . . . . . . . . . . . . . . . . 10 79 6.4.2. "geo" property . . . . . . . . . . . . . . . . . . . 10 80 6.5. Organizational Properties . . . . . . . . . . . . . . . . 10 81 6.5.1. "title" property . . . . . . . . . . . . . . . . . . 11 82 6.5.2. "role" property . . . . . . . . . . . . . . . . . . . 11 83 6.5.3. "logo" property . . . . . . . . . . . . . . . . . . . 11 84 6.5.4. "org" property . . . . . . . . . . . . . . . . . . . 11 85 6.6. Explanatory Properties . . . . . . . . . . . . . . . . . 11 86 6.6.1. "catagories" property . . . . . . . . . . . . . . . . 12 87 6.6.2. "note" property . . . . . . . . . . . . . . . . . . . 12 88 6.6.3. "sound" property . . . . . . . . . . . . . . . . . . 12 89 6.6.4. "uid" property . . . . . . . . . . . . . . . . . . . 12 90 6.6.5. "url" property . . . . . . . . . . . . . . . . . . . 13 91 6.6.6. "version" property . . . . . . . . . . . . . . . . . 13 92 7. Extension of jCard . . . . . . . . . . . . . . . . . . . . . 13 93 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 94 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 95 9.1. SIP Call-Info Header Field Purpose Token Request . . . . 13 96 9.2. SIP Call-Info Header Field Purpose Token Request . . . . 14 97 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 98 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 99 11.1. Normative References . . . . . . . . . . . . . . . . . . 14 100 11.2. Informative References . . . . . . . . . . . . . . . . . 15 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 103 1. Introduction 105 Traditional telephone network signaling protocols have long supported 106 delivering a 'calling name' from the originating side, though in 107 practice, the terminating side is often left to derive a name from 108 the calling party number by consulting a local address book or an 109 external database. SIP similarly can carry a 'display-name' in the 110 From header field value from the originating to terminating side, 111 though it is an unsecured field that is not commonly trusted. The 112 same is true of information in the Call-Info header field. 114 To allow calling parties to initiate, and called parties to receive, 115 a more comprehensive, deterministic, and extensible rich call data 116 for incoming calls, we describe new tokens for the SIP [RFC3261] 117 Call-Info header field and a corresponding "purpose" parameter. We 118 also define a new parameter of Call-Info designed for carrying a 119 "reason" value. For this document, depending on the policies of the 120 communications system, calling parties could either be the end user 121 device or an originating service provider, and called parties could 122 also similarly be an end user device or the terminating service 123 provider acting on behalf of the recipient of the call. 125 Used on its own, this specification assumes that called party user 126 agent can trust the SIP network or the SIP provider to deliver the 127 correct rich call data (RCD) information. This may not always be the 128 case and thus, the entity inserting the Call-Info header field and 129 the UAS relying on it SHOULD be part of the same trust domain 130 [RFC3324]. Alternatively, and likely the recommended approach, is 131 that the entity inserting the call-info header should also sign the 132 caller information via STIR mechanisms [RFC8224] and specifically 133 through the [I-D.ietf-stir-passport-rcd]. This STIR signature would 134 likely be provided by the caller itself or the originating service 135 provider using an authoritative signature to authenticate the 136 information is from the originator and hasn't been tampered with in 137 transmission. 139 [RFC7852] provides a means of carrying additional data about callers 140 for the purposes of emergency services (especially its Section 4.4 141 "Owner/Subscriber" information). This specification provides an 142 overlapping functionality for non-emergency cases. Rather than 143 overloading its "EmergencyCallData" Call-Info "purpose" parameter 144 value, this document defines a separate "purpose" parameter for the 145 more generic delivery of information via jCard [RFC7095]. This 146 document borrows from [RFC7852] the capability to carry a data 147 structure as a body, through the use of the "cid" URI scheme 148 [RFC2392]. 150 2. Terminology 152 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 153 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 154 "OPTIONAL" in this document are to be interpreted as described in BCP 155 14 [RFC2119] [RFC8174] when, and only when, they appear in all 156 capitals, as shown here. 158 3. Overview 160 The Call-Info header field, defined in [RFC3261] Section 20.9, 161 defines a purpose parameter currently with "info", "icon", and "card" 162 tokens. This document defines one new purpose value and one new 163 generic parameter for Call-Info. 165 The value "jcard" is to be used to associate rich call data related 166 to the identity of the calling party in the form of a jCard 167 [RFC7095]. While there is a "card" token that is already defined 168 with similar purpose, there are two primary reasons for the 169 definition and usage of jCard and the use of JSON over the XML based 170 vCard [RFC2426]. First, JSON has become the default and optimally 171 supported for transmission, parsing, and manipulation of data on IP 172 networks. Second, jCard has also been defined in 173 [I-D.ietf-stir-passport-rcd] and has been adopted by PASSporT 174 [RFC8225] because of the usage of JSON Web Tokens (JWT) [RFC7519]. 176 A generic parameter for "call-reason" is to be used to provide a 177 string or other object that is used to convey the intent or reason 178 the caller is calling to help the called party understand better the 179 context of the call and why they may want to answer the call. 181 4. "jcard" Call-Info Token 183 The use of the new Call-Info Token "jcard" is for the purpose of 184 supporting RCD associated with the identity of a calling party in a 185 SIP call [RFC3261] Section 20.9. The format of a Call-Info header 186 field when using the "jcard" is as follows. 188 The Call-Info header should include a URI where the resource pointed 189 to by the URI is a jCard JSON object defined in [RFC7095]. The web 190 server serving this file MUST use the MIME media type for JSON text 191 as application/json with a default encoding of UTF-8 [RFC4627]. This 192 also MAY be carried in the body of the SIP request bearing this Call- 193 Info via the "cid" URI scheme [RFC2392]. Alternatively, the URI MUST 194 define the use HTTPS or a transport that can validate the integrity 195 of the source of the resource as well as the transport channel the 196 resource is retrieved. 198 An example of a Call-Info header field is: 200 Call-Info: ;purpose=jcard 202 An example contents of a URL linked jCard JSON file is shown as 203 follows: 205 ["vcard", 206 [ 207 ["version", {}, "text", "4.0"], 208 ["fn", {}, "text", "James Bond"], 209 ["n", {}, "text", ["Bond", "James", "", "", "Mr."]], 210 ["adr", {"type":"work"}, "text", 211 ["", "", "3100 Massachusetts Avenue NW", "Washington", "DC", 212 "20008", "USA"] 213 ], 214 ["email", {}, "text", "007@mi6-hq.com"], 215 ["tel", { "type": ["voice", "text", "cell"], "pref": "1" }, "uri", 216 "tel:+1-202-555-1000"], 217 ["tel", { "type": ["fax"] }, "uri", "tel:+1-202-555-1001"], 218 ["bday", {}, "date", "19241116"] 219 ["logo", {}, "uri", 220 "https://upload.wikimedia.org/wikipedia/en/c/c5 221 /Fleming007impression.jpg"] 222 ] 223 ] 225 An example SIP INVITE using the "cid" URI scheme is as follows. 227 INVITE sip:alice@example.com SIP/2.0 228 Via: SIP/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bKnashds8 229 To: Alice 230 From: Bob ;tag=1928301774> 231 Call-ID: a84b4c76e66710 232 Call-Info: ;purpose=jcard;call-reason= \ 233 "For your ears only" 234 CSeq: 314159 INVITE 235 Max-Forwards: 70 236 Date: Fri, 25 Sep 2015 19:12:25 GMT 237 Contact: 238 Content-Type: multipart/mixed; boundary=boundary1 239 Content-Length: ... 241 --boundary1 243 Content-Type: application/sdp 245 v=0 246 o=UserA 2890844526 2890844526 IN IP4 pc33.atlanta.example.com 247 s=Session SDP 248 c=IN IP4 pc33.atlanta.example.com 249 t=0 0 250 m=audio 49172 RTP/AVP 0 251 a=rtpmap:0 PCMU/8000 253 --boundary1 255 Content-Type: application/vcard+json 256 Content-ID: <12155551212@example.com> 258 ["vcard",[["version",{},"text","4.0"],["fn",{},"text","James Bond" 259 ],["n",{},"text",["Bond","James","","","Mr."]],["adr",{"type": 260 "work"},"text",["","","3100 Massachusetts Avenue NW","Washington", 261 "DC","20008","USA"]],["email",{},"text","007@mi6-hq.com"],["tel", 262 {"type":["voice","text","cell"],"pref":"1"},"uri", 263 "tel:+1-202-555-1000"],["tel",{"type":["fax"]},"uri", 264 "tel:+1-202-555-1001"],["bday",{},"date","19241116"]["logo",{}, 265 "uri","https://upload.wikimedia.org/wikipedia/en/c/c5 266 /Fleming007impression.jpg"]]] 268 5. 'call-reason' Call-Info Parameter 270 In addition to the jCard value defined here, this specification also 271 defines a generic parameter of the Call-Info header called "call- 272 reason". The "call-reason" parameter is intended to convey a short 273 textual message suitable for display to an end user during call 274 alerting. As a general guideline, this message SHOULD be no longer 275 than 160 characters; displays that support this specification may be 276 forced to truncate messages that cannot fit onto a screen. This 277 message conveys the caller's intention in contacting the callee. It 278 is an optional parameter, and the sender of a SIP request cannot 279 guarantee that its display will be supported by the terminating 280 endpoint. The manner in which this reason is set by the caller is 281 outside the scope of this specification. 283 One alternative approach would be to use the baseline [RFC3261] 284 Subject header field value to convey the reason for the call. 285 Because the Subject header has seen little historical use in SIP 286 implementations, however, and its specification describes its 287 potential use in filtering, it seems more prudent to define a new 288 means of carrying a call reason indication. 290 An example of a Call-Info header field value with the "call-reason" 291 parameter follows: 293 Call-Info: ;purpose=jcard; 294 call-reason="For your ears only" 296 One can readily imagine a need for more structured call reason data 297 that could be reliably processed automatically. Future versions of 298 this specification may explore ways to provide a structured data 299 object in place of a textual string to support things like 300 internationalization or categories of reason that can be parsed by 301 machines. 303 6. Usage of jCard and property specific usage 305 Beyond the definition of the specific properties or JSON arrays 306 associated with each property. This specification defines a few 307 rules above and beyond [RFC7095] specific to making sure there is a 308 mimimum level of supported properties that every implementation of 309 this specification should adhere to. This includes the support of 310 intepreting the value of this property and the ability to render in 311 some form appropriate to the display capabilities of the device. 312 This includes requirements specific to either textual displays and 313 graphics capable displays. 315 6.1. Identification properties 317 These types are used to capture information associated with the 318 identification and naming of the entity associated with the jCard. 320 6.1.1. "fn" property 322 The "fn" property MUST be supported with the intent of providing a 323 formatted text corresponding to the name of the object the jCard 324 represents. Reference [RFC6350] Section 6.2.1. 326 Example: 327 ["fn", {}, "text", "Mr. John Q. Public\, Esq."] 329 6.1.2. "n" property 331 The "n" property SHOULD be supported with the intent of providing the 332 components of the name of the object the jCard represents. Reference 333 [RFC6350] Section 6.2.2. 335 Example: 336 ["n", {}, "text", "Public;John;Quinlan;Mr.;Esq."] 337 ["n", {}, "text", "Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P."] 339 6.1.3. "nickname" property 341 The "nickname" property SHOULD be supported with the intent of 342 providing the text corresponding to the nickname of the object the 343 jCard represents. Reference [RFC6350] Section 6.2.3. 345 Example: 346 ["nickname", {}, "text", "Robbie"] 347 ["nickname", {}, "text", "Jim,Jimmie"] 348 ["nickname", {}, "text", "TYPE=work:Boss"] 350 6.1.4. "photo" property 352 The "photo" property MUST be supported with the intent of an image or 353 photograph information that annotates some aspect of the object the 354 jCard represents. Reference [RFC6350] Section 6.2.4. 356 In addition to the definition of jCard, and to promote 357 interoperability and proper formatting and rendering of images, the 358 photo SHOULD correspond to a square image size of the sizes 128x128, 359 256x256, 512x512, or 1024x1024 pixels. 361 Example: 362 ["photo", {}, "uri", "http://www.example.com/photos/jqpublic.gif"] 364 6.2. Delivery Addressing Properties 366 These properties are concerned with information related to the 367 delivery addressing or label for the jCard object. 369 6.2.1. "adr" property 371 The "adr" property MUST be supported with the intent of providing the 372 delivery address of the object the jCard represents. Reference 373 [RFC6350] Section 6.3.1. 375 Example: 376 ["adr", {"type":"work"}, "text", 377 ["", "", "3100 Massachusetts Avenue NW", "Washington", "DC", 378 "20008", "USA"] 380 6.3. Communications Properties 382 These properties describe information about how to communicate with 383 the object the jCard represents. 385 6.3.1. "tel" property 387 The "tel" property MUST be supported with the intent of providing the 388 telephone number for telephony communication of the object the jCard 389 represents. Reference [RFC6350] Section 6.4.1. 391 Relative to the SIP From header field this information may provide 392 alternate telephone number or other related telephone numbers for 393 other uses. 395 Example: 396 ["tel", { "type": ["voice", "text", "cell"], "pref": "1" }, "uri", 397 "tel:+1-202-555-1000"] 398 ["tel", { "type": ["fax"] }, "uri", "tel:+1-202-555-1001"] 400 6.3.2. "email" property 402 The "email" property MUST be supported with the intent of providing 403 the electronic mail address for communication of the object the jCard 404 represents. Reference [RFC6350] Section 6.4.2. 406 Example: 407 ["email", {"type":"work"}, "text", "jqpublic@xyz.example.com"] 408 ["email", {"pref":"1"}, "text", "jane_doe@example.com"] 410 6.3.3. "lang" property 412 The "lang" property MUST be supported with the intent of providing 413 the language(s) that may be used for contacting of the object the 414 jCard represents. Reference [RFC6350] Section 6.4.4. 416 Example: 417 ["lang", {"type":"work", "pref":"1"}, "language-tag", "en"] 418 ["lang", {"type":"work", "pref":"2"}, "language-tag", "fr"] 419 ["lang", {"type":"home"}, "language-tag", "fr"] 421 6.4. Geographical Properties 423 These properties are concerned with information associated with 424 geographical positions or regions associated with the object the 425 jCard represents. 427 6.4.1. "tz" property 429 The "tz" property MUST be supported with the intent of providing the 430 time zone of the object the jCard represents. Reference [RFC6350] 431 Section 6.5.1. 433 Note: Seems the up-to-date reference for where time-zone names are 434 maintained is currently at this web address, https://www.iana.org/ 435 time-zones. 437 Example: 438 ["tz", {}, "text", "Raleigh/North America"] 440 6.4.2. "geo" property 442 The "geo" property MUST be supported with the intent of providing the 443 global positioning of the object the jCard represents. Reference 444 [RFC6350] Section 6.5.2. 446 Example: 447 ["geo", {}, "uri", "geo:37.386013,-122.082932"] 449 6.5. Organizational Properties 451 These properties are concerned with information associated with 452 characteristics of the organization or organizational units of the 453 object that the jCard represents. 455 6.5.1. "title" property 457 The "title" property MUST be supported with the intent of providing 458 the position or job of the object the jCard represents. Reference 459 [RFC6350] Section 6.6.1. 461 Example: 462 ["title", {}, "text", "Research Scientist"] 464 6.5.2. "role" property 466 The "role" property MUST be supported with the intent of providing 467 the position or job of the object the jCard represents. Reference 468 [RFC6350] Section 6.6.2. 470 Example: 471 ["role", {}, "text", "Project Leader"] 473 6.5.3. "logo" property 475 The "logo" property MUST be supported with the intent of specifying a 476 graphic image of a logo associated with the object the jCard 477 represents. Reference [RFC6350] Section 6.6.3. 479 Example: 480 ["logo", {}, "uri", "http://www.example.com/pub/logos/abccorp.jpg"] 482 ["logo", {}, "uri", "data:image/jpeg;base64,MIICajCCAdOgAwIBAgIC 483 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm 484 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 485 <...the remainder of base64-encoded data...>"] 487 6.5.4. "org" property 489 The "org" property MUST be supported with the intent of specifying 490 the organizational name and units of the object the jCard represents. 491 Reference [RFC6350] Section 6.6.2. 493 Example: 494 ["org", {}, "text", "ABC\, Inc.;North American Division;Marketing"] 496 6.6. Explanatory Properties 498 These properties are concerned with additional explanations, such as 499 that related to informational notes or revisions specific to the 500 jCard. 502 6.6.1. "catagories" property 504 The "catagories" property MUST be supported with the intent of 505 specifying application category information the object the jCard 506 represents. Reference [RFC6350] Section 6.7.1. 508 Example: 509 ["catagories", {}, "text", "TRAVEL AGENT"] 511 ["catagories", {}, "text", "INTERNET,IETF,INDUSTRY"] 513 6.6.2. "note" property 515 The "note" property MUST be supported with the intent of specifying 516 supplemental information or a comment the object the jCard 517 represents. Reference [RFC6350] Section 6.7.2. 519 Example: 520 ["note", {}, "text", "This fax number is operational 0800 to 1715 521 EST\, Mon-Fri."] 523 6.6.3. "sound" property 525 The "sound" property MUST be supported with the intent of specifying 526 a digital sound content information that annotates some aspect with 527 the object the jCard represents. This property is often used to 528 specify the proper pronunciation of the name property value of the 529 jCard. Reference [RFC6350] Section 6.7.5. 531 Example: 532 ["sound", {}, "uri", "http://www.example.com/pub/logos/abccorp.mp3"] 534 ["sound", {}, "uri", "data:audio/basic;base64,MIICajCCAdOgAwIBAgICBE 535 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm 536 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 537 <...the remainder of base64-encoded data...>"] 539 6.6.4. "uid" property 541 The "uid" property MUST be supported with the intent of specifying a 542 globally unique identifier corresponding to the object the jCard 543 represents. Reference [RFC6350] Section 6.7.6. 545 Example: 546 ["uid", {}, "uri", "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"] 548 6.6.5. "url" property 550 The "url" property MUST be supported with the intent of specifying a 551 uniform resource locator associated to the object the jCard 552 represents. Reference [RFC6350] Section 6.7.8. 554 Example: 555 ["url", {}, "uri", "https://example.org/french-rest/chezchic.html"] 557 6.6.6. "version" property 559 The "version" property MUST be included and is intended to specify 560 version of the vCard specification used to format this vCard. 561 Reference [RFC6350] Section 6.7.9. 563 Example: 564 ["version", {}, "text", "4.0"] 566 7. Extension of jCard 568 Part of the intent of the usage of jCard is that it has it's own 569 extensibility properties where new properties can be defined to relay 570 newly defined information related to a caller. This capability is 571 inherently supported as part of standard extensibility. However, 572 usage of those new properties should be published and registered 573 following [RFC7095] Section 3.6 or new specifications. 575 8. Acknowledgements 577 We would like to thank David Hancock and other members of the STIR 578 working group for helpful suggestions and comments for the creation 579 of this draft. 581 9. IANA Considerations 583 9.1. SIP Call-Info Header Field Purpose Token Request 585 [this RFC] defines the "jcard" token for use as a new token in the 586 Call-Info header in the "Header Field Parameters and Parameter 587 Values" registry defined by [RFC3968]. 589 +--------------+----------------+-------------------+------------+ 590 | Header Field | Parameter Name | Predefined Values | Reference | 591 +--------------+----------------+-------------------+------------+ 592 | Call-Info | jcard | No | [this RFC] | 593 +--------------+----------------+-------------------+------------+ 595 9.2. SIP Call-Info Header Field Purpose Token Request 597 [this RFC] defines the "call-reason" generic parameter for use as a 598 new parameter in the Call-Info header in the "Header Field Parameters 599 and Parameter Values" registry defined by [RFC3968]. The parameter's 600 token is "call-reason" and it takes the value of a quoted string. 602 10. Security Considerations 604 Revealing information such as the name, location, and affiliation of 605 a person necessarily entails certain privacy risks. SIP and Call- 606 Info has no particular confidentiality requirement, as the 607 information sent in SIP is in the clear anyway. Transport-level 608 security can be used to hide information from eavesdroppers, and the 609 same confidentiality mechanisms would protect any Call-Info or jCard 610 information carried or referred to in SIP. 612 11. References 614 11.1. Normative References 616 [I-D.ietf-stir-passport-rcd] 617 Peterson, J. and C. Wendt, "PASSporT Extension for Rich 618 Call Data", draft-ietf-stir-passport-rcd-08 (work in 619 progress), November 2020. 621 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 622 Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998, 623 . 625 [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", 626 RFC 2426, DOI 10.17487/RFC2426, September 1998, 627 . 629 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 630 A., Peterson, J., Sparks, R., Handley, M., and E. 631 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 632 DOI 10.17487/RFC3261, June 2002, 633 . 635 [RFC3324] Watson, M., "Short Term Requirements for Network Asserted 636 Identity", RFC 3324, DOI 10.17487/RFC3324, November 2002, 637 . 639 [RFC3968] Camarillo, G., "The Internet Assigned Number Authority 640 (IANA) Header Field Parameter Registry for the Session 641 Initiation Protocol (SIP)", BCP 98, RFC 3968, 642 DOI 10.17487/RFC3968, December 2004, 643 . 645 [RFC4627] Crockford, D., "The application/json Media Type for 646 JavaScript Object Notation (JSON)", RFC 4627, 647 DOI 10.17487/RFC4627, July 2006, 648 . 650 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 651 DOI 10.17487/RFC6350, August 2011, 652 . 654 [RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095, 655 DOI 10.17487/RFC7095, January 2014, 656 . 658 [RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token 659 (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015, 660 . 662 [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 663 J. Winterbottom, "Additional Data Related to an Emergency 664 Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, 665 . 667 [RFC8224] Peterson, J., Jennings, C., Rescorla, E., and C. Wendt, 668 "Authenticated Identity Management in the Session 669 Initiation Protocol (SIP)", RFC 8224, 670 DOI 10.17487/RFC8224, February 2018, 671 . 673 [RFC8225] Wendt, C. and J. Peterson, "PASSporT: Personal Assertion 674 Token", RFC 8225, DOI 10.17487/RFC8225, February 2018, 675 . 677 11.2. Informative References 679 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 680 Requirement Levels", BCP 14, RFC 2119, 681 DOI 10.17487/RFC2119, March 1997, 682 . 684 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 685 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 686 May 2017, . 688 Authors' Addresses 690 Chris Wendt 691 Comcast 692 Comcast Technology Center 693 Philadelphia, PA 19103 694 USA 696 Email: chris-ietf@chriswendt.net 698 Jon Peterson 699 Neustar Inc. 700 1800 Sutter St Suite 570 701 Concord, CA 94520 702 US 704 Email: jon.peterson@neustar.biz