Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - implications from new development for EHs
Fred Baker <fredbaker.ietf@gmail.com> Fri, 31 July 2020 14:01 UTC
Return-Path: <fredbaker.ietf@gmail.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 F24893A0B53
for <v6ops@ietfa.amsl.com>; Fri, 31 Jul 2020 07:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=gmail.com
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 YZb45zEs9yW9 for <v6ops@ietfa.amsl.com>;
Fri, 31 Jul 2020 07:01:33 -0700 (PDT)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com
[IPv6:2607:f8b0:4864:20::1030])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 85AA63A0A55
for <v6ops@ietf.org>; Fri, 31 Jul 2020 07:01:33 -0700 (PDT)
Received: by mail-pj1-x1030.google.com with SMTP id t15so7903745pjq.5
for <v6ops@ietf.org>; Fri, 31 Jul 2020 07:01:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=JtrjPct49JUf7V7QdyUMcfYpeIH5JQes0Ui2dXrtE/k=;
b=jPdT5S+ju7eDV4EHvyu/Ne/VKAAkBOMswjv8b0J6G6e985Rv8KPEzilDiM9BCTaP1z
TCTpxO1Hdh+dFdX0Im/tL37rM1yI7QIAzJN+F+zYqMraAZmg7sNpHjO5sovlASzt/LgK
srP8IiwTzoNigRcAM8zSyazvrGqSQ1cvA1uaZuuQBiVc6vdV10GHtsJbAO9bM4LMrLAo
FKr+qlxzZxYQQqzdMSkOG/+htBGq0QORHY9xl64908/60yRKaWgBjyRbWrm3RW+Cgja2
Ct/kCDsHWlmYNOxK3Zk6Jal+4OKeWz70QkrSPHhXwm4btnRz93nYOIM0yHUl2M0vppOU
5v0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=JtrjPct49JUf7V7QdyUMcfYpeIH5JQes0Ui2dXrtE/k=;
b=O1Bb7CfoUEJeocdsQxne2mdIgbNjO2AKZ4Wt3Pd1Y9tEuMJ2HiX5/pSiDsIfrrohxF
pWsFz5lerLOBoBGcaxAnKabRwCCBdQJUOL++uvV+MrfBm8xqpyIb+qcwdnLEL+4D6HiF
eQYGc9P7ZlaywSCRUOLHx2kI0jUSnEk4pI+NzOVtI2Df0JqrtMqDhj7an0nJCMpnsCsY
itjao/KXh/Tvzrka5oVEu4QC8j1SQA4+MC6bxzdWJ6hOB5o3EV2e5v6Bk9AQwrHpWmIS
CLOY7yuFgYzNysdWKVH4lfmDkMw0ZqN/vp4t8YJVpanyxSAoYVZAiDCcwZNqjZPtUVCW
5XmA==
X-Gm-Message-State: AOAM532W1z5Iu4LQe1Rvsgf8t3B/VxlmHMHrzxzFg1G19CCmdsVW0/Pr
kfq0AnL4iYVDDGQo3mrsJZc83/0z7xM=
X-Google-Smtp-Source: ABdhPJxQ1aEbOedwiZvkTG2FHBrXWwPrZLaBIelLKsQNyituTobm7kW47bSix/GfpjJTQLqGN0u1wA==
X-Received: by 2002:a17:902:6f:: with SMTP id
102mr3700118pla.163.1596204092600;
Fri, 31 Jul 2020 07:01:32 -0700 (PDT)
Received: from ?IPv6:2600:8802:5800:652::199f? ([2600:8802:5800:652::199f])
by smtp.gmail.com with ESMTPSA id c9sm8983096pjr.35.2020.07.31.07.01.31
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Fri, 31 Jul 2020 07:01:32 -0700 (PDT)
Content-Type: text/plain;
charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <4573db3f-ac8d-3103-1979-e803ae40f117@si6networks.com>
Date: Fri, 31 Jul 2020 07:01:31 -0700
Cc: IPv6 Operations <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <28BE382F-E455-4B22-95FE-18924DF0FCFE@gmail.com>
References: <d8d59ce07f7f4031a545ff6e24fdbb88@huawei.com>
<20200729084351.GG2485@Space.Net>
<32BAEAEA-7352-4BAE-ADA8-FDA2395D5732@employees.org>
<a6ed89a8-c12e-b8d2-c720-5cc02e127a68@si6networks.com>
<FCBD1043-A0B2-435A-9AB9-0FCE3566C769@employees.org>
<4573db3f-ac8d-3103-1979-e803ae40f117@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>,
otroan@employees.org
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1gOJUP2nzt0TZ8OxJiuVWwg58kU>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension
Headers - implications from new development for EHs
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: Fri, 31 Jul 2020 14:01:41 -0000
If I may make a minor suggestion... If you're going to throw brickbats at each other, that seems to be more appropriate to private exchanges. In 6man, there is a discussion regarding draft-ietf-6man-mtu-option, which looks at the issue of extension headers, and - based on data - makes suggestions of how one might use them in a manner that is not filtered by the network. Their approach seems to not start from "let's deprecate everything" or "any opinion that disagrees with mine is idiocy". Frankly, I think there might be value in it. > On Jul 29, 2020, at 3:50 AM, Fernando Gont <fgont@si6networks.com> wrote: > > On 29/7/20 07:43, otroan@employees.org wrote: >>>> Anyway I don't quite understand what this document adds to work describing ossification in general >>> >>> Avoiding rehashing the same discussion everytime the issue of EHs comes up? >> So you are proposing to fully embrace ossification and deprecate all EHs? > > I'm proposing to document and acknowledge reality. > > Are you proposing to continue in denial? > > Thanks, > -- > Fernando Gont > SI6 Networks > e-mail: fgont@si6networks.com > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 > > > > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops
- [v6ops] Operational Implications of IPv6 Packets … Vasilenko Eduard
- Re: [v6ops] Operational Implications of IPv6 Pack… Gert Doering
- Re: [v6ops] Operational Implications of IPv6 Pack… Vasilenko Eduard
- Re: [v6ops] Operational Implications of IPv6 Pack… Gert Doering
- Re: [v6ops] Operational Implications of IPv6 Pack… otroan
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Gert Doering
- Re: [v6ops] Operational Implications of IPv6 Pack… otroan
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Philip Homburg
- Re: [v6ops] Operational Implications of IPv6 Pack… Gert Doering
- Re: [v6ops] Operational Implications of IPv6 Pack… Tom Herbert
- Re: [v6ops] Operational Implications of IPv6 Pack… Gert Doering
- Re: [v6ops] Operational Implications of IPv6 Pack… Tom Herbert
- Re: [v6ops] Operational Implications of IPv6 Pack… Gert Doering
- Re: [v6ops] Operational Implications of IPv6 Pack… Tom Herbert
- Re: [v6ops] Operational Implications of IPv6 Pack… Joseph Touch
- Re: [v6ops] Operational Implications of IPv6 Pack… Owen DeLong
- Re: [v6ops] Operational Implications of IPv6 Pack… Joseph Touch
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Brian E Carpenter
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Fred Baker
- [v6ops] Operational Implications of IPv6 Packets … tom petch
- Re: [v6ops] Operational Implications of IPv6 Pack… Vasilenko Eduard
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Brian E Carpenter
- Re: [v6ops] Operational Implications of IPv6 Pack… tom petch
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… tom petch
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Gyan Mishra
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Ole Troan
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Gyan Mishra
- Re: [v6ops] Operational Implications of IPv6 Pack… Fernando Gont
- Re: [v6ops] Operational Implications of IPv6 Pack… Gyan Mishra