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 ]
Sander Steffann
sander at steffann.nl
Mon Apr 7 16:07:26 CEST 2014
Hi Marco, >> 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? Up to now: - add RFC 6946 (Processing of IPv6 "Atomic" Fragments) - add RFC 6620 (SAVI FCFS) / RFC 6583 - keep an eye on draft-gont-opsec-ipv6-firewall-reqs - remove RFC 4541 (MLD snooping) for layer-3 devices, they should support RFC 3810 (MLD) - remove RFC 3140 (Per Hop Behavior Identification Codes) > 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 :) Thanks! Sander
- 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 ]