Re: IPv6 header insertion in a controlled domain

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 11 December 2019 07:17 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1216120834 for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2019 23:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pWwa-2BbNy8r for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2019 23:17:56 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B94A8120833 for <ipv6@ietf.org>; Tue, 10 Dec 2019 23:17:55 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xBB7Hr4t010127 for <ipv6@ietf.org>; Wed, 11 Dec 2019 08:17:53 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D06A8201EC6 for <ipv6@ietf.org>; Wed, 11 Dec 2019 08:17:53 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C5C25200CE7 for <ipv6@ietf.org>; Wed, 11 Dec 2019 08:17:53 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xBB7HrP9008673 for <ipv6@ietf.org>; Wed, 11 Dec 2019 08:17:53 +0100
Subject: Re: IPv6 header insertion in a controlled domain
To: ipv6@ietf.org
References: <BN7PR05MB5699F86F6DF1F224DF4A6E32AE580@BN7PR05MB5699.namprd05.prod.outlook.com> <C27A0E92-AF13-477B-9A22-DAB05494DE61@steffann.nl> <BN7PR05MB569952E6B42D62D8AF8F7AD2AE580@BN7PR05MB5699.namprd05.prod.outlook.com> <7B56011B-F95E-4F6D-ACD7-E6A342F33DDE@employees.org> <BN7PR05MB5699D718910309436CC52130AE580@BN7PR05MB5699.namprd05.prod.outlook.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <274ed009-7211-9f8f-8500-bd436fba1b1d@gmail.com>
Date: Wed, 11 Dec 2019 08:17:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0
MIME-Version: 1.0
In-Reply-To: <BN7PR05MB5699D718910309436CC52130AE580@BN7PR05MB5699.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/afgEeg8ph98bF5TfvdQEqLa3TlM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Dec 2019 07:17:58 -0000


Le 09/12/2019 à 23:38, Ron Bonica a écrit :
> Ole,
> 
> If the Routing header is inserted by one transit node and not removed
> before it reaches its ultimate destination, authentication will fail.
> Won't it?

I agree, authentication would fail, because the initial ICV computation 
covers headers that are absent at the reception.

Alex

> 
> Ron
> 
> 
> 
> Juniper Business Use Only
> 
> -----Original Message----- From: otroan@employees.org
> <otroan@employees.org> Sent: Monday, December 9, 2019 9:32 AM To: Ron
> Bonica <rbonica@juniper.net> Cc: Sander Steffann
> <sander@steffann.nl>; 6man WG <ipv6@ietf.org> Subject: Re: IPv6
> header insertion in a controlled domain
> 
> Ron,
> 
>> I believe that the second does apply.
> 
> That's not at all obvious to me. Elaborate please.
> 
> Cheers, Ole
> 
>> Juniper Business Use Only
>> 
>> -----Original Message----- From: Sander Steffann
>> <sander@steffann.nl> Sent: Monday, December 9, 2019 1:41 AM To: Ron
>> Bonica <rbonica@juniper.net> Cc: Ole Troan <otroan@employees.org>;
>> 6man WG <ipv6@ietf.org> Subject: Re: IPv6 header insertion in a
>> controlled domain
>> 
>> Hi Ron,
>> 
>>> See Section 7.5 of .....
>> 
>> Not choosing to use AH to protect the SRH is one thing, but not
>> supporting an AH in the existing packet when doing header insertion
>> is quite another. I want to be sure the second doesn't apply.
>> 
>> Cheers Sander
>> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>