|
List Info
Thread:
|
|
|

|
2007-01-29 15:19:36 |
A.1. Changes in -03
a. Added free-busy example.
b. Better abstract.
c. Requiring DAV level 2 for locking of Inbox.
d. Do not require servers to actually save Outbox
requests.
e. Removed CALDAV:schedule-state Property. Clients now
must remove
inbox items after processing them, using locking etc
to prevent
race conditions.
f. Switched back to 2518 reference from 2518bis.
g. Updated to more recent XML reference.
h. Revised required features section to better match
caldav-access.
-------- Original Message --------
Subject: I-D ACTION:draft-desruisseaux-caldav-sched-03.txt
Date: Mon, 29 Jan 2007 15:50:02 -0500
From: Internet-Drafts ietf.org
Reply-To: internet-drafts ietf.org
To: i-d-announce ietf.org
A New Internet-Draft is available from the on-line
Internet-Drafts
directories.
Title : Scheduling Extensions to CalDAV
Author(s) : B. Desruisseaux, et al.
Filename : draft-desruisseaux-caldav-sched-03.txt
Pages : 43
Date : 2007-1-29
This document defines extensions to the Web Distributed
Authoring and
Versioning (WebDAV) protocol to specify a standard way
of exchanging
and processing scheduling messages based on the
iCalendar Transport-
Independent Interoperability Protocol (iTIP). This
document defines
the "calendar-schedule" feature of CalDAV.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/dr
aft-desruisseaux-caldav-sched-03.txt
To remove yourself from the I-D Announcement list, send a
message to
i-d-announce-request ietf.org with the word unsubscribe in the
body of
the message.
You can also visit h
ttps://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-desruisseaux-caldav-sched-03.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/s
hadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv ietf.org.
In the body type:
"FILE
/internet-drafts/draft-desruisseaux-caldav-sched-03.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.
_______________________________________________
I-D-Announce mailing list
I-D-Announce ietf.org
h
ttps://www1.ietf.org/mailman/listinfo/i-d-announce
_______________________________________________
Ietf-caldav mailing list -- Ietf-caldav osafoundation.org
See http://ietf.webdav.org
/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-
caldav
|
|
|
| Refernces, was: |

|
2007-01-30 06:59:44 |
Hmmm...
> o MUST support transport over TLS [RFC2246] as
defined in [RFC2818]
> (note that [RFC2246] has been obsoleted by
[RFC4346]);
So does a server need to implement RFC2246 or RFC4346? Does
it matter?
> [RFC2396] Berners-Lee, T., Fielding,
R., and L.
> Masinter, "Uniform
Resource Identifiers
> (URI): Generic Syntax",
RFC 2396,
> August 1998.
This has long ago been obsoleted by RFC3986...
Best regards, Julian
_______________________________________________
Ietf-caldav mailing list -- Ietf-caldav osafoundation.org
See http://ietf.webdav.org
/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-
caldav
|
|
| Re: Refernces, was: |

|
2007-01-30 11:30:40 |
Hi Julian,
--On January 30, 2007 1:59:44 PM +0100 Julian Reschke
<julian.reschke gmx.de> wrote:
> Hmmm...
>
>> o MUST support transport over TLS [RFC2246] as
defined in [RFC2818]
>> (note that [RFC2246] has been obsoleted by
[RFC4346]);
>
> So does a server need to implement RFC2246 or RFC4346?
Does it matter?
Hi Tim,
--On January 30, 2007 12:10:35 PM -0500 Tim Hare
<TimHare comcast.net>
wrote:
> Tongue-in-cheek, but only halfway: seems like we need
an RFC that
> specifies a protocol whereby RFCs can refer to related
topics by name,
> rather than number (sort of a DNS for RFCs). With
caveats, of course,
> because my RFC written today may not be compatible with
whatever the new
> version of [SomeProtocol] may be although we could and
should always hope
> that the authors of [SomeProtocolRevisionTwo] provide
backward
> compatibility.
Actually this is an important issue. In fact Chris Newman
posted a message
on this specific topic to the IETF apps area mailing list to
solicit
discussion there. I suggest moving this thread over there.
--
Cyrus Daboo
_______________________________________________
Ietf-caldav mailing list -- Ietf-caldav osafoundation.org
See http://ietf.webdav.org
/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-
caldav
|
|
| Re: Refernces, was: |

|
2007-01-30 12:00:36 |
Hi Julian,
--On January 30, 2007 1:59:44 PM +0100 Julian Reschke
<julian.reschke gmx.de> wrote:
>> [RFC2396] Berners-Lee, T.,
Fielding, R., and L.
>> Masinter, "Uniform
Resource Identifiers
>> (URI): Generic
Syntax", RFC 2396,
>> August 1998.
>
> This has long ago been obsoleted by RFC3986...
Thanks I have fixed this for the next draft.
--
Cyrus Daboo
_______________________________________________
Ietf-caldav mailing list -- Ietf-caldav osafoundation.org
See http://ietf.webdav.org
/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-
caldav
|
|
| IANA considerations, was: |

|
2007-01-30 13:41:59 |
Hi,
the spec needs to register the HTTP headers (see
<http://tools.i
etf.org/html/rfc3864>).
Best regards, Julian
_______________________________________________
Ietf-caldav mailing list -- Ietf-caldav osafoundation.org
See http://ietf.webdav.org
/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-
caldav
|
|
| Re: IANA considerations, was: |

|
2007-01-30 14:09:55 |
Hi Julian,
--On January 30, 2007 8:41:59 PM +0100 Julian Reschke
<julian.reschke gmx.de> wrote:
> the spec needs to register the HTTP headers (see
> <http://tools.i
etf.org/html/rfc3864>).
Thanks, I think we had that on our own TODO list. I will try
and get it in
for -04.
--
Cyrus Daboo
_______________________________________________
Ietf-caldav mailing list -- Ietf-caldav osafoundation.org
See http://ietf.webdav.org
/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-
caldav
|
|
[1-6]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|