Subject: [Ietf-calsify] Draft agenda for IETF66

From: aki.niemi at nokia.com (Aki Niemi)
Date: Fri Jun 30 03:37:14 2006

IETF66 Agenda
CALSIFY WG session
Wednesday, July 12, 2006
09:00 - 11:30

1. Agenda bash 			(Aki Niemi) 		5min

2. Rechartering update 		(Aki Niemi) 		10min

3. RFC2445bis issues 		(Bernard Desruisseaux)  60min	
   draft-ietf-calsify-rfc2445bis-01.txt

4. RFC2446bis issues		(Cyrus Daboo)		45min
   draft-ietf-calsify-2446bis-02.txt

5. RFC2447bis issues		(Alexey Melnikov)	20min
   draft-ietf-calsify-rfc2447bis-02.txt

6. General discussion		(Aki Niemi)		10min

7. AOB if time permits

Close at 11:30

Date: Fri, 30 Jun 2006 13:36:30 +0300
From: Aki Niemi <[email-masked]>
To: Calsify <[email-masked]>
Subject: [Ietf-calsify] Draft agenda for IETF66

IETF66 Agenda
CALSIFY WG session
Wednesday, July 12, 2006
09:00 - 11:30

1. Agenda bash 			(Aki Niemi) 		5min

2. Rechartering update 		(Aki Niemi) 		10min

3. RFC2445bis issues 		(Bernard Desruisseaux)  60min	
   draft-ietf-calsify-rfc2445bis-01.txt

4. RFC2446bis issues		(Cyrus Daboo)		45min
   draft-ietf-calsify-2446bis-02.txt

5. RFC2447bis issues		(Alexey Melnikov)	20min
   draft-ietf-calsify-rfc2447bis-02.txt

6. General discussion		(Aki Niemi)		10min

7. AOB if time permits

Close at 11:30

Date: Thu, 29 Jun 2006 15:31:18 -0400
From: Bernard Desruisseaux <[email-masked]>
To: Calsify WG <[email-masked]>
Subject: [Ietf-calsify] draft-ietf-calsify-rfc2445bis-01.txt

Folks,

I've submitted draft -01 of rfc2445bis last week.
While it has not been announced yet, it is already
available online:

http://www.ietf.org/internet-drafts/draft-ietf-calsify-rfc2445bis-01.txt

I also uploaded an HTML version that tracks all the
changes I did to the draft on the IETF Tools web site:

http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/draft-ietf-calsify-rfc2445bis-01.html

Cheers,
Bernard

To: [email-masked]
From: [email-masked]
Date: Thu, 29 Jun 2006 02:50:01 -0400
Cc: [email-masked]
Subject: [Ietf-calsify] I-D ACTION:draft-ietf-calsify-2446bis-02.txt 

--NextPart

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 Transport-Independent Interoperability Protocol (iTIP)
	Author(s)	: C. Daboo
	Filename	: draft-ietf-calsify-2446bis-02.txt
	Pages		: 122
	Date		: 2006-6-28
	
