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]/
[ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Lenz
slz at baycix.de
Tue Jul 19 14:33:35 CEST 2011
Hi, > >> I am not proposing a change with respect to existing RFCs; we must to >> live with existing /64 subnets as a minimum allocation. >> >> My comments apply for future networks beyond the current 2000::/3 range >> used by all RIRs. Beyond this range all options are still open. > > I don't think so. IPv6 as protocol applies over all ::/0, not only 2000::/3 > > Why do you think ND and SLAAC would behave differently in 4000::/3 ? indeed. That would be weird and cause all kinds of operational problems. But more importantly - why at all? It's not a waste of addresses, this has been discussed 68060 times on various mailinglists and at other places. The usual answer to such statements simply is "do the math!", for a reason. There are some issues with /64 default segments, like it causes some possible attack vectors on the infrastructure, but there are no issues with the size itself compared to the 128bit we have. So, "do the math!" :-) -- Mit freundlichen Grüßen / Kind Regards Sascha Lenz [SLZ-RIPE] Senior System- & Network Architect
- Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]