Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming

Fernando Gont <> Mon, 02 March 2020 18:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3AC7F3A0DD2 for <>; Mon, 2 Mar 2020 10:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QUBDkHCk9F2Z for <>; Mon, 2 Mar 2020 10:03:01 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EA8D93A0DBF for <>; Mon, 2 Mar 2020 10:03:00 -0800 (PST)
Received: from [] (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 706C4832C9; Mon, 2 Mar 2020 19:02:53 +0100 (CET)
To:, S Moonesamy <>, Martin Vigoureux <>, Suresh Krishnan <>
Cc: "" <>
References: =?utf-8?q?=3C17421=5F1575566127=5F5DE93B2F=5F17421=5F93=5F1=5F53?= =?utf-8?q?C29892C857584299CBF5D05346208A48D1A3DA=40OPEXCAUBM43=2Ecorporate?= =?utf-8?q?=2Eadroot=2Einfra=2Eftgroup=3E_=3C5518=5F1582908787=5F5E594573=5F?= =?utf-8?q?5518=5F436=5F1=5F53C29892C857584299CBF5D05346208A48DD1BCA=40OPEXC?= =?utf-8?q?AUBM43=2Ecorporate=2Eadroot=2Einfra=2Eftgroup=3E?= <> <> =?utf-8?q?=3C6=2E2=2E5=2E6=2E2=2E20200228132634=2E1060a610=40elandnews=2Eco?= =?utf-8?q?m=3E_=3C23625=5F1583158579=5F5E5D1533=5F23625=5F379=5F8=5F53C2989?= =?utf-8?q?2C857584299CBF5D05346208A48DD5266=40OPEXCAUBM43=2Ecorporate=2Eadr?= =?utf-8?q?oot=2Einfra=2Eftgroup=3E?= =?utf-8?q?=3C4eb1e184-31ad-41c9-ded3-5aa7fb89ef96=40gont=2Ecom=2Ear=3E_=3C1?= =?utf-8?q?5096=5F1583170126=5F5E5D424E=5F15096=5F398=5F1=5F53C29892C8575842?= =?utf-8?q?99CBF5D05346208A48DD5E43=40OPEXCAUBM43=2Ecorporate=2Eadroot=2Einf?= =?utf-8?q?ra=2Eftgroup=3E?=
From: Fernando Gont <>
Message-ID: <>
Date: Mon, 2 Mar 2020 15:01:26 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: =?utf-8?q?=3C15096=5F1583170126=5F5E5D424E=5F15096=5F398=5F1=5F?= =?utf-8?q?53C29892C857584299CBF5D05346208A48DD5E43=40OPEXCAUBM43=2Ecorporat?= =?utf-8?q?e=2Eadroot=2Einfra=2Eftgroup=3E?=
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 Mar 2020 18:03:03 -0000

On 2/3/20 14:28, wrote:
> Fernando,
>> From: Fernando Gont []
>> Sent: Monday, March 2, 2020 6:14 PM
>> To: DECRAENE Bruno TGI/OLN; S Moonesamy; Martin Vigoureux; Suresh Krishnan
>> Cc:
>> Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
>> On 2/3/20 11:16, wrote:
>> [...]
>>>> The summary provides by the Working Group Chair states that the
>>>> Responsible Area Director "has not accepted the related errata".  I
>>>> took a quick look at erratum eid5933; it is listed as "Reported".  As
>>>> the erratum has not been classified as per the relevant IESG
>>>> Statement, describing it as "not accepted" is inaccurate.
>>> The email from Suresh that I had cited in support of my statement, seemed and still seems clear to me.
>>> What was not clear to you in Suresh's email?
>>>>    I will process this and move it to the "Hold for Document Update" state
>>>>> Just to be clear, I believe that your stated decision of processing this errata as "Hold for document update" is not only incorrect, but also doesn't represent the consensus this working group got during the rfc2460bis effort -- now RFC8200.
>>> [...]
>>>>    > As such, I will formally Appeal your decision.
>>>> Please do go ahead. I stand by my assessment that this is a misuse of the Errata process and it is not a simple clarification as you claim."
>>> Please take another look now. Suresh has updated the status of the errata. I guess that your point is now moot.
>> It's not moot that you based your decision on wg consensus on something
>> that had not yet happened. The fact that the errata was marked as "held
>> for document update" days *after* you made your decision should be a
>> datapoint.
> That's indeed one data point.
> Another data point is that Suresh had stated his decision on the 6MAN mailing list before. That's _this_ decision that I explicitly referred to by providing the URL to this email.

That's a comment on a future decision,  not a decision that can be acted 

Simple: what would have happened if Suresh had changed his mind, and 
"verified" the erratum? -- You'd have a spring document that you claimed 
to have wg consensus based on an incorrect assumption.

i.e., the consensus outcome was sent based on an *assumption*, not on a 

Fernando Gont
e-mail: ||
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1