[OPSAWG]Invitation to sidemeeting on Intelligent Network Element

2025-03-16 Thread 刘毅松
Dear all, I would like to inform you of a side meeting on Intelligent Network Element, in meeting room 2, on Wednesday, 19 March, from 15:00-17:00 local Bangkok time. Here is the link for remote participation: https://ietf.webex.com/meet/ietfsidemeeting2 Organized by China Mobil

[OPSAWG]WG status slides -- PCAP and MUD

2025-03-16 Thread Michael Richardson
Hi, I will miss OPSAWG due the conflict with RATS. PCAP link types document is awaiting an IPR query, which I've expedited. The other two documents were reposted before the cutoff. I tried to make sure that draft-ietf-opsawg-mud-acceptable-urls was reposted before the draft deadline, since it wa

[OPSAWG]Re: Comments on draft-netana-nmop-message-broker-telemetry-message-00

2025-03-16 Thread Thomas.Graf
Dear Rob, Thanks a lot for the review. 1. Do you want to add any text to explain that the fields are optional, providing choice at to which fields are populated? Valid point, We will take it as action item for the next iteration. 1. Quite a few of these are unstructured strings. It wou

[OPSAWG]I-D Action: draft-ietf-opsawg-mud-acceptable-urls-13.txt

2025-03-16 Thread internet-drafts
Internet-Draft draft-ietf-opsawg-mud-acceptable-urls-13.txt is now available. It is a work item of the Operations and Management Area Working Group (OPSAWG) WG of the IETF. Title: Authorized update to MUD URLs Authors: Michael Richardson Wei Pan Eliot Lear Name:

[OPSAWG]Comments on draft-ietf-opsawg-prefix-lengths

2025-03-16 Thread John R Levine
As I said at the mic, I believe this will be very useful to help mail providers process IPv6 mail and is close to done. Minor suggestions; In section 3, for CGNAT rather than trying to squash the NAT size into the prefix size field, it'd be clearer to use a third column to say how big the poo