[spring] Who is the design ultimate authority over IPv6? (Re: WGLC - draft-ietf-spring-srv6-network-programming)

Mark Smith <markzzzsmith@gmail.com> Fri, 06 March 2020 06:32 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 947553A07FF; Thu, 5 Mar 2020 22:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Status: No, score=-0.598 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, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, SPF_HELO_NONE=0.001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pxlFStrdT-Bg; Thu, 5 Mar 2020 22:32:14 -0800 (PST)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 C3D763A0800; Thu, 5 Mar 2020 22:32:14 -0800 (PST)
Received: by mail-ot1-x32e.google.com with SMTP id j16so1437764otl.1; Thu, 05 Mar 2020 22:32:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=tMbE09svv0HvWbUeB7CS0i65KlOi2rT1GVG5PdHLTXY=; b=HvxkvL1YSpk/6SsrGVQ26uDXtANd8KH9gZMxhS6h/jizgodRJW5ZdktYwQ9e5SqAuh wJZXyhmxd2TbbZzbCMGAaSX6p2vZBjz/81Bc8O06R60ttL4ioxaBDPtpDs0lY0TQWANK 8Zcws/c8KmGJMuWy1J9D2UmEhUzfIb46UunQ4cdFu1BFsa6tuLnu5wdrlio7xf+CnDFn Xw0NVUK+4RQUsfKPo/hcisqvjQDrtQZLE/u/D2J0n1bE6GEAVrPH6wYTgr4dxi0Me02x mg+GfYfr3elbGIlJAC7gWmQ+qlaKLKstzTtUvD+N2ZrePz6D/kvlDCUCYQAlHGd2euhC wJLw==
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:content-transfer-encoding; bh=tMbE09svv0HvWbUeB7CS0i65KlOi2rT1GVG5PdHLTXY=; b=PaiSwqgSYJHdjWwQU6Sn1WfGhcghW51Mss4S+3T70R5H20ZjYOM9AIMF+ztmQklWod NGVx5yATxU1L1EtUmzm6Od3aWGZVx7MaQXK/miikWRdM5ysfRIh4fwtTk8i4FxV+teOC HGud4U5WZsY8ZUBLyrQNwJs4i5XlFLekH+HpBL7Y8zMWpAXX8nSYxWDa69ZNh0PKxDKu 6uBgSRPiEL7cXOyajDhQ+soPqxi3AAR09lzr4oH5wi7Jk4Yb5X9kdEi2jVMrH0ABNlQo bEIUm+Ex39Mt/OdcYlgLsfuYUgTcKAi2q8T6tup8M55GvFSnlaSV8SLhQ3u/SG/KYcVn FJkA==
X-Gm-Message-State: ANhLgQ3SfQ9vbX3Lhz3suEUhTD3ILZVZml07U0auyV+tY4eB3NQp4RGd vUXGFYaaZsdaOJMZ1G4tfqlqvPnwqHSIDlhsMFQ=
X-Google-Smtp-Source: =?utf-8?q?ADFU+vvmO3fpKMxg/2mG2qUO5mB5k/kV8w+JwBXZJoPK?= =?utf-8?q?iWtEbopbeGq40/Jl8oaWJKK+olPw/qxQK4jDY00XPQA2rwY=3D?=
X-Received: by 2002:a9d:6204:: with SMTP id g4mr1376597otj.94.1583476333780; Thu, 05 Mar 2020 22:32:13 -0800 (PST)
MIME-Version: 1.0
References: =?utf-8?q?=3C17421=5F1575566127=5F5DE93B2F=5F17421=5F93=5F1=5F53?= =?utf-8?q?C29892C857584299CBF5D05346208A48D1A3DA=40OPEXCAUBM43=2Ecorporate?= =?utf-8?q?=2Eadroot=2Einfra=2Eftgroup=3E?= =?utf-8?q?=3C6c674995-8cc7-c024-4181-60b160910f75=40si6networks=2Ecom=3E_?= =?utf-8?q?=3C29345=5F1576001884=5F5DEFE15C=5F29345=5F229=5F5=5F53C29892C857?= =?utf-8?q?584299CBF5D05346208A48D250B7=40OPEXCAUBM43=2Ecorporate=2Eadroot?= =?utf-8?q?=2Einfra=2Eftgroup=3E?= =?utf-8?q?=3C89402a30-129b-314f-90f1-ba6efcdd6a88=40si6networks=2Ecom=3E_?= =?utf-8?q?=3C16536=5F1576089460=5F5DF13774=5F16536=5F366=5F1=5F53C29892C857?= =?utf-8?q?584299CBF5D05346208A48D273AD=40OPEXCAUBM43=2Ecorporate=2Eadroot?= =?utf-8?q?=2Einfra=2Eftgroup=3E?=
In-Reply-To: =?utf-8?q?=3C16536=5F1576089460=5F5DF13774=5F16536=5F366=5F1=5F?= =?utf-8?q?53C29892C857584299CBF5D05346208A48D273AD=40OPEXCAUBM43=2Ecorporat?= =?utf-8?q?e=2Eadroot=2Einfra=2Eftgroup=3E?=
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 6 Mar 2020 17:31:47 +1100
Message-ID: <CAO42Z2z2s92yitCC0eLrNO3dXe_EarRSUZq8GmJ=QRdZ59d0ag@mail.gmail.com>
To: "bruno.decraene" <bruno.decraene@orange.com>
Cc: Fernando Gont <fgont@si6networks.com>, SPRING WG List <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/m4QQ4dJYPvUp-3RwL7AEekvHzbQ>
Subject: [spring] Who is the design ultimate authority over IPv6? (Re: WGLC - draft-ietf-spring-srv6-network-programming)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2020 06:32:17 -0000

