[OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)

Hi Thomas, All, Please note that I just submitted an initial shepherd writeup on the IETF Datatracker: https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-on-path-telemetry/shepherdwriteup/ Note that I found a DOWNREF that can be solved easily: the reference to RFC 7799 should be changed fro

[OPSAWG]Re: Opsdir last call review of draft-ietf-opsawg-collected-data-manifest-05

Hi Jean, Thank you for the follow-up. The changes made so far are clear enhancements to the spec. I think most of my comments were addressed. The main remaining point is this one: # Avoid misalignment with existing models to report system characteristics & ease integration. I noted your r

[OPSAWG]Re: [**EXTERNAL**] Re: Slot Request for draft-king-rokui-ainetops-usecases

Thanks, Benoit and Joe. For the benefit of the WG and a potential future request for WG presentation time, please find some background and motivation for our document below. * Artificial Intelligence (AI) for Network Operations https://datatracker.ietf.org/doc/draft-king-rokui-ainetops-

[OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)

Thank you Thomas for your quick reply. The new revision looks good to me. I will also review the shepherd writeup as soon as you submit the new version. Regards, Giuseppe From: thomas.g...@swisscom.com Sent: Thursday, March 6, 2025 1:48 PM To: Giuseppe Fioccola ; jclarke=40cisco@dmarc.ietf

[OPSAWG]Re: WG LAST CALL: Export of Delay Performance Metrics in IP Flow Information eXport (IPFIX)

Dear Giuseppe, Many thanks for the shepherd review. On behalf of the authors, I addressed the RFC 7799 downref and the idnits in -17 TXT: https://raw.githubusercontent.com/network-analytics/draft-ietf-opsawg-ipfix-on-path-telemetry/refs/heads/main/draft-ietf-opsawg-ipfix-on-path-telemetry-17.tx

[OPSAWG]WG LC: TACACS+ TLS and its YANG module (draft-ietf-opsawg-tacacs-tls13 & draft-ietf-opsawg-secure-tacacs-yang)

Hello, WG! With the IPR polls concluded (no IPR has yet been disclosed), the authors feel that these two drafts are ready. Therefore, we are kicking off a three-week combined WG LC for both draft-ietf-opsawg-tacacs-tls13 and

[OPSAWG]Re: IPR POLL: draft-ietf-opsawg-secure-tacacs-yang : A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)

Hi Joe, all, No, I'm not aware of any IPR that applies to this draft. Best Regards, Guangying Zheng Huawei Technologies Co., Ltd. Email: zhengguangy...@huawei.com http://www.huawei.com This e-mail and i

[OPSAWG]Re: draft-ietf-opsawg-oam-characterization - review

Dear authors, Can you please let the WG know what is the latest status regarding your document, after this shepherd review below Regards, Joe and Benoit On 1/15/2025 4:41 PM, Benoit Claise wrote: Dear all, As the new document shepherd, I've been spending some time reviewing the draft-ietf

[OPSAWG]DRAFT AGENDA: IETF 122 Draft OPSAWG/OPSAREA Agenda Ready

We have uploaded a draft agenda for our 122 OPSAWG/OPSAREA meeting at https://datatracker.ietf.org/doc/agenda-122-opsawg/. We had to turn down some requests that came in late in order to accommodate adopted and discussed work. Please let us know if we see anything amiss. Joe and Benoît ___