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

S Moonesamy <sm+ietf@elandsys.com> Tue, 03 March 2020 00:10 UTC

Return-Path: <sm@elandsys.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 7DD8B3A1466 for <ipv6@ietfa.amsl.com>; Mon, 2 Mar 2020 16:10:32 -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 DNaiIFB1YlHB for <ipv6@ietfa.amsl.com>; Mon, 2 Mar 2020 16:10:28 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id E08803A1464 for <ipv6@ietf.org>; Mon, 2 Mar 2020 16:10:28 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.81.5]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 0230ACWQ017503 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Mar 2020 16:10:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1583194223; x=1583280623; i=@elandsys.com; bh=GB9UW1c7lWP7nqJa5OUfyX59co1IPsQU9WzPRNtX9TI=; h=Date:To:From:Subject:In-Reply-To:References; b=QmuUbR643cNLIW7Jmvmv5GL9hH4wN6QCv1F7qDXT8B5MTtKq9EPqBlmadfG6D/Yb6 YSAvB+dWaW5Mzis6yEpgvX/dfrm1DQHPiwSqmb8GtKBg0c4CIZJWaCb2uOx1xj/CQQ U9QcFlbqI1Xho5X/TCLV1vqwGLcEgN8xCTgGk1AM=
Message-Id: <6.2.5.6.2.20200302154312.11583140@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 02 Mar 2020 16:09:58 -0800
To: Fernando Gont <fernando@gont.com.ar>, ipv6@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
In-Reply-To: <d5b5e59f-920b-68cd-800c-04c282deead3@gont.com.ar>
References: <17421_1575566127_5DE93B2F_17421_93_1_53C29892C857584299CBF5D05346208A48D1A3DA@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <5518_1582908787_5E594573_5518_436_1_53C29892C857584299CBF5D05346208A48DD1BCA@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <C8417F71-D61E-42AC-831E-B85269D5D4A5@steffann.nl> <9b677b7c-fe52-dbae-7f83-2b5be5194325@gont.com.ar> <6.2.5.6.2.20200228132634.1060a610@elandnews.com> <23625_1583158579_5E5D1533_23625_379_8_53C29892C857584299CBF5D05346208A48DD5266@OPEXCAUBM43.corporate.adroot.infra.ftgroup><4eb1e184-31ad-41c9-ded3-5aa7fb89ef96@gont.com.ar> <15096_1583170126_5E5D424E_15096_398_1_53C29892C857584299CBF5D05346208A48DD5E43@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <d5b5e59f-920b-68cd-800c-04c282deead3@gont.com.ar>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/YpNgacozwqi9M7l4FrV0MoamWMk>
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: Tue, 03 Mar 2020 00:10:33 -0000

Hi Fernando,

[Discussion moved to 6man)

At 10:01 AM 02-03-2020, Fernando Gont wrote:
>That's a comment on a future decision,  not a decision that can be acted upon.
>
>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 decision.

I was reminded of the following on reading the SPRING discussions: 
https://mailarchive.ietf.org/arch/msg/spfbis/VbT1OuHTouS9GrVR934EwOnzp64/

The points which you raised (please see quoted text) can be go both 
ways, i.e. favorably or unfavorably if it has to be considered 
formally.  I would rate the erratum as "minor" within the context of 
the dispute.  The rationale for that is that:

   (a) The decisions are distinct from each other.  A decision in 6MAN does,
       from a procedural perspective, cannot be used in a SPRING process
       discussion.

   (b) An erratum in an "approved" state does not reflect IETF 
Consensus.  There
       is a message [1] from Mr Klensin about that.

Please see the message at 
https://mailarchive.ietf.org/arch/msg/ipv6/_gG2foiugk5B7w3TpnPvBbjHDzs/ 
I would argue, from a process perspective, that the intent of the 
text under dispute should be read in that light.

Regards,
S. Moonesamy

1. https://mailarchive.ietf.org/arch/msg/ietf/r1WnAemu12WcdT7VoFpPUI3j6pk/