Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - implications from new development for EHs

Gert Doering <gert@space.net> Wed, 29 July 2020 10:40 UTC

Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB853A082F for <v6ops@ietfa.amsl.com>; Wed, 29 Jul 2020 03:40:44 -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 (2048-bit key) header.d=space.net
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 XKrXcaM4Q-I3 for <v6ops@ietfa.amsl.com>; Wed, 29 Jul 2020 03:40:41 -0700 (PDT)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (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 73CAA3A0827 for <v6ops@ietf.org>; Wed, 29 Jul 2020 03:40:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1596019240; x=1627555240; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=HuIucUOxJ0GwdqfUdmPtljAsE1TxV8HdNPQjiL4s9nM=; b=S+PoTM47ypmQy7yX0+QtwxVBqNOB4Z4Tm7Gylrnw8D4gpn4KVuX7Qx0f /TJBIKYW7NHOViZTMBpvJgi35PDlBR8KfDD4/gR6v1y04ApMtaQdx5kPD FvGCQuppr13nkN/I8QNQM5LZJ6aavCZWZHDQFJ63fcKZF8+usokucMn0t svbfHV5k1oHxIlL3G48bh7o6lxecSXVqoBuzCAohb/eHfCbkXLeBxioxB cqPG4mZfWyKzw5PQf07DHibVJBr7de7Ik4XFxxx7j099EZfd+9ig3vWR5 pF3orGYutcA0eO3nT9TI6IuFiig17AHf2mZkKoJpF8ZeQtOj7Djl0Xg5j w==;
IronPort-SDR: 9I6bL0wwBJGjEhLnDAs+bzRO8BVN1DGTQxkb9aTrVHVeaDPwDqe1gU9sE8KqW8WuavLx4QSVSY 1wRYBcslsSFwXc0XZzbLtIZ7V5UsRuiQRgtb6FdFQAykUoQ6QLoWDGU9WfbEuEeoazOteRzeKf W8m5IPmH+dG+cTBnmRMBLIyKcUnKYuzWI868Eqlg0VU2pL2HXXI7osRA1cL7mJqqqEGIj93WRK kh5pguPf8LOdoEBFJuayizqDtdBMsgPtEW2cwoDcfgNaZ433wIy0Cfo9HZW8Hm7DR4UgNMPtxm IfQ=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2020 12:40:34 +0200
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id CC8E740CFB for <v6ops@ietf.org>; Wed, 29 Jul 2020 12:40:34 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 72C2E40B9D; Wed, 29 Jul 2020 12:40:34 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 6ADF813D56; Wed, 29 Jul 2020 12:40:34 +0200 (CEST)
Date: Wed, 29 Jul 2020 12:40:34 +0200
From: Gert Doering <gert@space.net>
To: otroan@employees.org
Cc: Gert Doering <gert@space.net>, Vasilenko Eduard <vasilenko.eduard@huawei.com>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>
Message-ID: <20200729104034.GR2485@Space.Net>
References: <d8d59ce07f7f4031a545ff6e24fdbb88@huawei.com> <20200729084351.GG2485@Space.Net> <32BAEAEA-7352-4BAE-ADA8-FDA2395D5732@employees.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Mtq/OFd6AHmyovWL"
Content-Disposition: inline
In-Reply-To: <32BAEAEA-7352-4BAE-ADA8-FDA2395D5732@employees.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rEEPOGJ2CrMHKQyD62YU3iZOCCI>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - implications from new development for EHs
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2020 10:40:44 -0000

Hi,

On Wed, Jul 29, 2020 at 12:13:03PM +0200, otroan@employees.org wrote:
> "Do not assume ICMP, IP fragments, or any other transport protocol than TCP port 80,443 or UDP port 53 will work. Do not assume anything but IPv4 will work."

I'm not *that* depressed yet.

But yes, this seems to be reasonable advice to application programmers today.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279