<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" category="std" consensus="true" docName="draft-stepanek-icalendar-jscalendar-extensions-00" obsoletes="" updates="" submissionType="IETF" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">
  <front>
    <title abbrev="iCalendar JSCalendar Extensions">iCalendar Format Extensions for JSCalendar</title>
    <author initials="R." surname="Stepanek" fullname="Robert Stepanek">
      <organization>Fastmail</organization>
      <address>
        <postal>
          <extaddr>PO Box 234</extaddr>
          <street>Collins St. West</street>
          <city>Melbourne</city>
          <region>VIC</region>
          <code>8007</code>
          <country>Australia</country>
        </postal>
        <email>rsto@fastmailteam.com</email>
      </address>
    </author>
    <date year="2025" month="May" day="13"/>
    <area>art</area>
    <workgroup>calext</workgroup>
    <keyword>calendars</keyword>
    <keyword>iCalendar</keyword>
    <keyword>JSCalendar</keyword>
    <abstract>
      <t>This document defines a set of new elements for iCalendar and extends the use of existing ones. Their main purpose is to extend the semantics of iCalendar with elements defined in JSCalendar, but the new definitions also aim to be useful within just the iCalendar format.  This document updates RFC 5545 ("Internet Calendaring and Scheduling Core Object Specification (iCalendar)").</t>
    </abstract>
  </front>
  <middle>
    <section>
      <name>Introduction</name>
      <t>The JSCalendar <xref target="I-D.stepanek-jscalendarbis"/> format aims to be an alternative to the iCalendar <xref target="RFC5545"/> format for representation of calendaring data.  As such, it introduces new semantics that are not covered in the current definition of iCalendar and its various extensions.  Converting calendaring data between the two formats is defined in <xref target="I-D.ietf-calext-jscalendar-icalendar"/> with the goal of not losing any semantics during conversion. To achieve this, this document defines new elements iCalendar and extends existing definitions. Doing so, it follows the recommendations for introducing new iCalendar elements as specified in <xref target="RFC7986" section="3"/>.</t>
      <section anchor="notational-conventions" numbered="true" toc="default">
        <name>Notational Conventions</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
      </section>
      <section anchor="abnf-notations">
        <name>ABNF Notations</name>
        <t>The ABNF definitions in this document use the notations of <xref target="RFC5234"/>. ABNF rules not defined in this document are defined in either <xref target="RFC5234"/> (such as the ABNF for CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT) or <xref target="RFC5545"/>.
        </t>
      </section>
    </section>
    <section>
      <name>Updated Properties</name>
      <section>
        <name>GEO Property</name>
        <t>This specification modifies the definition of the "GEO" property to also allow "geo" URI values <xref target="RFC5870"/> as property values. The following additions are made to the definition of this property, originally specified in <xref target="RFC5545" section="3.8.1.6"/>:</t>
        <dl>
          <dt>Value Type (replaces original):</dt>
          <dd>The default value type for this property is FLOAT, the value MUST be two SEMICOLON-separated FLOAT values. The value type can also be set to URI, in which case the VALUE parameter <bcp14>MUST</bcp14> be set.</dd>
          <dt>Description (in addition to original):</dt>
          <dd>
            <t>A Uniform Resource Identifier for Geographic Locations ("geo" URI) allows for richer semantics than the FLOAT value, such as defining geographic altitude, location uncertainty or the coordinate's reference system. The GEO property value <bcp14>MAY</bcp14> be of type URI to contain such coordinates. Property values of type URI <bcp14>MUST</bcp14> be valid according to the "geo" URI scheme syntax defined in <xref target="RFC5870" section="3.3"/>.</t>
          </dd>
          <dt>Format Definition (replaces original):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
geo         = geofloat / geouri

geofloat    = "GEO" geoparam ":" geovalue CRLF

geoparam    = *(";" other-param)

;Latitude and Longitude components
geovalue    = float ";" float

geouri      = "GEO" geouriparam ":" uri CRLF

