Greetings, This announcement is being forwarded, as the announcements originally sent on 19 September 2026 appear in the mail archive [1][2] but may not have reached individuals. The issue has since been resolved.
[1] https://mailarchive.ietf.org/arch/msg/ietf-announce/HxF9sD6eYjLktGzyG7nB3rHLbuo/ [2] https://mailarchive.ietf.org/arch/msg/rfc-dist/02qXgi6oW86kDm8-yj7JMwmfKBw/ Thank you, RFC Editor Team Begin forwarded message: From: [email protected] Subject: RFC 10050 on Protocol-Specific Profiles for JSContact Date: September 19, 2026 at 10:34:42 AM PDT To: [email protected], [email protected] Cc: [email protected], [email protected], [email protected] A new Request for Comments is now available in online RFC libraries. RFC 10050 Title: Protocol-Specific Profiles for JSContact Author: R. Stepanek, M. Loffredo Status: Proposed Standard Stream: IETF Date: September 2026 Mailbox: [email protected], [email protected] Pages: 16 I-D Tag: draft-ietf-calext-jscontact-profiles-14 URL: https://www.rfc-editor.org/info/rfc10050 DOI: 10.17487/RFC10050 This document defines the "JSContact Profiles" registry, an IANA registry for named subsets of JSContact elements. The document aims to facilitate using JSContact in the context of contact data exchange protocols or other use cases in which supporting all JSContact semantics might be inappropriate. 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]
