Re: [OPSAWG] AD review draft-ietf-opsawg-mud-tls-12

Hi Paul, Thanks for the review. Please see inline On Sat, 20 Jan 2024 at 03:55, Paul Wouters wrote: > Hi, > > I am assisting Rob Wilton with some documents, as so I am the (temporary) > responsible AD for draft-ietf-opsawg-mud-tls > > I have reviewed this document and have a few questions and

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-teas-common-ac-04.txt

Hi all, This version implements a pending comment from the yangdoctors review: use "ro" rather than "rw" for last-changed leaf of admin-status. This change is also reflected in the other AC models. Cheers, Med > -Message d'origine- > De : OPSAWG De la part de internet- >

Re: [OPSAWG] [IPFIX] WG LC: IPFIX documents

https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-fixes Abstract The updates are also meant to bringing some consistency among the entries of the registry. Typo, "meant to bring in". 1. Introduction As the OPSAWG is currently considering This will soon become

Re: [OPSAWG] New I-D -> Guidelines for Charactering "OAM"

Dear Greg, Please see inline as *CMP2*. On Mon, Jan 22, 2024 at 2:56 PM Greg Mirsky wrote: > Dear Carlos, > > thank you for sharing your thoughts and responding to my notes. I have > added follow-up notes and questions below under the GIM2>> tag. But before > I go to the specific topics of our

Re: [OPSAWG] New I-D -> Guidelines for Charactering "OAM"

Dear Carlos, thank you for sharing your thoughts and responding to my notes. I have added follow-up notes and questions below under the GIM2>> tag. But before I go to the specific topics of our discussion, it is essential to bring forward the question of not how the 'OAM' abbreviation is expanded

[OPSAWG] Protocol Action: 'An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element' to Proposed Standard (draft-ietf-opsawg-rfc7125-update-07.txt)

The IESG has approved the following document: - 'An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element' (draft-ietf-opsawg-rfc7125-update-07.txt) as Proposed Standard This document is the product of the Operations and Management Area Working Group. The IESG

[OPSAWG] Last Call: (Finding and Using Geofeed Data) to Proposed Standard

The IESG has received a request from the Operations and Management Area Working Group WG (opsawg) to consider the following document: - 'Finding and Using Geofeed Data' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action.

[OPSAWG] I-D Action: draft-ietf-opsawg-teas-attachment-circuit-05.txt

Internet-Draft draft-ietf-opsawg-teas-attachment-circuit-05.txt is now available. It is a work item of the Operations and Management Area Working Group (OPSAWG) WG of the IETF. Title: YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service (ACaaS) Authors: Mohamed Boucadair

[OPSAWG] I-D Action: draft-ietf-opsawg-teas-common-ac-04.txt

Internet-Draft draft-ietf-opsawg-teas-common-ac-04.txt is now available. It is a work item of the Operations and Management Area Working Group (OPSAWG) WG of the IETF. Title: A Common YANG Data Model for Attachment Circuits Authors: Mohamed Boucadair Richard Roberts

Re: [OPSAWG] [IPFIX] WG LC: IPFIX documents

Med, The IE specified in Section 4.1 uses the new abstract data type defined in [I-D.ietf-opsawg-ipfix-tcpo-v6eh]. The unsigned256 type? It makes more sense to introduce a bitfield type. [Med] I think the use of unsigned256 is consistent with the current use in IP Flow Information Export

Re: [OPSAWG] [IPFIX] WG LC: IPFIX documents

Hi Paul, Thanks for the review. Please see inline. Cheers, Med De : ipv6 De la part de Aitken, Paul Envoyé : vendredi 19 janvier 2024 11:58 À : Joe Clarke (jclarke) ; opsawg@ietf.org Cc : t...@ietf.org; ts...@ietf.org; 6...@ietf.org; ip...@ietf.org Objet : Re: [IPv6] [IPFIX] WG LC: IPFIX