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] Latest draft for RIPE554-bis
- Previous message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
- Next message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Chown
Tim.Chown at jisc.ac.uk
Fri Nov 26 12:58:22 CET 2021
> On 26 Nov 2021, at 11:48, Jan Zorz - Go6 <jan at go6.si> wrote: > > On 26/11/2021 10:55, Tim Chown via ipv6-wg wrote: >> We do however have QoS requirements in RIPE554, e.g. in 4.4 and 4.5 there is Mandatory support for QoS [RFC2474, RFC3140] and two Optional items >> (QOS) Assured Forwarding [RFC2597] >> (QOS) Expedited Forwarding [RFC3246], >> So adding (QOS) Active Queue Management support [RFC7567] as optional is not a stretch, for 4.4 or for 4.7. > > So let's make it consistent, but then I would stop adding stuff and save this > for next version. > > Does this make sense? Yes, that’s what we agreed to do - the only thing that needs editing is the acknowledgements, unless new issues are raised before the 3rd Dec. Tim
- Previous message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
- Next message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]