Content-Type: multipart/alternative;
 boundary="------------No6o49p4GTzavtKOUodVzqQg"
Message-ID: <f0741217-62db-4b49-8232-d04d4e9a9719@gmail.com>
Date: Tue, 5 Aug 2025 23:50:18 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: secdir@ietf.org
Content-Language: en-US
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID-Hash: Y35FA2GKYN53GMKAUU6ZH7OWE3HXXRBB
Precedence: list
Subject: =?utf-8?q?=5Bsecdir=5D_Re=3A_Secdir_last_call_review_of_draft-ietf-calext-ic?=
 =?utf-8?q?al-tasks-13?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/secdir/xGK5zhhruDk36ryO5S0kkPi9HQk>

This is a multi-part message in MIME format.
--------------No6o49p4GTzavtKOUodVzqQg
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

See below for comments.

The updated spec is visible at 
https://calconnect.github.io/cc-ical-tasks/documents/draft-ietf-calext-ical-tasks.html 


> Reviewer: Joseph Salowey
> Review result: Has Issues
>
> I have reviewed this document as part of security directorate review.
>
> I think the document has one issue that should be addressed.  Shouldn't this
> document also reference RFC9253 in the security consideration since ti is
> dealing with Links?
Thanks - added the reference

--------------No6o49p4GTzavtKOUodVzqQg
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>See below for comments.
      <br>
      <br>
      The updated spec is visible at <a class="moz-txt-link-freetext"
href="https://calconnect.github.io/cc-ical-tasks/documents/draft-ietf-calext-ical-tasks.html">https://calconnect.github.io/cc-ical-tasks/documents/draft-ietf-calext-ical-tasks.html</a>
      <br>
      <blockquote type="cite">
        <pre class="wordwrap">Reviewer: Joseph Salowey
Review result: Has Issues

I have reviewed this document as part of security directorate review.

I think the document has one issue that should be addressed.  Shouldn't this
document also reference RFC9253 in the security consideration since ti is
dealing with Links?</pre>
      </blockquote>
      Thanks - added the reference<br>
    </p>
  </body>
</html>

--------------No6o49p4GTzavtKOUodVzqQg--