[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emix] Fw: Protocol Action: 'iCalendar Transport-Independent InteroperabilityProtocol (iTIP)' to Proposed Standard
To the extent that anything as large and anarchic as the IETF has formal committees, CalConnect *is* calsify. Calconnect is the trade consortium, calsify is the very much larger IETF mailing list that votes. (Note that the above is a politically incorrect statement and ignores the freewheeling nature of the IETF and the many contributions from the larger Calsify...) The RFCs in this area, 2245, 2446, 2447 define the critical Calendar / Schedule / Interval / Interoperation standards. All of them are somewhat long in the tooth. 2445 (the core ICalendar) got updated to 5545 in August. 5545 is the largest semantic set of the three. ITIP, 2446, also needed updating, in part to match the new 5545. If you look at the authors, you will recognize the same names. I expect (no private knowledge) that 2447 will be updated soon as well. This is slow and careful work because advancing a standard supported by so many vendors without breaking compatibility is hard work. People interested in the progress of the standard XML serialization might be interested in: http://xcal.cloudapp.net/ The Calendar and Scheduling Consortium has a detailed and far-reaching work-plan, not all of which is subject to the highly visible, highly politicized smart grid process - and is not part of PAP04. The richness and depth of that work is precisely why it is the appropriate foundation for the SG related work. tc "If something is not worth doing, it`s not worth doing well" - Peter Drucker Toby Considine TC9, Inc Chair, OASIS oBIX Technical Committee OASIS Technical Advisory Board Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.oasis-open.org blog: www.NewDaedalus.com -----Original Message----- From: Carl Reed [mailto:creed@opengeospatial.org] Sent: Thursday, October 15, 2009 5:03 PM To: emix@lists.oasis-open.org Subject: [emix] 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 --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]