[OPSAWG]Re: New Version Notification for draft-ymbk-opsawg-rpsl-extref-00.txt

2024-10-20 Thread John Levine
It appears that Randy Bush said: >not positive this i sthe best wg. but regexr is about epp etc. I agree that this is worth thinking about, but this draft feels like it either says too much or too little. >From the too little angle, what do the URLs point to? Will they all be CSV files with

[OPSAWG]Re: Publishing End-Site Prefix Lengths

2024-10-16 Thread John Levine
It appears that Randy Bush said: >chairs, > >can we please get a ten minute speaking slot in dublin for > >Name: draft-gasser-opsawg-prefix-lengths >Revision: 01 >Title:Publishing End-Site Prefix Lengths >Date: 2024-10-16 >Group:Individual Submission >Pages

[OPSAWG]Re: CALL FOR ADOPTION: Publishing End-Site Prefix Lengths

2025-01-27 Thread John Levine
It appears that Vasilis Giotsas said: >-=-=-=-=-=- > >I'm also supportive of this draft, I think it can be very useful if widely >adopted. > >One issue that some of my colleagues identified is the following: >There are malicious ASNs out there who acquire huge amounts of IP6 space >(like multiple

[OPSAWG]Re: CALL FOR ADOPTION: Publishing End-Site Prefix Lengths

2025-01-15 Thread John Levine
It appears that Joe Clarke (jclarke) said: >-=-=-=-=-=- > >As the IPR poll has concluded (no IPR has been reported), the authors and >chairs would like to call for adoption of >https://datatracker.ietf.org/doc/draft-gasser-opsawg-prefix-lengths/ . Please >reply on-list with comments, support fo

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

2025-04-16 Thread John Levine
It appears that Oliver Gasser said: >We have now published -02, which incorporates John's comments and some >more changes, mainly: > >- Added third field in the CSV file for CGNAT scenarios >- Added detailed prefixlen examples for different scenarios >- Added one more example to the Security Con