A new Request for Comments is now available in online RFC libraries.

        RFC 9982

        Title:      JSContact Version 2.0: A JSON Representation of Contact Data
        Author:     R. Stepanek
        Status:     Proposed Standard
        Stream:     IETF
        Date:       May 2026
        Mailbox:    [email protected]
        Pages:      7
        Updates:    RFC 9555

        I-D Tag:    draft-ietf-calext-jscontact-uid-08.txt

        URL:        https://www.rfc-editor.org/info/rfc9982

        DOI:        10.17487/RFC9982

This document defines version "2.0" of JSContact. It defines the uid property 
of a Card object to be optional, rather than mandatory, as defined previously 
in version "1.0". All other definitions of JSContact version "1.0" remain as 
defined in RFC 9553. This document updates RFC 9555 by redefining how to 
convert 
the now optional uid property from and to vCard. It also registers the vCard 
JSCOMPS 
parameter at IANA, which was defined but not registered in RFC 9555.

This document is a product of the Calendaring Extensions Working Group of the 
IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to