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/[email protected]/
[address-policy-wg] Proposal 2011-02 moving to Last Call
- Previous message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
- Next message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Bais
ebais at a2b-internet.com
Sun Oct 2 10:18:40 CEST 2011
Hi Michel and David, I like a technical discussion about scaling routers probably as much as you, however that is a bit outside the scope of the suggested policy I think. The policy proposal is to get it in line with v4 and also ARIN is having a similar policy. For companies that don't want to deal with the multi-homing requirement currently sign up to become a LIR. This particular part of the v6 policy (the multi-homing requirement) has been an issue for while already and it needs to be fixed. Although nobody can look into the future, experience from the ARIN region, figures from RIPE on PI (v4 and v6) in the DFZ, the supplied de-aggregation info, it doesn't show that with this policy the routing table will explode. As I also stated in my presentation on RIPE 62 in Amsterdam on 2011-02, currently it is a financial discussion for an end-customer, not a technical one. An end-customer can already decide for v6 without the multi-homing requirement, but somehow an end-customers that can't become a LIR or don't see themselves as an ISP, can't deploy v6 because they have no multi-homed network setup. There are people unlike ourselves, that just don't want to deal with the RIPE 'stuff' and are happy to leave that up to others if they can. Will this policy open the gates for everything to start requesting everything they like ? No. There are still other limitations in v6 that we don't see in v4 (like restrictions for colocation or DSL/access address usage, sub-allocation etc. ) You still need PA for those kind of requests. Kind regards, Erik Bais
- Previous message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
- Next message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]