OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Fw: Protocol Action: 'iCalendar Transport-Independent InteroperabilityProtocol (iTIP)' to Proposed Standard


Given the iCalendar discussion today.

Carl Reed
OGC

----- Original Message ----- 
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: "calsify mailing list" <ietf-calsify@osafoundation.org>; "Internet 
Architecture Board" <iab@iab.org>; "calsify chair" 
<calsify-chairs@tools.ietf.org>; "RFC Editor" <rfc-editor@rfc-editor.org>
Sent: Thursday, October 15, 2009 2:44 PM
Subject: Protocol Action: 'iCalendar Transport-Independent 
InteroperabilityProtocol (iTIP)' to Proposed Standard


> The IESG has approved the following document:
>
> - 'iCalendar Transport-Independent Interoperability Protocol (iTIP) '
>   <draft-ietf-calsify-2446bis-10.txt> as a Proposed Standard
>
>
> This document is the product of the Calendaring and Scheduling Standards 
> Simplification Working Group.
>
> The IESG contact persons are Lisa Dusseault and Alexey Melnikov.
>
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-calsify-2446bis-10.txt
>
> Technical Summary
>
> This memo updates RFC 2446, iTIP.  While no new protocol elements
> are introduced, a number are deprecated, while others are clarified.
> The examples are also improved.
>
> Working Group Summary
>
> There is rough consensus to move the document forward, and it wasn't
> all that rough.  We had one minor issue relating to a constraint table,
> as to readability, but that is editorial preference.
>
> Document Quality
>
> There are existing implementations, and a number of vendors plan to
> implement the specification.  We gratefully acknowledge Nigel Swinson for
> his review of the constraint table.
>
> RFC Editor Note
>
> adding to the beginning of Section 7.3:
>
>   New "REQUEST-STATUS" values can be registered using the process
>   described in Section 8.2.1 of [RFC5545].
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]