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] Website Launch: www.IPv6ActNow.org
- Previous message (by thread): [ipv6-wg] Website Launch: www.IPv6ActNow.org
- Next message (by thread): [ipv6-wg] Website Launch: www.IPv6ActNow.org
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Wed May 20 20:17:54 CEST 2009
On Wed, 2009-05-20 at 09:07 -0700, Leo Vegoda wrote: > On 20/05/2009 8:33, "Stream Service" <info at streamservice.nl> wrote: > > [...] > > > I don't think IPv4 will really go away. But is there an IPv6 range for > > internal use only? We would need something like that or we will keep using > > IPv4 for our internal network. > > See http://www.rfc-editor.org/rfc/rfc4193.txt > > It reserves FC00::/7 for local unicast. This works. Also, an IPv6 range for internal use is one you don't route. No need to get fancy. So one can use a /64 in the /48 you get from your provider for that purpose. Or you can use a /64 from the /48 in your 2002::/16 address for that purpose. -- Shane
- Previous message (by thread): [ipv6-wg] Website Launch: www.IPv6ActNow.org
- Next message (by thread): [ipv6-wg] Website Launch: www.IPv6ActNow.org
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]