[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 ]
Jan Zorz
jan at pragma.si
Mon Apr 7 19:34:19 CEST 2014
On 07/04/14 16:07, Sander Steffann wrote: > 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) To add my 2 cents worth... As mentioned, Fernando Gont submitted the IPv6 firewall requirements spec draft to IETF OPSEC WG and my feeling is that we have a better and more appropriate venue to carve the requirements that the operators and customers are requesting when buying the equipment. http://tools.ietf.org/html/draft-gont-opsec-ipv6-firewall-reqs-00 We are also looking into that and I'm currently talking to Fernando maybe to incorporate (or at least sync) the FW requirements in RIPE-554 with the ones he wrote in that draft. Still no precise idea how to make all this work, so all suggestions welcome ;) The other thing also is something about QOS, need to dig my mailbox or go back to Eric Vyncke and check what exactly was the issue so I can report back. Cheers, Jan
- 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 ]