Re: Removal of destination options that precede a routing header

Sander Steffann <sander@steffann.nl> Tue, 26 May 2020 16:04 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 24B493A07E5 for <ipv6@ietfa.amsl.com>; Tue, 26 May 2020 09:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 (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 NGucC7Mbbcoy for <ipv6@ietfa.amsl.com>; Tue, 26 May 2020 09:04:28 -0700 (PDT)
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 204F03A080E for <6man@ietf.org>; Tue, 26 May 2020 09:04:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 6EC0B49; Tue, 26 May 2020 18:04:11 +0200 (CEST)
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=1590509049; bh=JkKl5vZiEsr45/+GB+V LaqvbxTbaznXVc5QrCkIFNBY=; b=YTsGpo11PuqPnpWfq/AVzSeIwDW8xhT3yP2 6eIGw56vXYjpCM44HLZZouDqOus97FedFbpbZVOPgBIttk7M/fVV5nI/o6ZNfVn0 N97A8VCLPywa3vPMz/Np7mPps4JHbKpqT/0PNFcOTi6GtKnsKBjMN3hf/lbEnOsQ A1YZov6Y=
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 FgN55mOFgTYy; Tue, 26 May 2020 18:04:09 +0200 (CEST)
Received: from [IPv6:2a02:a213:a300:ce80:19f6:dcc2:c2ab:45c4] (unknown [IPv6:2a02:a213:a300:ce80:19f6:dcc2:c2ab:45c4]) (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 182573C; Tue, 26 May 2020 18:04:08 +0200 (CEST)
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Message-Id: <C0169F82-E302-4DE4-8263-1CC0D33D8E56@steffann.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_AF2BE394-C635-452F-8A40-FE1AEB1A0158"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Removal of destination options that precede a routing header
Date: Tue, 26 May 2020 18:04:07 +0200
In-Reply-To: <DM6PR13MB306639AE0C4395931FF1961ED2B00@DM6PR13MB3066.namprd13.prod.outlook.com>
Cc: 6man <6man@ietf.org>
To: James Guichard <james.n.guichard@futurewei.com>
References: <DM6PR13MB306686E9F1A444C05BB5EF56D2B00@DM6PR13MB3066.namprd13.prod.outlook.com> <27AD0B48-3DDD-4EE6-9325-B897727BB30C@steffann.nl> <CAJn5=Kfhd+OvPP7JrNAyZesBehoMuW2C7c6WhtWCBjaiciVzMw@mail.gmail.com> <601AA381-3E3D-4C63-9DA8-A9FB0977F533@steffann.nl> <DM6PR13MB306639AE0C4395931FF1961ED2B00@DM6PR13MB3066.namprd13.prod.outlook.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hlywP27C5MbuHBKDi6bwDG9z8a8>
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: Tue, 26 May 2020 16:04:34 -0000

Hi,

> Thank you for the clarification.
> 
> Dare I say It as I don’t want to start another long and exhausting email thread 😉 but it is kind of interesting as knowing this helps to clarify that when RFC 8200 is talking about the node identified in the destination address field of the IPv6 header then said node is able to process, delete and insert extension headers according to the text; in order to process DOH before a RH then that node must be the router as identified in the DA of the incoming packet and not the ultimate destination as previously argued in another thread.

I do interpret the text in a different way, but I agree that the current text can be interpreted like you describe as well. I'm not sure that was the intention, but that is what it is, and second guessing intention afterwards is rather pointless, so… :)

I do think that header insertion/deletion between the source and final destination can be harmful, but let's resolve that by looking forward to what we actually want. Looking back at 8200 and disagreeing on what it says isn't very productive. We already know we disagree. Let's provide better guidance to future protocol designers.

Cheers,
Sander