On Thu, 12 Dec 2019 at 05:37, <bruno.decraene@orange.com> wrote:
> Fernando,
> - Read the mailing list and you will see that everyone do not share your opinion. So at least one person is wrong. I think that it would help if everyone, including you, could consider that they/you _may_ be wrong, at least to better understand the comments been made by others.  And possibly the text from RFC 8200 is not clear, but this is what we have. And this is the text to use to support the claim that this text is violated.

The final interpretation and intent of text in RFC8200 should be up to
6man, not SPRING, when there is ambiguity and dispute, as 6man is the
ultimate design authority for IPv6.

RFC5704, "Uncoordinated Protocol Development Considered Harmful":

" In particular, the
   IAB considers it an essential principle of the protocol development
   process that only one SDO maintains design authority for a given
   protocol, with that SDO having ultimate authority over the allocation
   of protocol parameter code-points and over defining the intended
   semantics, interpretation, and actions associated with those code-

IETF WGs would qualify as standards development organisations.

Those of us in 6man during the clarifications in this area of RFC8200
know the intent. It was specifically about modification of the EH
chain, and was in response to the
'draft-voyer-6man-extension-header-insertion' Internet Draft.

> - Why have _you_ filled an errata against RFC 8200, in order to change the technical content of this section, if you don't agree that one may red " Destination Address field of the IPv6 header" as the IPv6 address present in the Destination Address field of the IPv6 header been received by the End node (or even sent by the source node)
> https://www.rfc-editor.org/errata/eid5933
> > > At minimum, I think that we can agree that there is another reading, as expressed by other WG participants, and hence I disagree with "of course".
> >
> > No, I argue that there is not.IN fact, I argue that folks have been
> > following that strategy for way too long, and that's quite frustrating.
> >
> >
> >
> > > Personally, I understand "Destination Address" as "Destination Address field of the IPv6 header." as indicated explicitly in the text quoted.
> >
> > The quoted text is from RFC8200. In the context of RFC8200 the
> > Destination Address can only contain the ultimate destination of the
> > packet. Where's the ambiguity?
> >
> > And let me ask you, as chair, another question, that will lead you to
> > the same place: is IPv6 and end to end protocol?
> That's not a question for a spring chair to answer.
> I'm reading the sentence in RFC8200. If we can't agree on the meaning of this explicit sentence, I don't think that discussing philosophical r religious question is going to help.
> > The fact that I may claim that RFC8200 contains a receipe for BBQ does
> > not actually mean that that's the case.
> You do realize that your above sentence also applies to yourself? So how is this helping to progress?
> Can we please focus on the RFC8200 sentence?  I'm really trying to understand your point.
> Let's stick to the texts of documents.
> >
> > > I'm fine with having this clarified with 6MAND chairs and AD. That been said, the Internet AD would have an opportunity to DISCUSS this.
> >
> > For the record, I think this is a major issue that should be cleared
> > before it can be claimed that there is consensus to request publication
> > of this document.
> OK, this is recorded.
> >
> >
> > >
> > >> does not specify any routing header type, and hence the meaning is
> > >> unambiguous (there's no destination other than the final destination of
> > >> the packet).
> > >>
> > >> This is of course in line with IPv6 being and end-to-end protocol, and
> > >> crucial for other related mechanisms to work as expected (such as IPsec
> > >> AH). Please also check: draft-smith-6man-in-flight-eh-insertion-harmful.
> > >>
> > >> So, in order to proceed with the document, there are multiple options
> > >> forward:
> > >>
> > >> 1) Just remove the corresponding text/behavior
> > >
> > > That is indeed one option. But as of today, this is not my assumption.
> > >
> > >> 2) Implement a similar mechanism in an RFC8200-compliant manner (e.g.,
> > >> re-encap)
> > >
> > > SRH insert is out of scope of this specification. So yes, IPv6 encaps is used.
> > > We are talking SRH removal. I'm assuming that you are referring to PSP. My understanding is that this function (PSP) is to distribute the (forwarding plane) load between the PSP and the USP. In a way similar to MPLS PHP. But in all cases, this is not about SRH insertion.
> >
> > It's about SRH removal, which is also forbiden by RFC8200.
> >
> >
> >
> >
> > >> 3) Do the necessary standards work to update RFC8200, such that it
> > >> allows this sort of behavior, and only ship the network-programming
> > >> draft for publication when at least 6man has consensus to proceed on
> > >> that path.
> > >
> > > Not the preferred path as of today.
> >
> > Yes, it should be evident that it seems the preferred path has been
> > (starting with EH insertion at the time) to circumvent existing
> > specifications.
> >
> >
> >
> > >
> > >> P.S.: I will go through the document once again... but the same
> > >> reasoning should be applied to any EH-insertion/removal at a place other
> > >> than the source of the packet or its final destination.
> > >
> > > It looks to me that SRH insertion and SRH removal are to be treated differently.
> >
> > I don't see how or why.
> SRH insertion is done by a node, on the path, which is not the destination of the IPv6 addresses.
> SRH removal is done by a node which is receiving the packet because it's IPv6 address is in the destination of the IPv6 packet.
> > Both violate the same requirement in RFC8200.
> We are not having a conversation, so let's not repeats the same point again and again.
> Your opinion has been noted. So does opinions on this same point expressed by other wg participants.
> >
> >
> >
> > Thanks,
> > --
> > Fernando Gont
> > SI6 Networks
> > e-mail: fgont@si6networks.com
> > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> >
> >
> >
> >
> _________________________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring