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] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bernhard Schmidt
berni at birkenwald.de
Mon Jun 21 22:12:39 CEST 2004
JORDI PALET MARTINEZ wrote: Hi Jordi, > As I commented already in one of my previous emails, I will just give a /32 to every LIR/ISP (not end user) unless: > 1) He explicitly states "I'm not going to use it" > or > 2) He request something bigger and properly justify it. I totally agree. Why not make a rule like 'only one sTLA per LIR' and 'has to be announced by the LIR itself or its upstream ISP(s)' and give a /32 out to every LIR? - ISPs (as long as they are LIRs, that should be the most of them) could deploy IPv6 without having to lie about their plans for 200 customers. They would not be bound to an upstream more than they are in current IPv4 world. The "has to announce by itself" would stop some kiddies wet dreams of asking their (not IPv6 capable for years) LIR to get a /32 for them to play with. - Companies with LIR status could deploy IPv6 as well. By being LIR and paying LIR fees they sort of help the community out there (more LIRs - more income - perhaps lower RIPE fees for everyone). - Companies without LIR status either have to become LIR (see above) or have to use their upstream's address space with all known consequences. As soon as there is a scalable/usable approach of multi6 there might be some thinking in the companies about whether one could save the LIR fees and go with multi6. Bernhard
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]