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

Fernando Gont <fgont@si6networks.com> Tue, 07 November 2017 21:24 UTC

Return-Path: <fgont.mobile@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 22FF5128B51 for <ipv6@ietfa.amsl.com>; Tue, 7 Nov 2017 13:24:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 bWz83AUPDzTJ for <ipv6@ietfa.amsl.com>; Tue, 7 Nov 2017 13:24:47 -0800 (PST)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::22f]) (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 C044B1279E5 for <ipv6@ietf.org>; Tue, 7 Nov 2017 13:24:46 -0800 (PST)
Received: by mail-ua0-x22f.google.com with SMTP id s41so454801uab.10 for <ipv6@ietf.org>; Tue, 07 Nov 2017 13:24:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ioeuljt/xr12ornRBJZh9RZ42pSJwmweJzzfn/9cyJo=; b=gflV8s45fvpbsFjD6EVkTMBWbqq9HCo5ux/ppRfKXvWj3iWZuujes9uCb7SAzR/vxN AdJncGC99kXfHx/0tLcGwGGSWUCcuOzzVtMQJo6uq9xWO0VNkBd/nd/xegMAK6Aq17hD M5snAjvLluuibHQtDnJR1H0NBiN/SmBBxdI4X6ukz6I6B9MQzoF21D8xiE7CWFUJ2KF1 HDUqHyv+5YH9a3cO+lkIVMzzEU4h0FaDdnknzXW3VsFU3t5916Pdvh7rmiD1ejzD8t4L 73u5jqpfguAPdHZaYkkmJHmEt8MQBJpwiu4pxmlxivjJE2MEA8FyyBN2OnEtqlabCEmk UDPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ioeuljt/xr12ornRBJZh9RZ42pSJwmweJzzfn/9cyJo=; b=gDji3lnujpnWq0NXAhRyfWbMxneK9cp0z+DMTMyFZVswZ5oCSw9F9D/8BAqTLGHzo6 Eo+F1wCMSD9vfkk26i7XQhEHQwzGlEl6MyqVgk3OXT8I/45cFhgzxTtrT4zRRk+ubBzA U0NVr72hUs2FHgDQE6gNiE+miYT33Kx4EG9ISOrNmxVqPtJOod5kERMIkvu2QS1rviJo dRvQfKQlyEdv/6Rw5MtW7XOyDL3Toen8mSjyyl49o8hY8jDqjjPN0raQKOEOglKGnpjY tSVA7Mh5yCzhTHm/JZj3/Ko4AGEHmP3N0FkIQQ0jNqOxcICVCyLpAdOovNu7mldqYZGt Fn+w==
X-Gm-Message-State: AJaThX6U7pkhLZK3zuLpdjt5KTAStK00VxTeVZSdt6Fr0FPyeiCkvS8k gWjO70PQUEeRC7gzoVmylc0ZAYSOgoxyiaheSjc=
X-Google-Smtp-Source: ABhQp+R7FIjpq+Fr4wHYFZWlaHGiC0BEPGsBdbfAGFFEp6StRWTkAulJvAHpA5QGLDa018mrAp8e0rsbdBC03ibxd4I=
X-Received: by 10.159.53.13 with SMTP id o13mr88125uao.183.1510089885718; Tue, 07 Nov 2017 13:24:45 -0800 (PST)
MIME-Version: 1.0
Sender: fgont.mobile@gmail.com
Received: by 10.103.19.129 with HTTP; Tue, 7 Nov 2017 13:24:45 -0800 (PST)
In-Reply-To: <52370287-9bd2-1e56-3aa2-f9d1c51455b4@gmail.com>
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>
From: Fernando Gont <fgont@si6networks.com>
Date: Tue, 7 Nov 2017 18:24:45 -0300
X-Google-Sender-Auth: 2OxkI6x6--gjqNFQboKyrRiLbI4
Message-ID: <CAG6TeAuDKfBcb_wMRS2fFnQSRBQGJWi4v_T=YcsQXz5OBYmDSw@mail.gmail.com>
Subject: Re: Updating to RFC6434 to deal with 8200-style header insertion by IPIP
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, "C. M. Heard" <heard@pobox.com>, 6man WG <ipv6@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="94eb2c03bb4e379d44055d6b33a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ezhjhe2EZwUykmOYH2WXb1o414o>
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: Tue, 07 Nov 2017 21:24:49 -0000

FWIW, I support Brian's proposed text.

On Tuesday, November 7, 2017, Brian E Carpenter <brian.e.carpenter@gmail.com>
wrote:

> On 08/11/2017 00:20, Tim Chown wrote:
> > Hi,
> >
> >> On 6 Nov 2017, at 19:35, Brian E Carpenter <brian.e.carpenter@gmail.com
> <javascript:;>> wrote:
> >>
> >> Hi Fernando,
> >>
> >> On 07/11/2017 07:02, Fernando Gont wrote:
> >>> On 11/02/2017 04:33 PM, Brian E Carpenter wrote:
> >>>> On 03/11/2017 04:26, C. M. Heard wrote:
> >>>>> On Thu, Nov 2, 2017, Michael Richardson <mcr+ietf@sandelman.ca
> <javascript:;>> wrote:
> >>>>>
> >>>>>>
> >>>>>> C. M. Heard <heard@pobox.com <javascript:;>> wrote:
> >>>>>>> On Wed, 01 Nov 2017, Michael Richardson wrote:
> >>>>>>>> Yet we skip other extension headers in order to find the ULP.
> >>>>>>
> >>>>>>> Not so. An end node that encounters an unrecognized extension
> header
> >>>>>> is
> >>>>>>
> >>>>>> Both AH and IPIP are well known and recognized extension headers.
> >>>>
> >>>> AH is an extension header. "IPIP" isn't. It's Protocol 41, and
> Protocol 41
> >>>> is otherwise known as IPv6. (That's why it's also called
> IPPROTO_IPV6).
> >>>> In RFC8200 terms that makes it an "upper-layer header". Strictly
> speaking,
> >>>> RFC8200 doesn't specify what to do with an unrecognized upper-layer
> header.
> >>>
> >>> Based on the std, anything that is unknown is an EH. In the context of
> >>> RFC8200/FC2460, there's only:
> >>>
> >>> * Known EHs
> >>> * Known ULP
> >>> * Unknown EHs
> >>
> >> Yes, that's what the text says but I wish we'd fixed it in 8200 to
> >> acknowledge that there is a 4th case (Unknown ULP) and that it
> >> cannot be distinguished from the 3rd case. Acknowledging that is
> >> much better than ignoring it. I'm happy with Ole's suggestion that
> >> this (and the resulting ICMP 1 behaviour) should be mentioned in
> >> 6434bis - as a clarification, not a new invention.
> >
> > This seems a reasonable approach to me.  Would you like to propose text,
> Brian?
>
> After this:
>
> 5.1.  Internet Protocol Version 6 - RFC 8200
>
>    The Internet Protocol Version 6 is specified in [RFC8200].  This
>    specification MUST be supported.
>
>    Any unrecognized extension headers or options MUST be processed as
>    described in RFC 8200.
>
> insert something like:
>
>    Note that it is impossible for a node to distinguish between an
>    unrecognized extension header and an unrecognized upper layer
>    protocol. Therefore, a node will behave in the same way for
>    either of these cases, in particular by returning an ICMP
>    Parameter Problem message with code 1 ("unrecognized Next Header
>    type encountered") even for an unrecognized upper layer protocol.
>
> (Protocol 41 is not special in this regard.)
>
>  - Brian
>
> >
> >> I also agree that there are enough potential issues in unexpected
> >> IPv6-in-IPv6 that is deserves its own draft.
> >
> > I’d agree. The same with header insertion for that matter. Focus on the
> issues and how/if they can be mitigated and in which contexts.
> >
> > Tim
> >
> >>
> >> Regards
> >>   Brian
> >>
> >>> with the last one being the default branch :-)
> >>>
> >>>
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org <javascript:;>
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >>
> >
>
>

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492