Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)

otroan@employees.org Fri, 06 December 2019 19:14 UTC

Return-Path: <otroan@employees.org>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F07112004A; Fri, 6 Dec 2019 11:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 OFqBU7Y62E5N; Fri, 6 Dec 2019 11:14:07 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 465E8120059; Fri, 6 Dec 2019 11:14:07 -0800 (PST)
Received: from astfgl.hanazo.no (unknown [IPv6:2a01:79c:cebd:47d8:c8b:f971:52ca:e1ba]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 817614E11B3C; Fri, 6 Dec 2019 19:14:06 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by astfgl.hanazo.no (Postfix) with ESMTP id D07A32528C30; Fri, 6 Dec 2019 20:13:57 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
From: otroan@employees.org
In-Reply-To: <CALx6S35Y0LgwHzBawJUQEyYcRULgSVsRLCW0f35aqsrjX5QasA@mail.gmail.com>
Date: Fri, 6 Dec 2019 20:13:57 +0100
Cc: Bob Hinden <bob.hinden@gmail.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, SPRING WG <spring@ietf.org>, 6man <6man@ietf.org>, "int-ads@ietf.org" <int-ads@ietf.org>, rtg-ads <rtg-ads@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>
Content-Transfer-Encoding: 7bit
Message-Id: <1CEE1555-3D12-4998-9C69-23757649E908@employees.org>
References: <BN7PR05MB5699EA5F4C041538560282A6AE5F0@BN7PR05MB5699.namprd05.prod.outlook.com> <52132FA9-669E-4B32-BDC8-6F06C98315F3@gmail.com> <CALx6S37r2JYbrMpN-qR3bD3kaOMj3xEceQC5JhVb8dqVzfq=5A@mail.gmail.com> <06B50938-0FC6-4901-9531-CC0385185F13@employees.org> <CALx6S35Y0LgwHzBawJUQEyYcRULgSVsRLCW0f35aqsrjX5QasA@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/QML63Pll67Csnhgvu-1j6Elgz2w>
Subject: Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)
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 Dec 2019 19:14:08 -0000

Tom,

> Bear in mind that quality discussion is real work by those
> participating. It is a lot of effort to carefully read drafts, give
> clear feedback, and respond to rebuttals. I would like to think that
> the work individuals put in is justified by the outcome, and I assume
> it the chairs prerogative to steer the discussion as necessary to
> drive towards a discernible outcome in a finite amount of time.

Absolutely.
Unfortunately the IETF process is open to attacks.
It appears that something akin to a proxy war is being fought.
Some things has to be in place for a consensus based process to work,
which looks to be missing here.

While the chairs have some tools to their disposition; for this to work
it requires the actors and the whole community to respect and
self-police that process.

How frustrating it may be for the spectators,
letting it play out may be the best option we got.

Best regards,
Ole