[calsify] RFC 9253 on Support for iCalendar Relationships

rfc-editor@rfc-editor.org Thu, 18 August 2022 23:21 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC4EC14CE47; Thu, 18 Aug 2022 16:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9sxGx-pO_l3R; Thu, 18 Aug 2022 16:21:44 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F844C152577; Thu, 18 Aug 2022 16:21:44 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id F03361527E0; Thu, 18 Aug 2022 16:21:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, calsify@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220818232143.F03361527E0@rfcpa.amsl.com>
Date: Thu, 18 Aug 2022 16:21:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/JL_3zBqwyYUBLUDuOgRIu-w0r94>
Subject: [calsify] RFC 9253 on Support for iCalendar Relationships
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Calendaring and Scheduling Standards Simplification <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2022 23:21:48 -0000

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

        
        RFC 9253

        Title:      Support for iCalendar Relationships 
        Author:     M. Douglass
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2022
        Mailbox:    mdouglass@bedework.com
        Pages:      19
        Updates:    RFC 5545

        I-D Tag:    draft-ietf-calext-ical-relations-11.txt

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

        DOI:        10.17487/RFC9253

This specification updates the iCalendar RELATED-TO property defined
in RFC 5545 by adding new relation types and introduces new iCalendar
properties (LINK, CONCEPT, and REFID) to allow better linking and
grouping of iCalendar components and related data.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC