Protocol Action: 'iCalendar Message-Based Interoperability Protocol (iMIP)' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 15 September 2010 19:30 UTC

Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 4BC5C3A6A9A; Wed, 15 Sep 2010 12:30:36 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'iCalendar Message-Based Interoperability Protocol (iMIP)' to Proposed Standard
Message-Id: <20100915193043.4BC5C3A6A9A@core3.amsl.com>
Date: Wed, 15 Sep 2010 12:30:36 -0700 (PDT)
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>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 15 Sep 2010 19:30:44 -0000

The IESG has approved the following document:
- 'iCalendar Message-Based Interoperability Protocol (iMIP)'
  <draft-ietf-calsify-rfc2447bis-11.txt> as a Proposed Standard

This document is the product of the Calendaring and Scheduling Standards
Simplification Working Group.

The IESG contact persons are Peter Saint-Andre and Alexey Melnikov.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-calsify-rfc2447bis/

Technical Summary

   This document, iCalendar Message-Based Interoperability Protocol
   (iMIP), specifies a binding from the iCalendar Transport-independent
   Interoperability Protocol (iTIP) to Internet email-based transports.
   Calendaring entries defined by the iCalendar Object Model (iCalendar)
   are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC
   2046, RFC 2047 and RFC 2049), and then transported over SMTP.  If
   approved, this document will obsolete RFC 2447.

Working Group Summary

   This document is a product of the CALSIFY WG.  It received reviews by
   several WG participants in prior to and during Working Group Last Call,
   with rough consensus that the changes from RFC 2447 are appropriate.

Document Quality

   The CALSIFY WG and the responsible area director have deemed the
   document to be of good quality.

Personnel

   The Working Group chair is Eliot Lear. The responsible area director is 
   Peter Saint-Andre.

RFC Editor Note

Add the following text to the document header:

  Obsoletes: RFC 2447

In Section 1:

OLD:
  This binding document provides the transport specific information
  necessary to convey iCalendar Transport-independent Interoperability
  Protocol (iTIP) [iTIP] over Internet email (using MIME) as defined in
  [RFC-5322] and [RFC-2045].

NEW:

  This document provides the transport specific information ("binding")
  necessary to convey iCalendar Transport-independent Interoperability
  Protocol (iTIP) [iTIP] over Internet email (using MIME) as defined in
  [RFC-5322] and [RFC-2045].