geouriparam = *(
               ;
               ; The following is REQUIRED,
               ; but MUST NOT occur more than once.
               ;
               (";" "VALUE" "=" "URI") /
               ;
               ; The following is OPTIONAL,
               ; and MAY occur more than once.
               ;
               (";" other-param)
               ;
               )
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <t>The following are examples of this property:</t>
            <sourcecode name=""><![CDATA[
GEO:37.386013;-122.082932

GEO;VALUE=URI:geo:48.198634,16.371648;crs=wgs84;u=40
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="new-properties">
      <name>New Properties</name>
      <section anchor="prop-digest">
        <name>DIGEST Property</name>
        <dl>
          <dt>Property Name:</dt>
          <dd>DIGEST</dd>
          <dt>Purpose:</dt>
          <dd>To represent the result of a hash function or a checksum.</dd>
          <dt>Value Type:</dt>
          <dd>TEXT</dd>
          <dt>Property Parameters:</dt>
          <dd>The <xref target="param-hash">"HASH" parameter</xref> <bcp14>MUST</bcp14> be specified exactly once on this property. The "LANGUAGE" parameter <bcp14>MUST NOT</bcp14> be specified on this property. Other IANA and non-standard parameters <bcp14>MAY</bcp14> be specified on this property.</dd>
          <dt>Conformance:</dt>
          <dd>This property can be specified once in a "VLOCALIZATION" calendar component.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This property represents the result of a hash function or checksum algorithm. The semantics and purpose of its property value <bcp14>MUST</bcp14> be defined for each calendar component which allows to specify the "DIGEST" property. See the definition of the  <xref target="comp-vlocalization">"VLOCALIZATION" component</xref> for an example.</t>
            <t>This document defines the "Property Set Digest", which is the result of applying the hash function specified in the "HASH" parameter to a set of iCalendar properties. This digest is created as follows, all strings <bcp14>MUST</bcp14> be UTF-8 encoded and in <xref target="UNorm">Unicode Normalization Form NFC</xref>:</t>
            <ol>
              <li>For each property in the set, reorder its parameters in ascending order by comparing its parameter names, breaking ties by parameter value. Parameter names and parameter values in form "paramtext" compare in uppercase, parameter values in form "quoted-string" compare case-sensitively.</li>
              <li>For each sorted property, generate an unfolded content line. Every content line ends with the CRLF sequence.</li>
              <li>Sort the resulting content line strings in ascending order, then concatenate them to a single string, preserving their CRLF endings.</li>
              <li>Apply the hash function to the string and set the result as the "DIGEST" property value.</li>
            </ol>
            <t>The Property Set Digest can produce different digests for property sets that are semantically equivalent. This is because it does not enforce setting or removing default parameter values, or the "VALUE" parameter, or applying any other iCalendar-specific normalization. As a result, differing digests only indicate that <em>something</em> changed in the property set, but if this change is significant depends on the semantics of the calendar component that specifies using the "DIGEST" property.</t>
          </dd>
          <dt>Format Definition:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
digest      = "DIGEST" digestparam ":" TEXT CRLF

digestparam = *(
               ;
               ; The following is REQUIRED,
               ; but MUST NOT occur more than once.
               ;
               (";" hashparam )
               ;
               ; The following is OPTIONAL,
               ; and MAY occur more than once.
               ;
               (";" other-param)
               ;
               )
]]></sourcecode>
          </dd>
          <dt>Example:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
