RE: draft-ietf-ipv6-node-requirements-11.txt
"Vishwas Manral" <Vishwas@sinett.com> Mon, 09 January 2006 03:39 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 1Evnso-00016n-CI; Sun, 08 Jan 2006 22:39:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Evnsj-00016c-6X for ipv6@megatron.ietf.org; Sun, 08 Jan 2006 22:39:43 -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 WAA10396 for <ipv6@ietf.org>; Sun, 8 Jan 2006 22:38:22 -0500 (EST)
Received: from 63-197-255-154.ded.pacbell.net ([63.197.255.154] helo=sinett.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Evnz7-0005xZ-Rl for ipv6@ietf.org; Sun, 08 Jan 2006 22:46:19 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 08 Jan 2006 19:39:16 -0800
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B2C3A50D@sinett-sbs.SiNett.LAN>
Thread-Topic: draft-ietf-ipv6-node-requirements-11.txt
Thread-Index: AcYSxDLZ0btyQAz6TpGEIP66SRAFrgCCkVIQ
From: Vishwas Manral <Vishwas@sinett.com>
To: Brian E Carpenter <brc@zurich.ibm.com>, Jari Arkko <jari.arkko@kolumbus.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: quoted-printable
Cc: john.loughney@nokia.com, ipv6@ietf.org, Dave Thaler <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
Hi Brian/ Jari, 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. Thanks, Vishwas -----Original Message----- From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian E Carpenter Sent: Friday, January 06, 2006 6:50 PM To: Jari Arkko Cc: john.loughney@nokia.com; ipv6@ietf.org; Dave Thaler Subject: Re: draft-ietf-ipv6-node-requirements-11.txt IMHO, the reference updates should be done during AUTH48 without further discussion, but making AH optional seems like a substantive change. Personally, I would support that change, i.e. s/MUST/MAY/. Brian (speaking only for myself) Jari Arkko wrote: > They should be updated. By the way I noticed recently > that the RFC Editor does not necessarily do "obsoleted by" > updates to references automatically. This stuff needs to > be done by the authors in AUTH48. And in this particular > case we have even text changes, as you point out. > > By the way, there are also substantive changes in the > new IPsec documents. For instance, AH support is no > longer a MUST. I think this should be reflected in the > node requirements document too, as that currently > says "AH [RFC-2402] MUST be supported.". > > There's probably an impact in the algorithms and key > management sections, too... > > --Jari > > Dave Thaler wrote: > >> The draft in the RFC-editors queue now references obsoleted (as of last >> month) RFCs. Specifically: >> RFC2401 is now obsoleted by RFC4301 >> RFC2402 is now obsoleted by RFC4302 >> RFC2404 is now obsoleted by RFC4305 >> RFC2406 is now obsoleted by RFC4303, RFC4305 >> RFC2407,2408,2409 are now obsoleted by RFC4306 >> >> Also two statements in section 8 are now obsolete as a result: >> "RFC-2401 is being updated by the IPsec Working Group." >> "RFC-2406 and RFC 2402 are being updated by the IPsec Working Group." >> >> Can these be updated? >> >> -Dave >> >> -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- draft-ietf-ipv6-node-requirements-11.txt Dave Thaler
- Re: draft-ietf-ipv6-node-requirements-11.txt Jari Arkko
- Re: draft-ietf-ipv6-node-requirements-11.txt Pekka Savola
- Re: draft-ietf-ipv6-node-requirements-11.txt Brian E Carpenter
- RE: draft-ietf-ipv6-node-requirements-11.txt Dave Thaler
- RE: draft-ietf-ipv6-node-requirements-11.txt john.loughney
- RE: draft-ietf-ipv6-node-requirements-11.txt Vishwas Manral
- RE: draft-ietf-ipv6-node-requirements-11.txt john.loughney
- RE: draft-ietf-ipv6-node-requirements-11.txt Vishwas Manral
- RE: draft-ietf-ipv6-node-requirements-11.txt john.loughney
- RE: draft-ietf-ipv6-node-requirements-11.txt Dave Thaler
- RE: draft-ietf-ipv6-node-requirements-11.txt Dave Thaler