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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 13 November 2017 00:14 UTC

Return-Path: <brian.e.carpenter@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 C87921241F5 for <ipv6@ietfa.amsl.com>; Sun, 12 Nov 2017 16:14:07 -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, 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 U2YehbLC6tcM for <ipv6@ietfa.amsl.com>; Sun, 12 Nov 2017 16:14:06 -0800 (PST)
Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (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 8A3071200C5 for <ipv6@ietf.org>; Sun, 12 Nov 2017 16:14:06 -0800 (PST)
Received: by mail-pg0-x22b.google.com with SMTP id p9so11414094pgc.8 for <ipv6@ietf.org>; Sun, 12 Nov 2017 16:14:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=pZJYr/mXOkWOGkH43M4LkeHNYFsoB/4wCzqNUe+1nZI=; b=BwZDieFVpuwQ8zqaslbEeaG4JS6kKdM0QMBVaDaPHH8g2DsxjCqgu6s0H2rEz171zg WJBvtoH2yEX7ygAR+6z97Oc7b5hUcNY29l3AW2WZPZJnfesSgH2C1DHHxVDREXwyMO0A /1qFhFNCDrnXsfAx/qooOUOb9ZCHzNjLLpsc1khf/4XffbzSVatiLoQ3IngmX7rdd1lo fjAu+RK3vIgELdVmUFN9tyJFVYB+jjjjsX7KCxi+BhwZcz832oywDAbKsxzxxMpduuYm l7KE3PxDi7f6j8YFM93YEcLoajZHH/AZh69aguNolQKuFcUF5L9iCD0H5nycrVNXydA6 WA2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=pZJYr/mXOkWOGkH43M4LkeHNYFsoB/4wCzqNUe+1nZI=; b=TAoJcDFuyvvcN2VnbpMXTQ4AE24y4y6H1f4JQgPE8CiG1O51RA6lYzCDRqslJx97f7 u3mFgsjS101K+qH5Nxbfj4wF4FCD2oE91k9ace6s+tjYQ1IQuB13mGAGV16GfGQcIYCR QS47oWYnQm+KB9D4N/mbcwN83sbVSiwu7AxxN8fRL+7WPHO0Pb/Hd+ICmbO4w4AOoLS7 VilwdpAS5euB0lP0vsUcW8/lrBnE8a/UeaQAr9ukTOfte/L6F3D8n9P8c3F4tIrBcih6 +Cac/Y5TqmsHi56o3U88wggQ8X8mqrZWgDDZ4Rn0MuBpTjcB90/K4apSTSpR8iYWiF1+ oUiw==
X-Gm-Message-State: AJaThX41eT9e6tV+fmdtX42l3e6xIOm/KjZlwG3W5w9FF/3SLN1WCLVx dWbYt8B46TFLOwXzPE3S0UI/cwAt
X-Google-Smtp-Source: AGs4zMZe3HQzicnhmhZYYfiwKPuN9t+S0Frr5M6M8jtWBc6zNq6ZsYGzZ+TulKPYV4wpWP/Jc5WMtw==
X-Received: by 10.98.69.86 with SMTP id s83mr8048365pfa.32.1510532045839; Sun, 12 Nov 2017 16:14:05 -0800 (PST)
Received: from [172.16.132.82] ([101.100.166.3]) by smtp.gmail.com with ESMTPSA id x79sm30998678pfa.156.2017.11.12.16.14.03 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Nov 2017 16:14:04 -0800 (PST)
Subject: Re: Updating to RFC6434 to deal with 8200-style header insertion by IPIP
To: 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> <1e62fab6-c434-a474-e53b-e4c7f2d83de0@gont.com.ar> <5cb2b9fd-8546-31fd-d984-d161aef16349@gmail.com> <49F3820E-A9A8-41C4-B6D0-EAEAE0941769@jisc.ac.uk> <52370287-9bd2-1e56-3aa2-f9d1c51455b4@gmail.com> <12447.1510153859@obiwan.sandelman.ca> <c104cb05-ee8f-7958-338b-1e30aa7942d1@gmail.com> <C62FA0EB-A212-47D0-B527-CB53946E127F@gmail.com> <45f01790-0561-68b9-e245-0a126c7e110b@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9c39822b-584b-557c-635a-a1529f94cbd5@gmail.com>
Date: Mon, 13 Nov 2017 12:55:46 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <45f01790-0561-68b9-e245-0a126c7e110b@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8TEYqgeQwegp12aErj4TL2FBZ6M>
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, 13 Nov 2017 00:14:08 -0000

On 12/11/2017 19:52, Fernando Gont wrote:
> Hi, Bob,
> 
> On 11/12/2017 10:50 AM, Bob Hinden wrote:
>> I went back and looked at the RFC8200 text that deals with header insertion.  It does not actually mention IPIP.  The published text in Section 4. "IPv6 Extension Headers" regarding header insertion is:
>>
>>    Extension headers (except for the Hop-by-Hop Options header) are not
>>    processed, inserted, or deleted by any node along a packet's delivery
>>    path, until the packet reaches the node (or each of the set of nodes,
>>    in the case of multicast) identified in the Destination Address field
>>    of the IPv6 header.
>>
>>    The Hop-by-Hop Options header is not inserted or deleted, but may be
>>    examined or processed by any node along a packet's delivery path,
>>    until the packet reaches the node (or each of the set of nodes, in
>>    the case of multicast) identified in the Destination Address field of
>>    the IPv6 header.  The Hop-by-Hop Options header, when present, must
>>    immediately follow the IPv6 header.  Its presence is indicated by the
>>    value zero in the Next Header field of the IPv6 header.
>>
>> Some earlier drafts include IPIP as a way of inserting headers, but that wasn’t included in what became RFC8200.
> 
> Does IPIP simply mean tunelling IP over IP?
> 
> If so, that'd be tunneling, rather than "header insertion".

Yes, but the point was to say that this is a valid way to attach extra
headers. And iirc we concluded that while true, it isn't necessary
to write it down.

(Also there's a proposed standard for this if you need it: RFC2473.)

   Brian