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] RIPE-554, it is time for an update
- Previous message (by thread): [ipv6-wg] RIPE-554, it is time for an update
- Next message (by thread): [ipv6-wg] RIPE-554, it is time for an update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Hogewoning
marcoh at marcoh.net
Mon Apr 7 15:59:08 CEST 2014
On 07 Apr 2014, at 15:52, Sander Steffann <sander at steffann.nl> wrote: > Hi WG, > > The authors of RIPE-554 have received suggestions for improving RIPE-554 over the years. Because we didn't want to publish a new document every couple of months (new document = new number = more confusion among users than it is worth) we just collected them. And now, almost 2 years after RIPE-554 was published, we think it is time to work on the next version! > > So, IPv6 WG, what would you like to see changed in RIPE-554? More/less explanatory text, more device types, adding or removing certain RFCs etc etc etc? Please let us know! Can you start by sending the current list of edits that you have shelved? That way we have a starting point and people can prevent doubles? For those concerned the current document is at http://www.ripe.net/ripe/docs/ripe-554 > To the WG chairs: can you please provide us with a slot at RIPE 68 so we can discuss this topic there? Yes :) Marco
- Previous message (by thread): [ipv6-wg] RIPE-554, it is time for an update
- Next message (by thread): [ipv6-wg] RIPE-554, it is time for an update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]