Re: I-D Action: draft-smith-6man-in-flight-eh-insertion-harmful-00.txt

Nick Hilliard <nick@foobar.org> Sun, 13 October 2019 10:25 UTC

Return-Path: <nick@foobar.org>
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 183C2120072 for <ipv6@ietfa.amsl.com>; Sun, 13 Oct 2019 03:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 jZghMoi6In21 for <ipv6@ietfa.amsl.com>; Sun, 13 Oct 2019 03:25:08 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3C6B120024 for <ipv6@ietf.org>; Sun, 13 Oct 2019 03:25:07 -0700 (PDT)
X-Envelope-To: ipv6@ietf.org
Received: from crumpet.foobar.org (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id x9DAP3DG039389 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 13 Oct 2019 11:25:04 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.foobar.org
Subject: Re: I-D Action: draft-smith-6man-in-flight-eh-insertion-harmful-00.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: 6man <ipv6@ietf.org>
References: <157059901123.30422.11220423219059958820@ietfa.amsl.com> <362b80f7-fedc-7227-2931-0006e6b81812@gmail.com> <f2548b48-2d8d-01f0-f05c-0027a5cdeb91@foobar.org> <57b3a7bd-3dc3-d8be-0ac4-7218abdd94d8@gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <51fdb3bc-3155-c0c8-a34b-f68868885a24@foobar.org>
Date: Sun, 13 Oct 2019 11:25:02 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 PostboxApp/7.0.5.2
MIME-Version: 1.0
In-Reply-To: <57b3a7bd-3dc3-d8be-0ac4-7218abdd94d8@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/ipv6/nOOY7VpUElocFdPj7ONvrG7HKqU>
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: Sun, 13 Oct 2019 10:25:10 -0000

Brian E Carpenter wrote on 13/10/2019 01:36:
> The packet is too dumb to know anything ;-). My question is how each
> node it traverses knows. Indeed, Mark's draft describes a scenario
> where the controlled domain argument breaks, because the exit node
> might not know that the packet had suffered EH insertion. The
> draft-voyer- scenario is not like that, because the affected IPv6
> headers are created locally and identifiable as such.

the world isn't nearly this pigeonholed though.  The edge around this 
"controlled domain" that you're implicitly suggesting is sharply-defined 
is in reality more of a blurry smear.  Think tunnels, leaks, back-doors, 
"SD-WAN" (whatever that means), policy routing, routed VPNs, etc.

If the ietf wants to define a new ipv6-like protocol which is not 
guaranteed to be interoperable with 8200, there's still space in 
www.iana.org/assignments/version-numbers to accommodate this :-)

Nick