The IETF has published RFC 10050, which establishes a new IANA registry for JSContact profiles. This standard enables protocol designers to define specific subsets of JSContact elements, improving interoperability for address book and directory services.
The publication of RFC 10050 provides a technical framework for streaming platforms and enterprise directory services to exchange contact data more efficiently by using specific profiles rather than the full JSContact semantics. By standardizing these subsets, the IETF reduces the need for proprietary contact formats, which simplifies cross-protocol data migration and library implementation. In the broader ecosystem, this move strengthens the JSON-based alternative to vCard, aligning contact management with modern web standards used in communication infrastructure. Watch for the first official profile registrations in the IANA registry to see which specific protocols, such as JMAP, lead the adoption of these restricted data subsets.
JSContact is part of a broader IETF effort to modernize contact data formats, with JMAP serving as the primary protocol expected to consume these profiles. The JMAP protocol itself, standardized in RFC 8620 and RFC 8621, was designed by Fastmail engineers as a replacement for IMAP and has been the main driver of JSContact adoption. Fastmail announced full JMAP support for its mail platform in 2025, making it one of the first production deployments of the protocol stack that JSContact profiles are designed to serve. The IETF CALCONNECT and JMAP working groups have been iterating on JSContact since 2019, with RFC 9554 defining the core JSContact data model and RFC 9555 specifying the conversion rules from vCard. RFC 10050 completes this suite by providing the registry mechanism that protocol implementers need to define constrained subsets for specific use cases.
The business case for JSContact profiles centers on reducing implementation complexity for directory service vendors and communication platform providers. The IETF JMAP working group charter explicitly identifies contact management as a core use case alongside mail and calendar access, and the profiles registry gives protocol designers a formal path to register interoperable subsets without requiring full JSContact compliance. Fastmail, which originated much of the JMAP and JSContact specification work through engineers including Robert Stepanek, has positioned the protocol as a foundation for third-party client developers building against modern mail and directory APIs. IIT-CNR researcher Mario Loffredo has contributed to multiple JSContact-related RFCs and presented implementation experience at IETF meetings, signaling academic and research-sector interest in the standard beyond commercial email providers.
From a technical standpoint, JSContact profiles compete with existing vCard-based approaches that dominate enterprise directory services today. RFC 9554, published in May 2024, defines the JSContact data model as a JSON-based alternative to vCard 4.0, and the profiles registry in RFC 10050 addresses a gap that vCard never solved: the lack of a formal mechanism for protocol-specific constrained subsets. In the streaming and communications infrastructure space, platforms that manage user directories, presence lists, or collaborative contact sharing could adopt JSContact profiles to reduce payload sizes and simplify client parsing. The IANA registry for JSContact profiles is now live and accepting registrations, meaning the first protocol-specific profiles could appear within months as JMAP client and server implementations mature.
The IETF has published RFC 10050, which establishes an IANA registry for JSContact profiles. This standard allows developers to define restricted subsets of contact data, replacing proprietary formats. It matters because it simplifies cross-protocol data migration and strengthens JSON-based contact management for modern web and enterprise directory services.
RFC 10050 creates a formal IANA registry for named and versioned subsets of JSContact elements, allowing protocol designers to define restricted property types and values for contact exchange.
JSContact is a JSON-based alternative to vCard 4.0. RFC 10050 addresses a gap in vCard by providing a formal mechanism for protocol-specific constrained subsets.
JSContact profiles are designed to support protocols like JMAP for Contacts and CardDAV by defining mandatory versus optional property contexts.
The IETF CALCONNECT and JMAP working groups have been iterating on JSContact since 2019. Key contributors include Fastmail engineers like Robert Stepanek and researcher Mario Loffredo.
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source
