Re: [ietf-calsify] [Editorial Errata Reported] RFC5545 (2516)

It looks like we need to set the status of this one to "Verified". Agreed?

On 9/13/10 2:57 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5545,
> "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5545&eid=2516
> 
> --------------------------------------
> Type: Editorial
> Reported by: David Wright <clarence <at> yrthwyndandfyre.com>
> 
> Section: 3.8.4.1
> 
> Original Text
> -------------
> Example:  The following is an example of this property's use when
>       another calendar user is acting on behalf of the "Attendee":
> 
>        ATTENDEE;SENT-BY=mailto:jan_doe <at> example.com;CN=John Smith:
>         mailto:jsmith <at> example.com
> 
> 
> Corrected Text
> --------------
> Example:  The following is an example of this property's use when
>       another calendar user is acting on behalf of the "Attendee":
> 

Re: [ietf-calsify] [Editorial Errata Reported] RFC5545 (2516)

  The ADs should approve this erratum.

Cheers,
Bernard

Le 2010-09-13 16:57, RFC Errata System a écrit :
> The following errata report has been submitted for RFC5545,
> "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5545&eid=2516
>
> --------------------------------------
> Type: Editorial
> Reported by: David Wright<clarence <at> yrthwyndandfyre.com>
>
> Section: 3.8.4.1
>
> Original Text
> -------------
> Example:  The following is an example of this property's use when
>        another calendar user is acting on behalf of the "Attendee":
>
>         ATTENDEE;SENT-BY=mailto:jan_doe <at> example.com;CN=John Smith:
>          mailto:jsmith <at> example.com
>
>
> Corrected Text
> --------------

[ietf-calsify] I-D ACTION:draft-ietf-calsify-rfc2447bis-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Calendaring and Scheduling Standards Simplification Working Group of the IETF.

	Title		: iCalendar Message-Based Interoperability Protocol (iMIP)
	Author(s)	: A. Melnikov
	Filename	: draft-ietf-calsify-rfc2447bis-11.txt
	Pages		: 23
	Date		: 2010-9-14
	
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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-calsify-rfc2447bis-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________

Re: [ietf-calsify] I-D ACTION:draft-ietf-calsify-rfc2447bis-11.txt

Internet-Drafts <at> ietf.org wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Calendaring and Scheduling Standards Simplification Working Group of the IETF.
>
>	Title		: iCalendar Message-Based Interoperability Protocol (iMIP)
>	Author(s)	: A. Melnikov
>	Filename	: draft-ietf-calsify-rfc2447bis-11.txt
>	Pages		: 23
>	Date		: 2010-9-14
>	
>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.
>  
>
This version cleans up/fixes some security related text and adds some 
additional references in various places. The major change is to require 
S/MIME for calendar object integrity and data confidentiality.

[ietf-calsify] matching up CUTYPE to vCard KIND

Hi,
   In trying to build a schema for representing resources we decided to re-use the vCard KIND property to
specify the type of the resource. In iCal, one would add a resource to an event by inviting it as an Attendee.
One can set the CUTYPE parameter to define what type of attendee it is. iCal defines INDIVIDUAL, GROUP,
RESOURCE, ROOM & UNKNOWN. KIND in vCard takes the values individual, group, org, location & thing. While
individual and group map exactly, the rest don't. Is it fair to say RESOURCE could map to thing? ROOM and
location are related but not exactly the same. Not sure if the org vCard KIND value makes sense for iCal CUTYPE.
  Can we try to reconcile the two values? Wanted to get the opinion of this group before asking the vCard list.

Thanks,
Ciny

[ietf-calsify] Protocol Action: 'iCalendar Message-Based Interoperability Protocol (iMIP)' to Proposed Standard

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

Re: [ietf-calsify] Protocol Action: 'iCalendar Message-Based Interoperability Protocol (iMIP)' to Proposed Standard

 Congratulations to Alexey for this milestone. 

With this milestone completed, it is anticipated that the calsify group
will close.  Discussion on futures should be held on the calsify mailing
list (ietf-calsify <at> osafoundation.org).

Regards,

Eliot

On 9/15/10 9:30 PM, The IESG wrote:
> 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

Re: [ietf-calsify] [Editorial Errata Reported] RFC5545 (2527)

Bernard, this erratum looks correct to me. Can you please confirm?

Thanks!

Peter

On 9/20/10 11:35 AM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5545,
> "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5545&eid=2527
> 
> --------------------------------------
> Type: Editorial
> Reported by: David Wright <clarence <at> yrthwyndandfyre.com>
> 
> Section: 3.8.5.2
> 
> Original Text
> -------------
>   Example:  The following are examples of this property:
> 
>        RDATE:19970714T123000Z
>        RDATE;TZID=America/New_York:19970714T083000
> 
>        RDATE;VALUE=PERIOD:19960403T020000Z/19960403T040000Z,
>         19960404T010000Z/PT3H
> 

Re: [ietf-calsify] [Editorial Errata Reported] RFC5545 (2527)

  ADs should approve this erratum.

Thanks,
Bernard

On 9/20/2010 1:35 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5545,
> "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5545&eid=2527
>
> --------------------------------------
> Type: Editorial
> Reported by: David Wright<clarence <at> yrthwyndandfyre.com>
>
> Section: 3.8.5.2
>
> Original Text
> -------------
>    Example:  The following are examples of this property:
>
>         RDATE:19970714T123000Z
>         RDATE;TZID=America/New_York:19970714T083000
>
>         RDATE;VALUE=PERIOD:19960403T020000Z/19960403T040000Z,
>          19960404T010000Z/PT3H
>
>         RDATE;VALUE=DATE:19970101,19970120,19970217,19970421