This document specifies a protocol using the iCalendar object
   specification to provide scheduling interoperability between
   different calendar systems.  This is done without reference to a
   specific transport protocol so as to allow multiple methods of
   communication between systems.  Subsequent documents will define
   profiles of this protocol using specific interoperable methods of
   communications between systems.

   iTIP complements the iCalendar object specification by adding
   semantics for group scheduling methods commonly available in current
   calendar systems.  These scheduling methods permit two or more
   calendar systems to perform transactions such as publish, schedule,
   reschedule, respond to scheduling requests, negotiation of changes or
   cancel.

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

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-calsify-2446bis-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-calsify-2446bis-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID: <[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsify-2446bis-02.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-calsify-2446bis-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <[email-masked]>

--OtherAccess--

--NextPart--

Date: Thu, 29 Jun 2006 08:46:17 +0200
From: Eliot Lear <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: [Ietf-calsify] current open issues

This is a multi-part message in MIME format.
--------------040309040108000402050400
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dear all,

Here is a list of all of the current open issues.  Now is the time to
get other issues out on the table so we can discuss them at the IETF
meeting in Montreal.  You can find this list at
http://www.ofcourseimright.com/cgi-bin/roundup/calsify.  All authors
have submitted updated versions of their drafts for discussion at IETF.

Eliot

ID 	Activity 	Title 	Status 	Creator 	Assigned To
(no priority set)
16 	2 weeks ago 	when BY extends past last occurrence
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue16>
unread 	lear 	 
bug
10 	6 days ago 	Reinhold Kainhofer: end date not inclusive
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue10>
unread 	lear 	bernard.desruisseaux
8 	6 days ago 	Reinhold Kainhofer: Deprecate P1D or P24H?
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue8>
chatting 	lear 	bernard.desruisseaux
14 	2 weeks ago 	Reinhold Kainhofer: meaning of DTSTART/DTEND with
recurrence rules
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue14>
unread 	lear 	bernard.desruisseaux
13 	2 weeks ago 	Reinhold Kainhofer: confusion in DTSTART text about "if
specified" and BY rules
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue13>
unread 	lear 	bernard.desruisseaux
12 	2 weeks ago 	Reinhold Kainhofer: VTIMEZONE error in RFC 2445?
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue12>
unread 	lear 	bernard.desruisseaux
9 	2 weeks ago 	Reinhold Kainhofer: Recurring Events: Start/End Time
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue9>
unread 	lear 	bernard.desruisseaux
7 	2 weeks ago 	Andrew N. Dowden: rfc 2445 - typo correction(s)
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue7>
unread 	lear 	bernard.desruisseaux
6 	2 weeks ago 	"Corrections" from Oliver Block
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue6>
unread 	lear 	bernard.desruisseaux
5 	4 weeks ago 	proposed changes to RRULE / EXDATE
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue5>
unread 	lear 	bernard.desruisseaux
4 	4 weeks ago 	Example error
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue4>
unread 	lear 	bernard.desruisseaux
3 	4 weeks ago 	bunch of other typos
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue3>
unread 	lear 	bernard.desruisseaux
2 	4 weeks ago 	typo in VTODO
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue2>
unread 	lear 	bernard.desruisseaux
1 	4 weeks ago 	Do we relax or clarify the line length limit?
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue1>
unread 	lear 	bernard.desruisseaux
feature
11 	2 weeks ago 	Reinhold Kainhofer: additional examples, VTIMEZONEs,
RRULEs
<http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue11>
unread 	lear 	bernard.desruisseaux

--------------040309040108000402050400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear all,<br>
<br>
Here is a list of all of the current open issues.&nbsp; Now is the time to
get other issues out on the table so we can discuss them at the IETF
meeting in Montreal.&nbsp; You can find this list at
<a class="moz-txt-link-freetext" href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify">http://www.ofcourseimright.com/cgi-bin/roundup/calsify</a>.&nbsp; All authors
have submitted updated versions of their drafts for discussion at IETF.<br>
<br>
Eliot<br>
<br>
<table class="list">
  <tbody>
    <tr>
      <th>ID</th>
      <th>Activity</th>
      <th>Title</th>
      <th>Status</th>
      <th>Creator</th>
      <th>Assigned&nbsp;To</th>
    </tr>
    <tr>
      <th class="group" colspan="6">(no priority set)</th>
    </tr>
    <tr>
      <td>16</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue16">when
BY extends past last occurrence</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>&nbsp;</td>
    </tr>
    <tr>
      <th class="group" colspan="6">bug</th>
    </tr>
    <tr>
      <td>10</td>
      <td class="date">6 days ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue10">Reinhold
Kainhofer: end date not inclusive</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>8</td>
      <td class="date">6 days ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue8">Reinhold
Kainhofer: Deprecate P1D or P24H?</a> </td>
      <td>chatting</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>14</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue14">Reinhold
Kainhofer: meaning of DTSTART/DTEND with recurrence rules</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>13</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue13">Reinhold
Kainhofer: confusion in DTSTART text about "if specified" and BY rules</a>
      </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>12</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue12">Reinhold
Kainhofer: VTIMEZONE error in RFC 2445?</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>9</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue9">Reinhold
Kainhofer: Recurring Events: Start/End Time</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>7</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue7">Andrew
N. Dowden: rfc 2445 - typo correction(s)</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>6</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue6">"Corrections"
from Oliver Block</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>5</td>
      <td class="date">4 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue5">proposed
changes to RRULE / EXDATE</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>4</td>
      <td class="date">4 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue4">Example
error</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>3</td>
      <td class="date">4 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue3">bunch
of other typos</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>2</td>
      <td class="date">4 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue2">typo
in VTODO</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <td>1</td>
      <td class="date">4 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue1">Do
we relax or clarify the line length limit?</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
    <tr>
      <th class="group" colspan="6">feature</th>
    </tr>
    <tr>
      <td>11</td>
      <td class="date">2 weeks ago</td>
      <td> <a
 href="http://www.ofcourseimright.com/cgi-bin/roundup/calsify/issue11">Reinhold
Kainhofer: additional examples, VTIMEZONEs, RRULEs</a> </td>
      <td>unread</td>
      <td>lear</td>
      <td>bernard.desruisseaux</td>
    </tr>
  </tbody>
</table>
<br>
</body>
</html>

--------------040309040108000402050400--

Date: Wed, 28 Jun 2006 11:56:20 +0200
From: Eliot Lear <[email-masked]>
To: Caleb Richardson <[email-masked]>
Subject: Re: [Ietf-calsify] Time Zone Rule Changeover
Cc: [email-masked]

[Chair hat off...]

Caleb,

You'll notice that nobody has answered your question, and I will not
either.  When an implementation fails to conform a standard it is either
because the standard is difficult to implement or because the
implementor just didn't do a good enough job.  Now is the time to decide
which is true.  There is an issue tracker and an upcoming meeting of the
Calsify working group.  Now is the time to raise and discuss these sorts
of questions.

Let me say that anyone who wants a change in the status quo should in
general send text.  Lacking that it's very difficult to argue pros and
cons on each side.

Eliot

Caleb Richardson wrote:
> This question concerns the switch from standard time to daylight
> savings time in the United States that will occur on March 11, 2007.
>
> From what I understand most versions of Outlook (and some other CUAs)
> can only process VTIMEZONE observances with at most one RRULE
> property. This has led most Olson database converters to discard all
> historical data and only use the most recent recurrence rule for each
> observance (if there are any).
>
> The switchover on March 11, 2007 will be the first that uses a new
> time zone recurrence rule standardized by the Energy Policy Act of
> 2005. The previous rule would have required a switchover on April 1,
> 2007.
>
> Which recurrence rule should I use?
>
> If I use the old rule then recurring events that are still happening
> next spring will be 1 hour off for that window and for a similar
> window every year.
>
> If I use the new rule then my events will be 1 hour off during a
> similar window this fall.
>
> Has anyone come up with a solution to this problem? I realize that
> many CUAs (including mine) will look at the TZID parameter and try to
> use their own strict time zone definitions before parsing the included
> one, but I feel that this is a serious problem regardless.
>
> Thanks,
>
> Caleb Richardson
>
> This VTIMEZONE definition uses the new recurrence rule:
>
> BEGIN:VTIMEZONE
> TZID:America/Los_Angeles
> X-LIC-LOCATION:America/Los_Angeles
> BEGIN:STANDARD
> TZOFFSETFROM:-0700
> TZOFFSETTO:-0800
> TZNAME:EST
> DTSTART:19701101T020000
> RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
> END:STANDARD
> BEGIN:DAYLIGHT
> TZOFFSETFROM:-0800
> TZOFFSETTO:-0700
> TZNAME:EDT
> DTSTART:19700308T020000
> RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
> END:DAYLIGHT
> END:VTIMEZONE
>
> This VTIMEZONE definition uses the old recurrence rule.
>
> BEGIN:VTIMEZONE
> TZID:America/Los_Angeles
> X-LIC-LOCATION:America/Los_Angeles
> BEGIN:STANDARD
> TZOFFSETFROM:-0700
> TZOFFSETTO:-0800
> TZNAME:PST
> DTSTART:19701025T020000
> RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
> END:STANDARD
> BEGIN:DAYLIGHT
> TZOFFSETFROM:-0800
> TZOFFSETTO:-0700
> TZNAME:PDT
> DTSTART:19700405T020000
> RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU
> END:DAYLIGHT
> END:VTIMEZONE
> _______________________________________________
> Ietf-calsify mailing list
> [email-masked]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>

Date: Thu, 22 Jun 2006 18:38:28 -0700
From: Caleb Richardson <[email-masked]>
To: [email-masked]
Subject: [Ietf-calsify] Time Zone Rule Changeover

This question concerns the switch from standard time to daylight savings 
time in the United States that will occur on March 11, 2007.

 From what I understand most versions of Outlook (and some other CUAs) 
can only process VTIMEZONE observances with at most one RRULE property. 
This has led most Olson database converters to discard all historical 
data and only use the most recent recurrence rule for each observance 
(if there are any).

The switchover on March 11, 2007 will be the first that uses a new time 
zone recurrence rule standardized by the Energy Policy Act of 2005. The 
previous rule would have required a switchover on April 1, 2007.

Which recurrence rule should I use?

If I use the old rule then recurring events that are still happening 
next spring will be 1 hour off for that window and for a similar window 
every year.

If I use the new rule then my events will be 1 hour off during a similar 
window this fall.

Has anyone come up with a solution to this problem? I realize that many 
CUAs (including mine) will look at the TZID parameter and try to use 
their own strict time zone definitions before parsing the included one, 
but I feel that this is a serious problem regardless.

Thanks,

Caleb Richardson

This VTIMEZONE definition uses the new recurrence rule:

BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
END:VTIMEZONE

This VTIMEZONE definition uses the old recurrence rule.

BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701025T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700405T020000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU
END:DAYLIGHT
END:VTIMEZONE

Date: Tue, 20 Jun 2006 09:57:06 -0400
From: Cyrus Daboo <[email-masked]>
To: Caleb Richardson <[email-masked]>, [email-masked]
Subject: Re: [Ietf-calsify] Include scheduling data in ITIP VEVENT REPLY?

Hi Caleb,

--On June 19, 2006 12:35:57 PM -0700 Caleb Richardson <[email-masked]> 
wrote:

> So this seems to indicate that no, scheduling data is not required to be
> included. However in my interoperability testing I have found that Google
> Calendar requires scheduling data to be present.
>
> What is the purpose of including VEVENT scheduling data in a REPLY? Why
> does the spec even indicate it as optional? Is Google correct in their
> requirement?

I think your reading of 2446 is correct - the original event data is not 
required in the REPLY (except for those items needed to identify it - UID 
etc). If Google has a problem with that, then I think you need to report it 
as a bug to them.

NB There is one minor issue with the 2446 text thought. It states that if 
you do include the original data it must be unchanged. But it also says a 
COMMENT property can be added to the reply. So what happens if the original 
also contained a COMMENT? Given that the COMMENT property can only occur at 
most once, it must be possible therefore to return the original data with a 
different COMMENT value, violating the 2446 'unchanged' rule.

-- 
Cyrus Daboo

Date: Mon, 19 Jun 2006 12:35:57 -0700
From: Caleb Richardson <[email-masked]>
To: [email-masked]
Subject: [Ietf-calsify] Include scheduling data in ITIP VEVENT REPLY?

Is is required to include the original scheduling data (DTSTART 
property, DTEND property, VTIMEZONE component, DURATION property) when 
sending an ITIP REPLY for a VEVENT?

RFC 2446 section 3.2.3:

The optional properties listed in the table below (those listed as "0+" 
or "0 or 1") MUST NOT be changed from those of the original request.  If 
property changes are desired the COUNTER message must be used.

RFC 2446 section 4.2.2

    BEGIN:VCALENDAR
    PRODID:-//ACME/DesktopCalendar//EN
    METHOD:REPLY
    VERSION:2.0
    BEGIN:VEVENT
    ATTENDEE;PARTSTAT=ACCEPTED:Mailto:[email-masked]
    ORGANIZER:MAILTO:[email-masked]
    UID:[email-masked]
    SEQUENCE:0
    REQUEST-STATUS:2.0;Success
    DTSTAMP:19970612T190000Z
    END:VEVENT
    END:VCALENDAR

So this seems to indicate that no, scheduling data is not required to be 
included. However in my interoperability testing I have found that 
Google Calendar requires scheduling data to be present.

What is the purpose of including VEVENT scheduling data in a REPLY? Why 
does the spec even indicate it as optional? Is Google correct in their 
requirement?

Thanks,

Caleb Richardson
[email-masked]

Date: Tue, 13 Jun 2006 09:01:39 +0200
From: Eliot Lear <[email-masked]>
To: Reinhold Kainhofer <[email-masked]>
Cc: [email-masked], CALSIFY Mailinglist <[email-masked]>
Subject: [Ietf-calsify] [issue] when BY extends past last occurrence

Reinhold Kainhofer wrote:

> -) Section 4.3.10 says:
>    "If BYxxx rule part values are found which are beyond the available
>    scope (ie, BYMONTHDAY=30 in February), they are simply ignored."
> 
> Here an example should be given (what the available scope is and what ignored 
> means here). E.g.
> 
>   DTSTART;TZID=Europe/Vienna: 20050201T120000
>   RRULE:FREQ=MONTHLY;BYMONTHDAY=30;FREQ=3
> results in occurrences on 1 Feb 2006, 30 May 2006, 30 Aug 2006, 30 Nov 2006, 
> 30 May 2006.
> I.e. "they are simply ignored" means that the whole occurrence is ignored, not 
> the rule part value (which would result in the day being taken from the 
> DTSTART) .

So what is needed here is a normative clarification of what is ignored.
 Do you have some preferred text you would like to propose?

Eliot

Date: Mon, 12 Jun 2006 13:28:53 -0700
From: Jeffrey Harris <[email-masked]>
To: Bernard Desruisseaux <[email-masked]>
Subject: Re: [Ietf-calsify] Error in RFC 2445 regarding DTSTAMP being optional (in the grammar)
Cc: CALSIFY Mailinglist <[email-masked]>

Hi Folks,

