RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

RFC 4791, "Calendaring Extensions to WebDAV (CalDAV)", March 2007

Note: This RFC has been updated by RFC 5689, RFC 6638, RFC 6764, RFC 7809, RFC 7953, RFC 8996

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 5846
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Дилян Палаузов
Date Reported: 2019-08-25

Section 5.2.3 says: 

Conformance:  This property MAY be defined on any calendar
 collection.  If defined, it MUST be protected and SHOULD NOT be
 returned by a PROPFIND DAV:allprop request (as defined in Section
 12.14.1 of [RFC2518]).

Description: ... Any attempt by the client to store calendar object
 resources with component types not listed in this property, if it
 exists, MUST result in an error, with the
 CALDAV:supported-calendar-component precondition (Section 5.3.2.1)
 being violated.  Since this property is protected, it cannot be
 changed by clients using a PROPPATCH request.  However, clients can
 initialize the value of this property when creating a new calendar
 collection with MKCALENDAR.

It should say:

Conformance:  This property MAY be defined on any calendar
 collection.  If defined, it MAY be protected and SHOULD NOT be
 returned by a PROPFIND DAV:allprop request (as defined in Section
 12.14.1 of [RFC2518]).

Description: ... Any attempt by the client to store calendar object
 resource with component types not listed in this property, if it
 exists, MUST result in an error, with the
 CALDAV:supported-calendar-component precondition (Section 5.3.2.1)
 being violated.  Clients can initialize the value of this property
 when creating a new calendar collection with MKCALENDAR. …

Notes:

The protected status of supported-calendar-component-set is removed, so that CUAs can add component types to existing callendars, like VAVAILABILITY, which component types were not defined, when the calendar was created.

Report New Errata



Advanced Search