This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] PA ??? life after death
- Previous message (by thread): [address-policy-wg] PA ??? life after death
- Next message (by thread): [address-policy-wg] PA ??? life after death
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maxim A Piskunov
ffamax at gmail.com
Tue Mar 12 19:16:02 CET 2019
Hello, Gert, Community. IPv4 - it's not outdated, exact about IPv4 we are talking. Not about IPv6. And we discuss way to continue support and effective use IPv4 while IPv4 will be not needed anymore. And while we still need IPv4 I wake up members to solve issues: 1. End-user should have independence of LIR 2. Independence of LIR may be obtained by conversion PA to PI and passing addresses to end-user. (/24 or greatest). 3. Even end-user using address from PA and address block /24 or greatest, we should change policy to allow conversion PA to PI for allocated to end-user's addresses if LIR placed under deregistration procedure. Community, please support my proposals. >I don't think anything built by Cisco in the last 10 years falls into the >"IPv4 in hardware, IPv6 in software" category anymore. Maybe even 15 years. > >Instead of spreading outdated information, better spend the time working >with those vendors that still ship broken implementations, or take your >money elsewhere. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20190312/bd40f224/attachment.html>
- Previous message (by thread): [address-policy-wg] PA ??? life after death
- Next message (by thread): [address-policy-wg] PA ??? life after death
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]