On 8 Dec 2022, at 21:34, Henk Birkholz wrote:
> Dear OPSAWG members,
>
> this starts a Working Group Adoption call for a bundle of two documents:
>
>> https://www.ietf.org/archive/id/draft-tuexen-opsawg-pcapng-05.html
>>
Dear Zhenqiang,
Thanks a lot for the feedback. Much appreciated.
I do not disagree that YANG push isn't capable of exporting control and
forwarding plane metrics. However it is not the best choice in terms of scale.
Table 1 of RFC 9232 gives a good summary. It even makes the distinction
Since this happened to cross my inbox, I want to reiterate that, in my
view, this document has not been properly reviewed by the TLS WG. As the
shepherd's writeup notes, previous reviews in the TLS group raised some
significant concerns about whether this draft's approach is advisable.
I would
Joe Clarke has requested publication of draft-ietf-opsawg-ipfix-srv6-srh-06 as
Proposed Standard on behalf of the OPSAWG working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-srv6-srh/
___
Hi Rob,
On 19.12.22 17:25, Rob Wilton (rwilton) wrote:
Hi Eliot, Scott,
Thanks for this document. Here is my AD review for
draft-ietf-opsawg-sbom-access-12.
Moderate level comments:
(1) p 3, sec 1. Introduction
To enable application-layer discovery, this memo defines a well-known
Hello Thomas,
As summarized in table 1 in RFC9232, gRPC is an application protocol, which can
be used to export all the telemetry metrics for Management Plane, Control
Plane, Forwarding Plane and External Data. By using GPB encoding, gRPC is
widely used to export real time performace metrics,
Hi Thomas and Benoit,
The changes are perfectly addressing my comments, thanks.
Best,
Jean
From: Benoit Claise
Sent: Thursday 5 January 2023 13:19
To: thomas.g...@swisscom.com; Jean Quilbeuf ;
zhoutianran=40huawei@dmarc.ietf.org; opsawg@ietf.org
Cc:
