Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10

2024-02-29 Thread Christian Huitema
On 2/29/2024 3:31 PM, Michael Richardson wrote: Christian, I don't know if I am understanding your shotgun parser comment right. My understanding is that I have unwittingly invoked one via my informal description how URLs should be matched, and that this is something to avoid. I have writte

Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10

2024-02-29 Thread Christian Huitema
On 2/29/2024 4:49 PM, Michael Richardson wrote: Eliot Lear wrote: > The data we are talking about scales to number of devices X number of > MUD-URL changes.  This can further be reduced by whether or not the MUD > file actually exists.  These are not large #s in the home, and i

Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10

2024-02-29 Thread Michael Richardson
Eliot Lear wrote: > The data we are talking about scales to number of devices X number of > MUD-URL changes.  This can further be reduced by whether or not the MUD > file actually exists.  These are not large #s in the home, and in the > enterprise, we have iron for such cases. A

Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10

2024-02-29 Thread Michael Richardson
Christian Huitema wrote: > I am not entirely convinced. This looks like keeping logs, keeping them > online, and accessing them in real-time. That can be challenging in > many environments. I would prefer that the draft be updated to present Why would this be a challenge? The MUD man

Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10

2024-02-29 Thread Michael Richardson
Christian Huitema wrote: > How do you know that a specific URL is a rollback? It looks easy when > the example say "revision1" and "revision2", but I am sure there are > cases where you cannot tell by just looking at the URL. You may be able > to download the "old" and "new" URL,

Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10

2024-02-29 Thread Michael Richardson
Christian, I don't know if I am understanding your shotgun parser comment right. My understanding is that I have unwittingly invoked one via my informal description how URLs should be matched, and that this is something to avoid. I have written the following diff: https://github.com/IETF-OPSAWG

Re: [OPSAWG] Comments on draft-claise-opsawg-collected-data-manifest-06

2024-02-29 Thread Jean Quilbeuf
Hi Jan, Many thanks for your comments, they make a lot of sense to me. The current working version (not in datatracker yet) is here: https://github.com/JeanQuilbeufHuawei/draft-collected-data-manifest/blob/46-comments-from-jan-lindblad/draft-ietf-opsawg-collected-data-manifest-03.txt The diff is

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

2024-02-29 Thread Benoit Claise
Dear OPSAWG co-chairs, Thanks for this summary email. Much appreciated. This draft will be presented in NMOP, in the context of "Anomaly detection and incident management" topic from the charter. Regards, Benoit (NMOP co-chair) On 2/29/2024 7:44 AM, Henk Birkholz wrote: Dear OPSAWG members,