Re: IPv6 header insertion in a controlled domain

Sander Steffann <sander@steffann.nl> Sun, 08 December 2019 12:49 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 9F22B12007A; Sun, 8 Dec 2019 04:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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 b9F0XyTjuDlM; Sun, 8 Dec 2019 04:49:09 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.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 13FC612000F; Sun, 8 Dec 2019 04:49:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 60A3E49; Sun, 8 Dec 2019 13:49:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:date:date:in-reply-to:from:from :subject:subject:mime-version:content-type:content-type:received :received; s=mail; t=1575809345; bh=K8T6WAb1q0brtVV6G9k9fVhAA5Uo QUWzcWZ5cWX4dZ4=; b=c+nY4ppi5/ee3bN3+ttDYHmzdBO6Y0kBdQEniywNLKcL 4WoogVToK33gmdU3PHo/9WuWzGB9gGSKj8yB/iMu/FOxbZtx9DkfB54iG5zF4WfK GZIQDvPq+hFfRYWLGbjCdHRasQ4AX0evisc5WugDADuEjPEQD5BvTHd36WN/aLg=
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 apUpKHFlrss7; Sun, 8 Dec 2019 13:49:05 +0100 (CET)
Received: from [IPv6:2a02:a213:a300:ce80:48c4:a854:5031:6d89] (unknown [IPv6:2a02:a213:a300:ce80:48c4:a854:5031:6d89]) (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 AAB813C; Sun, 8 Dec 2019 13:49:04 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_4A1B8EAA-6186-4921-BD92-A92D3138E3EA"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
Subject: Re: IPv6 header insertion in a controlled domain
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <324D4E35-97E8-42A2-912F-27C9FE033879@employees.org>
Date: Sun, 08 Dec 2019 13:49:03 +0100
Cc: Mark Smith <markzzzsmith@gmail.com>, 6man WG <ipv6@ietf.org>, SPRING WG <spring@ietf.org>
Message-Id: <D8B24DC3-A656-4101-B266-9E4732901E92@steffann.nl>
References: <CALx6S3588ja9AZzBQ0dqwx0j-ki6A5tusye+odQKPyAyF+hEww@mail.gmail.com> <10E890EA-3278-44EE-881E-EBC91D419587@employees.org> <88287cb0-c0c3-f990-4dd7-338df87c7fb2@joelhalpern.com> <4E76C386-FB1E-4E48-814D-BB626466BEE3@employees.org> <CAO42Z2ze7tmkGh=E-YrPuJHMeD8V6EuxgjjaJ33iz+Ms3abNsA@mail.gmail.com> <FDD7B5F4-B60D-425A-96C1-979BE647C0DA@employees.org> <CAO42Z2xMF5TM3BT=tA63A7QmiYRChPJywb1pSJquy_i5K_h=iA@mail.gmail.com> <324D4E35-97E8-42A2-912F-27C9FE033879@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Efm-M662MQznwCSXjLwx5czGHmI>
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, 08 Dec 2019 12:49:11 -0000

Hi Ole,

> I am not suggesting that header insertion is the _best_ approach. That I tihnk has to be evaluated on a per use case basis.
> I just want to see if we can reach agreement that it's a solution candidate, that given the deployment restrictions is technically sound.

If the mechanisms to make sure the rest of the internet doesn't need to suffer from header insertion are in place and reliable, then I don't care much what other operators do on their network. The IETF is about interoperability, and as long as others don't cause me trouble they can do whatever they want on their network. As Randy would say: "I'd recommend all my competitors to do header insertion" :)

As you said: whether header insertion is appropriate is something that everybody can decide for themselves on a per use case basis.

And based on my own experience and the research done by Fernando et all, I decide that header insertion isn't going to happen on my networks. So back to SPRING: I want a solution that works without header insertion (reasons given above). Please work on such a solution. I want to be able to choose an appropriate solution for my network, and something that includes header insertion isn't it. If the feelings about the architectural decision are so strongly opposite, we clearly need multiple solutions to choose from.

Cheers,
Sander