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

Fred Baker <fredbaker.ietf@gmail.com> Thu, 02 November 2017 18:04 UTC

Return-Path: <fredbaker.ietf@gmail.com>
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 97C9A13F742 for <ipv6@ietfa.amsl.com>; Thu, 2 Nov 2017 11:04:53 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LCR3Q8WyZw16 for <ipv6@ietfa.amsl.com>; Thu, 2 Nov 2017 11:04:52 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E87F13F54B for <ipv6@ietf.org>; Thu, 2 Nov 2017 11:04:52 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id g90so369724wrd.6 for <ipv6@ietf.org>; Thu, 02 Nov 2017 11:04:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=bI6O4Am2MkPGWvKA9MGfhLM6fSd27IwgzglQrz7iTks=; b=oaXmRK8voNSXArgJPdBX9IBZMzdK2GDxN0pwTV7UuX4wDjgokj9noCvQCzgMfcQEi2 De0EbFt2SlbBD2tVOLiFlg3zJJRmeSwu51Lb7o0l/JYXsxjYavXVuLsOPfEwVtjaxF0K yQePfStM7vxkwsmYfd9c7VgyZTDYJH/csdBcyBWIP3z/KRYupYjWEjrOHy1A56XfLfp5 +dMgY3LGitxESXwQYLp/z0zg91/2IDG3gIIfazgkcYjbOxgEBbVyaXq9mU9eK+YiH58B TS8ohIx9089x0rA+EeVkkleQ+4kN/eDSSJobQhYYFLKO4GcP1v+tQWJxRk32sUG3k1xk Vu3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=bI6O4Am2MkPGWvKA9MGfhLM6fSd27IwgzglQrz7iTks=; b=bpzWZtVyxQZ5+RnPhZDCZAsiQL0W1c6GkG9fAc5B1vjFyGOAth8esdbCRD5KemKJU+ h4Sx/dYYMVpu64aiFt93LrVTQZPElzbV/w0xclPx6dciswiY7lJ/2MePWSoMhaSTDmFs XhUoqQyg2EcwAmEA5KC9qPbEiIVC6Kkg06r5Bbd3DD+0vg0fXuv3I9OxKD2SDlacbHHi BkSPiWmOIwGb8OYQILkFWWM+iYFV2GZw1HdVWIE6ndw9bnCJu8uD7WZCsYEqSR/2DWgh YfAA2neqK2Vl5xPWm/Wtox2CJJLn7xcrZjVZ2JKMXjMtO6589LBx6iyucrTp5i3n3Ms3 FKqQ==
X-Gm-Message-State: AMCzsaUUAQdHZ7HHRpGZ/PDinwQlzdp5X7bZRpW3NVkNQfvCuISNV+6M PWrFc/7ZyXePLC456mg5gvI7eQ0P
X-Google-Smtp-Source: ABhQp+QWrkKjTMQZgRBAtKUTO4AvN0uzV+YslM6ofS+l8xGEAi0Uz7pHvUsyWHftb4fjsh4Gd36XqA==
X-Received: by 10.223.195.147 with SMTP id p19mr3639421wrf.176.1509645890595; Thu, 02 Nov 2017 11:04:50 -0700 (PDT)
Received: from [172.20.3.117] (bba409691.alshamil.net.ae. [83.110.17.243]) by smtp.gmail.com with ESMTPSA id n14sm267326wmh.37.2017.11.02.11.04.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Nov 2017 11:04:49 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <E80EFCC0-D43B-42F6-9A6B-B6748C26EEF3@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8B9752DB-041D-4FB8-8D78-8F158D2211C4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.11\))
Subject: Re: Updating to RFC6434 to deal with 8200-style header insertion by IPIP
Date: Thu, 2 Nov 2017 22:04:46 +0400
In-Reply-To: <alpine.DEB.2.20.1711021747310.16389@uplift.swm.pp.se>
Cc: "C. M. Heard" <heard@pobox.com>, Michael Richardson <mcr+ietf@sandelman.ca>, 6man WG <ipv6@ietf.org>
To: Mikael Abrahamsson <swmike@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> <alpine.DEB.2.20.1711021747310.16389@uplift.swm.pp.se>
X-Mailer: Apple Mail (2.3445.5.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xGXxDzsDzLN59qhErwF-vzE-oEo>
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 18:04:54 -0000


> On Nov 2, 2017, at 8:48 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> 
> Sure, but if the device understands IPSEC but has it turned off, what should it do?

It should behave as if it doesn't understand it. In context, it doesn't.