Dear OPSAWG, We have updated the draft draft-ietf-opsawg-ipfix-on-path-telemetry addressing the comments from the WGLC.
Thank you Joe and Giuseppe for the comments. On this iteration, we also have addressed some comments coming from IANA. There is this comment from IANA that we would appreciate the feedback from Greg as IPPM registry expert. So far, we are assuming that the section shown below need to be added. (this is already integrated into the submitted iteration) >>>>> from thread: >>>>> https://mailarchive.ietf.org/arch/msg/opsawg/iuGsCSOxlHNQMj1DKqVaaU333iY/ > 2) The Reference field that RFC 8911 (Section 7.1.5) places between the > Description and Change Controller appears to be missing. Interestingly, it's not present in RFC8912, which we took as a reference. Therefore it's not in IANA. See https://www.iana.org/assignments/performance-metrics/RTDNS_Active_IP-UDP-Poisson_RFC8912sec6_Seconds_Raw From RFC 8911: 7.1.5. Reference This entry gives the specification containing the candidate Registry Entry that was reviewed and agreed upon, if such an RFC or other specification exists. I guess this Reference field should be pointed to the RFC that created that entry, so RFC 8912 in this above case, right? Greg, as IPPM registry expert, do you confirm? If we agree. NEW INSERTION: 3.1.3 Reference [RFC-to-be] >>>>>> end thread Regards, Alex on behalf of the authors Title: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX) Authors: Thomas Graf Benoit Claise Alex Huang Feng Name: draft-ietf-opsawg-ipfix-on-path-telemetry-14.txt Pages: 32 Dates: 2024-11-04 Abstract: This document specifies new IP Flow Information Export (IPFIX) Information Elements to export the On-Path Telemetry measured delay on the OAM transit and decapsulating nodes. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-on-path-telemetry/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-on-path-telemetry-14 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-on-path-telemetry-14 > On 25 Oct 2024, at 14:28, Joe Clarke (jclarke) > <jclarke=40cisco....@dmarc.ietf.org> wrote: > > The WG LC has concluded. There were some comments raised that require > follow-up and a new draft from the authors, but nothing blocking has been > presented. Unfortunately, we didn’t get any directorate reviews. > > This document will be held pending the conclusion of LC on OAM > characterization and a revised draft. > > Who would like to act as shepherd for this draft? > > Joe > > From: Joe Clarke (jclarke) <jcla...@cisco.com <mailto:jcla...@cisco.com>> > Date: Thursday, October 10, 2024 at 11:07 > To: opsawg@ietf.org <mailto:opsawg@ietf.org> <opsawg@ietf.org > <mailto:opsawg@ietf.org>> > Subject: WG LAST CALL: Export of Delay Performance Metrics in IP Flow > Information eXport (IPFIX) > > This starts a two week WG LC for draft-ietf-opsawg-ipfix-on-path-telemetry > <https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-on-path-telemetry/>. > The authors have been polled and there is no known IPR on this work that > has been disclosed at this time. > > Please post comments and thoughts on this document’s readiness to the list. > If you are interested in being the shepherd for this document, please email > opsawg-chairs@. > > The WG LC will run until October 24. > > Thanks. > > Joe > _______________________________________________ > OPSAWG mailing list -- opsawg@ietf.org <mailto:opsawg@ietf.org> > To unsubscribe send an email to opsawg-le...@ietf.org > <mailto:opsawg-le...@ietf.org>
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