Given that the RFC was confused, I'd like to put in a vote in favor of
choosing optional for DTSTAMP, not MUST.  Lots of iCalendar in the wild
doesn't have a DTSTAMP, and I don't see a compelling reason for
requiring it (although I'd be happy to be informed of compelling reasons).

Sincerely,
Jeffrey

To: [email-masked]
From: [email-masked]
Date: Mon, 12 Jun 2006 15:50:01 -0400
Cc: [email-masked]
Subject: [Ietf-calsify] I-D ACTION:draft-ietf-calsify-rfc2447bis-02.txt 

--NextPart

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-02.txt
	Pages		: 22
	Date		: 2006-6-12
	
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 (iCAL) are
   composed using constructs from RFC 2822, RFC 2045, RFC 2046,
   RFC 2047, RFC 2048 and RFC 2049.

   This document is a product of Calendaring and Scheduling Standards
   Simplification (calsify) working group. More information about the
   IETF CALSIFY working group activities can be found on the IETF web
   site at <http://www.ietf.org/html.charters/calsify-charter.html>.

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

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-calsify-rfc2447bis-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-calsify-rfc2447bis-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID: <[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsify-rfc2447bis-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-calsify-rfc2447bis-02.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <[email-masked]>

--OtherAccess--

--NextPart--

Date: Mon, 12 Jun 2006 21:52:29 +0300
From: Aki Niemi <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: [Ietf-calsify] WG status update

Howdy,

Eliot and I thought it would be good to sum up where the working group
is at the moment, and what's happening next.

First, Eliot has posted the proposed text for the WGs rechartering,
which we will be sending to Lisa any day now.

Second, an issue tracker has been set up for the working group with the
intention to track all outstanding issues there and follow up that they
all get closed with appropriate action. It will mainly be a checklist
tool for the authors and chairs so not to let any bugs slip through.

We (the chairs and authors) will keep an eye on the list and register
all issues that pop up. Especially to help in this task, please try to
keep the subject line on topic, and change it if necessary. Perhaps even
tag your post's subject with "Issue:" just to be clear.

Third, as you may have seen, we've been (tentatively) scheduled for
Wednesday morning 9:00-11:00 at IETF66. We will be working towards an
agenda, but don't expect any big surprises there: the agenda will be
dedicated to working out issues in the RFC244x-bis drafts.

Cheers,
Aki & Eliot

Date: Mon, 12 Jun 2006 20:33:48 +0200
From: Eliot Lear <[email-masked]>
To: Bernard Desruisseaux <[email-masked]>
Subject: Re: [Ietf-calsify] And here's the first crack...
Cc: "[email-masked]" <[email-masked]>

This is a multi-part message in MIME format.
--------------060400000005020307000500
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Desruisseaux wrote:
> Eliot,
>
> You've used the wrong time zone.  All meetings are
> consistently starting 3 hours late!

I had San Diego on the brain.  I'm sure the people of Montreal wouldn't
like to know that I moved them all to the West, so let's try this
again.  Thanks to Bernard for catching my brain fart.  Here is a
(hopefully) more correct version.

Thanks,

Eliot

--------------060400000005020307000500
Content-Type: text/calendar; x-mac-type="0"; x-mac-creator="0"; name="a2.ics"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="a2.ics"

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Eliot Lear//gen-ietf-ical 2.1//EN
VERSION:2.0
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:America/Montreal
LAST-MODIFIED:20060614T102150Z
BEGIN:DAYLIGHT
DTSTART:20060402T020000
TZOFFSETTO:-0400
TZOFFSETFROM:-0500
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20061030T020000
TZOFFSETTO:-0500
TZOFFSETFROM:-0400
TZNAME:EST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060709T130000
DTEND;TZID=America/Montreal:20060709T144500
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY: Editing an RFC Tutorial
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060709T130000
DTEND;TZID=America/Montreal:20060709T144500
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY: What MIB Document Editors Need to Know
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060709T130000
DTEND;TZID=America/Montreal:20060709T144500
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY: New Comers
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060709T150000
DTEND;TZID=America/Montreal:20060709T164500
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY: Introduction to xml2rfc
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060709T150000
DTEND;TZID=America/Montreal:20060709T164500
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY: Routing\, Bridging and Switching Tutorial
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060709T170000
DTEND;TZID=America/Montreal:20060709T190000
LOCATION:Room 517D
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY: Welcome Reception
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - apparea - Applications Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - ipdvb - IP over DVB WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - netlmm - Network-based Localized Mobility
  Management WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - radext - RADIUS EXTensions WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - enum - Telephone Number Mapping WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - ccamp - Common Control and Measurement Pl
 ane WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - krb-wg - Kerberos WG WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T090000
DTEND;TZID=America/Montreal:20060710T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - offpath - Path-decouple Signaling for Dat
 a BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - trill - Transparent Interconnection of Lo
 ts of Links WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - bmwg - Benchmarking Methodology WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - xcon - Centralized Conferencing WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - speermint - Session PEERing for Multimedi
 a INTerconnect WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - sidr - Secure Inter-Domain Routing WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - kitten - Kitten (GSS-API Next Generation)
  WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - ltans - Long-Term Archive and Notary Serv
 ices WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T130000
DTEND;TZID=America/Montreal:20060710T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - rmt - Reliable Multicast Transport WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - lemonade - Enhancements to Internet email
  to support diverse service environments WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:GEN - ipr - Intellectual Property Rights WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - 16ng - IP over IEEE 802.16 Networks BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - shim6 - Site Multihoming by IPv6 Intermed
 iation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - capwap - Control And Provisioning of Wire
 less Access Points WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - forces - Forwarding and Control Element S
 eparation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - pkix - Public-Key Infrastructure (X.509) 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T152000
DTEND;TZID=America/Montreal:20060710T172000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - ternli - Transport-Enhancing Refinements 
 to the Network Layer BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T174000
DTEND;TZID=America/Montreal:20060710T184000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - widex - Widget Description Exchange Servi
 ce WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T174000
DTEND;TZID=America/Montreal:20060710T184000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - softwire - Softwires WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T174000
DTEND;TZID=America/Montreal:20060710T184000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:IRTF - NMRG - Network Management Research Group
  Charter
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T174000
DTEND;TZID=America/Montreal:20060710T184000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - dime - Diameter Maintenance and Extension
 s WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T174000
DTEND;TZID=America/Montreal:20060710T184000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - sasl - Simple Authentication and Security
  Layer WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T174000
DTEND;TZID=America/Montreal:20060710T184000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - tsvwg - Transport Area Working Group WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T185000
DTEND;TZID=America/Montreal:20060710T195000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - widex - Widget Description Exchange Servi
 ce WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T185000
DTEND;TZID=America/Montreal:20060710T195000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - hip - Host Identity Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T185000
DTEND;TZID=America/Montreal:20060710T195000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:IRTF - NMRG - Network Management Research Group
  Charter
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T185000
DTEND;TZID=America/Montreal:20060710T195000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - dime - Diameter Maintenance and Extension
 s WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T185000
DTEND;TZID=America/Montreal:20060710T195000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - sasl - Simple Authentication and Security
  Layer WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060710T185000
DTEND;TZID=America/Montreal:20060710T195000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - tsvwg - Transport Area Working Group WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - eai - Email Address Internationalization 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - dhc - Dynamic Host Configuration WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - 6lowpan - IPv6 over Low power WPAN WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:IRTF - SAMRG - Scalable Adaptive Multicast Rese
 arch Group
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - mboned - MBONE Deployment WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - sipping - Session Initiation Proposal Inv
 estigation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - nea - Network Endpoint Assessment BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T090000
DTEND;TZID=America/Montreal:20060711T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - nfsv4 - Network File System Version 4 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T130000
DTEND;TZID=America/Montreal:20060711T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - lemonade - Enhancements to Internet email
  to support diverse service environments WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T130000
DTEND;TZID=America/Montreal:20060711T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - dnsext - DNS Extensions WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T130000
DTEND;TZID=America/Montreal:20060711T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - ipfix - IP Flow Information Export WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T130000
DTEND;TZID=America/Montreal:20060711T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - geopriv - Geographic Location/Privacy WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T130000
DTEND;TZID=America/Montreal:20060711T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - idr - Inter-Domain Routing WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T130000
DTEND;TZID=America/Montreal:20060711T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - tls - Transport Layer Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T130000
DTEND;TZID=America/Montreal:20060711T150000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - behave - Behavior Engineering for Hindran
 ce Avoidance WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - sieve - Sieve Mail Filtering Language WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - mipshop - Mobility for IP: Performance\, 
 Signaling and Handoff Optimization WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - opsarea - Operations & Management Area Op
 en Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - simple - SIP for Instant Messaging and Pr
 esence Leveraging Extensions WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - l1vpn - Layer 1 Virtual Private Networks 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - btns - Better-Than-Nothing Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - dccp - Datagram Congestion Control Protoc
 ol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T152000
DTEND;TZID=America/Montreal:20060711T172000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - fecframe - FEC Framework WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T174000
DTEND;TZID=America/Montreal:20060711T184000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - monami6 - Mobile Nodes and Multiple Inter
 faces in IPv6 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T174000
DTEND;TZID=America/Montreal:20060711T184000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - mip4 - Mobility for IPv4 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T174000
DTEND;TZID=America/Montreal:20060711T184000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - pwe3 - Pseudo Wire Emulation Edge to Edge
  WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T174000
DTEND;TZID=America/Montreal:20060711T184000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - opsec - Operational Security Capabilities
  for IP Network Infrastructure WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T174000
DTEND;TZID=America/Montreal:20060711T184000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - ecrit - Emergency Context Resolution with
  Internet Technologies WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T174000
DTEND;TZID=America/Montreal:20060711T184000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - msec - Multicast Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T174000
DTEND;TZID=America/Montreal:20060711T184000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - rohc - Robust Header Compression WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T185000
DTEND;TZID=America/Montreal:20060711T195000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - nemo - Network Mobility WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T185000
DTEND;TZID=America/Montreal:20060711T195000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - ecrit - Emergency Context Resolution with
  Internet Technologies WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T185000
DTEND;TZID=America/Montreal:20060711T195000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - isis - IS-IS for IP Internets WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T185000
DTEND;TZID=America/Montreal:20060711T195000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - openpgp - An Open Specification for Prett
 y Good Privacy WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060711T185000
DTEND;TZID=America/Montreal:20060711T195000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - rohc - Robust Header Compression WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - calsify - Calendaring and Scheduling Stan
 dards Simplification WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - autoconf - Ad-Hoc Network Autoconfigurati
 on WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:IRTF - MobOpts - IP Mobility Optimizations Rese
 arch Group
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - v6ops - IPv6 Operations WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - mmusic - Multiparty Multimedia Session Co
 ntrol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - mpls - Multiprotocol Label Switching WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - emu - EAP Method Update WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T090000
DTEND;TZID=America/Montreal:20060712T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - nsis - Next Steps in Signaling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T130000
DTEND;TZID=America/Montreal:20060712T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - dmsp - Distributed Multimodal Synchroniza
 tion Protocol BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T130000
DTEND;TZID=America/Montreal:20060712T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - intarea - Internet Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T130000
DTEND;TZID=America/Montreal:20060712T150000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - sip - Session Initiation Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T130000
DTEND;TZID=America/Montreal:20060712T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - ospf - Open Shortest Path First IGP WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T130000
DTEND;TZID=America/Montreal:20060712T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - inch - Extended Incident Handling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T130000
DTEND;TZID=America/Montreal:20060712T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - ippm - IP Performance Metrics WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T130000
DTEND;TZID=America/Montreal:20060712T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - rserpool - Reliable Server Pooling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T151000
DTEND;TZID=America/Montreal:20060712T161000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:APP - atompub - Atom Publishing Format and Prot
 ocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T151000
DTEND;TZID=America/Montreal:20060712T161000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - mipshop - Mobility for IP: Performance\, 
 Signaling and Handoff Optimization WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T151000
DTEND;TZID=America/Montreal:20060712T161000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - grow - Global Routing Operations WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T151000
DTEND;TZID=America/Montreal:20060712T161000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - pim - Protocol Independent Multicast WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T151000
DTEND;TZID=America/Montreal:20060712T161000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - isms - Integrated Security Model for SNMP
  WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T151000
DTEND;TZID=America/Montreal:20060712T161000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - ips - IP Storage WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T161000
DTEND;TZID=America/Montreal:20060712T170000
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T170000
DTEND;TZID=America/Montreal:20060712T193000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:IETF Operations and Administration Plenary
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060712T170000
DTEND;TZID=America/Montreal:20060712T193000
LOCATION:THE AGENDA
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:HAS - NOT - BEEN UPLOADED YET
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T090000
DTEND;TZID=America/Montreal:20060713T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - mip6 - Mobility for IPv6 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T090000
DTEND;TZID=America/Montreal:20060713T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - ntp - Network Time Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T090000
DTEND;TZID=America/Montreal:20060713T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - dnsop - Domain Name System Operations WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T090000
DTEND;TZID=America/Montreal:20060713T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - sipping - Session Initiation Proposal Inv
 estigation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T090000
DTEND;TZID=America/Montreal:20060713T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - hoakey - Handover and Application Keying 
 and Pre-authentication BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T090000
DTEND;TZID=America/Montreal:20060713T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - tsvarea - Transport Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T130000
DTEND;TZID=America/Montreal:20060713T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - pana - Protocol for carrying Authenticati
 on for Network Access WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T130000
DTEND;TZID=America/Montreal:20060713T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - sip - Session Initiation Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T130000
DTEND;TZID=America/Montreal:20060713T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - manet - Mobile Ad-hoc Networks WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T130000
DTEND;TZID=America/Montreal:20060713T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - pce - Path Computation Element WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T130000
DTEND;TZID=America/Montreal:20060713T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - saag - Security Area Directorate Open Mee
 ting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T130000
DTEND;TZID=America/Montreal:20060713T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - tcpm - TCP Maintenance and Minor Extensio
 ns WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T151000
DTEND;TZID=America/Montreal:20060713T161000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - dna - Detecting Network Attachment WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T151000
DTEND;TZID=America/Montreal:20060713T161000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - l2vpn - Layer 2 Virtual Private Networks 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T151000
DTEND;TZID=America/Montreal:20060713T161000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - imss - Internet and Management Support fo
 r Storage WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T151000
DTEND;TZID=America/Montreal:20060713T161000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RTG - rpsec - Routing Protocol Security Require
 ments WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T151000
DTEND;TZID=America/Montreal:20060713T161000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - smime - S/MIME Mail Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T151000
DTEND;TZID=America/Montreal:20060713T161000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:TSV - nsis - Next Steps in Signaling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060713T170000
DTEND;TZID=America/Montreal:20060713T193000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:Technical Plenary
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060714T090000
DTEND;TZID=America/Montreal:20060714T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:GEN - genarea - General Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060714T090000
DTEND;TZID=America/Montreal:20060714T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:INT - l3vpn - Layer 3 Virtual Private Networks 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060714T090000
DTEND;TZID=America/Montreal:20060714T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:OPS - netconf - Network Configuration WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060714T090000
DTEND;TZID=America/Montreal:20060714T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:RAI - avt - Audio/Video Transport WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060714T090000
DTEND;TZID=America/Montreal:20060714T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - dkim - Domain Keys Identified Mail WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060714T090000
DTEND;TZID=America/Montreal:20060714T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:SEC - dkim - Domain Keys Identified Mail WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Montreal:20060714T123000
DTEND;TZID=America/Montreal:20060714T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T182915Z
SEQUENCE:2
SUMMARY:IRTF - HIPRG - Host Identity Protocol
END:VEVENT
END:VCALENDAR

--------------060400000005020307000500--

Date: Mon, 12 Jun 2006 09:33:57 -0400
From: Bernard Desruisseaux <[email-masked]>
To: Eliot Lear <[email-masked]>
Subject: Re: [Ietf-calsify] And here's the first crack...
Cc: "[email-masked]" <[email-masked]>

Eliot,

You've used the wrong time zone.  All meetings are
consistently starting 3 hours late!

Cheers,
Bernard

Eliot Lear wrote:
> ... at an iCalendar agenda file (attached).  Let me know if you run into
> problems.
> 
> Eliot
> 

Date: Mon, 12 Jun 2006 09:21:50 -0400
From: Bernard Desruisseaux <[email-masked]>
To: Reinhold Kainhofer <[email-masked]>
Subject: Re: [Ietf-calsify] Error in RFC 2445 regarding DTSTAMP being optional (in the grammar)
Cc: CALSIFY Mailinglist <[email-masked]>

Hi Reinhold,

The ABNFs are currently not in agreement with the text specified
in the Conformance section of DTSTAMP, DTSTART and UID.

The ABNF will be fixed.

Cheers,
Bernard

Reinhold Kainhofer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all,
> While reading rfc 2445 for the ISOC calendar conformance, I found that the 
> grammar for VEVENT, VTODO, VJOURNAL, VFREEBUSY all say that the dtstamp 
> property is optional (but must not appear more than once). However, the 
> section on DTSTAMP reads:
> 
> 4.8.7.2 Date/Time Stamp
> 
>    Property Name: DTSTAMP
> 
>    Purpose: The property indicates the date/time that the instance of
>    the iCalendar object was created.
> 
>    Value Type: DATE-TIME
> 
>    Property Parameters: Non-standard property parameters can be
>    specified on this property.
> 
>    Conformance: This property MUST be included in the "VEVENT", "VTODO",
>    "VJOURNAL" or "VFREEBUSY" calendar components.
> 
>    Description: The value MUST be specified in the UTC time format.
> 
> 
> So,clearly, the DTSTAMP property is not optional. I suppose this should be 
> changed in the grammar? 
> Or is it really optional and section 4.8.7.2 is wrong?
> 
> Cheers,
> Reinhold
> - -- 
> - ------------------------------------------------------------------
> Reinhold Kainhofer, Vienna, Austria
> email: [email-masked], http://reinhold.kainhofer.com/
>  * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
>  * K Desktop Environment, http://www.kde.org/, KOrganizer maintainer
>  * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> 
> iD8DBQFEieStTqjEwhXvPN0RAqZ0AJ9V/uW6TfV3nDMrXtAsDU/jzH3jowCgmXD9
> P3/6q17H2/DcQmmIxYD+rK0=
> =dOi8
> -----END PGP SIGNATURE-----
> _______________________________________________
> Ietf-calsify mailing list
> [email-masked]
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify

Date: Mon, 12 Jun 2006 09:25:11 +0200
From: Eliot Lear <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: [Ietf-calsify] And here's the first crack...

This is a multi-part message in MIME format.
--------------000307090503040501000305
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

... at an iCalendar agenda file (attached).  Let me know if you run into
problems.

Eliot

--------------000307090503040501000305
Content-Type: text/calendar; x-mac-type="0"; x-mac-creator="0"; name="a1.ics"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="a1.ics"

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Eliot Lear//gen-ietf-ical 2.1//EN
VERSION:2.0
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:US/Pacific
LAST-MODIFIED:20060614T102150Z
BEGIN:DAYLIGHT
DTSTART:20060402T020000
TZOFFSETTO:-0700
TZOFFSETFROM:-0800
TZNAME:PDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20061030T020000
TZOFFSETTO:-0800
TZOFFSETFROM:-0700
TZNAME:PST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060709T130000
DTEND;TZID=US/Pacific:20060709T144500
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY: Editing an RFC Tutorial
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060709T130000
DTEND;TZID=US/Pacific:20060709T144500
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY: What MIB Document Editors Need to Know
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060709T130000
DTEND;TZID=US/Pacific:20060709T144500
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY: New Comers
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060709T150000
DTEND;TZID=US/Pacific:20060709T164500
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY: Introduction to xml2rfc
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060709T150000
DTEND;TZID=US/Pacific:20060709T164500
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY: Routing\, Bridging and Switching Tutorial
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060709T170000
DTEND;TZID=US/Pacific:20060709T190000
LOCATION:Room 517D
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY: Welcome Reception
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - apparea - Applications Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - ipdvb - IP over DVB WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - netlmm - Network-based Localized Mobility
  Management WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - radext - RADIUS EXTensions WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - enum - Telephone Number Mapping WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - ccamp - Common Control and Measurement Pl
 ane WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - krb-wg - Kerberos WG WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T090000
DTEND;TZID=US/Pacific:20060710T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - offpath - Path-decouple Signaling for Dat
 a BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - trill - Transparent Interconnection of Lo
 ts of Links WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - bmwg - Benchmarking Methodology WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - xcon - Centralized Conferencing WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - speermint - Session PEERing for Multimedi
 a INTerconnect WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - sidr - Secure Inter-Domain Routing WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - kitten - Kitten (GSS-API Next Generation)
  WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - ltans - Long-Term Archive and Notary Serv
 ices WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T130000
DTEND;TZID=US/Pacific:20060710T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - rmt - Reliable Multicast Transport WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - lemonade - Enhancements to Internet email
  to support diverse service environments WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:GEN - ipr - Intellectual Property Rights WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - 16ng - IP over IEEE 802.16 Networks BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - shim6 - Site Multihoming by IPv6 Intermed
 iation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - capwap - Control And Provisioning of Wire
 less Access Points WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - forces - Forwarding and Control Element S
 eparation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - pkix - Public-Key Infrastructure (X.509) 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T152000
DTEND;TZID=US/Pacific:20060710T172000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - ternli - Transport-Enhancing Refinements 
 to the Network Layer BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T174000
DTEND;TZID=US/Pacific:20060710T184000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - widex - Widget Description Exchange Servi
 ce WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T174000
DTEND;TZID=US/Pacific:20060710T184000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - softwire - Softwires WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T174000
DTEND;TZID=US/Pacific:20060710T184000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:IRTF - NMRG - Network Management Research Group
  Charter
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T174000
DTEND;TZID=US/Pacific:20060710T184000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - dime - Diameter Maintenance and Extension
 s WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T174000
DTEND;TZID=US/Pacific:20060710T184000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - sasl - Simple Authentication and Security
  Layer WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T174000
DTEND;TZID=US/Pacific:20060710T184000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - tsvwg - Transport Area Working Group WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T185000
DTEND;TZID=US/Pacific:20060710T195000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - widex - Widget Description Exchange Servi
 ce WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T185000
DTEND;TZID=US/Pacific:20060710T195000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - hip - Host Identity Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T185000
DTEND;TZID=US/Pacific:20060710T195000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:IRTF - NMRG - Network Management Research Group
  Charter
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T185000
DTEND;TZID=US/Pacific:20060710T195000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - dime - Diameter Maintenance and Extension
 s WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T185000
DTEND;TZID=US/Pacific:20060710T195000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - sasl - Simple Authentication and Security
  Layer WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060710T185000
DTEND;TZID=US/Pacific:20060710T195000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - tsvwg - Transport Area Working Group WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - eai - Email Address Internationalization 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - dhc - Dynamic Host Configuration WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - 6lowpan - IPv6 over Low power WPAN WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:IRTF - SAMRG - Scalable Adaptive Multicast Rese
 arch Group
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - mboned - MBONE Deployment WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - sipping - Session Initiation Proposal Inv
 estigation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - nea - Network Endpoint Assessment BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T090000
DTEND;TZID=US/Pacific:20060711T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - nfsv4 - Network File System Version 4 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T130000
DTEND;TZID=US/Pacific:20060711T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - lemonade - Enhancements to Internet email
  to support diverse service environments WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T130000
DTEND;TZID=US/Pacific:20060711T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - dnsext - DNS Extensions WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T130000
DTEND;TZID=US/Pacific:20060711T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - ipfix - IP Flow Information Export WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T130000
DTEND;TZID=US/Pacific:20060711T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - geopriv - Geographic Location/Privacy WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T130000
DTEND;TZID=US/Pacific:20060711T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - idr - Inter-Domain Routing WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T130000
DTEND;TZID=US/Pacific:20060711T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - tls - Transport Layer Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T130000
DTEND;TZID=US/Pacific:20060711T150000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - behave - Behavior Engineering for Hindran
 ce Avoidance WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - sieve - Sieve Mail Filtering Language WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - mipshop - Mobility for IP: Performance\, 
 Signaling and Handoff Optimization WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - opsarea - Operations & Management Area Op
 en Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - simple - SIP for Instant Messaging and Pr
 esence Leveraging Extensions WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - l1vpn - Layer 1 Virtual Private Networks 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - btns - Better-Than-Nothing Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - dccp - Datagram Congestion Control Protoc
 ol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T152000
DTEND;TZID=US/Pacific:20060711T172000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - fecframe - FEC Framework WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T174000
DTEND;TZID=US/Pacific:20060711T184000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - monami6 - Mobile Nodes and Multiple Inter
 faces in IPv6 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T174000
DTEND;TZID=US/Pacific:20060711T184000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - mip4 - Mobility for IPv4 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T174000
DTEND;TZID=US/Pacific:20060711T184000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - pwe3 - Pseudo Wire Emulation Edge to Edge
  WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T174000
DTEND;TZID=US/Pacific:20060711T184000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - opsec - Operational Security Capabilities
  for IP Network Infrastructure WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T174000
DTEND;TZID=US/Pacific:20060711T184000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - ecrit - Emergency Context Resolution with
  Internet Technologies WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T174000
DTEND;TZID=US/Pacific:20060711T184000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - msec - Multicast Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T174000
DTEND;TZID=US/Pacific:20060711T184000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - rohc - Robust Header Compression WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T185000
DTEND;TZID=US/Pacific:20060711T195000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - nemo - Network Mobility WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T185000
DTEND;TZID=US/Pacific:20060711T195000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - ecrit - Emergency Context Resolution with
  Internet Technologies WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T185000
DTEND;TZID=US/Pacific:20060711T195000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - isis - IS-IS for IP Internets WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T185000
DTEND;TZID=US/Pacific:20060711T195000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - openpgp - An Open Specification for Prett
 y Good Privacy WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060711T185000
DTEND;TZID=US/Pacific:20060711T195000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - rohc - Robust Header Compression WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - calsify - Calendaring and Scheduling Stan
 dards Simplification WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - autoconf - Ad-Hoc Network Autoconfigurati
 on WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:IRTF - MobOpts - IP Mobility Optimizations Rese
 arch Group
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - v6ops - IPv6 Operations WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - mmusic - Multiparty Multimedia Session Co
 ntrol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - mpls - Multiprotocol Label Switching WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - emu - EAP Method Update WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T090000
DTEND;TZID=US/Pacific:20060712T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - nsis - Next Steps in Signaling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T130000
DTEND;TZID=US/Pacific:20060712T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - dmsp - Distributed Multimodal Synchroniza
 tion Protocol BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T130000
DTEND;TZID=US/Pacific:20060712T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - intarea - Internet Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T130000
DTEND;TZID=US/Pacific:20060712T150000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - sip - Session Initiation Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T130000
DTEND;TZID=US/Pacific:20060712T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - ospf - Open Shortest Path First IGP WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T130000
DTEND;TZID=US/Pacific:20060712T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - inch - Extended Incident Handling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T130000
DTEND;TZID=US/Pacific:20060712T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - ippm - IP Performance Metrics WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T130000
DTEND;TZID=US/Pacific:20060712T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - rserpool - Reliable Server Pooling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T151000
DTEND;TZID=US/Pacific:20060712T161000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:APP - atompub - Atom Publishing Format and Prot
 ocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T151000
DTEND;TZID=US/Pacific:20060712T161000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - mipshop - Mobility for IP: Performance\, 
 Signaling and Handoff Optimization WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T151000
DTEND;TZID=US/Pacific:20060712T161000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - grow - Global Routing Operations WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T151000
DTEND;TZID=US/Pacific:20060712T161000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - pim - Protocol Independent Multicast WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T151000
DTEND;TZID=US/Pacific:20060712T161000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - isms - Integrated Security Model for SNMP
  WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T151000
DTEND;TZID=US/Pacific:20060712T161000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - ips - IP Storage WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T161000
DTEND;TZID=US/Pacific:20060712T170000
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T170000
DTEND;TZID=US/Pacific:20060712T193000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:IETF Operations and Administration Plenary
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060712T170000
DTEND;TZID=US/Pacific:20060712T193000
LOCATION:THE AGENDA
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:HAS - NOT - BEEN UPLOADED YET
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T090000
DTEND;TZID=US/Pacific:20060713T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - mip6 - Mobility for IPv6 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T090000
DTEND;TZID=US/Pacific:20060713T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - ntp - Network Time Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T090000
DTEND;TZID=US/Pacific:20060713T113000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - dnsop - Domain Name System Operations WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T090000
DTEND;TZID=US/Pacific:20060713T113000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - sipping - Session Initiation Proposal Inv
 estigation WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T090000
DTEND;TZID=US/Pacific:20060713T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - hoakey - Handover and Application Keying 
 and Pre-authentication BOF
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T090000
DTEND;TZID=US/Pacific:20060713T113000
LOCATION:Room 520DEF
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - tsvarea - Transport Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T130000
DTEND;TZID=US/Pacific:20060713T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - pana - Protocol for carrying Authenticati
 on for Network Access WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T130000
DTEND;TZID=US/Pacific:20060713T150000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - sip - Session Initiation Protocol WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T130000
DTEND;TZID=US/Pacific:20060713T150000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - manet - Mobile Ad-hoc Networks WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T130000
DTEND;TZID=US/Pacific:20060713T150000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - pce - Path Computation Element WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T130000
DTEND;TZID=US/Pacific:20060713T150000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - saag - Security Area Directorate Open Mee
 ting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T130000
DTEND;TZID=US/Pacific:20060713T150000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - tcpm - TCP Maintenance and Minor Extensio
 ns WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T151000
DTEND;TZID=US/Pacific:20060713T161000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - dna - Detecting Network Attachment WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T151000
DTEND;TZID=US/Pacific:20060713T161000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - l2vpn - Layer 2 Virtual Private Networks 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T151000
DTEND;TZID=US/Pacific:20060713T161000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - imss - Internet and Management Support fo
 r Storage WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T151000
DTEND;TZID=US/Pacific:20060713T161000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RTG - rpsec - Routing Protocol Security Require
 ments WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T151000
DTEND;TZID=US/Pacific:20060713T161000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - smime - S/MIME Mail Security WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T151000
DTEND;TZID=US/Pacific:20060713T161000
LOCATION:Room 513C-F
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:TSV - nsis - Next Steps in Signaling WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060713T170000
DTEND;TZID=US/Pacific:20060713T193000
LOCATION:Room 520ABC
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:Technical Plenary
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060714T090000
DTEND;TZID=US/Pacific:20060714T113000
LOCATION:Room 518AB
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:GEN - genarea - General Area Open Meeting
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060714T090000
DTEND;TZID=US/Pacific:20060714T113000
LOCATION:Room 515
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:INT - l3vpn - Layer 3 Virtual Private Networks 
 WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060714T090000
DTEND;TZID=US/Pacific:20060714T113000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:OPS - netconf - Network Configuration WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060714T090000
DTEND;TZID=US/Pacific:20060714T113000
LOCATION:Room 519B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:RAI - avt - Audio/Video Transport WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060714T090000
DTEND;TZID=US/Pacific:20060714T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - dkim - Domain Keys Identified Mail WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060714T090000
DTEND;TZID=US/Pacific:20060714T113000
LOCATION:Room 519A
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:SEC - dkim - Domain Keys Identified Mail WG
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20060714T123000
DTEND;TZID=US/Pacific:20060714T150000
LOCATION:Room 513B
UID:[email-masked]
DTSTAMP:20060612T072036Z
SEQUENCE:1
SUMMARY:IRTF - HIPRG - Host Identity Protocol
END:VEVENT
END:VCALENDAR

--------------000307090503040501000305--

Date: Mon, 12 Jun 2006 09:24:07 +0200
From: Eliot Lear <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: [Ietf-calsify] [Fwd: CALSIFY - Requested session has been scheduled for IETF 66]

This is a multi-part message in MIME format.
--------------060705030007010700040307
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

FYI- this is very much subject to change.  We really need to get issues
on the table for this to be a meaningful meeting, IMHO.

Eliot

--------------060705030007010700040307
Content-Type: message/rfc822;
	name="CALSIFY - Requested session has been scheduled for IETF 66"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename*0="CALSIFY - Requested session has been scheduled for IETF 66"

To: [email-masked]
Cc: [email-masked], [email-masked], [email-masked],
	[email-masked]
From: IETF Secretariat <[email-masked]>
Subject: CALSIFY - Requested session has been scheduled for IETF 66 
Date: Sun, 11 Jun 2006 17:16:49 -0400

Dear Aki Niemi,

The sessions that you have requested have been scheduled.
Below is the scheduled session information followed by 
the information of sessions that you have requested.

CALSIFY Session 1 (2 hours)
Wednesday, Morning Session I 0900-1130
Room Name: Room 513B
----------------------------------------------

Requested Information:

---------------------------------------------------------
Working Group Name: calsify
Area Name: Applications Area
Session Requester: Aki Niemi

Number of Sessions: 1
Length of Session(s):  2 hours

Number of Attendees: 20
Conflicts to Avoid:
  First Priority:  apparea sieve imapext dkim
  Second Priority:  sip simple sipping
  BOF or IRTF Session: WARP

Special Requests:
  
---------------------------------------------------------

--------------060705030007010700040307--

From: Reinhold Kainhofer <[email-masked]>
Organization: Vienna University of Technology
To: CALSIFY Mailinglist <[email-masked]>
Date: Sat, 10 Jun 2006 01:19:57 +0200
Subject: [Ietf-calsify] Another error in rfc 2445: seconds are missing in several DTSTAMPs

Hi all,

While talking with Harvey Allen about their web calendars, he noticed that in 
several examples the seconds in the DTSTAMPs  date-times are missing (which 
according to the definitions of sections 4.3.5 and 4.3.12 is NOT allowed). 

In particular, the following example iCalendar pieces have only hour and 
minute, but no seconds:
    -) all examples in  section "4.6.1 Event Component"
    -) the example in section "4.6.2 To-do Component"
    -) the example in section "4.6.3 Journal Component"
    -) the third example in section "5 iCalendar Object Examples" 

