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

john.loughney@nokia.com Mon, 09 January 2006 08:18 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 1EvsEj-0001Ck-Ov; Mon, 09 Jan 2006 03:18:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EvsEf-0001CN-Mi for ipv6@megatron.ietf.org; Mon, 09 Jan 2006 03:18:40 -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 DAA25234 for <ipv6@ietf.org>; Mon, 9 Jan 2006 03:17:19 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EvsL6-0004XB-Vu for ipv6@ietf.org; Mon, 09 Jan 2006 03:25:18 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k098IVHi023139; Mon, 9 Jan 2006 10:18:33 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jan 2006 10:18:28 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jan 2006 10:18:28 +0200
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: Mon, 09 Jan 2006 10:18:27 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D01869A7D@esebe100.NOE.Nokia.com>
Thread-Topic: draft-ietf-ipv6-node-requirements-11.txt
Thread-Index: AcYSxDLZ0btyQAz6TpGEIP66SRAFrgCCkVIQAAmsy1A=
To: Vishwas@sinett.com, brc@zurich.ibm.com, jari.arkko@kolumbus.fi
X-OriginalArrivalTime: 09 Jan 2006 08:18:28.0302 (UTC) FILETIME=[44F3F6E0:01C614F5]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org, dthaler@windows.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

Vishwas,


>I see a few more inconsistencies regarding the same RFC: 
>
>   Since ESP encryption and authentication are both optional, support
>   for the NULL encryption algorithm [RFC-2410] and the NULL
>   authentication algorithm [RFC-2406] MUST be provided to maintain
>   consistency with the way these services are negotiated.
>
>
>From RFC4301
>            - confidentiality-only (MAY be supported)
>            - integrity only (MUST be supported)
>            - confidentiality and integrity (MUST be supported)
>
>I think only encryption is now optional in RFC4301. We do not 
>necessarily need to allow NULL authentication either. Actually 
>this is still a problem with RFC4305 and it was not updated 
>because the issue was found late in the RFC process.

What was the issue found late with RFC4305?

John

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