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 ]
Us
us at sweet-sorrow.com
Thu May 26 10:22:48 CEST 2011
On 05/26/2011 10:07 AM, Jasper Jans wrote: > Can anyone give me some real world experience with IPv6 numbering on P2P links in their network? > > I've seen the recommendations swing from '/64' to '/127 if your equipment can handle it' and even > to 'do not assign anything at all just use link-local' and access your devices over the loopback > which your IGP will distribute. > > The last option seems interesting to me from a IP assignment point of few. It safes me having > to allocate a block for this part of the infrastructure. I'm just wondering if in the long run > it will not make life harder. > > Jasper > > > Op dit e-mailbericht is een disclaimer van toepassing, welke te vinden is op http://www.espritxb.nl/disclaimer > > > Our ISP is trying to stick with /64 P2P address space. But I've also seen by one of our upstream providers, that they use /112. I don't want to mention them, because their service sucks and the P2P global IPs cannot be pinged, while LL addresses work Us
- 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 ]