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] IPv6 only network at RIPE 68
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Tue May 20 10:43:10 CEST 2014
* Marco Sommani > On 20/mag/2014, at 02:06, Tore Anderson <tore at fud.no> wrote: > >> The other component, the CLAT, is located on the end-user device >> itself. > > The CLAT must not necessarily stay on end-user devices, because it > may also be in a box at the border of a dual-stack customer network. The only sensible location for the CLAT in the wireline topology is on the CPE - which *is* an end-user device, as far as I'm concerned. :-) > On the other hand, I have to agree that this setup is useless for > the purpose of offering to participants the experience of an > IPv6-only world (actually, they would continue to experience > dual-stack). Indeed. While I suppose it is technically possible to contain a complete 464XLAT topology entirely within in the core of provider network (including the RIPE meeting infrastructure "core"), that would strike me as a utterly pointless exercise. Tore
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]