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

"Dave Thaler" <dthaler@windows.microsoft.com> Tue, 17 January 2006 06: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 1EykDe-0005lT-E7; Tue, 17 Jan 2006 01:21:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EykDb-0005kL-Mc for ipv6@megatron.ietf.org; Tue, 17 Jan 2006 01:21:24 -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 BAA19670 for <ipv6@ietf.org>; Tue, 17 Jan 2006 01:19:58 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EykLc-0008DX-U6 for ipv6@ietf.org; Tue, 17 Jan 2006 01:29:44 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 16 Jan 2006 22:21:10 -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); Mon, 16 Jan 2006 22:21:09 -0800
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Jan 2006 22:21:09 -0800
Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.5.41]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Jan 2006 22:21:09 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C61B2E.340AF2F3"
Date: Mon, 16 Jan 2006 22:21:04 -0800
Message-ID: <2E33960095B58E40A4D3345AB9F65EC115359609@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: yes
Thread-Topic: draft-ietf-ipv6-node-requirements-11.txt
Thread-Index: AcXSNJTcdGSVKnWqTaqSRW+EeTCC/AAIdsGgD/zKtqAAtExIkAGEzJbQ
From: Dave Thaler <dthaler@windows.microsoft.com>
To: john.loughney@nokia.com
X-OriginalArrivalTime: 17 Jan 2006 06:21:09.0309 (UTC) FILETIME=[34B0DED0:01C61B2E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: ipv6@ietf.org
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

John, what do you propose to do about RFC2893?
(email attached)

I am fine with the changes proposed below for the other items.

-Dave

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
Of
> john.loughney@nokia.com
> Sent: Monday, January 09, 2006 4:55 AM
> To: ipv6@ietf.org
> Subject: RE: draft-ietf-ipv6-node-requirements-11.txt
> 
> Hi all,
> 
> I propose to update the Node Requirements to handle these:
> 
>   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
> 
> Changes are:
> 
> "AH [RFC-4202] MAY be supported."
> 
> These texts would be removed:
>   "RFC-2401 is being updated by the IPsec Working Group."
>   "RFC-2406 and RFC 2402 are being updated by the IPsec Working
Group."
> 
> The plan would be to update these during AUTH48, assuming the WG
agrees
> with
> changes.
> 
> ========
> 
> OLD:
> 8.1 Basic Architecture
> 
>    Security Architecture for the Internet Protocol [RFC-2401] MUST be
>    supported. RFC-2401 is being updated by the IPsec Working Group.
> 
> NEW:
> 
> 8.1 Basic Architecture
> 
>    Security Architecture for the Internet Protocol [RFC-4301] MUST be
>    supported.
> 
> ==========
> 
> 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.
> 
> ============
> 
> I need to double-check sections 8.3 & 8.4, there are a few changes for
> these.  I will
> send suggested changes.
> 
> John
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
--- Begin Message ---
Here's another one:
RFC2893 is now obsoleted by RFC4213

Section 6.l.1 says:
"RFC 2893 is currently being updated."

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
Of
> Dave Thaler
> Sent: Thursday, January 05, 2006 3:05 PM
> To: john.loughney@nokia.com
> Cc: ipv6@ietf.org
> Subject: draft-ietf-ipv6-node-requirements-11.txt
> 
> 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
--------------------------------------------------------------------
--- End Message ---
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------