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

Andrew Alston <> Fri, 06 December 2019 22:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9AABD1209AF for <>; Fri, 6 Dec 2019 14:24:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7O9kmZKXPkZC for <>; Fri, 6 Dec 2019 14:24:44 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6AACB12018D for <>; Fri, 6 Dec 2019 14:24:44 -0800 (PST)
Received: from ( []) (Using TLS) by with ESMTP id uk-mta-115-KQsciWAfO3GUuFilqT6SXg-1; Fri, 06 Dec 2019 22:23:36 +0000
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.13; Fri, 6 Dec 2019 22:23:34 +0000
Received: from ([fe80::707f:9207:45d4:82bc]) by ([fe80::707f:9207:45d4:82bc%6]) with mapi id 15.20.2516.017; Fri, 6 Dec 2019 22:23:34 +0000
From: Andrew Alston <>
To: Ole Troan <>, Fernando Gont <>
CC: Ron Bonica <>, SPRING WG <>, 6man <>, "" <>, Bob Hinden <>, rtg-ads <>
Thread-Topic: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)
Date: Fri, 6 Dec 2019 22:23:34 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-GB
user-agent: Microsoft-MacOutlook/10.1f.0.191110
x-originating-ip: [2c0f:fe40:3:3:a1b6:dc2b:61a9:8e7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 128334a3-b0d3-4a46-1600-08d77a9aeea4
x-ms-traffictypediagnostic: DBBPR03MB5254:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0243E5FD68
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(39860400002)(366004)(346002)(136003)(189003)(199004)(6506007)(53546011)(102836004)(71190400001)(71200400001)(2616005)(110136005)(54906003)(186003)(76176011)(4326008)(33656002)(58126008)(99286004)(86362001)(6512007)(36756003)(66446008)(8936002)(5660300002)(8676002)(81156014)(81166006)(66476007)(66556008)(478600001)(66946007)(64756008)(76116006)(229853002)(91956017)(2906002)(305945005)(6486002)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:DBBPR03MB5254;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 4ns5nxVx4vURXaK8iAzZY/VLfnEr1iEMwbawHxYoOf2zZ0/EACCMqh3KsgeSatW8LIX0mJTTLPEVP2OMKyLe/sKJSRXYHtxZyH1r8F23hD/JYE/J9jeTvvmGefAhOLGq31G7/nM00YuzZMS2dfRawBFf7mRXOtuwd6GwnbMRnvXVJ+4Ua7xxM3Q6jKkrHUWLHtUgPINZFRxK3gSyzh4aStnJ1mF/d3i3nyL8TjfztzLG4lFPpxL9c2h9ZkSLIGSXk39TDehq22n8sT+5FsTkqpl3oi6lca5Q7EMA63UpIKrL6d71GPv4yZf8v7zqdJA5A8UoCRVW8NQQ6LvZmBa6LGswtgP+9tIHPoyJ7oPHKRp++HmkYfJDenVgNqMkpBLEUqug1BaMg2XQkQumrjAZUP/1InnIJaTU0sTp+hW95ck62QHt1/9fxJygy06gQMFX
x-ms-exchange-transport-forked: True
Content-ID: <>
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 128334a3-b0d3-4a46-1600-08d77a9aeea4
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Dec 2019 22:23:34.2938 (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: xWpack6IveKVXyKKf/PY8ajsoWROGZiAWzz/bF7exWGYQ20hlr67M7daLfraV2j+cbxmHDamvKgoiPWYSYYgBWEu4dcphylt9n+k/O1W3LA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBBPR03MB5254
X-MC-Unique: KQsciWAfO3GUuFilqT6SXg-1
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <>
Subject: Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)
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: Fri, 06 Dec 2019 22:24:46 -0000

Ole - so - let me understand something.

The definition of consensus - among other things - say that all outstanding objections have been addressed (though not potentially resolved).  When you have multiple people saying - a draft violates RFC8200 and that is a concern - and if such a thing is required, an update to RFC8200 should be done.  Multiple concerns have been raised - a number of which have not been addressed to the satisfaction of those asking the questions.

Yet - we now see documents being pushed through to last call without these things being addressed.  So I would ask - what exactly do you, as a working group chair propose we do - swallow our technical concerns and our objections and because we've said it once, and it's been ignored or swept under the rug, shrug our shoulders and say - oh well - that’s ok - we tried - and let something we believe to be technically flawed sail through?

I stood and very clearly stated multiple times that I believe that work on this stuff and the drafts which I am co-author on should continue in parallel - because for one - I believe in some ways - they address different things - yet - at the same time - that does not mean that I believe that we should accept things which we have deep technical concerns about.  

The engineering must come first - and it seems very clear to me that both myself and others - have significant technical and operational concerns - and I find it rather bizarre that you seem to imply that once these concerns are stated once - we should swallow it and accept a situation where these are not addressed and documents are shoved through to last call in the face of serious technical objection.

So - please - clarify for me - are you asking us to swallow our objections and just accept something that violates another rfc for which there is consensus just because we asked once, and the issue wasn't addressed - so that makes it somehow disappear?  Or what exactly are you expecting of us?


On 07/12/2019, 01:02, "Ole Troan" <> wrote:

    > On 6 Dec 2019, at 22:09, Fernando Gont <> wrote:
    > I don't think there is much room for interpretation here, but anyway I
    > should ask: are you suggesting that I have attacked or been attacking
    > the process?
    I would rather say taking advantage of the process.
    By reiterating the same assertive arguments again and again you contribute to polarization. Your strategy for consensus building seems to be one of attrition. 
    If you want to help make the process work, I would encourage you to reconsider that approach.