Re: Updating to RFC6434 to deal with 8200-style header insertion by IPIP

Fernando Gont <fernando@gont.com.ar> Mon, 06 November 2017 18:17 UTC

Return-Path: <fernando@gont.com.ar>
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 2C2DA13FC5A for <ipv6@ietfa.amsl.com>; Mon, 6 Nov 2017 10:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 nC44mWR1H7Qg for <ipv6@ietfa.amsl.com>; Mon, 6 Nov 2017 10:17:44 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E69CF13FB8E for <ipv6@ietf.org>; Mon, 6 Nov 2017 10:17:43 -0800 (PST)
Received: from [192.168.3.67] (unknown [181.165.119.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EE4AF8076E; Mon, 6 Nov 2017 19:17:40 +0100 (CET)
Subject: Re: Updating to RFC6434 to deal with 8200-style header insertion by IPIP
To: Michael Richardson <mcr+ietf@sandelman.ca>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "C. M. Heard" <heard@pobox.com>, 6man WG <ipv6@ietf.org>
References: <CACL_3VETxNVQ+YD5j6ZiWjycQ=ojAuWwB23offNdVKm+S9c_7A@mail.gmail.com> <23308.1509623865@obiwan.sandelman.ca> <CACL_3VFrcombGczXU6Zz=Pk1u2GE=wGG-r+yEefdHai1REqXmQ@mail.gmail.com> <c8911f45-2afc-9d26-c0a8-1017d034a251@gmail.com> <CACL_3VEjp2bJAAGgqaKcqdqHoitE6vw6M3=qO6YauVoKN-26=A@mail.gmail.com> <f7feace2-86d2-a2f0-5662-469405aa32e8@gmail.com> <7923.1509845822@obiwan.sandelman.ca>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <c3ff464a-4402-a5ce-adcd-0163b2b572c7@gont.com.ar>
Date: Mon, 6 Nov 2017 15:19:16 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <7923.1509845822@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8oAwrkV0kE5Wq_Q9x_MRJ49p8Eo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Nov 2017 18:17:45 -0000

On 11/04/2017 10:37 PM, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     > Yes, that particular elephant stands politely and quietly in the corner
>     > of the room. However, I'd just read the text you cite when I wrote my
>     > message and I'll stick to what I said: we *specify* action for an
>     > unrecognized extension header, but we ignore the elephant and *don't*
>     > specify action for an unrecognized ULP. Consider it a drafting error,
>     > or a design error. I agree with you about the practical effect: an
>     > unexpected IPIP packet is likely to generate ICMP 1 today.
> 
> okay, so shouldn't 6463 fix this part at least?

You can't, unless you close the door to new EHs or to new ULPs. See:
<https://www.ietf.org/archive/id/draft-gont-6man-ipv6-universal-extension-header-02.txt>

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1