From: Sean Turner <sean@sn3rd.com>
Message-Id: <9C9169D9-D04E-4476-AB6F-2F6164F652AD@sn3rd.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DC451994-C991-4069-9DE2-0CAE5BDCA5C5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Date: Mon, 15 Sep 2025 13:16:55 -0400
In-Reply-To: <89d5492e-50a9-4741-9c16-1b85a6a47552@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
References: 
 <175758091288.79361.11152252738330348294@dt-datatracker-f7c8fdcb7-pjx77>
 <06072BBA-4074-4E75-AA80-5F7ADD767398@akayla.com>
 <89d5492e-50a9-4741-9c16-1b85a6a47552@erg.abdn.ac.uk>
Message-ID-Hash: YIIBYCFWE3IGSKEWNYMJSAHTX6L6TXWS
CC: Joseph Mandel <joe@akayla.com>, The IESG <iesg@ietf.org>,
 draft-ietf-lamps-rfc5273bis@ietf.org, lamps-chairs@ietf.org, spasm@ietf.org,
 Russ Housley <housley@vigilsec.com>
Precedence: list
Subject: =?utf-8?q?=5Blamps=5D_Re=3A_Gorry_Fairhurst=27s_No_Objection_on_draft-ietf-l?=
 =?utf-8?q?amps-rfc5273bis-08=3A_=28with_COMMENT=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/spasm/x_XpouCTHLzQnBnRf7W5KcLOPYk>


--Apple-Mail=_DC451994-C991-4069-9DE2-0CAE5BDCA5C5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Gorry,

Do me a favor and look at my resposnes to Eric=E2=80=99 comments on 5272 =
& 5273 in relation to QUIC. I want to make sure it makes sense to you =
too.

spt

> On Sep 13, 2025, at 03:36, Gorry Fairhurst <gorry@erg.abdn.ac.uk> =
wrote:
>=20
> On 12/09/2025 20:38, Joe Mandel wrote:
>> Gorry,=20
>>=20
>> Thanks for the comments. We made those changes: =
https://github.com/lamps-wg/cmcbis/pull/126=20
>>=20
>> Joe
> Thanks for these updates,
>=20
> Gorry
>=20
>>=20
>>> On Sep 11, 2025, at 1:55=E2=80=AFAM, Gorry Fairhurst via Datatracker =
<noreply@ietf.org> <mailto:noreply@ietf.org> wrote:
>>>=20
>>> Gorry Fairhurst has entered the following ballot position for
>>> draft-ietf-lamps-rfc5273bis-08: No Objection
>>>=20
>>> When responding, please keep the subject line intact and reply to =
all
>>> email addresses included in the To and CC lines. (Feel free to cut =
this
>>> introductory paragraph, however.)
>>>=20
>>>=20
>>> Please refer to =
https://www.ietf.org/about/groups/iesg/statements/handling-ballot-position=
s/=20
>>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>>=20
>>>=20
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc5273bis/
>>>=20
>>>=20
>>>=20
>>> =
----------------------------------------------------------------------
>>> COMMENT:
>>> =
----------------------------------------------------------------------
>>>=20
>>> Please find 3 non-blocking COMMENTS, these concern the =
recommendations for the
>>> use of ports:
>>>=20
>>> (1) The current text says:
>>> /Client implementations MAY want to continue to allow for this to =
occur/
>>> - I know this is taken from a published RFC, but, for me, permitting =
a =E2=80=9Cwish=E2=80=9D
>>> using an RFC2119 keyword does not say anything useful. Please =
consider if this
>>> MAY could be rewritten to say which port (range) this requirement =
refers to,
>>> and avoids saying =E2=80=9Cwant=E2=80=9D. Perhaps something like: -  =
=E2=80=9CClient implementations
>>> MAY continue to use a port chosen from the Private Port range=E2=80=9D=
.
>>>=20
>>> (2) The current text says:
>>> /Servers SHOULD change to use the new port. /
>>> - Please could you update the text to clarify which service uses the =
=E2=80=9Cnew port=E2=80=9D
>>> ? Is it: TCP? HTTP/TCP? both? - I=E2=80=99d strongly also suggest =
noting the port
>>> number in the sentence with the RFC2119 keyword e.g.: A TCP server =
SHOULD use
>>> port  5318 assigned to the CMC service. Prior to [RFC6402], CMC did =
not have a
>>> registered port number and used an externally configured port from =
the Private
>>> Port range.
>>>=20
>>> (3) I was going to raise a DISCUSS on the final comment, but I=E2=80=99=
m not sure this
>>> is critical, and I expect some rewording will clarify the port =
usage: It seems
>>> like the client and the server could use different ways to identify =
the
>>> service. I think that possibility seems like it needs more =
clarification.
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Spasm mailing list -- spasm@ietf.org <mailto:spasm@ietf.org>
>>> To unsubscribe send an email to spasm-leave@ietf.org =
<mailto:spasm-leave@ietf.org>
>>=20
>=20


--Apple-Mail=_DC451994-C991-4069-9DE2-0CAE5BDCA5C5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: =
after-white-space;">Gorry,<div><br></div><div>Do me a favor and look at =
my resposnes to Eric=E2=80=99 comments on 5272 &amp; 5273 in relation to =
QUIC. I want to make sure it makes sense to you =
too.</div><div><br></div><div>spt<br =
id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>On Sep 13, 2025, at 03:36, Gorry Fairhurst =
&lt;gorry@erg.abdn.ac.uk&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div>

 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-8">
 =20
  <div>
    <div class=3D"moz-cite-prefix">On 12/09/2025 20:38, Joe Mandel =
