Thanks, Thomas.  -14 addressed my review concerns, and I see that the OAM 
terminology reference is removed here in -15.  I think it’s in Giuseppe’s hands 
now to produce the write-up, and then we can move forward.

Perhaps one nit in your definition of the Encapsulating Node…since the decap 
node removes the OAM header, should the definition of the encap node also 
mention adding that header?

Joe

From: thomas.g...@swisscom.com <thomas.g...@swisscom.com>
Date: Saturday, March 1, 2025 at 06:25
To: Joe Clarke (jclarke) <jcla...@cisco.com>, opsawg@ietf.org <opsawg@ietf.org>
Subject: RE: WG LAST CALL: Export of Delay Performance Metrics in IP Flow 
Information eXport (IPFIX)
Dear Joe, Dear Giuseppe,

Thanks a lot Giuseppe for taking on shepherd.

On behalf of the authors, we submitted -15 with the following changes


1.      Merged minor editorial input from Paul Aitken, Menachem Dodge and 
Martin Duke 
(https://mailarchive.ietf.org/arch/msg/opsawg/YXts3FJjcXRBW1gnHUma5aGLVU0/,https://mailarchive.ietf.org/arch/msg/opsawg/KZ1eLLHgDb2WIucySnZJHUuneIM/)

2.      Defined OAM terms and removed normative dependency


Here the diff: 
https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-on-path-telemetry-15

Please let us know wherever this addresses your comments.

Best wishes
Thomas

From: Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org>
Sent: Friday, February 28, 2025 6:37 PM
To: Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org>; opsawg@ietf.org
Subject: [OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP 
Flow Information eXport (IPFIX)

Be aware: This is an external email.

We wanted to update the WG on this draft.  First, we have a shepherd!  Giuseppe 
Fioccola has agreed to shepherd the draft.  Thank you!

The next steps are to remove the reference to the OAM characterization 
document, publish another revision, await Giuseppe’s write-up, and then move 
this forward to the IESG.

Joe

From: Joe Clarke (jclarke) 
<jclarke=40cisco....@dmarc.ietf.org<mailto:jclarke=40cisco....@dmarc.ietf.org>>
Date: Friday, October 25, 2024 at 09:29
To: opsawg@ietf.org<mailto:opsawg@ietf.org> 
<opsawg@ietf.org<mailto:opsawg@ietf.org>>
Subject: [OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP 
Flow Information eXport (IPFIX)
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
To unsubscribe send an email to opsawg-le...@ietf.org

Reply via email to