Re: SRH insertion vs SRH insertion + encapsulation

Fernando Gont <fgont@si6networks.com> Sat, 07 September 2019 23:26 UTC

Return-Path: <fgont@si6networks.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 E724D1201DC; Sat, 7 Sep 2019 16:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 yspZlKNocOZk; Sat, 7 Sep 2019 16:26:43 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2356C12013C; Sat, 7 Sep 2019 16:26:43 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-20.home.otenet.gr [94.69.228.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 56213861CF; Sun, 8 Sep 2019 01:26:38 +0200 (CEST)
Subject: Re: SRH insertion vs SRH insertion + encapsulation
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Robert Raszuk <robert@raszuk.net>, Mark Smith <markzzzsmith@gmail.com>
Cc: draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>, "6man@ietf.org" <6man@ietf.org>
References: <CAOj+MMETQa=OfovZak35VfnY+T6qzU9BxAhmFMXz1b7kSppyQg@mail.gmail.com> <CAO42Z2xMWN92m7iiLiEW2AFCx0iCMGAa_BvsRwzCzb_BnuzWhA@mail.gmail.com> <CAOj+MMGOKUjRFFq8Y977OV47x6qtCvSUixQh-7sgwAQidrtdPw@mail.gmail.com> <BYAPR05MB5463306B3328F460C2417764AEB50@BYAPR05MB5463.namprd05.prod.outlook.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <49dd15de-3985-babe-028a-6f2ac9bbe76b@si6networks.com>
Date: Sun, 08 Sep 2019 02:11:48 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <BYAPR05MB5463306B3328F460C2417764AEB50@BYAPR05MB5463.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rc8hBf4dsl9wBc5oiLj8NLOMMRI>
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: Sat, 07 Sep 2019 23:26:45 -0000

On 8/9/19 01:52, Ron Bonica wrote:
[...]
>  
> 
> IMHO, EH insertion modifies the semantics of the IPv6 source address.
> Today, the IPv6 source address indicates the source of an IP packet and
> **ALL** of its contents. If transit routers are allowed to insert
> extension headers, downstream routers can no longer identify the source
> of a packet and all of its contents.>
>  
> 
> Granted, in some cases, transit routers are allowed to modify a packet
> (e.g., Hop Count, DHCP, mutable options). But there is a big difference
> between changing a field whose value is know to me mutable and inserting
> a new option.

Indeed, it's a major modification (besides the associated issues that
have been pointed out a number of times by several folks).

That's why I think it's not even in the scope of 6man.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492