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 ]
Marco Hogewoning
marcoh at marcoh.net
Sun May 18 10:10:45 CEST 2014
> > Totally agree. I do hope that what I'm proposing is not going to put > much load on ops people. > I wonder if they got any complains coming to them about v6-only > network last week? What was their experience? > If ops team resources are the main concern, we need to think carefully > about the support model/troubleshooting plan for v6-only SSID but it > could be done. Stupid thought: would we be able to pull up enough volunteers to man/woman a support desk, similar to what ops does? At least for the London meeting. Simple task: spend a few hours (based on a pre-published schedule) at a designated spot so people can find you. Help them with troubleshooting, connecting and importantly document the issues. As such maybe we can create some sort of handover document, provide better statistical knowledge on workload and have some basic FAQ material which we can publish, also for others to use. DISCLAIMER: this idea just popped into my head, have no clue on what the RIPE NCC would think of such a setup Grtx, MarcoH -- "Good tests kill flawed theories; we remain alive to guess again"
- 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 ]