Re: [OPSAWG] AD review of draft-ietf-opsawg-9092-update-08

2024-01-20 Thread Randy Bush
> Please push -09, and I’ll push to the IETF LC. done randy ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] AD review of draft-ietf-opsawg-9092-update-08

2024-01-19 Thread Rob Wilton (rwilton)
Hi Randy, Please see inline … From: Randy Bush Date: Thursday, 18 January 2024 at 19:45 To: Rob Wilton (rwilton) Cc: draft-ietf-opsawg-9092-update@ietf.org , Mahesh Jethanandani , Ops Area WG Subject: Re: AD review of draft-ietf-opsawg-9092-update-08 hi rob, thanks for review

Re: [OPSAWG] AD review of draft-ietf-opsawg-9092-update-08

2024-01-18 Thread Randy Bush
hi rob, thanks for review. appreciated. > (1) p 4, sec 3. inetnum: Class > >Any particular inetnum: object SHOULD have, at most, one geofeed >reference, whether a remarks: or a proper geofeed: attribute when it >is implemented. If there is more than one, the geofeed: attribute >

[OPSAWG] AD review of draft-ietf-opsawg-9092-update-08

2024-01-17 Thread Rob Wilton (rwilton)
Hi Authors, OPSAWG, Please see my AD review comments for draft-ietf-opsawg-9092-update-08. My focus was on the diff between the latest draft and RFC 9092. I only have some relatively minor comments. Minor level comments: (1) p 4, sec 3. inetnum: Class Any particular inetnum