Dear IANA,
Thanks for the proactive review.
Let me cc opsawg, for transparency.
See inline.
On 7/18/2024 10:32 PM, Amanda Baber via RT wrote:
Dear Authors,
Before the IETF meeting, we check working group agendas for documents with
IANA-related issues. We have notes about the current version of this document:
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-on-path-telemetry-08
About Section 6.1: Should IANA separate the template in Section 3 into four
separate templates, with information about the other registrations removed from
each, or can the same template be reused four times?
We actually followed the example in RFC8912
About Section 6.2: Should any of the information earmarked for the “Reference”
field be moved to the registry's “Additional Information” field? For examples,
please see
https://www.iana.org/assignments/ipfix
That one is an important convention to agree upon early (this is the
first perf. metric IPFIX IE)
Let's take an example: 6.2.1. PathDelayMeanDeltaMicroseconds
Right now:
Reference: [RFC-to-be], OWDelay_HybridType1_Passive_IP_RFC[RFC-to-
be]_Seconds_Mean in the IANA Performance Metric Registry.
Your proposal
Reference: [RFC-to-be],
Additonal Information: OWDelay_HybridType1_Passive_IP_RFC[RFC-to-
be]_Seconds_Mean in the IANA Performance Metric Registry.
Your proposal would make sense in light
ofhttps://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-fixes/ , which says:
As discussed with IANA during the publication process of [RFC9487],
the "Additional Information" entry in [IANA-IPFIX] should contain a
link to an existing registry, when applicable, as opposed to having
Here is the key question: Since we have two registries as reference, should we put them
in "Reference"?
Or only use the IPFIX regisry information in the "Reference"?
As I mentioned, this is "just" a convention IMO.
Unless someone on the list has strong views, I propose that you, IANA, states
the convention you want.
Regards, Benoit
If you have any questions, just let us know. If you'd like to talk in person,
you can find us next to the RFC Editor's table from Monday through Thursday.
You can also request another review at any time by contacting us
ati...@iana.org.
For more information about IANA Considerations section requirements, please see
https://www.iana.org/help/protocol-registration
Best regards,
Amanda Baber
IANA Operations Manager
_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org
