[OPSAWG]Re: shepherd review for draft-boro-opsawg-teas-common-ac

2024-05-15 Thread Rokui, Reza
Thanks Med. Reza From: mohamed.boucad...@orange.com Date: Wednesday, May 15, 2024 at 3:41 PM To: Rokui, Reza , Joe Clarke (jclarke) , opsawg@ietf.org , Wubo (lana) , Richard Roberts , Oscar González de Dios , samier.barguil_gira...@nokia.com Subject: [**EXTERNAL**] RE: shepherd review for

[OPSAWG]Re: shepherd review for draft-boro-opsawg-teas-common-ac

2024-05-15 Thread mohamed . boucadair
Hi Reza, Thank you for the review. We don’t provide the full structure but snippets per the guidance in https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-11#name-tree-diagrams. We provided the following in Section 4: == The full tree diagram of the module can be generated

[OPSAWG]Re: shepherd review for draft-boro-opsawg-teas-common-ac

2024-05-15 Thread Rokui, Reza
Thanks Med. One more question. 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? [Reza] The document is well-written. Having said

[OPSAWG]Re: [Last-Call] Intdir last call review of draft-ietf-opsawg-tsvwg-udp-ipfix-08

2024-05-15 Thread Aitken, Paul
Med, Joe, - Reduced-size encoding per RFC7011 does not apply, unless you are restricting them to 64, 32, 16, and 8. [Med] There is no such restriction because of this part in the base spec: This behavior is indicated by the Exporter by specifying a size in the Template

[OPSAWG]I-D Action: draft-ietf-opsawg-ntw-attachment-circuit-11.txt

2024-05-15 Thread internet-drafts
Internet-Draft draft-ietf-opsawg-ntw-attachment-circuit-11.txt is now available. It is a work item of the Operations and Management Area Working Group (OPSAWG) WG of the IETF. Title: A Network YANG Data Model for Attachment Circuits Authors: Mohamed Boucadair Richard Roberts

[OPSAWG]Re: Shepherd review for draft-ietf-opsawg-ntw-attachment-circuit

2024-05-15 Thread Krzysztof Szarkowicz
Hi Med, Looks good now. From my perspective, no further changes are required. Cheers, Krzysztof On May 15, 2024, at 17:08, mohamed.boucad...@orange.com wrote: [External Email. Be cautious of content] Hi Krzysztof, Thank you for the review. Can you please check and let us know if any

[OPSAWG]Re: Secdir last call review of draft-ietf-opsawg-ipfix-tcpo-v6eh-11

2024-05-15 Thread Benoit Claise
Tero, We could potentially ask the RFC-editors to do this task? Or maybe they do it automatically? Regards, Benoit On 5/14/2024 4:31 PM, Tero Kivinen wrote: mohamed.boucad...@orange.com writes: In section 8.3 change This type MUST be encoded per

[OPSAWG]Re: Shepherd review for draft-ietf-opsawg-ntw-attachment-circuit

2024-05-15 Thread mohamed . boucadair
Hi Krzysztof, Thank you for the review. Can you please check and let us know if any further change is needed:

[OPSAWG]Shepherd review for draft-ietf-opsawg-ntw-attachment-circuit

2024-05-15 Thread Krzysztof Szarkowicz
Resending to the WG list > On May 2, 2024, at 11:26, Krzysztof Szarkowicz > wrote: > > Hi, > > > I have been asked to do the shepherd's review for > draft-ietf-opsawg-ntw-attachment-circuit document, with the intended traget > status "Standards Track". "Standards Track" is the

[OPSAWG]Re: WG LC: Attachment circuits work

2024-05-15 Thread Joe Clarke (jclarke)
We would like to thank the WG (and TEAS) for the reviews and comments during WG LC. LC has concluded, and comments have been addressed (today) for issues raised. We are still pending a couple of shepherd write-ups, but once we get them we can move these drafts forward to the IESG. Joe From:

[OPSAWG]Re: [Last-Call] Intdir last call review of draft-ietf-opsawg-tsvwg-udp-ipfix-08

2024-05-15 Thread mohamed . boucadair
Hi Joe, Thank you for the follow-up. A candidate version can be seen at: Diff: draft-ietf-opsawg-tsvwg-udp-ipfix.txt -