Feedback-ID: ia5d944da:Fastmail
MIME-Version: 1.0
Date: Mon, 19 Jan 2026 16:49:13 +0100
From: "Robert Stepanek" <rsto@fastmailteam.com>
To: calsify@ietf.org
Message-Id: <28f107ec-9269-443a-a452-30f8e9ddfd2c@app.fastmail.com>
In-Reply-To: <431e15d7-bfe2-49b6-bb63-28ed6c1cf694@gmail.com>
References: 
 <176253720795.1457955.14139416645668213448@dt-datatracker-5df8666cb-7l4w5>
 <577927e5-8e02-4ab4-8c9d-7956511822ec@dogfoodapp.fastmail.com>
 <431e15d7-bfe2-49b6-bb63-28ed6c1cf694@gmail.com>
Content-Type: multipart/alternative;
 boundary=3fcdbdf0545744f79ed82097400c5645
Message-ID-Hash: 4YRULUJDZAKEXKC5L4UWMCBLKYCVI4UX
Precedence: list
Subject: =?utf-8?q?=5Bcalsify=5D_Re=3A_WG_Last_Call=3A_draft-ietf-calext-icalendar-js?=
 =?utf-8?q?calendar-extensions-03_=28Ends_2025-12-19=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/calsify/itChjUEMAceMfmmQF9yERGang8o>

--3fcdbdf0545744f79ed82097400c5645
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Daniel,

thanks for the review. I now published version draft-ietf-calext-icalendar-jscalendar-extensions-05 <https://www.ietf.org/archive/id/draft-ietf-calext-icalendar-jscalendar-extensions-05.html>. Replies inline.

On Wed, Jan 7, 2026, at 6:20 PM, Daniel Migault wrote:
> The IANA section needs to be completed.
> 

Done.

> 12. Have reasonable efforts been made to remind all authors of the intellectual
>     property rights (IPR) disclosure obligations described in [BCP 79][7]? To
>     the best of your knowledge, have all required disclosures been filed?

Yes.
 
> 13. Has each author, editor, and contributor shown their willingness to be
>     listed as such? If the total number of authors and editors on the front page
>     is greater than five, please provide a justification.

Yes.

> 19. Will publication of this document change the status of any existing RFCs? If
>     so, does the Datatracker metadata correctly reflect this and are those RFCs
>     listed on the title page, in the abstract, and discussed in the
>     introduction? If not, explain why and point to the part of the document
>     where the relationship of this document to these other RFCs is discussed.

Yes. I updated the metadata, abstract and introduction accordingly.

> The ABNF parser (https://author-tools.ietf.org/abnf) returns some issues with the models. CRLF is undefined, but I am wondering if that is not because text is undefined as the following lines parses correctly:

The ABNF parser reports the following errors for draft-ietf-calext-icalendar-jscalendar-extensions-04:

; text UNDEFINED
; CRLF UNDEFINED
; other-param UNDEFINED
; uri UNDEFINED

But section 1.2. "ABNF Notations" states that the ABNFs in this document use definitions of RFC 5234 and RFC 5545. The ABNFs for "text", "other-param" and "uri" are defined in RFC 5545, the ABNF for "CRLF" is defined in RFC 5234. The issue is that the ABNF tool seems to only be able consider ABNFs defined in the same document and not consider ABNFs defined in other documents. I see no action required for this document.

Regards,
Robert
--3fcdbdf0545744f79ed82097400c5645
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>Hi Daniel,</=
div><div><br></div><div>thanks for the review. I now published version <=
a href=3D"https://www.ietf.org/archive/id/draft-ietf-calext-icalendar-js=
calendar-extensions-05.html">draft-ietf-calext-icalendar-jscalendar-exte=
nsions-05</a>. Replies inline.</div><div><br></div><div>On Wed, Jan 7, 2=
026, at 6:20 PM, Daniel Migault wrote:</div><blockquote type=3D"cite" id=
=3D"qt" style=3D""><p>The IANA section needs to be completed.</p></block=
quote><div><br></div><div>Done.</div><div><br></div><blockquote type=3D"=
cite" id=3D"qt" style=3D""><div><div>12. Have reasonable efforts been ma=
de to remind all authors of the=0A      intellectual</div><div>&nbsp;&nb=
sp;&nbsp; property rights (IPR) disclosure obligations described in [BCP=
=0A      79][7]? To</div><div>&nbsp;&nbsp;&nbsp; the best of your knowle=
dge, have all required disclosures been=0A      filed?</div></div></bloc=
kquote><div><br></div><div>Yes.</div><div>&nbsp;</div><blockquote type=3D=
"cite" id=3D"qt" style=3D""><div><div>13. Has each author, editor, and c=
ontributor shown their=0A      willingness to be</div><div>&nbsp;&nbsp;&=
nbsp; listed as such? If the total number of authors and editors on=0A  =
    the front page</div><div>&nbsp;&nbsp;&nbsp; is greater than five, pl=
ease provide a justification.</div></div></blockquote><div><br></div><di=
v>Yes.</div><div><br></div><blockquote type=3D"cite" id=3D"qt" style=3D"=
"><div><div>19. Will publication of this document change the status of a=
ny=0A      existing RFCs? If</div><div>&nbsp;&nbsp;&nbsp; so, does the D=
atatracker metadata correctly reflect this and=0A      are those RFCs</d=
iv><div>&nbsp;&nbsp;&nbsp; listed on the title page, in the abstract, an=
d discussed in=0A      the</div><div>&nbsp;&nbsp;&nbsp; introduction? If=
 not, explain why and point to the part of the=0A      document</div><di=
v>&nbsp;&nbsp;&nbsp; where the relationship of this document to these ot=
her RFCs is=0A      discussed.</div></div></blockquote><div><br></div><d=
iv>Yes. I updated the metadata, abstract and introduction accordingly.</=
div><div><br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><div><=
div>The ABNF parser (<a class=3D"qt-moz-txt-link-freetext" href=3D"https=
://author-tools.ietf.org/abnf">https://author-tools.ietf.org/abnf</a>) r=
eturns some=0A      issues with the models. CRLF is undefined, but I am =
wondering if=0A      that is not because text is undefined as the follow=
ing lines=0A      parses correctly:</div></div></blockquote><div><br></d=
iv><div>The ABNF parser reports the following errors for draft-ietf-cale=
xt-icalendar-jscalendar-extensions-04:</div><div><br></div><div>; text U=
NDEFINED</div><div>; CRLF UNDEFINED</div><div>; other-param UNDEFINED</d=
iv><div>; uri UNDEFINED</div><div><br></div><div>But section 1.2. "ABNF =
Notations" states that the ABNFs in this document use definitions of RFC=
 5234 and RFC 5545. The ABNFs for "text", "other-param" and "uri" are de=
fined in RFC 5545, the ABNF for "CRLF" is defined in RFC 5234. The issue=
 is that the ABNF tool seems to only be able consider ABNFs defined in t=
he same document and not consider ABNFs defined in other documents. I se=
e no action required for this document.</div><div><br></div><div>Regards=
,</div><div>Robert</div></body></html>
--3fcdbdf0545744f79ed82097400c5645--