IETF Logo Mail Archive

Re: [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition

Eric Gray <ewgray2k@gmail.com> Thu, 27 August 2020 20:21 UTC

Return-Path: <ewgray2k@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33E3A3A12A3; Thu, 27 Aug 2020 13:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5IkyEviBWiF5; Thu, 27 Aug 2020 13:21:04 -0700 (PDT)
Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B03B13A129D; Thu, 27 Aug 2020 13:20:59 -0700 (PDT)
Received: by mail-qv1-xf2c.google.com with SMTP id r19so3294906qvw.11; Thu, 27 Aug 2020 13:20:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=dQvnw/vQzyGmaZOikYy12gBJM99pcnQHW6WDIAXrXxQ=; b=qBhNnSofCvSHtfS24WhhXZ/0MQEPUhNeg2kne8ftgc9OEigGYWn1iPkjXKqs6dux64 PLCFGbHPc6x4P7Xb5QYwX80jms2ZQKHouKqHh2+NWmJTS3/X6hf9VLTSj1iW1cDolTwb JS1o3DjuzP27PKhcdyzqarqx4UVONqpqGH1TikPFY9oTKPxnZGTdR8V6Svliv4tIHV41 mL7XvOrYQUS32Eh8xQUQt0lrqJg2uliabwMqN4grbAa4p5egnFg2l2Iyz8Napx0skuTo Z2QB53H77l9BbJuNsiUNzx2+AYvyVZgmTuNfuQFMq/wkkdJj3LI0bxdQoS6KnOipR/by 4wFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=dQvnw/vQzyGmaZOikYy12gBJM99pcnQHW6WDIAXrXxQ=; b=YOtfjrBXtg3ap7zoi1K1wwwg+X6kvKltjklX/xIFKJJZW+7dVYiUoVV6OpqTnr77tt CTwzvXtduDjtUXjaMZgGryC9U5ej6kGdEHKRsWACkt3MgAJVLQeecRw7/KIofZHSew5c roVSlmfjlg54keOwxJwUrH1shdamUIy/JqjltKHRtP+Y04Vd9dSmTIDsncNs2/2Gxf5T X/qsz9x3kNo2u1QHA8DlXpnCdawbC9JenTmkbpThdTE+oJqmob22+eibyAEcTSM2Vsm9 sxXTFvapV82ZJ1zHjjlP/dOyDORYpK1XTsD7WuL/HHDuxuRx1cK9w9qbYITIDJzuBdtY NArg==
X-Gm-Message-State: AOAM532mg0u98Mg56rfSCJRdLfX8OcGI5HHB6egP7qcwzMIAZ3wlPDqX eVCMfmOc0We5ZpwU4sY46TyOgTJhu14T5UoN
X-Google-Smtp-Source: ABdhPJyO3SyuRrwAwspplJFsQL7DYRIRoH8k0q00Tv5nc6YNGH6obeCprqjaYmWCqnO6Q3NTI12pEg==
X-Received: by 2002:a0c:f607:: with SMTP id r7mr20939694qvm.219.1598559658377; Thu, 27 Aug 2020 13:20:58 -0700 (PDT)
Received: from ?IPv6:2601:85:4680:3329:944a:5c1b:1c90:bc44? ([2601:85:4680:3329:944a:5c1b:1c90:bc44]) by smtp.gmail.com with ESMTPSA id p33sm2895904qtp.49.2020.08.27.13.20.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Aug 2020 13:20:57 -0700 (PDT)
From: Eric Gray <ewgray2k@gmail.com>
Message-Id: <1BCC788D-A7AC-4B77-916A-DC3416A7BC96@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C5D3D50C-61ED-4BF5-906E-94A748B30E7A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 27 Aug 2020 16:20:56 -0400
In-Reply-To: <VI1PR0601MB215756864B9535C3D0E3FA5B9E550@VI1PR0601MB2157.eurprd06.prod.outlook.com>
Cc: Jari Arkko <jari.arkko@piuha.net>
To: TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
References: <CA+YzgTvnv5nUZ6OYx9GkFUxDHxAFNvYsx5LrFfho3860_MLfZA@mail.gmail.com> <330a76d8-2f05-795f-42a6-01de094b54b4@joelhalpern.com> <BYAPR13MB2437D23542B163D477B583C8D95A0@BYAPR13MB2437.namprd13.prod.outlook.com> <93726585-ccdd-3460-e6c6-540f98ec9084@joelhalpern.com> <BYAPR13MB243700523A1B5D597973C1CCD95A0@BYAPR13MB2437.namprd13.prod.outlook.com> <2265a594-f48f-3903-d998-3bb764df627a@joelhalpern.com> <b7b110ce14344cadb74b80ea9ccce144@huawei.com> <f07c0de8-6d51-7ffe-7ff5-8fb13212708a@joelhalpern.com> <3f563fbf4a3742a195e61d96844bd042@huawei.com> <MN2PR15MB29903640C9630924BA18B61E8F5B0@MN2PR15MB2990.namprd15.prod.outlook.com> <77124c508ce54822a70afc616c31e5cf@att.com> <CAE4dcxnYo8NCB_ADmd-Qv-5ZwZ5hpM4FtgnF=oLcELTO2i7o=w@mail.gmail.com> <5765E489-B949-424B-8217-8049948AFD08@att.com> <CA+YzgTssZ750UXoc0xzCzD63rbbp3uA_4mzasfLMgni1_Z8J+A@mail.gmail.com> <CF569281-FBA6-4A6F-9888-FA61FA423C1A@piuha.net> <a2a3697e-53d0-4d61-8323-532cb74d5444@Spark> <c45ed6dd357842818c5840793cb17f36@huawei.com> <30c835f5ce644ccf8f3568cdccb07b0a@huawei.com> <HE1PR07MB4156650423734880FBB37ADBF0540@HE1PR07MB4156.eurprd07.prod.outlook.com> <a9b7e19b7dac474a8a9355746fadf129@huawei.com> <VI1PR0601MB215756864B9535C3D0E3FA5B9E550@VI1PR0601MB2157.eurprd06.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/g6OvxM3sStwG0flQ9efrobT2oNI>
Subject: Re: [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2020 20:21:06 -0000

With the changes suggested by the WG chairs, regarding removal of the appendix and adding placeholder text to the draft, draft-nsdt-teas-transport-slice-definition is even more ready for adoption than it was when presented at IETF 108.

I support the adoption of this draft.

I also realize that there is work cut out for the working group before this draft should be considered finished, and I see a lot of the discussion going on in the adoption thread as being somewhat ahead of its time - because the draft should be adopted as suggested by the WG Chairs - before we delve into the actual content and details.

As a co-editor of the Framework draft, I believe there are some simple ways to polish both drafts further along the lines of suggestions made by many people in this thread - but that is a discussion for after we decide to adopt the drafts.

Some of that discussion has already started - in background mode, as well as in this thread - but much of it should wait until we can make appropriate suggestions to the WG and gain some high degree of consensus on what to actually do.

—
Eric

v2.23.0 | Report a Bug | By Email