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:26:32 CET 2010
On 9.11.10 4:29, Francis Dupont wrote: > We would appreciate if you let us know by the end of November 17, 2010 if > you have read the document and whether you support the publication of the > document. > > => yes Hi, Thnx for your support (for support from all of you :) ) > > 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. Theoretically I agree with you. But we try not to currently exclude too much hardware. What percentage of current equipment you can buy supports IPsec-v3 ? > > BTW I think the correct spelling for UPNP is UPnP (lower case 'n'). Will fix, 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 ]