Protocol Action: 'Calendar Availability' to Proposed Standard (draft-ietf-calext-availability-04.txt)

The IESG <> Mon, 11 July 2016 15:05 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id EC82E12D1DE; Mon, 11 Jul 2016 08:05:26 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Protocol Action: 'Calendar Availability' to Proposed Standard (draft-ietf-calext-availability-04.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 11 Jul 2016 08:05:26 -0700
Archived-At: <>
Cc:, Daniel Migault <>,,,,, The IESG <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 11 Jul 2016 15:05:27 -0000

The IESG has approved the following document:
- 'Calendar Availability'
  (draft-ietf-calext-availability-04.txt) as Proposed Standard

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

The IESG contact persons are Alexey Melnikov, Ben Campbell and Alissa

A URL of this Internet Draft is:

Technical Summary

   This document specifies a new iCalendar calendar 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 iTIP free-busy
   requests, to generate repeating blocks of available or busy time with
   exceptions as needed.

   This document also defines extensions to CalDAV calendar-access and
   calendar-auto-schedule which specify how this new calendar component
   can be used when doing free-busy time evaluation in CalDAV.

Working Group Summary

   The document was approved by 7 people to be a working group document. Two people commented the document while implementing it. The document was approved by 2 non-authors during the WGLC. No one objected. Actually one asked for clarifications and then approved the current version.

Document Quality

   The document is well written. From Mailing list discussions two people have implemented these components. One implementers asked clarifications, and the document reflects these discussions.


   Daniel Migault is the document shepherd and Alexey Melnikov is the Responsible AD.