idnits 2.17.1 draft-ietf-jmap-jscontact-04.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 19, 2021) is 1134 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 778 == Missing Reference: 'String' is mentioned on line 582, but not defined -- Looks like a reference, but probably isn't: '2' on line 780 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 23, 2021 IIT-CNR 6 February 19, 2021 8 JSContact: A JSON representation of contact data 9 draft-ietf-jmap-jscontact-04 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 23, 2021. 38 Copyright Notice 40 Copyright (c) 2021 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. organizations . . . . . . . . . . . . . . . . . . . . 6 70 2.2.4. jobTitles . . . . . . . . . . . . . . . . . . . . . . 7 71 2.2.5. roles . . . . . . . . . . . . . . . . . . . . . . . . 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. photos . . . . . . . . . . . . . . . . . . . . . . . 8 77 2.3.5. preferredContactMethod . . . . . . . . . . . . . . . 9 78 2.3.6. preferredContactLanguages . . . . . . . . . . . . . . 9 79 2.4. Address and Location properties . . . . . . . . . . . . . 9 80 2.4.1. addresses . . . . . . . . . . . . . . . . . . . . . . 9 81 2.5. Additional properties . . . . . . . . . . . . . . . . . . 11 82 2.5.1. anniversaries . . . . . . . . . . . . . . . . . . . . 11 83 2.5.2. personalInfo . . . . . . . . . . . . . . . . . . . . 11 84 2.5.3. notes . . . . . . . . . . . . . . . . . . . . . . . . 12 85 2.5.4. categories . . . . . . . . . . . . . . . . . . . . . 12 86 3. JSGroupCard . . . . . . . . . . . . . . . . . . . . . . . . . 12 87 3.1. Group properties . . . . . . . . . . . . . . . . . . . . 12 88 3.1.1. members . . . . . . . . . . . . . . . . . . . . . . . 12 89 4. Common types . . . . . . . . . . . . . . . . . . . . . . . . 13 90 4.1. LocalizedString . . . . . . . . . . . . . . . . . . . . . 13 91 4.2. Resource . . . . . . . . . . . . . . . . . . . . . . . . 13 92 5. Implementation Status . . . . . . . . . . . . . . . . . . . . 14 93 5.1. IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . . 14 94 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 95 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 96 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 97 8.1. Normative References . . . . . . . . . . . . . . . . . . 15 98 8.2. Informative References . . . . . . . . . . . . . . . . . 16 99 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 17 100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 102 1. Introduction 104 This document defines a data model for contact card data normally 105 used in address book or directory applications and services. It aims 106 to be an alternative to the vCard data format [RFC6350] and to 107 provide a JSON-based standard representation of contact card data. 109 The key design considerations for this data model are as follows: 111 o Most of the initial set of attributes should be taken from the 112 vCard data format [RFC6350] and extensions ([RFC6473], [RFC6474], 113 [RFC6715], [RFC6869], [RFC8605]). The specification should add 114 new attributes or value types, or not support existing ones, where 115 appropriate. Conversion between the data formats need not fully 116 preserve semantic meaning. 118 o The attributes of the cards data represented must be described as 119 a simple key-value pair, reducing complexity of its 120 representation. 122 o The data model should avoid all ambiguities and make it difficult 123 to make mistakes during implementation. 125 o Extensions, such as new properties and components, MUST NOT lead 126 to requiring an update to this document. 128 The representation of this data model is defined in the I-JSON format 129 [RFC7493], which is a strict subset of the JavaScript Object Notation 130 (JSON) Data Interchange Format [RFC8259]. Using JSON is mostly a 131 pragmatic choice: its widespread use makes JSCard easier to adopt, 132 and the availability of production-ready JSON implementations 133 eliminates a whole category of parser-related interoperability 134 issues. 136 1.1. Relation to the xCard and jCard formats 138 The xCard [RFC6351] and jCard [RFC7095] specifications define 139 alternative representations for vCard data, in XML and JSON format 140 respectively. Both explicitly aim to not change the underlying data 141 model. Accordingly, they are regarded as equal to vCard in the 142 context of this document. 144 1.2. Terminology 146 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 147 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 148 "OPTIONAL" in this document are to be interpreted as described in BCP 149 14 [RFC2119] [RFC8174] when, and only when, they appear in all 150 capitals, as shown here. 152 1.3. Vendor-specific Property Extensions and Values 154 Vendors MAY add additional properties to JSContact objects to support 155 their custom features. The names of these properties MUST be 156 prefixed with a domain name controlled by the vendor to avoid 157 conflict, e.g. "example.com/customprop". 159 Some JSContact properties allow vendor-specific value extensions. If 160 so, vendor-specific values MUST be prefixed with a domain name 161 controlled by the vendor, e.g. "example.com/customrel". 163 Vendors are strongly encouraged to register any new property values 164 or extensions that are useful to other systems as well, rather than 165 using a vendor-specific prefix. 167 2. JSCard 169 MIME type: "application/jscontact+json;type=jscard" 171 A JSCard object stores information about a person, organization or 172 company. 174 2.1. Metadata properties 176 2.1.1. uid 178 Type: "String" (mandatory). 180 An identifier, used to associate the object as the same across 181 different systems, addressbooks and views. [RFC4122] describes a 182 range of established algorithms to generate universally unique 183 identifiers (UUID), and the random or pseudo-random version is 184 recommended. For compatibility with [RFC6350] UIDs, implementations 185 MUST accept both URI and free-form text. 187 2.1.2. prodId 189 Type: "String" (optional). 191 The identifier for the product that created the JSCard object. 193 2.1.3. updated 195 Type: "String" (optional). 197 The date and time when the data in this JSCard object was last 198 modified. The timestamp MUST be formatted as specified in [RFC3339]. 200 2.1.4. kind 202 Type: "String" (optional). The kind of the entity the Card 203 represents. 205 The value MUST be either one of the following values, registered in a 206 future RFC, or a vendor-specific value: 208 o "individual": a single person 210 o "org": an organization 212 o "location": a named location 214 o "device": a device, such as appliances, computers, or network 215 elements 217 o "application": a software application 219 2.1.5. relatedTo 221 Type: "String[Relation]" (optional). 223 Relates the object to other JSCard objects. This is represented as a 224 map of the URI (or single text value) of the related objects to a 225 possibly empty set of relation types. The Relation object has the 226 following properties: 228 o relation: "String[Boolean]" (optional, default: empty Object) 229 Describes how the linked object is related to the linking object. 230 The relation is defined as a set of relation types. If empty, the 231 relationship between the two objects is unspecified. Keys in the 232 set MUST be one of the RELATED property [RFC6350] type parameter 233 values, or an IANA-registered value, or a vendor-specific value. 234 The value for each key in the set MUST be true. 236 Note, the Relation object only has one property; it is specified as 237 an object with a single property to allow for extension in the 238 future. 240 2.2. Name and Organization properties 242 2.2.1. fullName 244 Type: "LocalizedString" (optional). 246 The full name (e.g. the personal name and surname of an individual, 247 the name of an organization) of the entity represented by this card. 249 2.2.2. name 251 Type: "NameComponent[]" (optional). 253 The name components of the name of the entity represented by this 254 JSCard. Name components SHOULD be ordered such that their values 255 joined by whitespace produce a valid full name of this entity. 257 A NameComponent has the following properties: 259 o value: "String" (mandatory). The value of this name component. 261 o type: "String" (mandatory). The type of this name component. The 262 value MUST be either one of the following values, registered in a 263 future RFC, or a vendor-specific value: 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. organizations 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. jobTitles 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. roles 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. photos 357 Type: "File[]" (optional). 359 An array of File objects that contain photographs or images 360 associated with this card. A typical use case is to include an 361 avatar for display along the contact name. 363 A File object has the following properties: 365 o href: "String" (mandatory). A URI where to fetch the data of this 366 file. 368 o mediaType: "String" (optional). The content-type of the file, if 369 known. 371 o size: "UnsignedInt" (optional). The size, in octets, of the file 372 when fully decoded (i.e., the number of octets in the file the 373 user would download), if known. 375 o isPreferred: Boolean (optional, default: false). Whether this 376 file is preferred as photo for this card. This SHOULD only be 377 one. 379 2.3.5. preferredContactMethod 381 Type : "String" (optional) 383 Defines the preferred contact method or resource with additional 384 information about this card. The value MUST be the property name of 385 one of the Resource lists: "emails", "phones", "online". 387 2.3.6. preferredContactLanguages 389 Type : "String[ContactLanguage[]]" (optional) 391 Defines the preferred languages for contacting the entity associated 392 with this card. The keys in the object MUST be [RFC5646] language 393 tags. The values are a (possibly empty) list of contact language 394 preferences for this language. Also see the definition of the VCARD 395 LANG property (Section 6.4.4., [RFC6350]). 397 A ContactLanguage object has the following properties: 399 o type: "String" (optional). Defines the context of this 400 preference. This could be "work", "home" or another value. 402 o preference: "Number" (optional). Defines the preference order of 403 this language for the context defined in the type property. If 404 set, the property value MUST be between 1 and 100 (inclusive). 405 Lower values correspond to a higher level of preference, with 1 406 being most preferred. If not set, the default MUST be to 407 interpret the language as the least preferred in its context. 408 Preference orders SHOULD be unique across language for a specific 409 type. 411 A valid ContactLanguage object MUST have at least one of its 412 properties set. 414 2.4. Address and Location properties 416 2.4.1. addresses 418 Type: Address[] (optional). 420 An array of Address objects, containing physical locations. An 421 Address object has the following properties: 423 o context: "String" (optional, default "other"). Specifies the 424 context of the address information. The value MUST be either one 425 of the following values, registered in a future RFC, or a vendor- 426 specific value: 428 * "private" An address of a residence. 430 * "work" An address of a workplace. 432 * "billing" An address to be used for billing. 434 * "postal" An address to be used for delivering physical items. 436 * "other" An address not covered by the above categories. 438 o label: "String" (optional). A label describing the value in more 439 detail. 441 o fullAddress: "LocalizedString" (optional). The complete address, 442 excluding type and label. This property is mainly useful to 443 represent addresses of which the individual address components are 444 unknown, or to provide localized representations. 446 o street: "String" (optional). The street address. This MAY be 447 multiple lines; newlines MUST be preserved. 449 o extension: "String" (optional) The extended address, such as an 450 apartment or suite number, or care-of address. 452 o locality: "String" (optional). The city, town, village, post 453 town, or other locality within which the street address may be 454 found. 456 o region: "String" (optional). The province, such as a state, 457 county, or canton within which the locality may be found. 459 o country: "String" (optional). The country name. 461 o postOfficeBox: "String" (optional) The post office box. 463 o postcode: "String" (optional). The postal code, post code, ZIP 464 code or other short code associated with the address by the 465 relevant country's postal system. 467 o countryCode: "String" (optional). The ISO-3166-1 country code. 469 o coordinates: "String" (optional) A [RFC5870] "geo:" URI for the 470 address. 472 o timeZone: "String" (optional) Identifies the time zone this 473 address is located in. This SHOULD be a time zone name registered 474 in the IANA Time Zone Database [1]. Unknown time zone identifiers 475 MAY be ignored by implementations. 477 o isPreferred: Boolean (optional, default: false). Whether this 478 Address is the preferred for its type. This SHOULD only be one 479 per type. 481 2.5. Additional properties 483 2.5.1. anniversaries 485 Type : Anniversary[] (optional). 487 Memorable dates and events for the entity represented by this card. 488 An Anniversary object has the following properties: 490 o type: "String" (mandatory). Specifies the type of the 491 anniversary. This RFC predefines the following types, but 492 implementations MAY use additional values: 494 * "birth": a birth day anniversary 496 * "death": a death day anniversary 498 * "other": an anniversary not covered by any of the known types. 500 o label: "String" (optional). A label describing the value in more 501 detail, especially if the type property has value "other" (but MAY 502 be included with any type). 504 o date: "String" (mandatory). The date of this anniversary, in the 505 form "YYYY-MM-DD" (any part may be all 0s for unknown) or a 506 [RFC3339] timestamp. 508 o place: Address (optional). An address associated with this 509 anniversary, e.g. the place of birth or death. 511 2.5.2. personalInfo 513 Type: PersonalInformation[] (optional). 515 A list of personal information about the entity represented by this 516 card. A PersonalInformation object has the following properties: 518 o type: "String" (mandatory). Specifies the type for this personal 519 information. Allowed values are: 521 * "expertise": a field of expertise or credential 523 * "hobby": a hobby 524 * "interest": an interest 526 * "other": an information not covered by the above categories 528 o value: "String" (mandatory). The actual information. This 529 generally is free-text, but future specifications MAY restrict 530 allowed values depending on the type of this PersonalInformation. 532 o level: "String" (optional) Indicates the level of expertise, or 533 engagement in hobby or interest. Allowed values are: "high", 534 "medium" and "low". 536 2.5.3. notes 538 Type: "LocalizedString[]" (optional). 540 Arbitrary notes about the entity represented by this card. 542 2.5.4. categories 544 Type: "String[Boolean]" (optional). The set of free-text or URI 545 categories that relate to the card. The set is represented as an 546 object, with each key being a category. The value for each key in 547 the object MUST be "true". 549 3. JSGroupCard 551 MIME type: "application/jscontact+json;type=jsgroupcard" 553 A JSGroupCard object represents a group of cards. Its members may be 554 JSCards or JSGroupCards. 556 Both JSGroupCard and JSCard share the same namespace for the "uid" 557 property. All properties for a JSCard are also defined for 558 JSGroupCard, with the exception that the "kind" property MUST be set 559 to "group". 561 3.1. Group properties 563 3.1.1. members 565 Type: "String[Boolean]" (mandatory). The members of this group. 567 The set is represented as an object, with each key being the uid of 568 another JSCard or JSGroupCard. The value for each key in the object 569 MUST be "true". 571 4. Common types 573 4.1. LocalizedString 575 A LocalizedString object has the following properties: 577 o value: "String" (mandatory). The property value. 579 o language: "String" (optional). The [RFC5646] language tag of this 580 value, if any. 582 o localizations: "String[String]" (optional). A map from [RFC5646] 583 language tags to the value localized in that language. 585 4.2. Resource 587 A Resource object has the following properties: 589 o context: "String" (optional) Specifies the context in which to use 590 this resource. Pre-defined values are: 592 * "private": The resource may be used to contact the card holder 593 in a private context. 595 * "work": The resource may be used to contact the card holder in 596 a professional context. 598 * "other": The resource may be used to contact the card holder in 599 some other context. A label property MAY be help to identify 600 its purpose. 602 o type: "String" (optional). Specifies the property-specific 603 variant of the resource. This MUST be taken from the set of 604 allowed types specified in the respective contact method property. 606 o labels: "String[Boolean]" (optional). A set of labels that 607 describe the value in more detail, especially if the type property 608 has value "other" (but MAY be included with any type). The keys 609 in the map define the label, the values MUST be "true". 611 o value: "String" (mandatory). The actual resource value, e.g. an 612 email address or phone number. 614 o mediaType: "String" (optional). Used for properties with URI 615 values. Provides the media type [RFC2046] of the resource 616 identified by the URI. 618 o isPreferred: Boolean (optional, default: false). Whether this 619 resource is the preferred for its type. This SHOULD only be one 620 per type. 622 5. Implementation Status 624 NOTE: Please remove this section and the reference to [RFC7942] prior 625 to publication as an RFC. This section records the status of known 626 implementations of the protocol defined by this specification at the 627 time of posting of this Internet-Draft, and is based on a proposal 628 described in [RFC7942]. The description of implementations in this 629 section is intended to assist the IETF in its decision processes in 630 progressing drafts to RFCs. Please note that the listing of any 631 individual implementation here does not imply endorsement by the 632 IETF. Furthermore, no effort has been spent to verify the 633 information presented here that was supplied by IETF contributors. 634 This is not intended as, and must not be construed to be, a catalog 635 of available implementations or their features. Readers are advised 636 to note that other implementations may exist. According to 637 [RFC7942], "this will allow reviewers and working groups to assign 638 due consideration to documents that have the benefit of running code, 639 which may serve as evidence of valuable experimentation and feedback 640 that have made the implemented protocols more mature. It is up to 641 the individual working groups to use this information as they see 642 fit". 644 5.1. IIT-CNR/Registro.it 646 o Responsible Organization: Institute of Informatics and Telematics 647 of National Research Council (IIT-CNR)/Registro.it 649 o Location: https://rdap.pubtest.nic.it/ [2] 651 o Description: This implementation includes support for RDAP queries 652 using data from the public test environment of .it ccTLD. The 653 RDAP server does not implement any security policy because data 654 returned by this server are only for experimental testing 655 purposes. The RDAP server returns responses including JSCard in 656 place of jCard when queries contain the parameter jscard=1. 658 o Level of Maturity: This is a "proof of concept" research 659 implementation. 661 o Coverage: This implementation includes all of the features 662 described in this specification. 664 o Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it 666 6. IANA Considerations 668 TBD 670 7. Security Considerations 672 TBD 674 8. References 676 8.1. Normative References 678 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 679 Extensions (MIME) Part Two: Media Types", RFC 2046, 680 DOI 10.17487/RFC2046, November 1996, 681 . 683 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 684 Requirement Levels", BCP 14, RFC 2119, 685 DOI 10.17487/RFC2119, March 1997, 686 . 688 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 689 Unique IDentifier (UUID) URN Namespace", RFC 4122, 690 DOI 10.17487/RFC4122, July 2005, 691 . 693 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 694 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 695 September 2009, . 697 [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource 698 Identifier for Geographic Locations ('geo' URI)", 699 RFC 5870, DOI 10.17487/RFC5870, June 2010, 700 . 702 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 703 DOI 10.17487/RFC6350, August 2011, 704 . 706 [RFC6351] Perreault, S., "xCard: vCard XML Representation", 707 RFC 6351, DOI 10.17487/RFC6351, August 2011, 708 . 710 [RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095, 711 DOI 10.17487/RFC7095, January 2014, 712 . 714 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, 715 DOI 10.17487/RFC7493, March 2015, 716 . 718 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 719 Code: The Implementation Status Section", BCP 205, 720 RFC 7942, DOI 10.17487/RFC7942, July 2016, 721 . 723 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 724 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 725 May 2017, . 727 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 728 Interchange Format", STD 90, RFC 8259, 729 DOI 10.17487/RFC8259, December 2017, 730 . 732 8.2. Informative References 734 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 735 A., Peterson, J., Sparks, R., Handley, M., and E. 736 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 737 DOI 10.17487/RFC3261, June 2002, 738 . 740 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 741 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 742 . 744 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", 745 RFC 3966, DOI 10.17487/RFC3966, December 2004, 746 . 748 [RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' 749 URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010, 750 . 752 [RFC6473] Saint-Andre, P., "vCard KIND:application", RFC 6473, 753 DOI 10.17487/RFC6473, December 2011, 754 . 756 [RFC6474] Li, K. and B. Leiba, "vCard Format Extensions: Place of 757 Birth, Place and Date of Death", RFC 6474, 758 DOI 10.17487/RFC6474, December 2011, 759 . 761 [RFC6715] Cauchie, D., Leiba, B., and K. Li, "vCard Format 762 Extensions: Representing vCard Extensions Defined by the 763 Open Mobile Alliance (OMA) Converged Address Book (CAB) 764 Group", RFC 6715, DOI 10.17487/RFC6715, August 2012, 765 . 767 [RFC6869] Salgueiro, G., Clarke, J., and P. Saint-Andre, "vCard 768 KIND:device", RFC 6869, DOI 10.17487/RFC6869, February 769 2013, . 771 [RFC8605] Hollenbeck, S. and R. Carney, "vCard Format Extensions: 772 ICANN Extensions for the Registration Data Access Protocol 773 (RDAP)", RFC 8605, DOI 10.17487/RFC8605, May 2019, 774 . 776 8.3. URIs 778 [1] https://www.iana.org/time-zones 780 [2] https://rdap.pubtest.nic.it/ 782 Authors' Addresses 784 Robert Stepanek 785 FastMail 786 PO Box 234, Collins St West 787 Melbourne, VIC 8007 788 Australia 790 Email: rsto@fastmailteam.com 792 Mario Loffredo 793 IIT-CNR 794 Via Moruzzi,1 795 Pisa, 56124 796 Italy 798 Email: mario.loffredo@iit.cnr.it