IETF Logo Mail Archive

Re: draft-ietf-ipv6-deprecate-01-01-candidate-02

Elwyn Davies <elwynd@dial.pipex.com> Wed, 27 June 2007 12:12 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3WNq-0007iU-DN; Wed, 27 Jun 2007 08:12:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3WNo-0007dX-Dv for ipv6@ietf.org; Wed, 27 Jun 2007 08:12:28 -0400
Received: from smtp.aaisp.net.uk ([81.187.81.51]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3WNo-0008U0-5z for ipv6@ietf.org; Wed, 27 Jun 2007 08:12:28 -0400
Received: from 247.254.187.81.in-addr.arpa ([81.187.254.247]) by smtp.aaisp.net.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.62) (envelope-from <elwynd@dial.pipex.com>) id 1I3WNE-00063W-7S; Wed, 27 Jun 2007 13:11:52 +0100
Message-ID: <4682546B.5010405@dial.pipex.com>
Date: Wed, 27 Jun 2007 13:13:31 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <3CC9E5E1-0095-4273-BF9E-FA0273F5B86C@ca.afilias.info> <4682354C.5010906@gmail.com>
In-Reply-To: <4682354C.5010906@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-01-01-candidate-02
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>
Errors-To: ipv6-bounces@ietf.org

I also think this is in good shape.

One addition that would be useful is to reference the v6ops security 
overview (draft-ietf-v6ops-security-overview-06.txt currently in AUTH48 
and about to be published as RFC 4942).
This also discusses security issues with RH0 (including the 
amplification attack) and routing headers in general.

Regards,
Elwyn

Brian E Carpenter wrote:
> FWIW, my opinion is 'ship it'. It seems like time
> to get a formal readout of (rough) WG consensus
> on this.
>
>     Brian
>
> --------------------------------------------------------------------
> 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
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email