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] Guidance Requested: Changing the Status of PI Address Space
- Previous message (by thread): [address-policy-wg] Guidance Requested: Changing the Status of PI Address Space
- Next message (by thread): [address-policy-wg] Guidance Requested: Changing the Status of PI Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sonderegger Olaf ABRAXAS INFORMATIK AG
Olaf.Sonderegger at abraxas.ch
Wed Jun 26 11:10:55 CEST 2013
Hi all My question is: Why RIPE NCC should go one step back instead one step forward? I remember an idea to remove status "Provider Aggregatable" (PA) and "Provider Independent" (PI) for IPv6 addresses [see Ref 1 / Ref 2]. If we go ahead with this idea and open it for any kind of IP address, than final result is the same as current guidance request. Ref 1: http://ripe62.ripe.net/presentations/148-wg.pdf<http://ripe62.ripe.net/presentations/148-wg.pdf%20/> Ref 2: http://ripe63.ripe.net/presentations/143-wg3.pdf I think, I could accept request as our first step in direction of removing status "Provider Aggregatable" (PA) and "Provider Independent" (PI). Best regards, Olaf Sonderegger -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20130626/62618def/attachment.html>
- Previous message (by thread): [address-policy-wg] Guidance Requested: Changing the Status of PI Address Space
- Next message (by thread): [address-policy-wg] Guidance Requested: Changing the Status of PI Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]