Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming (off-topic)

Andrew Alston <Andrew.Alston@liquidtelecom.com> Mon, 02 March 2020 07:06 UTC

Return-Path: <andrew.alston@liquidtelecom.com>
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 225783A0E5E for <spring@ietfa.amsl.com>; Sun, 1 Mar 2020 23:06:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 66-am2nI4uhG for <spring@ietfa.amsl.com>; Sun, 1 Mar 2020 23:06:40 -0800 (PST)
Received: from eu-smtp-delivery-182.mimecast.com (eu-smtp-delivery-182.mimecast.com [207.82.80.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D29F3A0E62 for <spring@ietf.org>; Sun, 1 Mar 2020 23:06:39 -0800 (PST)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-he1eur04lp2059.outbound.protection.outlook.com [104.47.13.59]) (Using TLS) by relay.mimecast.com with ESMTP id uk-mta-114-o-bAMZo8OAK25WE4SsY5lw-1; Mon, 02 Mar 2020 07:06:32 +0000
X-MC-Unique: o-bAMZo8OAK25WE4SsY5lw-1
Received: from DBBPR03MB5415.eurprd03.prod.outlook.com (20.179.47.79) by DBBPR03MB5432.eurprd03.prod.outlook.com (20.179.46.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.16; Mon, 2 Mar 2020 07:06:30 +0000
Received: from DBBPR03MB5415.eurprd03.prod.outlook.com ([fe80::31cd:8171:1d1f:2fa9]) by DBBPR03MB5415.eurprd03.prod.outlook.com ([fe80::31cd:8171:1d1f:2fa9%5]) with mapi id 15.20.2772.019; Mon, 2 Mar 2020 07:06:30 +0000
From: Andrew Alston <Andrew.Alston@liquidtelecom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Robert Raszuk <robert@raszuk.net>
CC: SPRING WG <spring@ietf.org>
Thread-Topic: [spring] WGLC - draft-ietf-spring-srv6-network-programming (off-topic)
Thread-Index: AQHV8AlrhCaVYkceMUu4Xlknso/BkKg0WtCAgAAEQACAAH4BYA==
Date: Mon, 02 Mar 2020 07:06:30 +0000
Message-ID: <DBBPR03MB5415EAB1D2D2992CF7A39FBAEEE70@DBBPR03MB5415.eurprd03.prod.outlook.com>
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> <9449c98e-b1d6-2c74-b78d-df3f5ba15ebc@nokia.com> <6.2.5.6.2.20200229223634.093850f0@elandnews.com> <DBBPR03MB54150500DA829FBAB73DFEC1EEE60@DBBPR03MB5415.eurprd03.prod.outlook.com> <6.2.5.6.2.20200301111046.0c0499b0@elandnews.com> <CAOj+MMH3eyjoQe=SokYQ89HM2po01G1V=kgO+653EKx8eaobzw@mail.gmail.com> <abc665ae-603b-49d9-9ce5-c51c3072e571@joelhalpern.com>
In-Reply-To: <abc665ae-603b-49d9-9ce5-c51c3072e571@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2c0f:fe40:3:1:7439:99c2:1044:543c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 5bbb5a65-9e89-4bbb-71c2-08d7be783bd9
x-ms-traffictypediagnostic: DBBPR03MB5432:
x-microsoft-antispam-prvs: <DBBPR03MB54324C40D325F1846BCDAB14EEE70@DBBPR03MB5432.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 033054F29A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39860400002)(396003)(136003)(376002)(366004)(346002)(199004)(189003)(9686003)(5660300002)(55016002)(71200400001)(8676002)(81156014)(81166006)(66574012)(186003)(66446008)(66946007)(66476007)(66556008)(64756008)(76116006)(316002)(110136005)(86362001)(6506007)(7696005)(52536014)(478600001)(33656002)(4326008)(8936002)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:DBBPR03MB5432; H:DBBPR03MB5415.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jesmvBpli2w9IbOn6qwQpuqLNqIL8bfk7wQ5SX01w10oxfZDG4T3I3OG9u9II/pXFRH+QB7AMHiGsI0Nk50mKzFRXGY/O5UZK7Q04vyJMZPdYpkVkOQ7MPUWmqFJbF8mospYMhl0CYAr/DenugSl4h4+U9sx91j+GfKrDreIJJySe2e+5a+WxAPBnwvs+WroKHhHXAMvXWtSvAOpcrysvtp4U/+4U0BVAkfdcDwmePbAFKPlVQ8kkbESNtFNft+oiCuNg2M1hYjGk7jasKXfJiZOJU8aN7rnBl9gfXpy83/McDrnwCrPF2ukWjmep1SSIkCE8/+l3Wl46tQZ1wZ/O5f7DYGBsiR3OPA+wDWvHJsEbIg36P9K6JxslqkbOcBIXL1CifKwzlBoqt7kU2vaj9XYJZZxvb/IL2/q4YUjTgn2HOOQss9BjB36E0Js4/5h
x-ms-exchange-antispam-messagedata: kKybUJusDbvHDL//zWfxzTV/3NPsVGfrlqMte7IAOfq3KS3MCUYsaHZYGvxp2NX68K8Z15fFUBMSI+t7w36EjyvI/2ZE8cnoyFR6rXYA9akSaFif+8wiIxNcZkfOatxbkyR05xMnpwckKkzaD3Uvkpuqex9SX5JPseXMd1C0j6xWMySvxNujGsIkPjGy3EU/iEsogdXOkMVODocT921smA==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: liquidtelecom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5bbb5a65-9e89-4bbb-71c2-08d7be783bd9
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Mar 2020 07:06:30.4954 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 68792612-0f0e-46cb-b16a-fcb82fd80cb1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4Gx092Q1dE2iZzFGecnw973dGrVHb4Utydw1uuqwVQkpwKNamUGJZm/i4n0bCvJeD2bNUpnM+k12o4NA3hEiny+04pnHQFPZBGcBezZms7o=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBBPR03MB5432
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: liquidtelecom.com
Content-Type: multipart/alternative; boundary="_000_DBBPR03MB5415EAB1D2D2992CF7A39FBAEEE70DBBPR03MB5415eurp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/69Firzet3kET3nKUt8jK2wPhy-c>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming (off-topic)
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: Mon, 02 Mar 2020 07:06:43 -0000

The usual practice when a hair o-authors a document is for the co-chair
to manage all aspects of the document life cycle. In this case, due to
the co-chair being unavailable, we have a bit of a problem. For
non-contentious documents, we can easily manage anyway. In this case,
the document is quite contentious. Which makes things complicated.

Yours,
Joel

In any normal circumstance, I would agree there would be far less of a problem – and we could find an simple way to manage this.  This however, is not a normal situation.

You have a write up of the LC – that states “We had to move this document forward” – there is absolutely nothing in the IETF process that states any document has to move forward in the absence of consensus.  The IETF says – we move forward based on consensus, not based on majority will of the working group to move something forward in the face of sustained unaddressed objections.
You have a write up of the LC – which not once – other than in the context of RFC8200 and consensus achieved on that – mentions the word consensus in the context of this RFC – and last I checked, rough consensus was the basis for moving documents forward.
You have multiple issues that have not been addressed – you have a deep point of contention about RFC8200 – you have promises made at the microphone in Montreal (with the chair’s blessing) about providing an analysis of address space used, you have a concern that has been raised about RFC7112, and more and more individuals coming out and saying – we don’t agree with this – for technical reasons.

Now, in light of this – there are going to be questions – particularly in light of the fact that both the chair in question, and the AD in question, have their names on drafts either as contributors or authors which are either the draft in question, or have direct normative references to the draft on question.  Intentional and gaming the process – that I cannot say – it is up to each individual to decide on their own action and I do not know these individuals well enough to judge myself, however, I think it is naïve of anyone to believe that there will not be serious questions raised as to the impartiality of participants in the closure  of last call when we are facing such contentious issues, a very clear lack of consensus, and a series of unaddressed issues.

Thanks

Andrew