Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - OAM

Fernando Gont <fgont@si6networks.com> Mon, 27 July 2020 10:47 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE7623A187B; Mon, 27 Jul 2020 03:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 gK8mUkc8bpoW; Mon, 27 Jul 2020 03:47:23 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E6473A1854; Mon, 27 Jul 2020 03:47:22 -0700 (PDT)
Received: from [IPv6:2800:810:464:1f7:4ccc:6def:a83b:96ef] (unknown [IPv6:2800:810:464:1f7:4ccc:6def:a83b:96ef]) (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 2947C280CE7; Mon, 27 Jul 2020 10:47:17 +0000 (UTC)
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>, IPv6 Operations <v6ops@ietf.org>
Cc: "draft-gont-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-gont-v6ops-ipv6-ehs-packet-drops@ietf.org>
References: <ab6cb83e1ed74a63a494c83f63c9d371@huawei.com> <556c9c3a-b8e5-eb3d-cecb-dfe66cf98ac2@si6networks.com> <16647bab75e0466794ab711b960770fd@huawei.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <2a4e0970-f2f2-710b-6081-fbf7e9085285@si6networks.com>
Date: Mon, 27 Jul 2020 07:17:23 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <16647bab75e0466794ab711b960770fd@huawei.com>
Content-Type: text/plain; charset="koi8-r"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/nuNETyTnJmQv6a-qBmTnuW8-c6o>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - OAM
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 10:47:25 -0000

On 27/7/20 06:56, Vasilenko Eduard wrote:
> Hi Fernando,
> May be me misunderstood the point of the draft in 1st place.
> I do see it as a warning list for potential issues that admin should research a little deeper before he/she would enable some EHs.

Nope.

What this document tries to do is to shed some light into why packets 
with EHs are largely dropped in the public Internet.

And essentially it notes that in many cases operators don't have many 
other options.

RFC7872 (as well as other studies referenced in our draft) have provided 
data about the extent to which packets with EHs are dropped in the 
public Internet.

And this document elaborates on the operational reality that many 
operators have not much of a choce than resorting to dropping them.

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