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

Fernando Gont <fgont@si6networks.com> Wed, 16 September 2020 09:43 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 EC4033A0F6C for <v6ops@ietfa.amsl.com>; Wed, 16 Sep 2020 02:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level:
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=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 V-JWX-h5vCoM for <v6ops@ietfa.amsl.com>; Wed, 16 Sep 2020 02:43:47 -0700 (PDT)
Received: from skynet.si6networks.com (unknown [83.247.7.195]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6560C3A0F68 for <v6ops@ietf.org>; Wed, 16 Sep 2020 02:43:41 -0700 (PDT)
Received: from [IPv6:2800:810:464:1088:9dfd:9390:d75d:cb60] (unknown [IPv6:2800:810:464:1088:9dfd:9390:d75d:cb60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by skynet.si6networks.com (Postfix) with ESMTPSA id B97561F32; Wed, 16 Sep 2020 06:43:38 -0300 (-03)
To: tom petch <ietfc@btconnect.com>
Cc: IPv6 Operations <v6ops@ietf.org>
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> <DEB1318E-0E5B-4093-A691-8E1FD35B9F50@strayalpha.com> <A197EF3A-1E1E-40F1-BB50-68469E3C8E63@delong.com> <44481FC7-6E3F-4D5A-A5A9-A338C1836EA1@strayalpha.com> <2ad804a2-e714-6256-3afa-4d4a92fd6d3c@si6networks.com> <9c026e30-149b-172f-0953-456fb2d1e715@gmail.com> <AM7PR07MB6248A43FCBBB5D34AA2DA9AAA0230@AM7PR07MB6248.eurprd07.prod.outlook.com> <7bc1ea18-01c5-54f7-a65d-a53722a4d3c9@si6networks.com> <AM7PR07MB624842F364784EF3AC5B0647A0200@AM7PR07MB6248.eurprd07.prod.outlook.com> <591f5a76-b375-7391-ad4b-bf14ad215536@si6networks.com> <AM7PR07MB6248051BB6A4DCCD8545C730A0200@AM7PR07MB6248.eurprd07.prod.outlook.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <e66b4848-634d-0905-6bc4-7cd76dd62ea8@si6networks.com>
Date: Wed, 16 Sep 2020 05:40:41 -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: <AM7PR07MB6248051BB6A4DCCD8545C730A0200@AM7PR07MB6248.eurprd07.prod.outlook.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/1Z7057MaWVTeYKpJ3rnNEqEhnp0>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers
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: Wed, 16 Sep 2020 09:43:53 -0000

Hi, Tom,

On 15/9/20 13:08, tom petch wrote:
> From: Fernando Gont <fgont@si6networks.com> Sent: 15 September 2020
> 12:24
> 
> Hi, Tom,
> 
> On 15/9/20 06:05, tom petch wrote: [...]
>> 
>> I wouldn't mind writing a Section that sits between the current
>> Sections 2 and 3 with more background on extension headers, if you
>> think that would be of value.
>> 
>> <tp> Yes please.  One page or two pages max, summarising why they
>> were thought a good idea, the different types and their uses, how
>> widely used they are  and with references;  RFC8200 may be
>> Normative but it takes a while to appear and that after RFC2460!

Ok.  I will craft text and send it to the list for review before
incorporating it.



> An intro to EHs -- and e.g., how the structure compares to the IPv4 
> packet structure is simply and doable. OTOH, what you suggest might
> now. :-)
> 
> e.g.,Not sure one can tell how widely used they are. Also, getting
> into enumerating EHs will result in the relevant section becoming
> stale soon, since there seems to be quite a bit of development in
> this area.
> 
> <tp> My sense is of the middle part of the I-D, the technical detail,
> is floating in mid-air, lacking an introduction, lacking a
> conclusion. and as such will only convince those who are already
> convinced.

FWIW, at lesast from my pov, we don't really want to convince people (of
doing this or that), but rather want to document the reasons for which
people may drop packets with EHs. i.e. documenting that such packets may
be dropped for very valid rational reasons.


> I have to read between the lines to divine that there is a connection
> between fragmentation and EH, between length of packet header and EH,
> between security and EH and so on.  By not making the connection
> explicit, I think that you will lose your target audience.

Fair enough. I'm always keen to improving the document, so thanks for 
the suggestion!

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