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/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 on P2P links
- Previous message (by thread): [ipv6-wg] IPv6 on P2P links
- Next message (by thread): [ipv6-wg] IPv6 on P2P links
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lars Erik Utsi Gullerud
lerik at nolink.net
Thu May 26 10:50:14 CEST 2011
On 26.05.2011 10:45, Lars Erik Utsi Gullerud wrote: > The reasoning behind /124 (rather than e.g. /127) for us, is simply to > make addressing more "human-readable" as well as simpler to manage in > terms of reverse DNS. Using /124 you always end up on a > "human-friendly" boundary so your networks are xx::10/124, xx::20/124, > xx::30/124 and so on, and you can then assign hosts that are always > like xx::10:1/124 + xx::10:2/124 (rather than having your tech staff > trying to sort out hexadecimal stuff in their heads). This also fits > very nicely with nibble addressing in ip6.arpa as every network is its > own "nibble". I believe someone wrote an I-D about using /124s a while > back, but my memory isn't what it used to be... Correcting myself here (not enough coffee yet) - the host addresses should of course be xx::11/124 and xx::12/124 and so on in the text above. :) Regards, Lars Erik
- Previous message (by thread): [ipv6-wg] IPv6 on P2P links
- Next message (by thread): [ipv6-wg] IPv6 on P2P links
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]