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] Last Call (20101117): Requirements For IPv6 in ICT Equipment
- Previous message (by thread): [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment
- Next message (by thread): [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Zorz @ go6.si
jan at go6.si
Tue Nov 9 10:23:48 CET 2010
On 9.11.10 3:56, Mohsen Souissi wrote: > I support this document to be published. Good work, well done. > > Some suggestions: > > - RFC 2461 (2 occurrences) to be replaced by RFC 4861? > - RFC 2462 (1 occurrence) to be replaced by RFC 4862 Hi, fixed, thnx for head up. Will be visible in next version of the draft. > What about load balancers, these types of equipment can hardly fit in > the categories defined (if I'm correct). Yet they might be a pain in > termes ov v6-v4 functional and performance parity. This document is intended to be published as BCP and we can add/change things also later, after publication. I agree load balancers hardly fit in any category, but we had to stop expanding the complexity at some point :) If we find approach how to specify that without adding more complexity, we can add that later, if community will agree on that. thnx, /jan
- Previous message (by thread): [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment
- Next message (by thread): [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]