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

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 02 November 2017 16:48 UTC

Return-Path: <swmike@swm.pp.se>
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 00A5513F74C for <ipv6@ietfa.amsl.com>; Thu, 2 Nov 2017 09:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 BFcvZSaZ6joz for <ipv6@ietfa.amsl.com>; Thu, 2 Nov 2017 09:48:37 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 F2B4A13F58F for <ipv6@ietf.org>; Thu, 2 Nov 2017 09:48:36 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2EA27B6; Thu, 2 Nov 2017 17:48:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1509641314; bh=Ny+9END9xALZGgVR9he3rmSHw9eFURhM0R4x+RtjF4c=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=VkNHgyIpcTiNksksr+u8/DuDvZBmZ6+4EilW5tQrpKu0raQLSgaq+hHx0QKPnXjNc QPELkuO5C16VxiSGZ7s1vlZ4UrUzKUDIUCqEiQZ04hkLC0RhJgV10OKY6zLVRVZOSb /7CaJmtJhnx5dHFq0iYYSTAk9yckFi+imHJv9k7s=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 2C1B3B5; Thu, 2 Nov 2017 17:48:34 +0100 (CET)
Date: Thu, 2 Nov 2017 17:48:34 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "C. M. Heard" <heard@pobox.com>
cc: 6man WG <ipv6@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Updating to RFC6434 to deal with 8200-style header insertion by IPIP
In-Reply-To: <CACL_3VFrcombGczXU6Zz=Pk1u2GE=wGG-r+yEefdHai1REqXmQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1711021747310.16389@uplift.swm.pp.se>
References: <CACL_3VETxNVQ+YD5j6ZiWjycQ=ojAuWwB23offNdVKm+S9c_7A@mail.gmail.com> <23308.1509623865@obiwan.sandelman.ca> <CACL_3VFrcombGczXU6Zz=Pk1u2GE=wGG-r+yEefdHai1REqXmQ@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Q4zN6c7prMUNCiwEAxJZ58IqBtg>
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: Thu, 02 Nov 2017 16:48:39 -0000

On Thu, 2 Nov 2017, C. M. Heard wrote:

>> Right. I forgot that IPSEC is an extension header in IPv6, I tought of it as
>> something that was encapsulated. So I take back what I said.
>
> No, you were right the first time. Unknown extension headers are not
> skipped; they cause the packet to be discarded (see RFC 8200, Sec 4).

Sure, but if the device understands IPSEC but has it turned off, what 
should it do?

I don't know.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se