IETF Logo Mail Archive

Re: I-D ACTION:draft-jabley-ipv6-rh0-is-evil-00.txt

"Ebalard, Arnaud" <Arnaud.Ebalard@eads.net> Thu, 10 May 2007 14:55 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 1HmA3L-0005As-Lu; Thu, 10 May 2007 10:55:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmA3K-0005AN-L9 for ipv6@ietf.org; Thu, 10 May 2007 10:55:34 -0400
Received: from mx1.its.eads.net ([193.56.40.66]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmA3H-00083p-QU for ipv6@ietf.org; Thu, 10 May 2007 10:55:34 -0400
Received: from fr-gate2.mailhub.intra.corp ([53.154.16.34]) by mx1.its.eads.net with Microsoft SMTPSVC(6.0.3790.2499); Thu, 10 May 2007 16:53:06 +0200
Received: from sfrsu800.hq.corp ([10.21.8.22]) by fr-gate2.mailhub.intra.corp with Microsoft SMTPSVC(5.0.2195.6713); Thu, 10 May 2007 16:58:24 +0200
Received: from [172.16.23.99] (10.251.5.23 [10.251.5.23]) by gecko.hq.corp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id H92ZL7YV; Thu, 10 May 2007 16:55:33 +0200
X-Mailer: Apple Mail (2.752.2)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 10 May 2007 16:55:31 +0200
Message-ID: <F69C6132-7582-45FF-828B-5B2C1DBEA538@eads.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: I-D ACTION:draft-jabley-ipv6-rh0-is-evil-00.txt
Thread-Index: AceTE0Kgvq4w9nkHQ3G0UyKZHnqopA==
From: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
To: Brian Haberman <brian@innovationslab.net>
X-OriginalArrivalTime: 10 May 2007 14:58:24.0562 (UTC) FILETIME=[A8992920:01C79313]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: I-D ACTION:draft-jabley-ipv6-rh0-is-evil-00.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>
Errors-To: ipv6-bounces@ietf.org

Le 10 mai 07 à 15:50, Brian Haberman a écrit :

> What happens if the packet is encrypted?

If you mean ESP-encrypted, ESP is "viewed as an end-to-end payload and
thus should appear after hop-by-hop, routing, and fragmentation  
extension
headers". -- quoted from RFC 2406. Note that it is just a "should".

So, for ESP-protected traffic, this should be similar to any other  
upper layer protocol. And, if the Routing Header is protected (and  
the endpoint of the IPsec connection accepts that order), it will  
still be dropped in the context of the draft (i.e. by the node the  
packet is addressed to).

a+

-- Arnaud Ebalard
EADS Innovation Works - IT Sec Research Engineer
PGP KeyID:047A5026 FingerPrint:47EB85FEB99AAB85FD0946F30255957C047A5026

--------------------------------------------------------------------
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