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 ]
Mohsen Souissi
mohsen.souissi at nic.fr
Tue Nov 9 05:46:33 CET 2010
Following Francis's messages, some references updates below: On 09 Nov, Francis Dupont wrote: [...] | | As long as we get at least 8 statements of support and no significant issues | are raised, we will ask the RIPE NCC to publish the document after fixing | minor editorial issues (if found). | | => there is at least one error: IKEv2 relies on IPsec-v3 so it is not | possible to require IPsec-v2 and IKEv2 with IPsec-v3 optional. | There are two ways to solve this: make IKEv2 optional or IMHO far better | swap IPsec-v2 and IPsec-v3. For IKEv2: s/[RFC4306, RFC4718]/[RFC5996] For IPsec-v3: s/[RFC2401]/[RFC4301] s/[RFC2402]/[RFC4302, RFC4835] s/[RFC2406]/[RFC4303, RFC4835] Btw, to monitor which RFC obsoletes/is obsoloted by/updates/is updated by which RFC(s), I would recommend this very good reference: http://www.rfc-editor.org/cgi-bin/rfcsearch.pl Mohsen.
- 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 ]