Content-Type: multipart/alternative;
 boundary="------------eRbaavkMBtIzcQ5VhxQaged5"
Message-ID: <4acb2653-7c70-4534-86b1-c17bfa1c97a5@erg.abdn.ac.uk>
Date: Mon, 11 Aug 2025 14:18:05 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: "Dale R. Worley" <worley@ariadne.com>, tievens@cisco.com,
 gen-art@ietf.org, draft-ietf-tsvwg-usr-exp.all@ietf.org, last-call@ietf.org,
 tsvwg@ietf.org
References: <87a549ipp2.fsf@hobgoblin.ariadne.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: UNIVERSITY OF ABERDEEN
In-Reply-To: <87a549ipp2.fsf@hobgoblin.ariadne.com>
Message-ID-Hash: Y7ILQQ6UWWIL5ITWNMOQELWVWMCVF6YW
Precedence: list
Subject: =?utf-8?q?=5Btsvwg=5D_Re=3A_=5BGen-art=5D_Re=3A_draft-ietf-tsvwg-usr-exp-10_?=
 =?utf-8?q?ietf_last_call_Genart_review?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/tsvwg/wkwI_LlaCra1Ku6As_mCaq8Yy_Q>

This is a multi-part message in MIME format.
--------------eRbaavkMBtIzcQ5VhxQaged5
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 08/08/2025 20:22, Dale R. Worley wrote:
> worley@ariadne.com (Dale R. Worley) writes:
>> - In section 4, there is much discussion of PExIDs but you have to read
>>    the whole section very carefully to find out what they *are*.  I
>>    suggest that the section start with a paragraph that explains that:
>>
>>     A PExID is a 32-bit unsigned integer encoded in network standard byte
>>     order.  It is used in an experimental protocol by being prepended to
>>     the protocol's transport data, in front of each separate message or
>>     byte stream.  PExIDs MUST be registered in the registry created by
>>     this document.
> Hmmm, indeed, why not put that paragraph in the introduction, so someone
> reading the introduction can learn what a PExID is, not just the idea?
>
> Dale

I also think a possibly slightly "thinner" version of the above text 
would be a really nice addition as a part of the intro, where the PExID 
is first mentioned!

I'd also encourage this to provide an expansion of the PExID term when 
it is first used.

... although, I think the current text probably needs to remain describe 
the normative requirements presented in section 4.

Best wishes,

Gorry


--------------eRbaavkMBtIzcQ5VhxQaged5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 08/08/2025 20:22, Dale R. Worley
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:87a549ipp2.fsf@hobgoblin.ariadne.com">
      <pre wrap="" class="moz-quote-pre"><a class="moz-txt-link-abbreviated" href="mailto:worley@ariadne.com">worley@ariadne.com</a> (Dale R. Worley) writes:
</pre>
      <blockquote type="cite">
        <pre wrap="" class="moz-quote-pre">- In section 4, there is much discussion of PExIDs but you have to read
  the whole section very carefully to find out what they *are*.  I
  suggest that the section start with a paragraph that explains that:

   A PExID is a 32-bit unsigned integer encoded in network standard byte
   order.  It is used in an experimental protocol by being prepended to
   the protocol's transport data, in front of each separate message or
   byte stream.  PExIDs MUST be registered in the registry created by
   this document.
</pre>
      </blockquote>
      <pre wrap="" class="moz-quote-pre">
Hmmm, indeed, why not put that paragraph in the introduction, so someone
reading the introduction can learn what a PExID is, not just the idea?

Dale
</pre>
    </blockquote>
    <p>I also think a possibly slightly "thinner" version of the above
      text would be a really nice addition as a part of the intro, where
      the <span style="white-space: pre-wrap">PExID is first mentioned</span>! </p>
    <p>I'd also encourage this to provide an expansion of <span
      style="white-space: pre-wrap">the PExID</span> term when it is
      first used.</p>
    <p>... although, I think the current text probably needs to remain
      describe the normative requirements presented in section 4.</p>
    <p>Best wishes,</p>
    <p>Gorry</p>
    <p><br>
    </p>
  </body>
</html>

--------------eRbaavkMBtIzcQ5VhxQaged5--