IETF Logo Mail Archive

RE: draft-ietf-ipv6-node-requirements-11.txt

"Dave Thaler" <dthaler@windows.microsoft.com> Thu, 02 February 2006 20:02 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4key-0000xJ-VM; Thu, 02 Feb 2006 15:02:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4kes-0000ta-Fh for ipv6@megatron.ietf.org; Thu, 02 Feb 2006 15:02:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04539 for <ipv6@ietf.org>; Thu, 2 Feb 2006 15:00:35 -0500 (EST)
Received: from mail1.microsoft.com ([131.107.3.125]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4kq7-00013q-Q5 for ipv6@ietf.org; Thu, 02 Feb 2006 15:14:02 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 2 Feb 2006 12:02:00 -0800
Received: from red-hub-04.redmond.corp.microsoft.com ([157.54.3.6]) by mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Feb 2006 12:01:59 -0800
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.69.169]) by red-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Feb 2006 12:01:59 -0800
Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.5.41]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Feb 2006 12:01:59 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 02 Feb 2006 12:01:57 -0800
Message-ID: <2E33960095B58E40A4D3345AB9F65EC11583E8FF@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: draft-ietf-ipv6-node-requirements-11.txt
Thread-Index: AcXSNJTcdGSVKnWqTaqSRW+EeTCC/AAIdsGgD/zKtqAAtExIkATFyLhA
From: Dave Thaler <dthaler@windows.microsoft.com>
To: john.loughney@nokia.com, ipv6@ietf.org
X-OriginalArrivalTime: 02 Feb 2006 20:01:59.0407 (UTC) FILETIME=[86A56FF0:01C62833]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
Cc: Charlie Kaufman <charliek@exchange.microsoft.com>
Subject: RE: draft-ietf-ipv6-node-requirements-11.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
Of
> john.loughney@nokia.com
[...]
> ==========
> 
> OLD:
> 8.2 Security Protocols
> 
>    ESP [RFC-2406] MUST be supported. AH [RFC-2402] MUST be supported.
>    RFC-2406 and RFC 2402 are being updated by the IPsec Working Group.
> 
> NEW
> 8.2 Security Protocols
> 
>    ESP [RFC-4306] MUST be supported. AH [RFC-4302] MAY be supported.
              ^^^^

Typo... ESP is RFC 4303 not RFC 4306 (which is IKEv2).


Also on the IKEv1 vs IKEv2 RFCs: the two are not interoperable, just
like IPv4 and IPv6 are not interoperable.  So the problem is that
existing implementations support IKEv1 only and if new implementations
support IKEv2 only, then they can't talk.

So the question I have is whether it should mention both.
By comparison the document says "IPv6 nodes MAY support IPv4".

-Dave

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email