(Simply search for the regexp "T[0-9][0-9][0-9][0-9][^0-9]" to find them)

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: [email-masked], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/

Date: Fri, 09 Jun 2006 18:13:20 -0400
From: Hervey Allen <[email-masked]>
Organization: Network Startup Resource Center
To: Reinhold Kainhofer <[email-masked]>
Subject: Re: [Ietf-calsify] [Fwd: icalendar feeds for network/tech meeting calendar]
Cc: Joe Abley <[email-masked]>, [email-masked]

Reinhold Kainhofer wrote:

>> Hervey Allen is the programmer responsible for the code, and I know  
>> he would love to receive feedback. 
> 
> Thanks a lot for the links. Unfortunately the files are not entirely correct 
> iCalendar. I admit it's only a small flaw, and doesn create any problems as 
> far as I can see, but they use local-time values for DTSTAMP:
> 
> DTSTAMP:20060609T041633
> 
> 
> RFC 2445, however, clearly says that DTSTAMP MUST be in UTC (see "4.8.7.2 
> Date/Time Stamp"):
> " Description: The value MUST be specified in the UTC time format."
> 

Thank you Reinhold! So, I dug a bit deeper. It appears that 
what I was basically missing is the "Z" designator at the 
end of the UTC timestamp for DTSTAMP and that seconds don't 
appear to be necessary according to the samples given in the 
RFC:

http://www.ietf.org/rfc/rfc2445.txt

Currently DTSTAMP looks like this (as an example):

DTSTAMP:20060609T1535Z

Does this look OK to you?

> I opened the wrc-all.ics calendar with korganizer and it seems to work just 
> fine (at least the dates coincide with the table on the web page, and the 
> titles seem correct, too).
> 

Cool. I had not tested with Korganizer and was hoping to 
find someone who would.

> And an additional suggestion:
> As each workshop has its own information page, you can attach the 
> corresponding URL to the event:
> ATTACH:http://ws.edu.isoc.org/helpfiles/workshop_info_main.php?id=175
> 
> Several calendaring applications (e.g. korganizer) then show a link to this 
> page in the preview pane for the event.
> 

I've added the ATTACH field per your suggestion. Is this 
working for you?

Thank you for the feedback. Very helpful.

Sincerely,
	Hervey
-- 
-------------------------------------------------
Hervey Allen      Network Startup Resource Center
[email-masked] GPG Key Fingerprint:
AC08 31CB E453 6C65 2AB3 4EDB CEEB 5A74 C6E5 624F

From: Reinhold Kainhofer <[email-masked]>
Organization: Vienna University of Technology
To: CALSIFY Mailinglist <[email-masked]>
Date: Fri, 9 Jun 2006 23:14:21 +0200
Subject: [Ietf-calsify] Error in RFC 2445 regarding DTSTAMP being optional (in the grammar)

Hi all,
While reading rfc 2445 for the ISOC calendar conformance, I found that the 
grammar for VEVENT, VTODO, VJOURNAL, VFREEBUSY all say that the dtstamp 
property is optional (but must not appear more than once). However, the 
section on DTSTAMP reads:

4.8.7.2 Date/Time Stamp

   Property Name: DTSTAMP

   Purpose: The property indicates the date/time that the instance of
   the iCalendar object was created.

   Value Type: DATE-TIME

   Property Parameters: Non-standard property parameters can be
   specified on this property.

   Conformance: This property MUST be included in the "VEVENT", "VTODO",
   "VJOURNAL" or "VFREEBUSY" calendar components.

   Description: The value MUST be specified in the UTC time format.

So,clearly, the DTSTAMP property is not optional. I suppose this should be 
changed in the grammar? 
Or is it really optional and section 4.8.7.2 is wrong?

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: [email-masked], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/

From: Reinhold Kainhofer <[email-masked]>
Organization: Vienna University of Technology
To: [email-masked]
Subject: Re: [Ietf-calsify] [Fwd: icalendar feeds for network/tech meeting calendar]
Date: Fri, 9 Jun 2006 23:07:05 +0200
Cc: [email-masked]

Am Freitag, 9. Juni 2006 20:35 schrieb Eliot Lear:
> Encapsulated message
>   icalendar feeds for network/tech meeting calendar
> From: Joe Abley <[email-masked]>
>   To: IETF Discussion <[email-masked]>
>   Date: Today 18:40:53
>    
> This is not especially on-topic here, but since (a) there are  
> probably more people here who have an interest in debugging/reviewing  
> RFC 2445 documents than anywhere else and (b) there are probably more  
> people here for whom a maintained calendar of meetings is a wildly  
> useful thing, I thought I'd forward it.
>
> Hervey Allen is the programmer responsible for the code, and I know  
> he would love to receive feedback. 

Thanks a lot for the links. Unfortunately the files are not entirely correct 
iCalendar. I admit it's only a small flaw, and doesn create any problems as 
far as I can see, but they use local-time values for DTSTAMP:

DTSTAMP:20060609T041633

RFC 2445, however, clearly says that DTSTAMP MUST be in UTC (see "4.8.7.2 
Date/Time Stamp"):
" Description: The value MUST be specified in the UTC time format."

> I believe all testing to date has  
> been done with Apple's iCal and Mozilla Sunbird.

I opened the wrc-all.ics calendar with korganizer and it seems to work just 
fine (at least the dates coincide with the table on the web page, and the 
titles seem correct, too).

And an additional suggestion:
As each workshop has its own information page, you can attach the 
corresponding URL to the event:
ATTACH:http://ws.edu.isoc.org/helpfiles/workshop_info_main.php?id=175

Several calendaring applications (e.g. korganizer) then show a link to this 
page in the preview pane for the event.

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: [email-masked], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/

Date: Fri, 09 Jun 2006 20:35:16 +0200
From: Eliot Lear <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: [Ietf-calsify] [Fwd: icalendar feeds for network/tech meeting calendar]

This is a multi-part message in MIME format.
--------------080008050606050802080806
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

FYI

--------------080008050606050802080806
Content-Type: message/rfc822;
	name="icalendar feeds for network/tech meeting calendar"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="icalendar feeds for network/tech meeting calendar"

From: Joe Abley <[email-masked]>
Date: Fri, 9 Jun 2006 12:40:53 -0400
To: IETF Discussion <[email-masked]>
Subject: icalendar feeds for network/tech meeting calendar

This is not especially on-topic here, but since (a) there are  
probably more people here who have an interest in debugging/reviewing  
RFC 2445 documents than anywhere else and (b) there are probably more  
people here for whom a maintained calendar of meetings is a wildly  
useful thing, I thought I'd forward it.

Hervey Allen is the programmer responsible for the code, and I know  
he would love to receive feedback. I believe all testing to date has  
been done with Apple's iCal and Mozilla Sunbird.

The calendar is provided by ISOC and NSRC.

Begin forwarded message:

> From: Hervey Allen <[email-masked]>
> Date: 9 June 2006 11:35:52 EDT (CA)
> To: [email-masked]
> Subject: [net-meeting-coord] iCal feeds for Network Training Events  
> Calendar available
> Reply-To: [email-masked]
>
> The Network Education and Training Calendar of Events located here:
>
> http://ws.edu.isoc.org/calendar/
>
> Now has several iCal feeds available. You can choose from all  
> events (past and future), upcoming or previous. The feeds are  
> available here:
>
> http://ws.edu.isoc.org/calendar/ical/
>
> In addition, if you are interested in adding an event to the  
> calendar that you think belongs you can create an account on the  
> site and then add an event using this page:
>
> http://ws.edu.isoc.org/organizers/create-event.php
>
> All this is linked off the main calendar page.
>
> Questions or comments can be sent to myself or [email-masked].
>
> - Hervey Allen
>
> -- 
> -------------------------------------------------
> Hervey Allen      Network Startup Resource Center
> [email-masked] GPG Key Fingerprint:
> AC08 31CB E453 6C65 2AB3 4EDB CEEB 5A74 C6E5 624F
>
> ______________________________________________________________________ 
> ______
> archive: http://ws.edu.isoc.org/archive/net-meeting-coord/index.html
> calendar: http://ws.edu.isoc.org/calendar/
>

_______________________________________________
Ietf mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf

--------------080008050606050802080806--

Date: Tue, 06 Jun 2006 17:31:40 +0200
From: Eliot Lear <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: [Ietf-calsify] [Fwd: 66th IETF - Visa Requirements for Canada]

This is a multi-part message in MIME format.
--------------060407070000090302010507
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

For those attending IETF 66 in Montreal, please be advised of Canadian
visa requirements found at the web sites in the attached message.

This will not apply to those of us streaming from home ;-)

Eliot

--------------060407070000090302010507
Content-Type: message/rfc822; name="66th IETF - Visa Requirements for Canada"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="66th IETF - Visa Requirements for Canada"

To: IETF Announcement list <[email-masked]>
From: IETF Secretariat <[email-masked]>
Date: Tue, 06 Jun 2006 10:18:47 -0400
Cc: [email-masked]
Subject: 66th IETF - Visa Requirements for Canada 

66th IETF Meeting
Montreal, Quebec, Canada
July 9-14, 2006
Hosted by Ericsson  http://www.ericsson.com

Don=E2=80=99t forget to check visa requirements for entering Canada. You =
can get more
information at:
=20
http://www.ietf.org/meetings/visa_requirements.html or
http://www.cic.gc.ca/english/visit/visas.html

For more hotel information and meeting registration:=20
http://www.ietf.org/meetings/IETF-66.html=20

--------------060407070000090302010507--

From: Reinhold Kainhofer <[email-masked]>
Organization: Vienna University of Technology
To: [email-masked]
Subject: Re: [Ietf-calsify] Re: calsify and kcal
Date: Mon, 5 Jun 2006 22:00:23 +0200

Am Sonntag, 4. Juni 2006 01:57 schrieb Reinhold Kainhofer:
> I also found a web page where it was described to include some paragraph in
> a possible rfc 2445 revision, but I can't find that page again....

Okay, I found a printout and googled for that page... Seems it was the 
conclusion of a discussion on ietf-calendar (which is a real goldmine of 
problems and clarifications of RFC 2445ff.) 

It was a clarification that RDATE with VALUE=DATE does inherit the time from 
DTSTART, while EXDATE with VALUE=DATE does not inherit the time and excludes 
all events on that given day. To exclude only one particular instance, you 
need to use VALUE=DATE-TIME:
http://tipi.sourceforge.net/doc/recur/apa.html

I suppose that the issues listed as "Incorporated" at 
http://www.softwarestudio.org/iCal/2445Issues.html are included in the latest 
draft? (Sorry, haven't checked it myself...). Also, several of the "Discuss" 
items there are really items that should be discussed and clarified in rfc 
2445bis.

Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: [email-masked], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/

Date: Mon, 05 Jun 2006 18:12:04 +0200
From: Eliot Lear <[email-masked]>
To: "[email-masked]" <[email-masked]>
Subject: [Ietf-calsify] revised charter, take 2

This is a multi-part message in MIME format.
--------------020901030209090406030104
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

This one defers decision of draft v. ps until the fall.  Comments?

Eliot

--------------020901030209090406030104
Content-Type: text/html; x-mac-type="0"; x-mac-creator="0";
	name="calsify-charter.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="calsify-charter.html"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>Calendaring and Scheduling Standards Simplification (calsify) Charter</title></head>
<body style="background-color: rgb(255, 255, 255);"><center>
<table border="0" cellpadding="0" cellspacing="0"><tbody><tr>
<td><a href="/home.html"><img src="/images/header/ietflogo_sm.gif" border="0"></a></td><td><a href="/home.html"><img src="/images/header/home11.gif" border="0"></a></td>
<td><img src="/images/header/separator.gif" border="0"></td><td><a href="/html.charters/wg-dir.html"><img src="/images/header/wg11.gif" border="0"></a></td>
<td><img src="/images/header/separator.gif" border="0"></td><td><a href="/meetings/meetings.html"><img src="/images/header/meetings11.gif" border="0"></a></td>
<td><img src="/images/header/separator.gif" border="0"></td><td><a href="/proceedings/directory.html"><img src="/images/header/proceed11.gif" border="0"></a></td>
<td><img src="/images/header/separator.gif" border="0"></td><td><a href="/ID.html"><img src="/images/header/id-index11.gif" border="0"></a></td>
<td><img src="/images/header/separator.gif" border="0"></td><td><a href="/rfc.html"><img src="/images/header/rfc11.gif" border="0"></a></td>
</tr></tbody></table>
</center><hr>
<h1>Calendaring and Scheduling Standards Simplification (calsify)</h1>
<p>Last Modified: 2006-04-25 <br>
</p><h2>Chair(s):</h2>
<li> <a href="mailto:[email-masked]">Eliot Lear
&lt;[email-masked]&gt;</a>
<br><br></li><li> <a href="mailto:[email-masked]">Aki Niemi
&lt;[email-masked]&gt;</a>
<br><br><h2>Applications Area Director(s):</h2>
</li><li> <a href="mailto:[email-masked]">Ted
Hardie &lt;[email-masked]&gt;</a>
<br></li><li> <a href="mailto:[email-masked]">Lisa Dusseault
&lt;[email-masked]&gt;</a>
<br><h2>Applications Area Advisor:</h2>
</li><li> <a href="mailto:[email-masked]">Lisa
Dusseault &lt;[email-masked]&gt;</a>
<br><h2>Mailing Lists:</h2> General Discussion:
[email-masked]<br>
To Subscribe: <a href="http://lists.osafoundation.org/mailman/listinfo/ietf-calsify">http://lists.osafoundation.org/mailman/listinfo/ietf-calsify</a><br>
Archive: <a href="http://lists.osafoundation.org/pipermail/ietf-calsify/">http://lists.osafoundation.org/pipermail/ietf-calsify/</a><br>
</li>
<h2>Description of Working Group:</h2>
The Calendaring and Scheduling standards, defined in RFC's 2445, 2446,<br>and
2447 were released in November 1998, and further described in RFC<br>3283.
They were designed to progress the level of interoperability<br>between
dissimilar calendaring and scheduling systems. The Calendaring<br>and
Scheduling Core Object Specification, iCalendar, succeeded in<br>establishing
itself as the common format for exchanging calendaring<br>information
across the Internet. On the other hand, only basic<br>interoperability
has been achieved between different scheduling systems.<br><br>The
Calsify working group is chartered to:<br><br>(1) Revise the Calendaring
and Scheduling Standards to advance the<br>state of interoperable
calendaring and scheduling by addressing<br>the known
interoperability issues, &nbsp;errata, and problems found based on<br>implementation experience.<br><br>(2) Clarify
the registration process for iCalendar extensions (i.e.,<br>the
current core object specification only provides a template<br>to
register new properties).<br><br>(3) Provide a means to ease transition from, and to co-exist with,<br>the earlier iCalendar standards to the new ones. <br><br>Proposing an XML representation or
transformation of iCalendar<br>objects is out of the scope of
this working group.<br><br>Depending on the results of the update process on the standards documents the working<br>group will consider whether advancing the documents to draft standard is appropriate. &nbsp;If<br>we decide to move the documents to draft status, milestones may get changed and/or added<br>to allow for any additional work necessary to advance the documents.<br><br>
<h2>Goals and Milestones:</h2>
<table><tbody>
<tr align="left" valign="top"><td></td><td valign="top" width="70">Done</td><td>&nbsp;&nbsp;</td><td>Submit
iMIP bis draft 00 </td></tr>
<tr align="left" valign="top"><td></td><td valign="top" width="70">Done</td><td>&nbsp;&nbsp;</td><td>Submit
iCalendar bis draft 00, with formatting changes from RFC2445. </td></tr>
<tr align="left" valign="top"><td></td><td valign="top" width="70">Done</td><td>&nbsp;&nbsp;</td><td>Submit
iTIP bis draft 00 </td></tr>

<tr align="left" valign="top"><td></td><td valign="top" width="70">June 2006</td><td>&nbsp;&nbsp;</td><td>Submit
updated version of rfc2445bis&nbsp; draft </td></tr>
<tr><td></td><td>June 2006</td><td></td><td>Submit updated version of rfc2446bis draft</td></tr><tr><td></td><td>June 2006</td><td></td><td>Submit updated version of rfc2447bis draft</td></tr><tr align="left" valign="top"><td></td><td valign="top" width="70">Sep 2006</td><td>&nbsp;&nbsp;</td><td>Working Group Last Call on rfc2445bis draft </td></tr>
<tr align="left" valign="top"><td></td><td valign="top" width="70">Oct 2006</td><td>&nbsp;&nbsp;</td><td>Working Group Last Call on rfc2447bis draft</td></tr>

<tr align="left" valign="top"><td></td><td valign="top" width="70">Oct 2006</td><td>&nbsp;&nbsp;</td><td>Working Group Last Call on rfc2446bis draft </td></tr>
<tr><td></td><td>Nov 2006</td><td></td><td>Decide whether documents move to PS or DS</td></tr><tr align="left" valign="top"><td></td><td valign="top" width="70">Jan 2007</td><td>&nbsp;&nbsp;</td><td>Submit rfc2446bis draft to IESG </td></tr>
<tr align="left" valign="top"><td></td><td valign="top" width="70">Jan 2007</td><td>&nbsp;&nbsp;</td><td>Submit rfc2445bis to IESG </td></tr>
<tr align="left" valign="top"><td></td><td valign="top" width="70">Jan 2007</td><td>&nbsp;&nbsp;</td><td>Submit rfc2447bis to IESG </td></tr>

</tbody></table><h2>Internet-Drafts:</h2>
<a href="/internet-drafts/draft-ietf-calsify-rfc2447bis-01.txt">
iCalendar Message-Based Interoperability Protocol (iMIP) </a>
(34975 bytes)<br>
<a href="/internet-drafts/draft-ietf-calsify-2446bis-01.txt">
iCalendar Transport-Independent Interoperability Protocol (iTIP) </a>
(296391 bytes)<br>
<a href="/internet-drafts/draft-ietf-calsify-rfc2445bis-00.txt">
Internet Calendaring and Scheduling Core Object Specification
(iCalendar) </a> (295173 bytes)<br>
<h2>No Request For Comments</h2>
<hr><i> IETF Secretariat - Please send questions, comments,
and/or
suggestions to </i>
<a href="mailto:[email-masked]">[email-masked]</a>.
<p><a href="/html.charters/wg-dir.html">
<img src="/icons/back.gif"> Return to working group
directory. </a> </p><p>
<a href="/home.html"><img src="/icons/back.gif">
<img src="/icons/back.gif">
Return to IETF home page. </a>
</p></body></html>
--------------020901030209090406030104--

From: Reinhold Kainhofer <[email-masked]>
Organization: Vienna University of Technology
To: Eliot Lear <[email-masked]>
Date: Sun, 4 Jun 2006 01:57:08 +0200
Cc: CALSIFY Mailinglist <[email-masked]>
Subject: [Ietf-calsify] Re: calsify and kcal

Hello Eliot,

Am Samstag, 3. Juni 2006 17:46 schrieb Eliot Lear:
> My name is Eliot Lear and I am one of the co-chairs of the IETF calsify
> working group.  We are currently revising our charter and re-enlivening
> the group.  I see that you have done a lot of work on kcal, and I was
> wondering if you wanted to comment on shortcomings or interoperability
> issues you've found with RFCs 2445, 2446, and 2447.  We maintain an
> active list now, if you're not already on it.  It's
> [email-masked].
>
> Are you interested in participating?

Thanks a lot for the hint. I've been subscribed for about two years now, and I 
have mainly concerns about the recurrence rules (the examples are rather 
trivial, the border cases and cases that would need clarification are not 
included in the RFC). But also some other areas might/should be cleared.

- -) For example, the P1D vs. PT24H discussion (whether there is a difference, 
which of them should be deprecated/removed, etc). My stance is written in 
http://lists.osafoundation.org/pipermail/ietf-calsify/2005-April/000607.html:
P1D means that the event ends exactly at the same (local) time the next day, 
even if that is only 23 hours or 25 hours later due to a DST shift, while 
P24H is always exactly 24 hours. Maybe an example highlighting these 
differences might help.

- -) But then we also have the problem what should happen if the end date of a 
DURATION: P1D event does not exist:
http://lists.osafoundation.org/pipermail/ietf-calsify/2005-April/000561.html

