iCalendar.org

  * [ Home  ](/Home.html)
  * Specifications ****
    * [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
    * [ New Properties for iCalendar (RFC 7986)  ](/RFC-Specifications/iCalendar-RFC-7986/)
    * [ iCalendar Venue (Draft)  ](/RFC-Specifications/iCalendar-Venue-Draft/)
    * [ CalDAV Access (RFC 4791)  ](/RFC-Specifications/CalDAV-Access-RFC-4791/)
    * [ CalDAV Scheduling (RFC 6638)  ](/RFC-Specifications/CalDAV-Scheduling-RFC-6638/)
  * [ Validator  ](/validator.html)
  * [ PHP Library  ](/php-library.html)
  * [ RRULE Tool  ](/rrule-tool.html)
  * [ Resources  ](/resources.html)
  * [ News  ](/News/)
  * [ Contact Us  ](/contact-us.html)

[ ![iCalendar.org](https://icalendar.org/images/clipart/icalendar600.png) ](/)

  1. You are here: 
  2. [ Home  ](/Home.html)
  3. [ Specifications  ](/RFC-Specifications/all/)
  4. [ iCalendar (RFC 5545)  ](/RFC-Specifications/iCalendar-RFC-5545/)
  5. 8.2.1. iCalendar Elements Registration Procedure 

Try out our new [ RRULE tool ](/rrule-tool.html) for creating RRULE compatible
strings.

#  8.2.1. iCalendar Elements Registration Procedure

f  Share

URL

The IETF will create a mailing list, icalendar@ietf.org, which can be used for
public discussion of iCalendar elements proposals prior to registration. Use
of the mailing list is strongly encouraged. The IESG will appoint a designated
expert who will monitor the icalendar@ietf.org mailing list and review
registrations.

Registration of new iCalendar elements MUST be reviewed by the designated
expert and published in an RFC. A Standards Track RFC is REQUIRED for the
registration of new value data types that modify existing properties, as well
as for the registration of participation status values to be used in [
"VEVENT" ](/iCalendar-RFC-5545/3-6-1-event-component.html) calendar
components. A Standards Track RFC is also REQUIRED for registration of
iCalendar elements that modify iCalendar elements previously documented in a
Standards Track RFC.

The registration procedure begins when a completed registration template,
defined in the sections below, is sent to icalendar@ietf.org and
iana@iana.org. The designated expert is expected to tell IANA and the
submitter of the registration within two weeks whether the registration is
approved, approved with minor changes, or rejected with cause. When a
registration is rejected with cause, it can be re-submitted if the concerns
listed in the cause are addressed. Decisions made by the designated expert can
be appealed to the IESG Applications Area Director, then to the IESG. They
follow the normal appeals procedure for IESG decisions.

[ Previous article: 8.2. New iCalendar Elements Registration  Prev
](/iCalendar-RFC-5545/8-2-new-icalendar-elements-registration.html) [ Next
article: 8.2.2. Registration Template for Components  Next  ](/iCalendar-
RFC-5545/8-2-2-registration-template-for-components.html)

_This document was automatically converted to XHTML using an RFC to HTML
converter with the original text document at the Internet Engineering Task
Force web site at[ ietf.org ](http://www.ietf.org) . The original text
document should be referred to if there are any errors or discrepancies found
in this document. _

###  Need to test your iCalendar feeds?

The [ iCalendar Validator ](/validator.html) provides developers and testers a
method to validate their iCalendar feeds, which can take data from either a
URL, file or text snippet and compare it against the [ RFC 5545 specification
](/RFC-Specifications/iCalendar-RFC-5545/) . We believe we have one of the
best iCalendar validation tools available on the internet. More information
about the validator can be [ found here ](/More-Info/about-the-icalendar-
validator.html) .

This site is maintained by [ Z Content ](http://zcontent.net) , a developer of
PHP iCalendar tools for the Joomla Content Management System. It is hoped this
site will help foster the use of iCalendar and open standards.

Read our [ priva