RFC Errata
RFC 2739, "Calendar Attributes for vCard and LDAP", January 2000
Note: This RFC has been updated by RFC 6350
Source of RFC: calsch (app)See Also: RFC 2739 w/ inline errata
Errata ID: 6624
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Prakhar Makhija
Date Reported: 2021-06-30
Verifier Name: RFC Editor
Section 2.3.3 says:
2.3.3 CAPURI Property IANA Registration To: ietf-mime-directory@imc.org Subject: Registration of CAPURI type for application/directory MIME type vCard profile. Type name: CAPURI Type purpose: To specify a protocol independent location from which a calendaring and scheduling client (i.e., CUA) can communicate with a user's entire calendar. Type encoding: 8bit Type value: A single URI value. Type special notes: Where multiple CAPURI properties are specified, the default CAPURI property is indicated with the PREF parameter. Intended usage: Refer to section 1.3.
It should say:
2.3.3 CAPURI Property IANA Registration To: ietf-mime-directory@imc.org Subject: Registration of CAPURI type for application/directory MIME type vCard profile. Type name: CAPURI Type purpose: To specify a protocol independent location from which a calendaring and scheduling client (i.e., CUA) can communicate with a user's entire calendar. Type encoding: 8bit Type value: A single URI value. Type special notes: Where multiple CAPURI properties are specified, the default CAPURI property is indicated with the PREF parameter. Intended usage: Refer to section 1.2.
Notes:
Usage Reference Section was incorrect