Re: Spring Appeal and [Errata Rejected] RFC8200 (6003)

Robert Raszuk <robert@raszuk.net> Fri, 15 May 2020 22:53 UTC

Return-Path: <robert@raszuk.net>
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 9423C3A0A18 for <ipv6@ietfa.amsl.com>; Fri, 15 May 2020 15:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 ogIcCJxPS0FC for <ipv6@ietfa.amsl.com>; Fri, 15 May 2020 15:53:18 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 A695A3A09F4 for <ipv6@ietf.org>; Fri, 15 May 2020 15:53:18 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id d16so3522513edq.7 for <ipv6@ietf.org>; Fri, 15 May 2020 15:53:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YVxW3Nz4nemq+XVnonN5t767Q0NHlDk+fsoM3zw6Yok=; b=Yf9pFXumqOopUlwTlNohm5e37wBpTF2J1jU9YediORkqDvW9w5hF1u/E1qfOEOJFsz KQKIUjMZ/5LJ3YbhwC+wo4UFLl1gJg5cUC6upZVTOz4AFmIDXV7e0jR2Ga8Qde4h9gjj xW6cmUwn67w7RKcXWCq551zXJfAhCgswg+GpByB5AuzW1ZUblYaTfSqXw9QITLY1I0ai +R/kVi6D3orZrrtEzExxSNbtyceVMOTvRQTIsL9m+of9iyHO2J6K/2fLHXKBnupjAGx3 zmFSZeAOKt1a+FTEGH0IQcVRoGm8QoY9yqvv7hG9xdPQ3tf4Do9A34mEuaNeQROFMTi4 Mb6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YVxW3Nz4nemq+XVnonN5t767Q0NHlDk+fsoM3zw6Yok=; b=SlvAv+BwGDUKwOmp8/KUsAJECKWC5iyiMSxOW8bEsb4HWE6k7LW6x+kqlOC71WizUO gq0PNThDo6wYsA74K2ibPhhFUaQhBDFMP2PTSrLTyBKWJdYhmQttPAdf+hEucMyIME+P YemP93y42F0HdWgLEcj1OQX7PUdnhpxMpW6VTqxPmyvpYzAw5aaULpQSlUVzRRPI9Fn8 1Hjqlj+Vzjln8xt84tSfn/H4/ENUnUpOxkge5nI33/wfmgtIsf8p/t5dffSKjs3miCFs dfrrOyPKXXWmd0ctSPwEv0ID742ayfXHL4/8rP/4nMJ9WOXP1/eF0KJgpfXKh2Iz6/HY aRvw==
X-Gm-Message-State: AOAM533x7emxtkySKzVJi3DnG3fwKngAutn3JaRH1SkYFTGoStpVI5tx e5fWSlGGC61PYOX1GecLYV2359HR6qR3vxVMCp9yZA==
X-Google-Smtp-Source: ABdhPJwr7yIPRGoDUKNgAfsranHDomJZg3sadHnYe3SGOweP4DCTb87RQbjD0NZZ8C+zWrnQAJYpMebsTmzKfCnJKHY=
X-Received: by 2002:a50:f111:: with SMTP id w17mr2115825edl.41.1589583196977; Fri, 15 May 2020 15:53:16 -0700 (PDT)
MIME-Version: 1.0
References: <20200510184112.9643EF406D6@rfc-editor.org> <030874d9-28f5-48da-befb-f0a210c51347@si6networks.com> <A1A84435-E0A3-403C-A1CF-CC83F75BCC0B@employees.org> <ffea7f98-b5a8-7afd-727b-eba50087aa32@si6networks.com> <CAMGpriXR55WawsnEnUYfdNUkvmTS34e4QjfSpDoNFZk-=Qabpw@mail.gmail.com> <58642567-BDF2-4243-B2DF-E5F12E38FF89@steffann.nl>
In-Reply-To: <58642567-BDF2-4243-B2DF-E5F12E38FF89@steffann.nl>
From: Robert Raszuk <robert@raszuk.net>
Date: Sat, 16 May 2020 00:53:07 +0200
Message-ID: <CAOj+MMEj2XGOu-vZ7jQmQyuL4DRhEzz1yd9aHDjeTaiNWTM3Og@mail.gmail.com>
Subject: Re: Spring Appeal and [Errata Rejected] RFC8200 (6003)
To: Sander Steffann <sander@steffann.nl>
Cc: Erik Kline <ek.ietf@gmail.com>, Fernando Gont <fgont@si6networks.com>, Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cc1fa605a5b7ad38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_681wVFl4Bm6ZduyTDR0xgkfU7w>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 15 May 2020 22:53:21 -0000

> It mentions _the_ node identified in the DA, singular.

Lol ...

How can DA contain more then one destination node address (other then
multicast) in the view of RFC8200 ?

Unbelievable what is happening on this WG list.

Have a great weekend,
R.



On Sat, May 16, 2020 at 12:33 AM Sander Steffann <sander@steffann.nl> wrote:

> Hi Erik,
>
> > RFC 8200 includes an exemption to this behaviour for nodes whose
> > address appears in the Destination Address field of the IPv6 header.
> > This text has not changed from 1883 to 2460 to 8200.
>
> I disagree with your interpretation of the text of 8200. It says:
>
>    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.
>
> It mentions _the_ node identified in the DA, singular. It only specifies
> multiple nodes in the case of multicast. The combination of using singular
> and only using plural when explicitly talking about multicast reads to me
> as only referring to the final destination. The use of the word "until"
> signals the same to me. Using "until" for something that can occur multiple
> times sequentially in a packets lifetime would be very confusing.
>
> Now, this does pose a problem, because strict reading of that text also
> means that a node can only learn that it is not the final destination by
> processing the routing header. As I read it, that node can process the
> routing header but then has to stop further processing when it finds out it
> is not the final destination. In blunt English: any further processing of
> headers is none of its business. As I understand it that is also the reason
> that a separate destination options header may appear *before* the routing
> header.
>
> Cheers,
> Sander
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>