Re: [Technical Errata Reported] RFC8200 (5933)

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 December 2019 20:12 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 E06EA1200C3 for <ipv6@ietfa.amsl.com>; Thu, 12 Dec 2019 12:12:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_HELO_NONE=0.001, 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 OTnuaQEl3r91 for <ipv6@ietfa.amsl.com>; Thu, 12 Dec 2019 12:12:21 -0800 (PST)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 8A0D8120024 for <ipv6@ietf.org>; Thu, 12 Dec 2019 12:12:21 -0800 (PST)
Received: by mail-pg1-x52b.google.com with SMTP id x7so78788pgl.11 for <ipv6@ietf.org>; Thu, 12 Dec 2019 12:12:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=mpFp5R3OT8Q/k3WmSeCdIURtzwhr6gYUK238ZA1Ndic=; b=nF+zzuTYztqCIAb38/sxoeGkyJ9gPycUq0RPUK3BxhtISrreVc0XZ4Gli0xY87KGp0 MbYuPDeNag8rSc+ux79VNUUIVKm+pjusMnqXOeoyxXlLnXhMGjece5d84tucJCIGbFxb hOSvlcLIg1CZ4ZvOppfhkCKWdhJVSd9uNkaWHIX8rmUWxSoLSIdwHYjSOu1x1pnOH3SA VTi1UewQZBqd4v/tNM12YsTjD2IquEZEbh5tOpH9HyLvm8RvaHmWXH+qNHPYbTG2FsbV C87wON0ujVRK1j0NeITudD+nBkN3BvrabasCSUb3Qik9n/3v6fsRgTcWRz7DSwZ+JstW HE1A==
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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=mpFp5R3OT8Q/k3WmSeCdIURtzwhr6gYUK238ZA1Ndic=; b=ma3c0P1dBPW0YYqjl9ZGfTuz6Lq+KtUd/QtAp9DiC5GmH4V3bRqsMTdfRE3/l+5FBS 63HmqmZCLZiffzLJRgPBoHpOBZCyPK+joqzbfKsgXNslUUV7Zaz5U+nzupK4c/rESjaj DQMmiM6G84rk3QvBobJRhOWAYrUghLS4vTX7QYK+IaiXINgDWXavV4ZCAVsBut6L9HTK 1gDQPKclcL7/6vl7kMMRT+OXZlFsM3PUjkKSSLVzzkxuNT5psqqX02HSqfY5LVEwI8Fm G9hMk0toB3kfDsTyH6xM/98WKHXdt8Pc514tyRrFHUVJFdelw61gP7WqRGf79Uuj4ob5 mf2w==
X-Gm-Message-State: APjAAAWB6xh1HdlqRNUdWBhE57Mb1kcauRyd7D2yjoU+08R99s/dRA/a ikNJVH52ZpFzvZRYK0xl6BzZ7CWn
X-Google-Smtp-Source: APXvYqwTQDuPpD7GmQktlxm7kEE9SucK+oP95Qi9xRhWnWvPFX0IJcz1wSzE6D+m/FLQvp/seWVDHg==
X-Received: by 2002:a63:3f4f:: with SMTP id m76mr12317403pga.353.1576181540423; Thu, 12 Dec 2019 12:12:20 -0800 (PST)
Received: from [192.168.178.30] (228.147.69.111.dynamic.snap.net.nz. [111.69.147.228]) by smtp.gmail.com with ESMTPSA id d22sm8098249pfn.164.2019.12.12.12.12.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Dec 2019 12:12:19 -0800 (PST)
Subject: Re: [Technical Errata Reported] RFC8200 (5933)
To: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
References: <20191211032724.46F77F406F3@rfc-editor.org> <ead110b0-3198-2894-3c63-9362276b0cc4@gmail.com> <cffb0a8e-2119-a474-4dce-f3b5a67dac47@si6networks.com> <bfa67fe0-850d-941d-a446-559a2907da25@gmail.com> <4efde70d-e368-3b47-58c7-f7b5fb3c13d3@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1331438c-27d3-092c-b13f-66f2314bdfa7@gmail.com>
Date: Fri, 13 Dec 2019 09:12:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <4efde70d-e368-3b47-58c7-f7b5fb3c13d3@si6networks.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Y-0NkNH0R_YBhNyt3oyLvLxUPDY>
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: Thu, 12 Dec 2019 20:12:23 -0000

On 12-Dec-19 18:45, Fernando Gont wrote:
> On 11/12/19 23:22, Brian E Carpenter wrote:
>> Yes, a note that updating Segments Left is legal would fix it I think.
> 
> It would seems to me that more is needed. For instance, for RHT0 you had
> to swap the address in the Destination Address with  with the next
> segment in the RHT0 payload.

Yes, decrementing Segments Left presumably applies to all routing headers,
but you are correct that other changes might be specified.

> 
> So I guess the text should look something like:
> 
>     A Routing Header is not inserted, or deleted by any node along a
>     packet's delivery path, until the packet reaches the final
>     destination node (or each of the set of final destination nodes, in
>     the case of multicast). A Routing Header is not processed by any
>     node along a packet's delivery path, until the packet reaches the
>     destination node (or each of the set of destination nodes, in the
>     case of multicast) identified by the Destination Address field of
>     the IPv6 header.
> 
> ?

OK

> 
> I wonder if it might be better to keep the insertion/deletion part in a
> single place, to avoid repetiton, and then just discuss processing, but
> not insertion/deletion.  -- Or whether repetition is needed for each of
> the "special" EHs, such that folk do not assume that the comments on
> insertion/deletion do not applyto the "special" EHs.

I would prefer spelling it out in detail to avoid doubt.

   Brian