[auth48] Re: [IANA #1448936] IANA actions for RFC-to-be 9951 (draft-ietf-opsawg-ipfix-on-path-telemetry-23)

[[e-mail]]

Dear Amanda,

Thanks a lot. I reviewed both registries and they look good to me.

Regarding your question on action 2. The reason why the performance metrics 4.4.2 subsections have "OWDelay_HybridType1_IP_RFC9951_" in the title name is because with the exception of the output types, all definitions for each entry are the same. To avoid repeating section 4, 4 times, we opted to put the "OWDelay_HybridType1_IP_RFC9951_" in the 4.4.2 subsections. That helps readability and makes it clear that only this changes among OWDelay_HybridType1_IP performance metrics.

Therefore I think it is reasonable to refer to "OWDelay_HybridType1_IP" in section 4.4.2. To make it clear that "The one-way delay of one IP packet is a Singleton" refers to OWDelay_HybridType1_IP. I suggest to leave it as suggested.

Best wishes
Thomas

-----Original Message-----
From: Amanda Baber via RT <[e-mail]>
Sent: Friday, April 3, 2026 4:55 AM
To: [e-mail]
Cc: Graf Thomas, SCS-INI-NET-VNC-E2E <[e-mail]>; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
Subject: [IANA #1448936] IANA actions for RFC-to-be 9951 (draft-ietf-opsawg-ipfix-on-path-telemetry-23)


Be aware: This is an external email.



Dear Authors,

Can you check that these actions have been completed correctly? I also have a question about each of them.

ACTION 1:

The following entries have been added to the IPFIX Information Elements registry:

ElementID: 530
Name: pathDelayMeanDeltaMicroseconds
Abstract Data Type: unsigned32
Data Type Semantics: deltaCounter
Status: current
Description: This Information Element identifies the mean path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to OWDelay_HybridType1_IP_RFC9951_Seconds_Mean in the IANA [Performance Metric] Registry.
Additional Information: OWDelay_HybridType1_IP_RFC9951_Seconds_Mean in the IANA [Performance Metric] registry.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Revision: 0
Date: 2026-04-02

ElementID: 531
Name: pathDelayMinDeltaMicroseconds
Abstract Data Type: unsigned32
Data Type Semantics: deltaCounter
Status: current
Description: This Information Element identifies the lowest path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to the OWDelay_HybridType1_IP_RFC9951_Seconds_Min in the IANA [Performance Metric] Registry.
Additional Information: OWDelay_HybridType1_IP_RFC9951_Seconds_Min in the IANA [Performance Metric] registry.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Revision: 0
Date: 2026-04-02

ElementID: 532
Name: pathDelayMaxDeltaMicroseconds
Abstract Data Type: unsigned32
Data Type Semantics: deltaCounter
Status: current
Description: This Information Element identifies the highest path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to OWDelay_HybridType1_IP_RFC9951_Seconds_Max in the IANA [Performance Metric] Registry.
Additional Information: OWDelay_HybridType1_IP_RFC9951_Seconds_Max in the IANA [Performance Metric] registry.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Revision: 0
Date: 2026-04-02

ElementID: 533
Name: pathDelaySumDeltaMicroseconds
Abstract Data Type: unsigned64
Data Type Semantics: deltaCounter
Status: current
Description: This Information Element identifies the sum of the path delay of all packets in the Flow, in microseconds, between an OAM header encapsulating node and the local node with the OAM domain (either an OAM header transit node or an OAM header decapsulating node), according to OWDelay_HybridType1_IP_RFC9951_Seconds_Sum in the IANA [Performance Metric] Registry.
Additional Information: OWDelay_HybridType1_IP_RFC9951_Seconds_Sum in the IANA [Performance Metric] registry.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Revision: 0
Date: 2026-04-02

Note: we'll update the references to point to RFC 9511 once the final link is available.

QUESTION:

Should we provide links to the individual performance metric registration templates as well as the registry?

Please see
https://www.iana.org/assignments/ipfix

ACTION 2:

The following entries have been added to the Performance Metrics registry:

Identifier: 27
Name: OWDelay_HybridType1_IP_RFC9951_Seconds_Mean
URI: https://www.iana.org/assignments/performance-metrics/OWDelay_HybridType1_IP_RFC9951_Seconds_Mean
Description: This metric assesses the mean of one-way delays of all successfully forwarded IP packets constituting a single Flow. The measurement of one-sway delay is based on a single Observation Point [RFC7011] somewhere in the network.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Change Controller: IETF
Version: 1.0

Identifier: 28
Name: OWDelay_HybridType1_IP_RFC9951_Seconds_Min
URI: https://www.iana.org/assignments/performance-metrics/OWDelay_HybridType1_IP_RFC9951_Seconds_Min
Description: This metric assesses the minimum of one-way delays of all successfully forwarded IP packets constituting a single Flow. The measurement of one-way delay is based on a single Observation Point [RFC7011] somewhere in the network.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Change Controller: IETF
Version: 1.0

Identifier: 29
Name: OWDelay_HybridType1_IP_RFC9951_Seconds_Max
URI: https://www.iana.org/assignments/performance-metrics/OWDelay_HybridType1_IP_RFC9951_Seconds_Max
Description: This metric assesses the maximum of one-way delays of all successfully forwarded IP packets constituting a single Flow. The measurement of one-way delay is based on a single Observation Point [RFC7011] somewhere in the network.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Change Controller: IETF
Version: 1.0

Identifier: 30
Name: OWDelay_HybridType1_IP_RFC9951_Seconds_Sum
URI: https://www.iana.org/assignments/performance-metrics/OWDelay_HybridType1_IP_RFC9951_Seconds_Sum
Description: This metric assesses the maximum of one-way delays of all successfully forwarded IP packets constituting a single Flow. The measurement of one-way delay is based on a single Observation Point [RFC7011] somewhere in the network.
Reference: [RFC-ietf-opsawg-ipfix-on-path-telemetry-23]
Change Controller: IETF
Version: 1.0

QUESTION:

For each registration template, I've removed the IDs, Names, URIs, and Descriptions associated with the other three registrations. I haven't done this for the "Reference Definition" field, though, because I'm not sure whether the three lines that precede Section 4.4.2.1 would need to be left in place, edited, or removed. What do you want us to do with this text?

==

For all output types:

OWDelay_HybridType1_IP:  The one-way delay of one IP packet is a
   Singleton.

For each <statistic> Singleton, one of the following subsections applies.

==

Please see
https://www.iana.org/assignments/performance-metrics

thanks,
Amanda

On Tue Mar 31 05:54:08 2026, [e-mail] wrote:
> Hi IANA,
>
> Re:
> > After discussion with the authors, we will hold off on performing
> > the IANA actions for this document until the RFC number is assigned.
>
>
> The number 9951 has been assigned to this document. It is currently in
> AUTH48 state.
>
> The files are here:
>   https://www.rfc-editor.org/authors/rfc9951.txt
>   https://www.rfc-editor.org/authors/rfc9951.html
>   https://www.rfc-editor.org/authors/rfc9951.pdf
>
> https://www.rfc-editor.org/authors/rfc9951-diff.html (all changes from the approved I-D)
>
> https://www/.
> rfc-editor.org%2Fauthors%2Frfc9951-rfcdiff.html&data=05%7C02%7CThomas.
> Graf%40swisscom.com%7C737f1f73f9764e0c574a08de912c6ea9%7C364e5b87c1c74
> 20d9beec35d19b557a1%7C0%7C0%7C639107817366923959%7CUnknown%7CTWFpbGZsb
> 3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjo
> iTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Dj9FItIy2R%2BzN4Zj5de09Ff
> adO%2B4XP%2BnGj1dzcHgkz0%3D&reserved=0 (side by side diff)
>
> Thank you.
>
> Alice Russo
> RFC Production Center
>
> > On Oct 15, 2025, at 5:09 PM, Sabrina Tanamal via RT <drafts-
> > [e-mail]> wrote:
> >
> > RFC Editor,
> >
> > After discussion with the authors, we will hold off on performing
> > the IANA actions for this document until the RFC number is assigned.
> > The Performance Metric registrations in Sections 4 and 6.1 will need
> > to reference [RFC-to-be], so we plan to add these entries to the
> > registries once the RFC reference is available.
> >
> > Similarly, the IPFIX registrations in Section 6.2 include references
> > to the Performance Metric registrations, so we will also defer those
> > actions until the RFC number is available.
> >
> > For your reference, we have reserved the following values so that
> > you may proceed with publication of the document:
> >
> > Performance Metric Values:
> >
> > 27 OWDelay_HybridType1_IP_RFC[RFC-to-be]_Seconds_Mean
> > 28 OWDelay_HybridType1_IP_RFC[RFC-to-be]_Seconds_Min
> > 29 OWDelay_HybridType1_IP_RFC[RFC-to-be]_Seconds_Max
> > 30 OWDelay_HybridType1_IP_RFC[RFC-to-be]_Seconds_Sum
> >
> > IPFIX:
> >
> > 530 pathDelayMeanDeltaMicroseconds
> > 531 pathDelayMinDeltaMicroseconds
> > 532 pathDelayMaxDeltaMicroseconds
> > 533 pathDelaySumDeltaMicroseconds
> >
> > Please let us know if you have any questions or need any additional
> > information. Please reply to this message to acknowledge receipt.
> >
> > Best regards,
> >
> > Sabrina Tanamal
> > IANA Operations Manager
> >