For RRULEs it's clear that the occurence (start tiem) simply doesn't happen 
(as it's "out of scope"), but here the start time exists, only the end time 
doesn't.

- -) For recurring events, nothing in the RFC 2445  tells you how to properly 
calculate the end date/time (see 
http://lists.osafoundation.org/pipermail/ietf-calsify/2005-April/000483.html 
and 
http://lists.osafoundation.org/pipermail/ietf-calsify/2005-April/000491.html). 
I suppose it should be start date/time of the occurrence plus the duration, 
calculated from the initial DTSTART and DTEND (or DURATION), right? RFC 2446 
has one sentence for VTODOS, but RFC 2445 doesn't even have that.
Now, the problem is, how do we calculate the duration of the initial DTSTART 
and DTEND? In particular, is there a way to express a daily recurrence rule 
that specifies an event that always starts at 01:00 and ends at 13:00 (both 
local time)? The problems again appear when DST shifts happen.

- -) Section 4.3.10 says:
   "If BYxxx rule part values are found which are beyond the available
   scope (ie, BYMONTHDAY=30 in February), they are simply ignored."

Here an example should be given (what the available scope is and what ignored 
means here). E.g.

  DTSTART;TZID=Europe/Vienna: 20050201T120000
  RRULE:FREQ=MONTHLY;BYMONTHDAY=30;FREQ=3
