On 2008-11-11 at 15:47 -0800, Jo Rhett wrote: > On Nov 10, 2008, at 7:29 AM, Yves Dorfsman wrote: > > Currently with ipv4, ISPs typically "give" you x numbers of ip > > addresses > > based on the type of fees you pay. Typically 2 for base/home > > internet, and > > 15 for basic professional internet access, etc... > > > > How does it work for ISPs offereing ipv6 ? How many addresses do they > > typically make available for the most basics plans ? > > I've heard that /92 will be common for small end user assignments.
Heard where, from whom? Anything less than a /64 is asinine as it breaks stateless autoconfiguration on ethernet (64-bit node identifier), it breaks the privacy extensions (64-bit node identifier from MD5) and so has just blocked use of the most commonly deployed client implementations in the end-user OSes. /92 will just condemn the affected organisations to an even worse IPv6 experience and a second class status of poorly supported systems. It sounds like a proposal from someone blowing their mouth based on a wet finger in the air because of the number of bits available, rather than from someone who understands IPv6. It needs to be, at longest, a /64 assignment. It should be on a 4-bit boundary if you want reverse DNS to be delegatable (nibble-based splitting and reversing for reverse DNS). /64 is parsimonious. /60 or /56 are lengths I've heard from people trying to dodge RFC 3177 "IAB/IESG Recommendations on IPv6 Address Allocations to Sites" which suggests /48. Because IANA is supposed to follow RFC 3177 when allocating to the RIRs, the RIRs (ARIN, RIPE, etc) should be able to get as much address space as needed to allocate to ISPs which are following this policy. If you have reason to believe that ARIN is not looking to follow this and if you work at an ARIN customer, it's in your interests to push back before your end-user support costs are pushed up by such a policy. -Phil _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
