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] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Tinka
mtinka at globaltransit.net
Wed Feb 3 11:13:40 CET 2010
On Wednesday 03 February 2010 05:58:01 pm Martin Millnert wrote: > Given 1), it makes a lot of sense to put 2) + 3) on a > separate SSID. Give it a well-descriptive name and > that's it... Problem solved! Attendees can do testing on > their *own* terms, which is bound to make them happier. This is what we do, shall be doing and have done at a regional meeting in Asia-Pac. Cheers, Mark. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. URL: </ripe/mail/archives/ipv6-wg/attachments/20100203/8defe8e8/attachment.sig>
- Previous message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
- Next message (by thread): [ipv6-wg] RFC 1918 in "production networks" (was IPv6 experiments at future RIPE Meetings)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]