Re: Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)

S Moonesamy <sm+ietf@elandsys.com> Fri, 28 February 2020 06:05 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21A263A10CF for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 22:05:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 0McCGk5xhQa5 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 22:05:04 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE023A10CC for <ietf@ietf.org>; Thu, 27 Feb 2020 22:05:04 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.182.47]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 01S64nZe028801 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Feb 2020 22:05:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1582869903; x=1582956303; i=@elandsys.com; bh=5xq89wE8XBv3lEONb19ooHesKXgDhA97EWUlM+6xvgc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nn8+mMi7QRUbWEivdPjkz2mlcQ9AUV/PbK/sIhfFcGGD9/tdNjP1F8CcyLkST3HZT tbAWuXtoU+ApufgjGknWd/BLPqGlVW5QtTIQ1T5d7FZpHdWfJGcotNUBPXQm4xMS8c LEQREYQqNHYjsaxCVcYwVv9rySf8pEP1VCkfJraI=
Message-Id: <6.2.5.6.2.20200227210551.0f2f09d8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Feb 2020 22:03:57 -0800
To: Fernando Gont <fgont@si6networks.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)
Cc: jinmei@wide.ad.jp
In-Reply-To: <7ef2831d-9766-a76a-48f7-79317cb32239@si6networks.com>
References: <876c9105-3da4-e614-2db0-bea025b54663@si6networks.com> <7749f91f-03f1-cc14-bae8-5fe68c88879f@si6networks.com> <6.2.5.6.2.20200227151910.1077c270@elandnews.com> <e90c70d8-12b0-b3c7-384b-fd9e5fc39a11@si6networks.com> <6.2.5.6.2.20200227173633.0ef5ba98@elandnews.com> <7ef2831d-9766-a76a-48f7-79317cb32239@si6networks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aabTsZ4JdV4GSjJpczMwarXTOkE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2020 06:05:07 -0000

Hi Fernando,
At 08:21 PM 27-02-2020, Fernando Gont wrote:
>Yeah, of course erratas change text.There wouldn't be erratas if 
>they were no-ops. The point is that they don't change the 
>spirit/intent of the text.
>
>Again: what do you think is the existing behavior, and how different 
>that is from that described in the proposed errata?

My reading of the Last Call is that there was a text change to 
address the issue which was raised during the discussion of the 
I-D.  That may have introduced some ambiguity and the differing 
interpretations which were discussed on two Working Group mailing list.

I could argue that there isn't any difference if I had a strong view 
on the matter.  I don't have any such view currently.

At 08:54 PM 27-02-2020, Fernando Gont wrote:
>They clearly are not. I have no idea whatsoever where you got this from.
>
>Yes, there's no protocol police. But such behavior does not conform 
>to the IPv6 standard, nor with the existing architecture.

I found the first page [1] of a document from a multi-mission 
laboratory quite interesting.

Regards,
S. Moonesamy

1. http://r.elandsys.com/r/51642