RFC 7953 on Calendar Availability

rfc-editor@rfc-editor.org Wed, 17 August 2016 21:38 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF9312D7C4; Wed, 17 Aug 2016 14:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.869
X-Spam-Level:
X-Spam-Status: No, score=-103.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3CFxotzqcASM; Wed, 17 Aug 2016 14:38:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D25312D7D0; Wed, 17 Aug 2016 14:38:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 96870B80C0C; Wed, 17 Aug 2016 14:38:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7953 on Calendar Availability
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160817213828.96870B80C0C@rfc-editor.org>
Date: Wed, 17 Aug 2016 14:38:28 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FV9_5mwkCh_0ZViF4x3GnTrG1PU>
Cc: drafts-update-ref@iana.org, calsify@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 21:38:45 -0000

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

        
        RFC 7953

        Title:      Calendar Availability 
        Author:     C. Daboo, M. Douglass
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2016
        Mailbox:    cyrus@daboo.name, 
                    mdouglass@sphericalcowgroup.com
        Pages:      24
        Characters: 47971
        Updates:    RFC 4791, RFC 5545, RFC 6638

        I-D Tag:    draft-ietf-calext-availability-04.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7953

This document specifies a new iCalendar (RFC 5545) component that
allows the publication of available and unavailable time periods
associated with a calendar user.  This component can be used in
standard iCalendar free-busy lookups, including the iCalendar
Transport-independent Interoperability Protocol (iTIP; RFC 5546)
free-busy requests, to generate repeating blocks of available or busy
time with exceptions as needed.

This document also defines extensions to the Calendaring Extensions
to WebDAV (CalDAV) calendar access protocol (RFC 4791) and the
associated scheduling protocol (RFC 6638) to specify how this new
calendar component can be used when evaluating free-busy time.

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