DIGEST;HASH=MD5:a16d6a19dd1d5c3baf591276eff96433
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section>
        <name>SHOW-WITHOUT-TIME Property</name>
        <dl>
          <dt>Property Name:</dt>
          <dd>SHOW-WITHOUT-TIME</dd>
          <dt>Purpose:</dt>
          <dd>To indicate that the exact time span is not important when displaying this calendar object.</dd>
          <dt>Value Type:</dt>
          <dd>BOOLEAN -- no default</dd>
          <dt>Property Parameters:</dt>
          <dd>IANA and non-standard parameters can be specified on this property.</dd>
          <dt>Conformance:</dt>
          <dd>This property can be specified once in a "VEVENT" or "VTODO" calendar component.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This indicates that the exact time span is not important to display to the user when rendering this calendar object. An example of this is an event that conceptually occurs all day, but in contrast to a DATE value is limited to a specific time zone or business hours. While the time component is important for free-busy calculations and checking for scheduling clashes, calendars may choose to display it as an all-day event and/or display the object separately to other objects to enhance the user's view of their schedule.</t>
            <t>This property only is for presentation purposes, it does not have any impact on the temporal characteristics of a calendar object.</t>
            <t>This property <bcp14>MAY</bcp14> be specified on VEVENT components where the DTSTART property is of type DATE-TIME, or in VTODO components where either the DTSTART or DUE property is specified and has type DATE-TIME. In all other cases it <bcp14>MUST NOT</bcp14> be set. If this property is set, its property value <bcp14>MUST</bcp14> be "TRUE", e.g. it <bcp14>MUST</bcp14> be omitted rather than having value "FALSE".</t>
            <t>Implementations that are unaware of the "SHOW-WITHOUT-TIME" property might inadvertently preserve this property when changing a calendar object's temporal type from DATE-TIME to DATE. Implementations <bcp14>SHOULD</bcp14> therefore ignore rather than reject the incorrectly specified SHOW-WITHOUT-TIME property. They <bcp14>MUST NOT</bcp14> preserve the ill-specified property in the calendaring data.</t>
          </dd>
          <dt>Format Definition:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
showwt      = "SHOW-WITHOUT-TIME" showwtparam ":" "TRUE" CRLF

showwtparam = *(
               ;
               ; The following is REQUIRED,
               ; but MUST NOT occur more than once.
               ;
               (";" "VALUE" "=" "BOOLEAN") /
               ;
               ; The following is OPTIONAL,
               ; and MAY occur more than once.
               ;
               (";" other-param)
               ;
               )
]]></sourcecode>
          </dd>
          <dt>Example:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
SHOW-WITHOUT-TIME;VALUE=BOOLEAN:TRUE
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="prop-uri">
        <name>URI Property</name>
        <dl>
          <dt>Property Name:</dt>
          <dd>URI</dd>
          <dt>Purpose:</dt>
          <dd>To associate a Uniform Resource Identifier (URI) with a calendar component.</dd>
          <dt>Value Type:</dt>
          <dd>URI -- no default</dd>
          <dt>Property Parameters:</dt>
          <dd>The "LANGUAGE" parameter <bcp14>MUST NOT</bcp14> be specified on this property. Other IANA and non-standard parameters can be specified on this property.</dd>
          <dt>Conformance:</dt>
          <dd>This property can be specified once in a "VCONFERENCE" calendar component.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This property associates a Uniform Resource Identifier <xref target="RFC3986"/> with a calendar component. In contrast to the "UID" property, which defines its values to be of type TEXT, this property requires its value to be a syntactically valid URI. In contrast to the "URL" property, this property neither provides a dynamic rendition of the associated calendar component, nor does it <em>locate</em> a resource - it only identifies the calendar component.</t>
            <t>The semantics and purpose of this identifier <bcp14>MUST</bcp14> be defined for each calendar component containing the "URI" property. This document defines the semantics of the "URI" property for the "VCONFERENCE" component. Similarly, future iCalendar extensions might consider using the "URI" property in cases where associating calendaring data by use of the "UID" and "RELATED-TO" properties is not possible.</t>
          </dd>
          <dt>Format Definition:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
uriprop     = "URI" uriparam ":" uri CRLF

uriparam = *(
            ;
            ; The following is REQUIRED,
            ; but MUST NOT occur more than once.
            ;
            (";" "VALUE" "=" "URI") /
            ;
            ; The following is OPTIONAL,
            ; and MAY occur more than once.
            ;
            (";" other-param)
            ;
            )
]]></sourcecode>
          </dd>
          <dt>Example:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