results in occurrences on 1 Feb 2006, 30 May 2006, 30 Aug 2006, 30 Nov 2006, 
30 May 2006.
I.e. "they are simply ignored" means that the whole occurrence is ignored, not 
the rule part value (which would result in the day being taken from the 
DTSTART) .

- -) End date not inclusive: For date/times, the non-inclusive end date/time is 
clear, but for date-only events, most (all?) implementations understand the 
non-inclusive end date as the first day after the event. E.g. DTEND: 20060604 
means that the event goes on until June 3. The consensus was to clear this up 
in the RFC and define this as standard (although I suppose this will 
introduce some inconsistency somewhere. I thought about this a while back, 
but can't remember now).
Frank Dawson explained somewhere that it was actually intended to mean that 
the event's end is 20060604T23:59:59... But it seems no-one implemented it 
this way.

When I re-wrote the whole recurrence class for libkcal, I had several cases 
where the RFC should be made more clear, but I seem to have deleted my mails 
to calsify in my mail client. It's been on my to-do list for ages to write 
them down and send them again to calsify for consideration of the revised 
draft, but I haven't found the time for it yet. I think I sent them to 
ietf-calendar. 

Okay, I found some mails:

- -) The interaction between the BY* rule parts should be exemplified. I wrote 
several examples in 
http://www.imc.org/ietf-calendar/mail-archive/msg06787.html
I didn't give the answers there, but they now most seem pretty clear to me and 
they might help in understanding how the rrule parts are supposed to be 
evaluated. 

