idnits 2.17.1 draft-ietf-jmap-jscontact-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 (February 10, 2020) is 1527 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) -- Looks like a reference, but probably isn't: '1' on line 759 == Missing Reference: 'String' is mentioned on line 535, but not defined -- Looks like a reference, but probably isn't: '2' on line 761 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 JMAP R. Stepanek 3 Internet-Draft FastMail 4 Intended status: Standards Track M. Loffredo 5 Expires: August 13, 2020 IIT-CNR 6 February 10, 2020 8 JSContact: A JSON representation of contact data 9 draft-ietf-jmap-jscontact-01 11 Abstract 13 This specification defines a data model and JSON representation of 14 contact card information that can be used for data storage and 15 exchange in address book or directory applications. It aims to be an 16 alternative to the vCard data format and to be unambiguous, 17 extendable and simple to process. In contrast to the JSON-based 18 jCard format, it is not a direct mapping from the vCard data model 19 and expands semantics where appropriate. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on August 13, 2020. 38 Copyright Notice 40 Copyright (c) 2020 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. Relation to the xCard and jCard formats . . . . . . . . . 3 57 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 58 1.3. Vendor-specific Property Extensions and Values . . . . . 4 59 2. JSCard . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 2.1. Metadata properties . . . . . . . . . . . . . . . . . . . 4 61 2.1.1. uid . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 2.1.2. prodId . . . . . . . . . . . . . . . . . . . . . . . 4 63 2.1.3. updated . . . . . . . . . . . . . . . . . . . . . . . 5 64 2.1.4. kind . . . . . . . . . . . . . . . . . . . . . . . . 5 65 2.1.5. relatedTo . . . . . . . . . . . . . . . . . . . . . . 5 66 2.2. Name and Organization properties . . . . . . . . . . . . 6 67 2.2.1. fullName . . . . . . . . . . . . . . . . . . . . . . 6 68 2.2.2. name . . . . . . . . . . . . . . . . . . . . . . . . 6 69 2.2.3. organization . . . . . . . . . . . . . . . . . . . . 6 70 2.2.4. jobTitle . . . . . . . . . . . . . . . . . . . . . . 7 71 2.2.5. role . . . . . . . . . . . . . . . . . . . . . . . . 7 72 2.3. Contact and Resource properties . . . . . . . . . . . . . 7 73 2.3.1. emails . . . . . . . . . . . . . . . . . . . . . . . 7 74 2.3.2. phones . . . . . . . . . . . . . . . . . . . . . . . 7 75 2.3.3. online . . . . . . . . . . . . . . . . . . . . . . . 8 76 2.3.4. preferredContactMethod . . . . . . . . . . . . . . . 8 77 2.3.5. preferredContactLanguages . . . . . . . . . . . . . . 8 78 2.4. Address and Location properties . . . . . . . . . . . . . 9 79 2.4.1. addresses . . . . . . . . . . . . . . . . . . . . . . 9 80 2.5. Additional properties . . . . . . . . . . . . . . . . . . 10 81 2.5.1. anniversaries . . . . . . . . . . . . . . . . . . . . 10 82 2.5.2. personalInfo . . . . . . . . . . . . . . . . . . . . 11 83 2.5.3. notes . . . . . . . . . . . . . . . . . . . . . . . . 11 84 2.5.4. categories . . . . . . . . . . . . . . . . . . . . . 11 85 2.6. Common JSCard types . . . . . . . . . . . . . . . . . . . 12 86 2.6.1. LocalizedString . . . . . . . . . . . . . . . . . . . 12 87 2.6.2. Resource . . . . . . . . . . . . . . . . . . . . . . 12 88 3. JSCardGroup . . . . . . . . . . . . . . . . . . . . . . . . . 13 89 3.1. Properties . . . . . . . . . . . . . . . . . . . . . . . 13 90 3.1.1. uid . . . . . . . . . . . . . . . . . . . . . . . . . 13 91 3.1.2. name . . . . . . . . . . . . . . . . . . . . . . . . 13 92 3.1.3. cards . . . . . . . . . . . . . . . . . . . . . . . . 13 93 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 13 94 4.1. IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . . 14 95 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 96 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 97 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 98 7.1. Normative References . . . . . . . . . . . . . . . . . . 14 99 7.2. Informative References . . . . . . . . . . . . . . . . . 16 100 7.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 17 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 103 1. Introduction 105 This document defines a data model for contact card data normally 106 used in address book or directory applications and services. It aims 107 to be an alternative to the vCard data format [RFC6350] and to 108 provide a JSON-based standard representation of contact card data. 110 The key design considerations for this data model are as follows: 112 o Most of the initial set of attributes should be taken from the 113 vCard data format [RFC6350] and extensions ([RFC6473], [RFC6474], 114 [RFC6715], [RFC6869], [RFC8605]). The specification should add 115 new attributes or value types, or not support existing ones, where 116 appropriate. Conversion between the data formats need not fully 117 preserve semantic meaning. 119 o The attributes of the cards data represented must be described as 120 a simple key-value pair, reducing complexity of its 121 representation. 123 o The data model should avoid all ambiguities and make it difficult 124 to make mistakes during implementation. 126 o Extensions, such as new properties and components, MUST NOT lead 127 to requiring an update to this document. 129 The representation of this data model is defined in the I-JSON format 130 [RFC7493], which is a strict subset of the JavaScript Object Notation 131 (JSON) Data Interchange Format [RFC8259]. Using JSON is mostly a 132 pragmatic choice: its widespread use makes JSCard easier to adopt, 133 and the availability of production-ready JSON implementations 134 eliminates a whole category of parser-related interoperability 135 issues. 137 1.1. Relation to the xCard and jCard formats 139 The xCard [RFC6351] and jCard [RFC7095] specifications define 140 alternative representations for vCard data, in XML and JSON format 141 respectively. Both explicitly aim to not change the underlying data 142 model. Accordingly, they are regarded as equal to vCard in the 143 context of this document. 145 1.2. Terminology 147 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 148 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 149 "OPTIONAL" in this document are to be interpreted as described in BCP 150 14 [RFC2119] [RFC8174] when, and only when, they appear in all 151 capitals, as shown here. 153 1.3. Vendor-specific Property Extensions and Values 155 Vendors MAY add additional properties to JSContact objects to support 156 their custom features. The names of these properties MUST be 157 prefixed with a domain name controlled by the vendor to avoid 158 conflict, e.g. "example.com/customprop". 160 Some JSContact properties allow vendor-specific value extensions. If 161 so, vendor-specific values MUST be prefixed with a domain name 162 controlled by the vendor, e.g. "example.com/customrel". 164 Vendors are strongly encouraged to register any new property values 165 or extensions that are useful to other systems as well, rather than 166 using a vendor-specific prefix. 168 2. JSCard 170 MIME type: "application/jscontact+json;type=jscard" 172 A JSCard object stores information about a person, organization or 173 company. 175 2.1. Metadata properties 177 2.1.1. uid 179 Type: "String" (mandatory). 181 An identifier, used to associate the object as the same across 182 different systems, addressbooks and views. [RFC4122] describes a 183 range of established algorithms to generate universally unique 184 identifiers (UUID), and the random or pseudo-random version is 185 recommended. For compatibility with [RFC6350] UIDs, implementations 186 MUST accept both URI and free-form text. 188 2.1.2. prodId 190 Type: "String" (optional). 192 The identifier for the product that created the JSCard object. 194 2.1.3. updated 196 Type: "String" (optional). 198 The date and time when the data in this JSCard object was last 199 modified. The timestamp MUST be formatted as specified in [RFC3339]. 201 2.1.4. kind 203 Type: "String" (optional). The kind of the entity the Card 204 represents. 206 The value MUST be either one of the following values, registered in a 207 future RFC, or a vendor-specific value: 209 o "individual": a single person 211 o "org": an organization 213 o "location": a named location 215 o "device": a device, such as appliances, computers, or network 216 elements 218 o "application": a software application 220 2.1.5. relatedTo 222 Type: "String[Relation]" (optional). 224 Relates the object to other JSCard objects. This is represented as a 225 map of the URI (or single text value) of the related objects to a 226 possibly empty set of relation types. The Relation object has the 227 following properties: 229 o relation: "String[Boolean]" (optional, default: empty Object) 230 Describes how the linked object is related to the linking object. 231 The relation is defined as a set of relation types. If empty, the 232 relationship between the two objects is unspecified. Keys in the 233 set MUST be one of the RELATED property [RFC6350] type parameter 234 values, or an IANA-registered value, or a vendor-specific value. 235 The value for each key in the set MUST be true. 237 Note, the Relation object only has one property; it is specified as 238 an object with a single property to allow for extension in the 239 future. 241 2.2. Name and Organization properties 243 2.2.1. fullName 245 Type: "LocalizedString" (optional). 247 The full name (e.g. the personal name and surname of an individual, 248 the name of an organization) of the entity represented by this card. 250 2.2.2. name 252 Type: "NameComponent[]" (optional). 254 The name components of the name of the entity represented by this 255 JSCard. Name components SHOULD be ordered such that their values 256 joined by whitespace produce a valid full name of this entity. 258 A NameComponent has the following properties: 260 o value: "String" (mandatory). The value of this name component. 262 o type: "String" (mandatory). The type of this name component. 263 Valid name component types are: 265 * "prefix". The value is a honorific title(s), e.g. "Mr", "Ms", 266 "Dr". 268 * "personal". The value is a personal name(s), also known as 269 "first name", "given name". 271 * "surname". The value is a surname, also known as "last name", 272 "family name". 274 * "additional". The value is an additional name, also known as 275 "middle name". 277 * "suffix". The value is a honorific suffix, e.g. "B.A.", 278 "Esq.". 280 * "nickname". The value is a nickname. 282 2.2.3. organization 284 Type: "LocalizedString[]" (optional). 286 The company or organization name and units associated with this card. 287 The first entry in the list names the organization, and any following 288 entries name organizational units. 290 2.2.4. jobTitle 292 Type : "LocalizedString[]" (optional). 294 The job title(s) or functional position(s) of the entity represented 295 by this card. 297 2.2.5. role 299 Type : "LocalizedString[]" (optional). 301 The role(s), function(s) or part(s) played in a particular situation 302 by the entity represented by this card. In contrast to a job title, 303 the roles might differ for example in project contexts. 305 2.3. Contact and Resource properties 307 2.3.1. emails 309 Type: "Resource[]" (optional). 311 An array of Resource objects where the values are URLs in the 312 "mailto" scheme [RFC6068] or free-text email addresses. The default 313 value of the "type" property is "email". If set, the type MUST be 314 "email" or "other". 316 2.3.2. phones 318 Type: "Resource[]" (optional). 320 An array of Resource objects where the values are URIs scheme or 321 free-text phone numbers. Typical URI schemes are the [RFC3966] "tel" 322 or [RFC3261] "sip" schemes, but any URI scheme is allowed. Types 323 are: 325 o "voice" The number is for calling by voice. 327 o "fax" The number is for sending faxes. 329 o "pager" The number is for a pager or beeper. 331 o "other" The number is for some other purpose. A label property 332 MAY be included to display next to the number to help the user 333 identify its purpose. 335 2.3.3. online 337 Type: "Resource[]" (optional). 339 An array of Resource objects where the values are URIs or usernames 340 associated with the card for online services. Types are: 342 o "uri" The value is a URI, e.g. a website link. 344 o "username" The value is a username associated with the entity 345 represented by this card (e.g. for social media, or an IM client). 346 A label property SHOULD be included to identify what service this 347 is for. For compatibility between clients, this label SHOULD be 348 the canonical service name, including capitalisation. e.g. 349 "Twitter", "Facebook", "Skype", "GitHub", "XMPP". 351 o "other" The value is something else not covered by the above 352 categories. A label property MAY be included to display next to 353 the number to help the user identify its purpose. 355 2.3.4. preferredContactMethod 357 Type : "String" (optional) 359 Defines the preferred contact method or resource with additional 360 information about this card. The value MUST be the property name of 361 one of the Resource lists: "emails", "phones", "online", "other". 363 2.3.5. preferredContactLanguages 365 Type : "String[ContactLanguage[]]" (optional) 367 Defines the preferred languages for contacting the entity associated 368 with this card. The keys in the object MUST be [RFC5646] language 369 tags. The values are a (possibly empty) list of contact language 370 preferences for this language. Also see the definition of the VCARD 371 LANG property (Section 6.4.4., [RFC6350]). 373 A ContactLanguage object has the following properties: 375 o type: "String" (optional). Defines the context of this 376 preference. This could be "work", "home" or another value. 378 o preference: "Number" (optional). Defines the preference order of 379 this language for the context defined in the type property. If 380 set, the property value MUST be between 1 and 100 (inclusive). 381 Lower values correspond to a higher level of preference, with 1 382 being most preferred. If not set, the default MUST be to 383 interpret the language as the least preferred in its context. 384 Preference orders SHOULD be unique across language for a specific 385 type. 387 A valid ContactLanguage object MUST have at least one of its 388 properties set. 390 2.4. Address and Location properties 392 2.4.1. addresses 394 Type: Address[] (optional). 396 An array of Address objects, containing physical locations. An 397 Address object has the following properties: 399 o context: "String" (optional, default "other"). Specifies the 400 context of the address information. The value MUST be either one 401 of the following values, registered in a future RFC, or a vendor- 402 specific value: 404 * "private" An address of a residence. 406 * "work" An address of a workplace. 408 * "billing" An address to be used for billing. 410 * "postal" An address to be used for delivering physical items. 412 * "other" An address not covered by the above categories. 414 o label: "String" (optional). A label describing the value in more 415 detail. 417 o fullAddress: "LocalizedString" (optional). The complete address, 418 excluding type and label. This property is mainly useful to 419 represent addresses of which the individual address components are 420 unknown, or to provide localized representations. 422 o street: "String" (optional). The street address. This MAY be 423 multiple lines; newlines MUST be preserved. 425 o extension: "String" (optional) The extended address, such as an 426 apartment or suite number, or care-of address. 428 o locality: "String" (optional). The city, town, village, post 429 town, or other locality within which the street address may be 430 found. 432 o region: "String" (optional). The province, such as a state, 433 county, or canton within which the locality may be found. 435 o country: "String" (optional). The country name. 437 o postOfficeBox: "String" (optional) The post office box. 439 o postcode: "String" (optional). The postal code, post code, ZIP 440 code or other short code associated with the address by the 441 relevant country's postal system. 443 o countryCode: "String" (optional). The ISO-3166-1 country code. 445 o coordinates: "String" (optional) A [RFC5870] "geo:" URI for the 446 address. 448 o timeZone: "String" (optional) Identifies the time zone this 449 address is located in. This SHOULD be a time zone name registered 450 in the IANA Time Zone Database [1]. Unknown time zone identifiers 451 MAY be ignored by implementations. 453 o isPreferred: Boolean (optional, default: false). Whether this 454 Address is the preferred for its type. This SHOULD only be one 455 per type. 457 2.5. Additional properties 459 2.5.1. anniversaries 461 Type : Anniversary[] (optional). 463 Memorable dates and events for the entity represented by this card. 464 An Anniversary object has the following properties: 466 o type: "String" (mandatory). Specifies the type of the 467 anniversary. This RFC predefines the following types, but 468 implementations MAY use additional values: 470 * "birth": a birth day anniversary 472 * "death": a death day anniversary 474 * "other": an anniversary not covered by any of the known types. 476 o label: "String" (optional). A label describing the value in more 477 detail, especially if the type property has value "other" (but MAY 478 be included with any type). 480 o date: "String" (mandatory). The date of this anniversary, in the 481 form "YYYY-MM-DD" (any part may be all 0s for unknown) or a 482 [RFC3339] timestamp. 484 o place: Address (optional). An address associated with this 485 anniversary, e.g. the place of birth or death. 487 2.5.2. personalInfo 489 Type: PersonalInformation[] (optional). 491 A list of personal information about the entity represented by this 492 card. A PersonalInformation object has the following properties: 494 o type: "String" (mandatory). Specifies the type for this personal 495 information. Allowed values are: 497 * "expertise": a field of expertise or credential 499 * "hobby": a hobby 501 * "interest": an interest 503 * "other": an information not covered by the above categories 505 o value: "String" (mandatory). The actual information. This 506 generally is free-text, but future specifications MAY restrict 507 allowed values depending on the type of this PersonalInformation. 509 o level: "String" (optional) Indicates the level of expertise, or 510 engagement in hobby or interest. Allowed values are: "high", 511 "medium" and "low". 513 2.5.3. notes 515 Type: "LocalizedString[]" (optional). 517 Arbitrary notes about the entity represented by this card. 519 2.5.4. categories 521 Type: "String[]" (optional). A list of free-text or URI categories 522 that relate to the card. 524 2.6. Common JSCard types 526 2.6.1. LocalizedString 528 A LocalizedString object has the following properties: 530 o value: "String" (mandatory). The property value. 532 o language: "String" (optional). The [RFC5646] language tag of this 533 value, if any. 535 o localizations: "String[String]" (optional). A map from [RFC5646] 536 language tags to the value localized in that language. 538 2.6.2. Resource 540 A Resource object has the following properties: 542 o context: "String" (optional) Specifies the context in which to use 543 this resource. Pre-defined values are: 545 * "private": The resource may be used to contact the card holder 546 in a private context. 548 * "work": The resource may be used to contact the card holder in 549 a professional context. 551 * "other": The resource may be used to contact the card holder in 552 some other context. A label property MAY be help to identify 553 its purpose. 555 o type: "String" (optional). Specifies the property-specific 556 variant of the resource. This MUST be taken from the set of 557 allowed types specified in the respective contact method property. 559 o labels: "String[Boolean]" (optional). A set of labels that 560 describe the value in more detail, especially if the type property 561 has value "other" (but MAY be included with any type). The keys 562 in the map define the label, the values MUST be "true". 564 o value: "String" (mandatory). The actual resource value, e.g. an 565 email address or phone number. 567 o mediaType: "String" (optional). Used for properties with URI 568 values. Provides the media type [RFC2046] of the resource 569 identified by the URI. 571 o isPreferred: Boolean (optional, default: false). Whether this 572 resource is the preferred for its type. This SHOULD only be one 573 per type. 575 3. JSCardGroup 577 MIME type: "application/jscontact+json;type=jscardgroup" 579 A JSCardGroup object represents a named set of JSCards. 581 3.1. Properties 583 3.1.1. uid 585 Type : "String" (mandatory). 587 A globally unique identifier. The same requirements as for the 588 JSCard uid property apply. 590 3.1.2. name 592 Type: "String" (optional). 594 The user-visible name for the group, e.g. "Friends". This may be 595 any UTF-8 string of at least 1 character in length and maximum 255 596 octets in size. The same name may be used by two different groups. 598 3.1.3. cards 600 Type : "JSCard[]" (mandatory). The cards in the group. 601 Implementations MUST preserve the order of list entries. 603 4. Implementation Status 605 NOTE: Please remove this section and the reference to [RFC7942] prior 606 to publication as an RFC. This section records the status of known 607 implementations of the protocol defined by this specification at the 608 time of posting of this Internet-Draft, and is based on a proposal 609 described in [RFC7942]. The description of implementations in this 610 section is intended to assist the IETF in its decision processes in 611 progressing drafts to RFCs. Please note that the listing of any 612 individual implementation here does not imply endorsement by the 613 IETF. Furthermore, no effort has been spent to verify the 614 information presented here that was supplied by IETF contributors. 615 This is not intended as, and must not be construed to be, a catalog 616 of available implementations or their features. Readers are advised 617 to note that other implementations may exist. According to 618 [RFC7942], "this will allow reviewers and working groups to assign 619 due consideration to documents that have the benefit of running code, 620 which may serve as evidence of valuable experimentation and feedback 621 that have made the implemented protocols more mature. It is up to 622 the individual working groups to use this information as they see 623 fit". 625 4.1. IIT-CNR/Registro.it 627 o Responsible Organization: Institute of Informatics and Telematics 628 of National Research Council (IIT-CNR)/Registro.it 630 o Location: https://rdap.pubtest.nic.it/ [2] 632 o Description: This implementation includes support for RDAP queries 633 using data from the public test environment of .it ccTLD. The 634 RDAP server does not implement any security policy because data 635 returned by this server are only for experimental testing 636 purposes. The RDAP server returns responses including JSCard in 637 place of jCard when queries contain the parameter jscard=1. 639 o Level of Maturity: This is a "proof of concept" research 640 implementation. 642 o Coverage: This implementation includes all of the features 643 described in this specification. 645 o Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it 647 5. IANA Considerations 649 TBD 651 6. Security Considerations 653 TBD 655 7. References 657 7.1. Normative References 659 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 660 Extensions (MIME) Part Two: Media Types", RFC 2046, 661 DOI 10.17487/RFC2046, November 1996, 662 . 664 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 665 Requirement Levels", BCP 14, RFC 2119, 666 DOI 10.17487/RFC2119, March 1997, 667 . 669 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 670 Unique IDentifier (UUID) URN Namespace", RFC 4122, 671 DOI 10.17487/RFC4122, July 2005, 672 . 674 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 675 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 676 September 2009, . 678 [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource 679 Identifier for Geographic Locations ('geo' URI)", 680 RFC 5870, DOI 10.17487/RFC5870, June 2010, 681 . 683 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 684 DOI 10.17487/RFC6350, August 2011, 685 . 687 [RFC6351] Perreault, S., "xCard: vCard XML Representation", 688 RFC 6351, DOI 10.17487/RFC6351, August 2011, 689 . 691 [RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095, 692 DOI 10.17487/RFC7095, January 2014, 693 . 695 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, 696 DOI 10.17487/RFC7493, March 2015, 697 . 699 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 700 Code: The Implementation Status Section", BCP 205, 701 RFC 7942, DOI 10.17487/RFC7942, July 2016, 702 . 704 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 705 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 706 May 2017, . 708 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 709 Interchange Format", STD 90, RFC 8259, 710 DOI 10.17487/RFC8259, December 2017, 711 . 713 7.2. Informative References 715 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 716 A., Peterson, J., Sparks, R., Handley, M., and E. 717 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 718 DOI 10.17487/RFC3261, June 2002, 719 . 721 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 722 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 723 . 725 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", 726 RFC 3966, DOI 10.17487/RFC3966, December 2004, 727 . 729 [RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' 730 URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010, 731 . 733 [RFC6473] Saint-Andre, P., "vCard KIND:application", RFC 6473, 734 DOI 10.17487/RFC6473, December 2011, 735 . 737 [RFC6474] Li, K. and B. Leiba, "vCard Format Extensions: Place of 738 Birth, Place and Date of Death", RFC 6474, 739 DOI 10.17487/RFC6474, December 2011, 740 . 742 [RFC6715] Cauchie, D., Leiba, B., and K. Li, "vCard Format 743 Extensions: Representing vCard Extensions Defined by the 744 Open Mobile Alliance (OMA) Converged Address Book (CAB) 745 Group", RFC 6715, DOI 10.17487/RFC6715, August 2012, 746 . 748 [RFC6869] Salgueiro, G., Clarke, J., and P. Saint-Andre, "vCard 749 KIND:device", RFC 6869, DOI 10.17487/RFC6869, February 750 2013, . 752 [RFC8605] Hollenbeck, S. and R. Carney, "vCard Format Extensions: 753 ICANN Extensions for the Registration Data Access Protocol 754 (RDAP)", RFC 8605, DOI 10.17487/RFC8605, May 2019, 755 . 757 7.3. URIs 759 [1] https://www.iana.org/time-zones 761 [2] https://rdap.pubtest.nic.it/ 763 Authors' Addresses 765 Robert Stepanek 766 FastMail 767 PO Box 234, Collins St West 768 Melbourne, VIC 8007 769 Australia 771 Email: rsto@fastmailteam.com 773 Mario Loffredo 774 IIT-CNR 775 Via Moruzzi,1 776 Pisa, 56124 777 Italy 779 Email: mario.loffredo@iit.cnr.it