--- 1/draft-ietf-jmap-jscontact-vcard-00.txt 2020-10-12 00:13:12.682028735 -0700 +++ 2/draft-ietf-jmap-jscontact-vcard-01.txt 2020-10-12 00:13:12.746030357 -0700 @@ -1,19 +1,19 @@ jmap M. Loffredo Internet-Draft IIT-CNR/Registro.it Intended status: Informational R. Stepanek -Expires: January 14, 2021 FastMail - July 13, 2020 +Expires: April 14, 2021 FastMail + October 11, 2020 JSContact: Converting from and to vCard - draft-ietf-jmap-jscontact-vcard-00 + draft-ietf-jmap-jscontact-vcard-01 Abstract This document provides informational guidance for converting the contact card defined by JSContact specification, namely JSCard, from and to vCard. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -22,21 +22,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on January 14, 2021. + This Internet-Draft will expire on April 14, 2021. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -101,26 +101,28 @@ 2.10.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . 32 2.10.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . 33 2.10.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . 34 2.11. Additional Clarifications about Mapping . . . . . . . . . 35 2.11.1. Media type . . . . . . . . . . . . . . . . . . . . . 35 2.11.2. Timezone . . . . . . . . . . . . . . . . . . . . . . 35 2.12. Extended Properties . . . . . . . . . . . . . . . . . . . 36 2.13. vCard Unmatched Properties . . . . . . . . . . . . . . . 36 2.14. JSCard Required Properties . . . . . . . . . . . . . . . 36 2.15. JSCard Unmatched Properties . . . . . . . . . . . . . . . 36 - 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 - 4. Security Considerations . . . . . . . . . . . . . . . . . . . 37 - 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 - 5.1. Normative References . . . . . . . . . . . . . . . . . . 37 - 5.2. Informative References . . . . . . . . . . . . . . . . . 38 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 + 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 + 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 37 + 4.1. CNR . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 37 + 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 6.1. Normative References . . . . . . . . . . . . . . . . . . 38 + 6.2. Informative References . . . . . . . . . . . . . . . . . 39 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 1. Introduction 1.1. Motivation The JSContact specification [draft-ietf-jmap-jscontact] has been defined to represent contact card information as a more efficient alternative to vCard [RFC6350] and its JSON-based version named jCard [RFC7095]. @@ -249,23 +251,23 @@ with the full name translations in various languages regardless of the presence of the ALTID parameter. Each translation corresponds to a different entry of the "localizations" map (Figure 3). 2.2.2. N and NICKNAME Both the N and NICKNAME elements are converted into equivalent items of the "name" array (Figure 3): o the N components are transformed into related "NameComponent" - objects as reported in Table 1. Name components SHOULD be ordered - such that their values joined by whitespace produce a valid full - name of this entity; + objects as presented in Table 1. Name components SHOULD be + ordered such that their values joined by whitespace produce a + valid full name of this entity; o Each NICKNAME element is mapped onto an object whose "type" member is set to "nickname" +--------------------+--------------+ | N component | "type" value | +--------------------+--------------+ | Honorific Prefixes | prefix | | Given Names | personal | | Family Names | surname | @@ -412,21 +414,21 @@ TBD 2.3. Delivery Addressing Properties 2.3.1. ADR An ADR element is represented as an "Address" object in the "addresses" array (Figure 6). The ADR components are transformed into the "Address" members as - reported in Table 2. + presented in Table 2. +------------------+----------------+ | ADR component | Address member | +------------------+----------------+ | p.o. box | postOfficeBox | | extended address | extension | | street address | street | | locality | locality | | region | region | | postal code | postcode | @@ -1475,52 +1477,83 @@ If an extended property is a resource, JSCard already allows to represent it by setting the "type" member to "other" and specifying a value for the "labels" map. Any other property supporting a custom feature MAY be added and its name MUST be prefixed with a specific domain name to avoid conflict, e.g. "example.com/customprop". 2.13. vCard Unmatched Properties - Any vCard property or parameter that doesn't have a direct - counterpart in JSContact is treated as an extended property. The - following mapping rules MUST be applied: - - o an unmatched property is converted into an extended property whose - name is prefixed by "ietf.org/rfc6350/" - - o an unmatched parameter is converted into an extended property - whose name is prefixed by "ietf.org/rfc6350//" + Any vCard property that doesn't have a direct counterpart in + JSContact is treated as an extended property whose name is prefixed + by "ietf.org/rfc6350/". - In both cases, the resulting names MUST be in lowercase. + The resulting name MUST be in lowercase. 2.14. JSCard Required Properties While converting a vCard into a JSCard, only the topmost "uid" member is required. 2.15. JSCard Unmatched Properties The "preferredContactMethod" member doesn't match any vCard element. 3. IANA Considerations This document has no actions for IANA. -4. Security Considerations +4. Implementation Status - This document doesn't report any security consideration. + NOTE: Please remove this section and the reference to RFC 7942 prior + to publication as an RFC. -5. References + This section records the status of known implementations of the + protocol defined by this specification at the time of posting of this + Internet-Draft, and is based on a proposal described in [RFC7942]. + The description of implementations in this section is intended to + assist the IETF in its decision processes in progressing drafts to + RFCs. Please note that the listing of any individual implementation + here does not imply endorsement by the IETF. Furthermore, no effort + has been spent to verify the information presented here that was + supplied by IETF contributors. This is not intended as, and must not + be construed to be, a catalog of available implementations or their + features. Readers are advised to note that other implementations may + exist. -5.1. Normative References + According to RFC 7942, "this will allow reviewers and working groups + to assign due consideration to documents that have the benefit of + running code, which may serve as evidence of valuable experimentation + and feedback that have made the implemented protocols more mature. + It is up to the individual working groups to use this information as + they see fit". + +4.1. CNR + + Responsible Organization: National Research Council (CNR) of Italy + Location: https://github.com/consiglionazionaledellericerche/ + jscontact-tools + Description: This implementation includes tools for JSContact + creation, validation, serialization/deserialization and conversion + from vCard, xCard and jCard. + Level of Maturity: This is an "alpha" test implementation. + Coverage: This implementation includes all of the features + described in this specification. + Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it + +5. Security Considerations + + This document doesn't present any security consideration. + +6. References +6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, DOI 10.17487/RFC6350, August 2011, . @@ -1540,26 +1573,31 @@ . [RFC6869] Salgueiro, G., Clarke, J., and P. Saint-Andre, "vCard KIND:device", RFC 6869, DOI 10.17487/RFC6869, February 2013, . [RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095, DOI 10.17487/RFC7095, January 2014, . + [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running + Code: The Implementation Status Section", BCP 205, + RFC 7942, DOI 10.17487/RFC7942, July 2016, + . + [RFC8605] Hollenbeck, S. and R. Carney, "vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP)", RFC 8605, DOI 10.17487/RFC8605, May 2019, . -5.2. Informative References +6.2. Informative References [draft-ietf-jmap-jscontact] "JSContact: A JSON representation of contact data", . [time-zones] "Time Zone Database", . [uri-schemes]