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-only network during RIPE 71
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nicolas CARTRON
nicolas at ncartron.org
Mon Oct 26 14:26:11 CET 2015
> On 26 Oct 2015, at 11:35, Luuk Hendriks <luuk.hendriks at utwente.nl> wrote: > [...] > > What I remember from the last meeting is that often the applications seem to be the problem (Skype, for example). I think the most important thing here is the availability of 'troubleshooting information', so people know where to look in case things don't work. > Jen made a list with troublesome applications: if that list is available at the network operation room, it can function as a shortcut. 'Program $X is not working? Try the legacy ssid' > > And +1 on removing terminology like 'legacy'. Looks like a good approach to me. +1 -- Nico CARTRON
- Previous message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
- Next message (by thread): [ipv6-wg] IPv6-only network during RIPE 71
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]