URI;VALUE=URI:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="new-parameters">
      <name>New Parameters</name>
      <section anchor="param-hash">
        <name>HASH Parameter</name>
        <dl>
          <dt>Parameter Name:</dt>
          <dd>HASH</dd>
          <dt>Purpose:</dt>
          <dd>To specify a hash function for a hash digest.</dd>
          <dt>Description:</dt>
          <dd>
            <t>In context of the "DIGEST" property, this parameter specifies the hash function that was used to create the property value. Any parameter value is allowed, it is not an enumerated value to allow future parameter values incorporate parameters for hash functions. The same case sensitivity as for other parameters value applies: "paramtext" values are case-insensitive, "quoted-string" values are case-sensitive. This document defines the semantics for the following parameter value:</t>
            <dl>
              <dt>Parameter Value:</dt>
              <dd>MD5 (case-insensitive)</dd>
              <dt>Description</dt>
              <dd>This produces the <xref target="RFC1321">MD5 Message-Digest</xref> from its input string. This hash <bcp14>MUST NOT</bcp14> be used for cryptographic purposes and the security considerations of <xref target="RFC6151"/> apply. The result of this hash is hex-encoded with all characters in lowercase.</dd>
            </dl>
          </dd>
          <dt>Format Definition:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
hashparam = "HASH" "=" param-value *("," param-value)
]]></sourcecode>
          </dd>
          <dt>Example:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
DIGEST;HASH=MD5:a16d6a19dd1d5c3baf591276eff96433
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="new-components">
      <name>New Components</name>
      <section>
        <name>VCONFERENCE Component</name>
        <dl>
          <dt>Component Name:</dt>
          <dd>VCONFERENCE</dd>
          <dt>Purpose:</dt>
          <dd>This component provides additional information about a virtual conference specified in the <xref target="RFC7986" section="5.11" sectionFormat="parens">CONFERENCE property</xref>.</dd>
          <dt>Conformance:</dt>
          <dd>This component can be specified multiple times in any component that allows to specify the "CONFERENCE" property.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This component augments information provided by the "CONFERENCE" property for a virtual meeting or conference. Specifically, this specification adds support for long-form plain text and rich-text descriptions, which can not feasibly be provided in the "LABEL" parameter of the "CONFERENCE" property.</t>
            <t>A "VCONFERENCE" component by itself does not represent a virtual meeting and it does not replace information provided by the "CONFERENCE" property. Instead, a calendar component that specifies the "VCONFERENCE" component <bcp14>MUST</bcp14> also specify a "CONFERENCE" property, and that "CONFERENCE" property value <bcp14>MUST</bcp14> match the value of the <xref target="prop-uri">"URI" property</xref> specified in the "VCONFERENCE" component. The URI values <bcp14>MUST</bcp14> be equal character strings, as specified in <xref target="RFC3986" section="6"/>.</t>
            <t>A "VCONFERENCE" component <bcp14>MAY</bcp14> contain one "DESCRIPTION" property and multiple "STYLED-DESCRIPTION" properties, but one of them <bcp14>MUST NOT</bcp14> specify the "DERIVED" parameter and all others <bcp14>MUST</bcp14> specify the "DERIVED" parameter (e.g. it must have one and only one non-derived description). For future extensibility, this specification does not define the "DESCRIPTION" or "STYLED-DESCRIPTION" properties to be mandatory, but a "VCONFERENCE" component <bcp14>MUST</bcp14> contain at least one property other than the "URI" property.</t>
            <t>Implementations that are unaware of the "VCONFERENCE" component might inadvertently preserve this component when removing its related "CONFERENCE" property from the calendar object. Changing the URI value of the "CONFERENCE" property is in this context considered a removal followed by inserting a new element. Implementations <bcp14>SHOULD</bcp14> therefore ignore rather than reject such incorrectly specified "VCONFERENCE" components. They <bcp14>MUST NOT</bcp14> preserve the ill-specified component in the calendaring data.</t>
          </dd>
          <dt>Format Definition:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
