Re: New Version Notification for draft-voyer-6man-extension-header-insertion-08.txt

Sander Steffann <sander@steffann.nl> Sat, 23 November 2019 21:19 UTC

Return-Path: <sander@steffann.nl>
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 4C64D12004F for <ipv6@ietfa.amsl.com>; Sat, 23 Nov 2019 13:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
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 g3n689ZRhxFG for <ipv6@ietfa.amsl.com>; Sat, 23 Nov 2019 13:19:21 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC17B120024 for <6man@ietf.org>; Sat, 23 Nov 2019 13:19:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id AFC9655; Sat, 23 Nov 2019 22:19:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:in-reply-to:date:date:subject:subject :mime-version:content-type:content-type:message-id:from:from :received:received; s=mail; t=1574543954; bh=BmtI6LnQqnjJF1GDrcb mQOatQFZle4vAsfmI417TCT4=; b=ZdtkTmf19P/acTcoz0Xq1inHmFpuk5GlGXF qgNUUeDCFoFptgfagEKEZqeZprHUMYD4rnhJ4XTNr/OZkrxe/X1jEgXDMdgutqoU saTg6KLjLtvSjTfevOX8+q/Jh93LmBS4ceRTXvFuU6ClU1BAv1IcqBXoer6u950i 5pGFSKGI=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GcDpDROJmqrS; Sat, 23 Nov 2019 22:19:14 +0100 (CET)
Received: from [IPv6:2a02:a213:a300:ce80:d4c1:89f2:698b:7c60] (unknown [IPv6:2a02:a213:a300:ce80:d4c1:89f2:698b:7c60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 164E154; Sat, 23 Nov 2019 22:19:13 +0100 (CET)
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Message-Id: <C03A0BD7-0662-4C5C-B4D9-6FE776A53AD6@steffann.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_E26DC315-5505-42B8-871C-D0273B393817"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
Subject: Re: New Version Notification for draft-voyer-6man-extension-header-insertion-08.txt
Date: Sat, 23 Nov 2019 22:19:07 +0100
In-Reply-To: <51AAA37A-847E-48B9-8965-7449898B8F18@employees.org>
Cc: Fernando Gont <fgont@si6networks.com>, 6man <6man@ietf.org>
To: Ole Troan <otroan@employees.org>
References: <157422734071.5406.14331301768750185617.idtracker@ietfa.amsl.com> <851F7007-3DD5-42F3-8884-8842DA07EE53@cisco.com> <1cfd682f-d6bc-a697-38a7-933aa0485b8a@si6networks.com> <D4436EF5-2B97-44A4-915D-EF7611590B51@steffann.nl> <51AAA37A-847E-48B9-8965-7449898B8F18@employees.org>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rBLBhfhnJiTPEgjlQIWvmT3OGGE>
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, 23 Nov 2019 21:19:23 -0000

Hi Ole,

> A whole session at the IETF meeting in Singapore was spent on the topic of header insertion in general and in the context of SR.
> Progress was made.
> I would encourage you to review that session.
> Video recording is here: https://www.youtube.com/watch?v=ZJU0m1EhjaI
> 
> My reading of the working group session was to proceed work on both drafts. With neither draft updating RFC8200.

Then let me state clearly on the list:
- I still object to EH insertion and do not consider the risks to be mitigated enough to drop my objection.
- I object to not updating RFC8200 in any RFC that contradicts its content. If EH insertion should be accepted by this WG despite the objections then implementers reading RFC8200 need to know that a conscious exception has been made. This will influence their understanding of the IPv6 protocol and its expected behaviour.

RFC8200 is very clear:

"""
   Extension headers (except for the Hop-by-Hop Options header) are not
   processed, inserted, or deleted by any node along a packet's delivery
   path, until the packet reaches the node (or each of the set of nodes,
   in the case of multicast) identified in the Destination Address field
   of the IPv6 header.
"""

There is no "except when defined otherwise" in that text.

> Let's focus on communicating and understanding the positions of each "camp" and proceed with the technical arguments.
> I would discouarge "process arguments".

I agree to this on the discussion about how harmful EH insertion can be. Let's start with draft-smith-6man-in-flight-eh-insertion-harmful and evaluate how draft-voyer-6man-extension-header-insertion deals with all the possible failure scenarios.

Regarding updating RFC8200, I definitely want to raise a "process argument".

> If you believe those are necessary, please take those with the chairs and AD and we can summarize to the group.

I hope the above is a good summary :)

Cheers,
Sander