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

Brian E Carpenter <brc@zurich.ibm.com> Fri, 06 January 2006 13:21 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 1EurX2-0005Uj-PP; Fri, 06 Jan 2006 08:21:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EurX0-0005Ub-AE for ipv6@megatron.ietf.org; Fri, 06 Jan 2006 08:21:22 -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 IAA01175 for <ipv6@ietf.org>; Fri, 6 Jan 2006 08:20:06 -0500 (EST)
Received: from mtagate2.uk.ibm.com ([195.212.29.135]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eurcp-0001UO-U6 for ipv6@ietf.org; Fri, 06 Jan 2006 08:27:28 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id k06DKZWT170194 for <ipv6@ietf.org>; Fri, 6 Jan 2006 13:20:42 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k06DKR1n037458 for <ipv6@ietf.org>; Fri, 6 Jan 2006 14:20:27 +0100
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id k06DKQ3F026407 for <ipv6@ietf.org>; Fri, 6 Jan 2006 14:20:26 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id k06DKQkX026389; Fri, 6 Jan 2006 14:20:26 +0100
Received: from zurich.ibm.com (sig-9-145-249-81.de.ibm.com [9.145.249.81]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id OAA83072; Fri, 6 Jan 2006 14:20:25 +0100
Message-ID: <43BE6E94.6050201@zurich.ibm.com>
Date: Fri, 06 Jan 2006 14:20:20 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
References: <2E33960095B58E40A4D3345AB9F65EC11514D9E3@win-msg-01.wingroup.windeploy.ntdev.microsoft.com> <43BE2928.3090706@kolumbus.fi>
In-Reply-To: <43BE2928.3090706@kolumbus.fi>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
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

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
>> --------------------------------------------------------------------
>>
>>  
>>
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


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