Content-Type: multipart/alternative;
 boundary="------------ny7S70yS6tfI1UK69Z7RWD64"
Message-ID: <e944f55e-596a-45c7-a990-e777ab8056b3@iotconsultancy.nl>
Date: Mon, 24 Nov 2025 16:06:16 +0100
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>, anima <anima@ietf.org>
References: <tencent_1E7D9B1D5F6FA1025FE88D43@qq.com>
 <cb6c358d-21d0-414d-a99f-7abf686e5f2b@iotconsultancy.nl>
 <369125.1762825378@dyas>
Content-Language: en-US
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
Organization: IoTconsultancy.nl
In-Reply-To: <369125.1762825378@dyas>
Message-ID-Hash: NZNFPUJAQ5OZB4LCZFLJ6AEXO6QRWOCF
Precedence: list
Subject: =?utf-8?q?=5BAnima=5D_Re=3A_WGLC_for_draft-ietf-anima-rfc8366bis-14=2C_ends_?=
 =?utf-8?q?October_7th_/_3_review_questions?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/anima/VHmKuwUYN2ppYRLp6pP3JyR13rQ>

This is a multi-part message in MIME format.
--------------ny7S70yS6tfI1UK69Z7RWD64
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

> I didn't see any inconsistent capitalization among the Terminology, but I
> could have missed some.
> If you see specific things, let's fix them now, but the RPC will deal with
> the rest.

Coming back to this question; I did see specific things that are 
probably easy to find/see and also fix now.
The RPC can fix things for sure, but changes they make aren't 
necessarily visible to the WG or the wider community; and then only one 
document author typically gets to make the call.
While I think we prefer to have the WG decide on this and make the 
AD/IESG/IETF reviewers life easier.

So that there should be no doubt if a "Voucher Request" is the same 
thing as a "voucher-request" or not  :)

My proposal for terms is:
1) have pledge, registrar, voucher, voucher request, voucher artifact, 
certificate authority,  all in lowercase to prevent lots of uppercase in 
ordinary text.  Change "voucher-request" to "voucher request" except 
where language-wise impossible.
   Currently Pledge is capitalized while other terms are mostly not. I 
don't see a reason to have Pledge be an exception.
   (Uppercased all of these terms can be done also if we really prefer 
that...)
2) use uppercase (also for these terms) in section titles and similar 
headings (as is common)
3) use uppercase (also for these terms) in the Terminology section (so 
that readers know it's referring to another Term from the same list 
which they can look up).
4) use single quotes ('example', 'signerInfo', ... ) for referring to 
literal field names

I can add these things to the editorial PR if that's ok?

Esko

On 11-11-2025 02:42, Michael Richardson wrote:
> I went through some of the terms, and I fixed a few things that some
> reviewers have complained about, DNS Registrar != BRSKI Registrar.
> I didn't see any inconsistent capitalization among the Terminology, but I
> could have missed some.
> If you see specific things, let's fix them now, but the RPC will deal with
> the rest.

-- 
*IoTconsultancy.nl* | Email/Teams: esko.dijk@iotconsultancy.nl | +31 6 
2385 8339

--------------ny7S70yS6tfI1UK69Z7RWD64
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>
    <pre wrap="" class="moz-quote-pre">
&gt; I didn't see any inconsistent capitalization among the Terminology, but I
&gt; could have missed some.
&gt; If you see specific things, let's fix them now, but the RPC will deal with
&gt; the rest.</pre>
    Coming back to this question; I did see specific things that are
    probably easy to find/see and also fix now.<br>
    The RPC can fix things for sure, but changes they make aren't
    necessarily visible to the WG or the wider community; and then only
    one document author typically gets to make the call.<br>
    While I think we prefer to have the WG decide on this and make the
    AD/IESG/IETF reviewers life easier.<br>
    <br>
    So that there should be no doubt if a "Voucher Request" is the same
    thing as a "voucher-request" or not  :)<br>
    <br>
    My proposal for terms is: <br>
    1) have pledge, registrar, voucher, voucher request, voucher
    artifact, certificate authority,  all in lowercase to prevent lots
    of uppercase in ordinary text.  Change "voucher-request" to "voucher
    request" except where language-wise impossible.<br>
      Currently Pledge is capitalized while other terms are mostly not.
    I don't see a reason to have Pledge be an exception.<br>
      (Uppercased all of these terms can be done also if we really
    prefer that...)<br>
    2) use uppercase (also for these terms) in section titles and
    similar headings (as is common)<br>
    3) use uppercase (also for these terms) in the Terminology section
    (so that readers know it's referring to another Term from the same
    list which they can look up).<br>
    4) use single quotes ('example', 'signerInfo', ... ) for referring
    to literal field names<br>
    <br>
    I can add these things to the editorial PR if that's ok?<br>
    <br>
    Esko<br>
    <br>
    <div class="moz-cite-prefix">On 11-11-2025 02:42, Michael Richardson
      wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:369125.1762825378@dyas">
      <pre class="moz-quote-pre" wrap="">I went through some of the terms, and I fixed a few things that some
reviewers have complained about, DNS Registrar != BRSKI Registrar.
I didn't see any inconsistent capitalization among the Terminology, but I
could have missed some.
If you see specific things, let's fix them now, but the RPC will deal with
the rest.</pre>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <b>IoTconsultancy.nl</b> | Email/Teams:
      <a class="moz-txt-link-abbreviated" href="mailto:esko.dijk@iotconsultancy.nl">esko.dijk@iotconsultancy.nl</a> | +31 6 2385 8339</div>
    <br>
  </body>
</html>

--------------ny7S70yS6tfI1UK69Z7RWD64--