vconfc    = "BEGIN" ":" "VCONFERENCE" CRLF
            *(
             ;
             ; The following are REQUIRED,
             ; but MUST NOT occur more than once.
             ;
             uriprop /
             ;
             ; The following are OPTIONAL,
             ; but MUST NOT occur more than once.
             ;
             description /
             ;
             ; The following are OPTIONAL,
             ; and MAY occur more than once
             ;
             styleddescription
             ;
             ;
             ; The following are OPTIONAL,
             ; and MAY occur more than once.
             ;
             x-prop / iana-prop
             ;
             )
            "END" ":" "VCONFERENCE" CRLF
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <t>The following is an example of this component:</t>
            <sourcecode name=""><![CDATA[
BEGIN:VCONFERENCE
URI;VALUE=URI:https://chat.example.com/x?id=123456
DESCRIPTION:This is the first in a series of sessions:\n
 ...
END:VCONFERENCE
CONFERENCE;VALUE=URI;FEATURE=AUDIO,VIDEO;
 LABEL=Product Brainstorming Session:https://chat.example.com/x?id=123456
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="comp-vlocalization">
        <name>VLOCALIZATION Component</name>
        <dl>
          <dt>Component Name:</dt>
          <dd>VLOCALIZATION</dd>
          <dt>Purpose:</dt>
          <dd>To provide internationalized and localized alternate text representations of calendar component elements.</dd>
          <dt>Conformance:</dt>
          <dd>This component can be specified multiple times in any component that allows to specify at least one property with the "LANGUAGE" parameter.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This component provides internationalized and localized alternate text representations of properties specified in a calendar component. Its main purpose is for use with descriptive elements such as the "SUMMARY" or "DESCRIPTION" properties, but it <bcp14>MAY</bcp14> be used with any property on which the "LANGUAGE" parameter can be set.</t>
            <t>A "VLOCALIZATION" component <bcp14>MUST</bcp14> contain one or more properties which each <bcp14>MUST</bcp14> specify exactly once the "LANGUAGE" parameter. The "LANGUAGE" parameter values <bcp14>MAY</bcp14> differ between properties. The component <bcp14>MUST</bcp14> specify the <xref target="prop-uri">"URI" property</xref> exactly once. A calendar component that contains the "VLOCALIZATION" component is then localized to a specific human language by replacing all its properties where the "ALTREP" parameter value matches the "URI" property value of the "VLOCALIZATION" with those properties in the "VLOCALIZATION" component, for which the "LANGUAGE" parameter value matches the language tag of the target human language.</t>
            <t>The localized calendar component <bcp14>MUST</bcp14> be valid, e.g. mandatory properties <bcp14>MUST</bcp14> be set. The URI values of the "ALTREP" parameter and "URI" property <bcp14>MUST</bcp14> be compared as character strings, as specified in <xref target="RFC3986" section="6"/>. The URI value <bcp14>MUST</bcp14> be a valid URI in the "urn" scheme <xref target="RFC8141"/> with namespace identifier "uuid" <xref target="RFC9562"/>.</t>
            <t>The "VLOCALIZATION" component <bcp14>SHOULD</bcp14> only contain properties for which a property of the same name also is specified in the non-localized component, e.g. a "VLOCALIZATION" component is only meant to provide alternate text representations, not to add new content.</t>
            <t>Implementations that are unaware of the "VLOCALIZATION" component might change property values in the non-localized component, inadvertently invalidating the contents of the localized properties. To mitigate this, implementations <bcp14>MUST</bcp14> specify the <xref target="prop-digest">"DIGEST"</xref> property at least once in the "VLOCALIZATION" component. The property value <bcp14>MUST</bcp14> be the "Property Set Digest" as defined in <xref target="prop-digest"/>, where the property set consists of all those properties in the non-localized component, for which the "ALTREP" parameter value matches the "URI" property value of the "VLOCALIZATION" component. The "ALTREP" parameter is part of the hashed property. Multiple "DIGEST" properties <bcp14>MUST</bcp14> each specify a different "HASH" parameter value.</t>
            <t>Implementations <bcp14>MUST</bcp14> consider a "VLOCALIZATION" component as outdated, if the "DIGEST" property value does not match the expected digest. How to handle outdated localizations is implementation-specific, but implementations <bcp14>MUST</bcp14> not preserve "VLOCALIZATION" components with outdated "DIGEST" property values.</t>
          </dd>
          <dt>Format Definition:</dt>
          <dd>
            <sourcecode name=""><![CDATA[
vlocalizationc = "BEGIN" ":" "VLOCALIZATION" CRLF
                 *(
                  ;
                  ; The following is REQUIRED,
                  ; but MUST NOT occur more than once.
                  ;
                  uriprop
                  ;
                  ; The following is REQUIRED,
                  ; and MAY occur more than once.
                  ; "HASH" parameter values MUST differ.
                  ;
                  digest
                  ;
                  ; The following are OPTIONAL,
                  ; and MAY occur more than once.
                  ; At least one MUST have the
                  ; "LANGUAGE" parameter set.
                  ;  
                  x-prop / iana-prop
                  ;
                  )
                 "END" ":" "VLOCALIZATION" CRLF
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <t>The following is an example of this component:</t>
            <sourcecode name=""><![CDATA[
DTSTART;VALUE=DATE:20250701
SUMMARY;LANGUAGE="en-ca"
 ;ALTREP="urn:uuid:cd92c017-f7b0-4ac1-a852-c1d28ab172e5"
 :Canada Day
DESCRIPTION;LANGUAGE="en-ca"
 ;ALTREP="urn:uuid:cd92c017-f7b0-4ac1-a852-c1d28ab172e5"
 :Canada Day celebrates the anniversary of Canadian Confederation
 which occurred on July 1, 1867.
BEGIN:VLOCALIZATION
URI;VALUE=URI:urn:uuid:cd92c017-f7b0-4ac1-a852-c1d28ab172e5
DIGEST;HASH=MD5:863f0708251b33990b43830a8ca754e4
SUMMARY;LANGUAGE="fr-ca"
 :Fête du Canada
DESCRIPTION;LANGUAGE="fr-ca"
 :La Fête du Canada est un jour férié commémorant la date de
 formation du Canada le 1er juillet 1867.
END:VLOCALIZATION
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This specification extends <xref target="RFC5545"/>.  The same security considerations as outlined in <xref target="RFC5545" sectionFormat="of" section="7"/> apply. In addition, <xref target="param-hash"/> refers to the security considerations of the MD5 Message-Digest Algorithm.</t>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <t>TBD</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.1321.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.3986.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5234.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5545.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5870.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.6151.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.7986.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8141.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.9562.xml"/>
      </references>
    </references>
    <references>
      <name>Informative References</name>
      <reference anchor="I-D.ietf-calext-jscalendar-icalendar" target="https://datatracker.ietf.org/doc/draft-ietf-calext-jscalendar-icalendar/">
        <front>
          <title>JSCalendar: Converting from and to iCalendar</title>
          <author fullname="Robert Stepanek" initials="R." surname="Stepanek">
            <organization>Fastmail</organization>
          </author>
          <date day="12" month="May" year="2025"/>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-calext-jscalendar-icalendar"/>
      </reference>
      <reference anchor="I-D.stepanek-jscalendarbis" target="https://datatracker.ietf.org/doc/draft-stepanek-jscalendarbis/">
        <front>
          <title>JSCalendar: A JSON Representation of Calendar Data</title>
          <author fullname="Neil Jenkins" initials="N.M." surname="Jenkins">
            <organization>Fastmail</organization>
          </author>
          <author fullname="Robert Stepanek" initials="R." surname="Stepanek">
            <organization>Fastmail</organization>
          </author>
          <date day="12" month="May" year="2025"/>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-stepanek-jscalendarbis"/>
      </reference>
      <reference anchor="UNorm" target="https://www.unicode.org/reports/tr15/" quoteTitle="false">
        <front>
          <title>UTS #15, Unicode Normalization Forms</title>
          <author/>
          <date/>
        </front>
      </reference>
    </references>
    <section anchor="acknowledgments" numbered="false">
      <name>Acknowledgments</name>
      <t>The descriptions of Canada Day in the example in <xref target="comp-vlocalization"/> were copied from the <eref target="https://en.wikipedia.org/wiki/Canada_Day">English Wikipedia website</eref> which makes the text available under the <eref target="https://en.wikipedia.org/wiki/Wikipedia:Text_of_the_Creative_Commons_Attribution-ShareAlike_4.0_International_License">Creative Commons Attribution-ShareAlike 4.0 License</eref>.</t>
    </section>
  </back>
</rfc>