wrote:<br>
    </div>
    <blockquote type=3D"cite" =
cite=3D"mid:06072BBA-4074-4E75-AA80-5F7ADD767398@akayla.com">
      <meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3DUTF-8">
      <div dir=3D"auto" style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">Gorry,&nbsp;
        <div><br>
        </div>
        <div>Thanks for the comments. We made those changes:&nbsp;<a =
href=3D"https://github.com/lamps-wg/cmcbis/pull/126" =
moz-do-not-send=3D"true" =
class=3D"moz-txt-link-freetext">https://github.com/lamps-wg/cmcbis/pull/12=
6</a>&nbsp;</div>
        <div><br>
        </div>
        <div>Joe<br id=3D"lineBreakAtBeginningOfMessage">
        </div>
      </div>
    </blockquote><p>Thanks for these updates,</p><p>Gorry</p>
    <blockquote type=3D"cite" =
cite=3D"mid:06072BBA-4074-4E75-AA80-5F7ADD767398@akayla.com">
      <div dir=3D"auto" style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">
        <div>
          <div><br>
            <blockquote type=3D"cite">
              <div>On Sep 11, 2025, at 1:55=E2=80=AFAM, Gorry Fairhurst =
via
                Datatracker <a class=3D"moz-txt-link-rfc2396E" =
href=3D"mailto:noreply@ietf.org">&lt;noreply@ietf.org&gt;</a> =
wrote:</div>
              <br class=3D"Apple-interchange-newline">
              <div>
                <div>Gorry Fairhurst has entered the following ballot
                  position for<br>
                  draft-ietf-lamps-rfc5273bis-08: No Objection<br>
                  <br>
                  When responding, please keep the subject line intact
                  and reply to all<br>
                  email addresses included in the To and CC lines. (Feel
                  free to cut this<br>
                  introductory paragraph, however.)<br>
                  <br>
                  <br>
                  Please refer to
<a class=3D"moz-txt-link-freetext" =
href=3D"https://www.ietf.org/about/groups/iesg/statements/handling-ballot-=
positions/">https://www.ietf.org/about/groups/iesg/statements/handling-bal=
lot-positions/</a>
                  <br>
                  for more information about how to handle DISCUSS and
                  COMMENT positions.<br>
                  <br>
                  <br>
                  The document, along with other ballot positions, can
                  be found here:<br>
<a class=3D"moz-txt-link-freetext" =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc5273bis/">htt=
ps://datatracker.ietf.org/doc/draft-ietf-lamps-rfc5273bis/</a><br>
                  <br>
                  <br>
                  <br>
=
----------------------------------------------------------------------<br>=

                  COMMENT:<br>
=
----------------------------------------------------------------------<br>=

                  <br>
                  Please find 3 non-blocking COMMENTS, these concern the
                  recommendations for the<br>
                  use of ports:<br>
                  <br>
                  (1) The current text says:<br>
                  /Client implementations MAY want to continue to allow
                  for this to occur/<br>
                  - I know this is taken from a published RFC, but, for
                  me, permitting a =E2=80=9Cwish=E2=80=9D<br>
                  using an RFC2119 keyword does not say anything useful.
                  Please consider if this<br>
                  MAY could be rewritten to say which port (range) this
                  requirement refers to,<br>
                  and avoids saying =E2=80=9Cwant=E2=80=9D. Perhaps =
something like: -
                  &nbsp;=E2=80=9CClient implementations<br>
                  MAY continue to use a port chosen from the Private
                  Port range=E2=80=9D.<br>
                  <br>
                  (2) The current text says:<br>
                  /Servers SHOULD change to use the new port. /<br>
                  - Please could you update the text to clarify which
                  service uses the =E2=80=9Cnew port=E2=80=9D<br>
                  ? Is it: TCP? HTTP/TCP? both? - I=E2=80=99d strongly =
also
                  suggest noting the port<br>
                  number in the sentence with the RFC2119 keyword e.g.:
                  A TCP server SHOULD use<br>
                  port &nbsp;5318 assigned to the CMC service. Prior to
                  [RFC6402], CMC did not have a<br>
                  registered port number and used an externally
                  configured port from the Private<br>
                  Port range.<br>
                  <br>
                  (3) I was going to raise a DISCUSS on the final
                  comment, but I=E2=80=99m not sure this<br>
                  is critical, and I expect some rewording will clarify
                  the port usage: It seems<br>
                  like the client and the server could use different
                  ways to identify the<br>
                  service. I think that possibility seems like it needs
                  more clarification.<br>
                  <br>
                  <br>
                  <br>
                  _______________________________________________<br>
                  Spasm mailing list -- <a =
class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:spasm@ietf.org">spasm@ietf.org</a><br>
                  To unsubscribe send an email to <a =
class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:spasm-leave@ietf.org">spasm-leave@ietf.org</a><br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote><p><br>
    </p>
  </div>

</div></blockquote></div><br></div></body></html>=

--Apple-Mail=_DC451994-C991-4069-9DE2-0CAE5BDCA5C5--