If you think they are all trivial to answer, or not realistic cases, look at 
all VTIMEZONE definitions:
http://www.imc.org/ietf-calendar/mail-archive/msg06789.html

The whole thread contains lots of thoughts about how rrules are actually 
supposed to be evaluated, which is far from trivial as soon as multiple BY* 
parts are involved.

- -) In one of the cases above, I (or rather Sam Roberts) think the RFC has an 
error which resulted in all these "wrong"(?) VTIMEZONE definitions:
http://www.imc.org/ietf-calendar/mail-archive/msg06792.html

- -) RFC 2445 says in section 4.3.10 "The "DTSTART" property 
value, if specified, counts as the first occurrence.". The "if specified" in 
this context is supposed to mean "if it matches the BY* rules", or "if it 
would be generated as a recurrence date by the RRULE". 
It does not mean if it is specified (i.e. exists) in the VEVENT at all.
(http://www.imc.org/ietf-calendar/mail-archive/msg06796.html)

- -) section 4.8.5.4 "Recurrence Rule" says 
"   The "DTSTART" and "DTEND" property pair or "DTSTART" and "DURATION"
   property pair, specified within the iCalendar object defines the
   first instance of the recurrence. "

Here, "first instance of the recurrence" does NOT mean the recurrence 
generated by that particular RRULE, but it rather means the whole set of 
occurences of the event (which is calculated of the DTSTART + RRULE dates + 
RDATE - EXRULE dates - EXDATE). This is particularly important as otherwise 
an EXRULE would always exclude the original start date/time.

I also found a web page where it was described to include some paragraph in a 
possible rfc 2445 revision, but I can't find that page again.... 

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: [email-masked], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/