Hi WG,
The preliminary agenda is just posted.
https://datatracker.ietf.org/meeting/115/materials/agenda-115-opsawg-00
Please see if there is anything missing.
The speakers please send over your slides before the meeting.
Look forward to seeing you in London.
Cheers,
Tianran, Joe, Henk
Hi Thomas,
Only looking at the abstraction, I think you do not get Greg's comment on
on-path telemetry.
IMO, this IPFIX extension should only focus on the data export, while
independent of specific on-path telemetry protocols.
The following draft is a very useful reference for on path
Tue, Oct 18, 2022 at 12:14:39PM +, Joe Clarke (jclarke):
> Hello, authors. Ahead of IETF 115, we’d like to get an update on the status
> of this work. Since adoption, on-list traffic has been silent (though there
> has been discussion on the SSH work).
>
> I believe there are still some
Dear OPSAWG and IPPM,
On behalf of the authors. Thank you very much for the comments at IETF 114 in
Philadelphia and on the list.
We addressed your feedback in a new document version and renamed the draft
document from draft-tgraf-opsawg-ipfix-inband-telemetry to
Having been just added as co-author, No, I'm not aware of any IPR that
applies to this draft"
> On Oct 12, 2022, at 12:46 PM, Joe Clarke (jclarke) wrote:
>
> Authors and contributors, please respond on-list as to whether or not you are
> aware of any IPR that pertains to this work.
>
>
Dear OPSAWG,
On behalf of the authors. The -02 version includes besides editorial changes
and nits the following updates:
- Expanded the terminology section
- The srhFlagsIPv6 and srhSegmentEndpointBehavior registries have now a
reference to the Segment Routing Header registry. Thanks Med for
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group
WG of the IETF.
Title : Export of Segment Routing over IPv6 Information in IP
Flow Information Export (IPFIX)
Elwyn, thank you for your review. I have entered a No Objection ballot for this
document.
Lars
> On 2022-10-10, at 14:53, Elwyn Davies via Datatracker
> wrote:
>
> Reviewer: Elwyn Davies
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General
Lars Eggert has entered the following ballot position for
draft-ietf-opsawg-yang-vpn-service-pm-13: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
The following errata report has been submitted for RFC8520,
"Manufacturer Usage Description Specification".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7173
--
Type: Technical
Reported by:
Dear OPSAWG,
This new draft https://datatracker.ietf.org/doc/draft-quilbeuf-opsawg-
configuration-tracing/ aims at tracing a configuration change in a device back
to the service request made to an orchestrator that caused the configuration
change in the device.
I will present this draft
Hi Murray,
Thanks for the comment.
I suggest we go for these changes:
(1) Section 3
OLD:
Before using the model, the controller needs to establish topology
visibility of the network and VPN. For example, the controller can
use network information from [RFC8345],
Murray Kucherawy has entered the following ballot position for
draft-ietf-opsawg-yang-vpn-service-pm-13: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Hi Martin,
Thanks for the helpful comments. Please see inline.
Regards,
Bo
-Original Message-
From: Martin Duke via Datatracker [mailto:nore...@ietf.org]
Sent: Thursday, October 20, 2022 11:36 AM
To: The IESG
Cc: draft-ietf-opsawg-yang-vpn-service...@ietf.org; opsawg-cha...@ietf.org;
14 matches
Mail list logo
