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 prefix delegation BCOP document available for comments and suggestions
- Previous message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
- Next message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Tue Apr 4 10:59:24 CEST 2017
On Wed, 29 Mar 2017, Philip Homburg wrote: > Hooking up CPEs to an ethernet-like link without actually running a > routing protocol has its own set of issues. PPPoE framing is also simple > enough that it should not cost a lot of CPU time. Encap/decap is always costly unless mitigated by special hardware (which of course costs money, but in volume can be low). ISPs are doing PPPoE because of other reasons, not because it's easy on the forwarding plane. Most of the motivation I've been seeing revolves around the same reasons enterprise want DHCPv6 IA_NA "that's what we've 'always' been doing and we have the systems to support it". I prefer IPoE, but that seems to be common here in the nordics, but the rest of the world seems to have converged around PPPoE. -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
- Next message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]