[secdir] Re: Secdir last call review of draft-ietf-opsawg-ipfix-tcpo-v6eh-11

[Benoit Claise <[e-mail]>]

Tero,

We could potentially ask the RFC-editors to do this task?
Or maybe they do it automatically?

Regards, Benoit

On 5/14/2024 4:31 PM, Tero Kivinen wrote:
> [e-mail] writes:
>>> In section 8.3 change
>>>
>>> 					This type MUST be encoded per
>>>     Section 6.1.1 of [RFC7011].  Reduced-Size encoding (Section
>>> 6.2 of
>>>     [RFC7011]) applies to this data type.
>>>
>>> to
>>>
>>> 					This type MUST be encoded per
>>>     Section 6.1.1 of IPFIX specification [RFC7011]. Reduced-Size
>>>     encoding (Section 6.2 of IPFIX specification [RFC7011])
>>> applies to
>>>     this data type.
>>>
>>> --
>> [Med] This is a matter of editing taste. I'm not fun of expanding
>> the ref title.
> I think it is important for lowering the bar to getting people
> involved in the IETF protocols. If you need to learn mapping of
> tens or hundreds of rfc numbers to the actual titles, before you can
> easily read documents it makes it much harder to read the document,
> and causes extra work for the reader.
>
> Expanding it by the author once, will save that mapping to be done by
> people who read it. There are RFCs where there is less readers than
> writers, but I hope that is exception not a norm.
>
> When I was reviewing that draft, I had to google the RFC numbers
> multiple times (even the same ones) just to make sure which one is
> which.
>
> Also it is bad form of using reference as a noun. It makes [1] to [2]
> text when some of the [3] is not near the part using it.
>
> [1] https://dictionary.cambridge.org/dictionary/english/difficult
> [2] https://dictionary.cambridge.org/dictionary/english/read
> [3] https://dictionary.cambridge.org/dictionary/english/text
>
>>> Section 9.1 [IANA-EH] url is wrong, it points to the "Next Header
>>> Types" registry, not to the "IPv6 Extension Header Types"
>>> registry.
>> [Med] This is on purpose because the RFC Editor does not cite the specific URLs, only the URL of the registry group.
>>
>>> Correct url is
>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>>> Fwww.iana.org%2Fassignments%2Fipv6-parameters%2Fipv6-
>>> parameters.xhtml%23extension-
>>> header&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Ce04d445565
>>> be47dc729308dc703d9ca0%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0
>>> %7C638508657119400747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
>>> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdat
>>> a=sAElkvoUqJFN0K5eFgX%2F73LEbbqAWqerHq0IDzQsy%2Bo%3D&reserved=0
> The link I provided pointed directly to the registry you referenced
> to. If yo go to the registry itself the beginning of it has table of
> contents, which provides links to exact registries.