Re: IPv6 header insertion in a controlled domain

Sander Steffann <sander@steffann.nl> Mon, 09 December 2019 06:40 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 6978B120074 for <ipv6@ietfa.amsl.com>; Sun, 8 Dec 2019 22:40:45 -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 HHM-sgmEfXxj for <ipv6@ietfa.amsl.com>; Sun, 8 Dec 2019 22:40:43 -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 4BE1912003E for <ipv6@ietf.org>; Sun, 8 Dec 2019 22:40:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id EEA7349; Mon, 9 Dec 2019 07:40:40 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:in-reply-to:references:message-id:date:date:subject :subject:mime-version:from:from:content-transfer-encoding :content-type:content-type:received:received; s=mail; t= 1575873638; bh=xbZVJIJLS2n7UVIcKkGAELHs4JPzRSEaV0LQFNYbVG0=; b=l oJgOSOXcneJ2748YPCjuYNZ8naT6ZXVtSPWUSZF67x8KGNO4RbVBC75TvpiDL2Cl BgLz04kZrwOAiPa3klJxp9JYFKKxBJuNKZZIAVWPs0Jq6j3vDrblT2W2Ndfwnf52 BVNcZegJQYCBe67ke0xHYIZfPlOn37ec8+i+U+FQHo=
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 xLphjAIFognP; Mon, 9 Dec 2019 07:40:38 +0100 (CET)
Received: from [IPv6:2a02:a213:a300:ce80:8c71:5639:5927:7aaa] (unknown [IPv6:2a02:a213:a300:ce80:8c71:5639:5927:7aaa]) (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 D70553C; Mon, 9 Dec 2019 07:40:37 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Mime-Version: 1.0 (1.0)
Subject: Re: IPv6 header insertion in a controlled domain
Date: Mon, 09 Dec 2019 07:40:37 +0100
Message-Id: <C27A0E92-AF13-477B-9A22-DAB05494DE61@steffann.nl>
References: <BN7PR05MB5699F86F6DF1F224DF4A6E32AE580@BN7PR05MB5699.namprd05.prod.outlook.com>
Cc: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
In-Reply-To: <BN7PR05MB5699F86F6DF1F224DF4A6E32AE580@BN7PR05MB5699.namprd05.prod.outlook.com>
To: Ron Bonica <rbonica@juniper.net>
X-Mailer: iPhone Mail (17B111)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZWJOZxNaDZE1S9iO_G9916R7ybE>
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: Mon, 09 Dec 2019 06:40:45 -0000

Hi Ron,

> See Section 7.5 of https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-26

Not choosing to use AH to protect the SRH is one thing, but not supporting an AH in the existing packet when doing header insertion is quite another. I want to be sure the second doesn't apply.

Cheers
Sander