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] status of 2011-02
- Previous message (by thread): [address-policy-wg] status of 2011-02
- Next message (by thread): [address-policy-wg] status of 2011-02
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Bais
erik at bais.name
Mon Dec 12 10:11:45 CET 2011
Hi Geza, ➢ I see that we still disagree on many points. I see your comments and I understand your concern, however as stated in the presentation on the policy, this is not a technical discussion as customers currently are registering for LIR membership to avoid the multi-homing requirement for PI v6. Having (end-)customers register for a LIR membership to avoid the multi-homing requirement or having v6 PI without the multi-homing requirement doesn't make a technical difference imho. I’ve had several customers already take the LIR route in order to avoid the multi-homing requirement. They ‘bought’ themselves into the community by becoming a LIR and suddenly nobody cares anymore if they are multi-homed or not and have their own v6 prefix. Other customers have stopped deployment of v6 altogether. As if there is still time to wait with the implementation of v6. None of us can look into the future, however if we see how the v6 PI uptake is in other regions with a similar policy in place, the worst case scenario isn’t going to be the reality. And both the community and the RIPE NCC will keep a close watch on growth of the number of prefixes. Regards, Erik Bais Co-author of 2011-02
- Previous message (by thread): [address-policy-wg] status of 2011-02
- Next message (by thread): [address-policy-wg] status of 2011-02
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]