Re: [v6ops] I-D Action: draft-gont-v6ops-ipv6-ehs-packet-drops-04.txt

Fernando Gont <fernando@gont.com.ar> Mon, 27 July 2020 07:39 UTC

Return-Path: <fernando@gont.com.ar>
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 5F78F3A07B9 for <v6ops@ietfa.amsl.com>; Mon, 27 Jul 2020 00:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level:
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.267, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 xlG3PIY-GBC3 for <v6ops@ietfa.amsl.com>; Mon, 27 Jul 2020 00:39:48 -0700 (PDT)
Received: from tools.si6networks.com (v6toolkit.go6lab.si [IPv6:2001:67c:27e4::57]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA8033A1772 for <v6ops@ietf.org>; Mon, 27 Jul 2020 00:39:48 -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 tools.si6networks.com (Postfix) with ESMTPSA id F17BD3FF71; Mon, 27 Jul 2020 09:39:43 +0200 (CEST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IPv6 Operations <v6ops@ietf.org>
References: <159574132870.611.12077598721404194383@ietfa.amsl.com> <cc504d98-93ad-d14d-3362-e59b323d4b90@gmail.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <5f0f7715-ff53-e5b2-6803-df1aac573060@gont.com.ar>
Date: Mon, 27 Jul 2020 03:49:49 -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: <cc504d98-93ad-d14d-3362-e59b323d4b90@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jNz8OA9CoMTOCJB--P3G100bkFs>
Subject: Re: [v6ops] I-D Action: draft-gont-v6ops-ipv6-ehs-packet-drops-04.txt
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 07:39:50 -0000

On 26/7/20 19:14, Brian E Carpenter wrote:
> Hi,
> 
> IMHO this is useful work.
> 
>> A number of recent RFCs have discussed issues related to IPv6 extension headers,
> 
> I suggest to add RFC7045 to the bullet list, and delete the reference to it
> in the previous paragraph. In fact, the structure of the "Previous Work"
> section is a bit strange, with a prose paragraph followed by a bullet list.
> Maybe restructure that (e.g. transform it into a single longer bullet list)?

That's a good point.

I wonder if we could somehow separate:
* Std work that has become incorporated into the core spec.

* Other Std work that affects EHs but hasn't been incorporated into the 
core spec (e.g., RFC6980)

BTW... it seems that RFC7045 has not really been incorporated into 
RFC8200?   I mean, other work (e.g. RFC6946 has been incorporated into 
RFC8200, and currently their raison d'etre is mostly for the reader to 
find additional information -- but from the pov of RFC8200 is not really 
necessary to read RFC6946). OTOH, it would seem that RFC7045 still 
applies to RFC8200 in the very same way it applies/applied to RFC2460?
So in a way it should be in the bulleted list, but otoh it doesn't seem 
to have been incorporated into RFC8200 -- while it still applies to it?


Modulo RFC6980 (and RFC7045), it would seem that the first para (prose) 
could also be arranged as a set of bullets, noting something along the 
lines of "documents that discuss operational implications of EHs"?

And I guess we could also arrange the measurements stuff (last para) in 
their own set of bullets?

Thanks!

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1