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

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 27 August 2020 15:15 UTC

Return-Path: <jmh@joelhalpern.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 0A3643A0DCA; Thu, 27 Aug 2020 08:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.048
X-Spam-Level:
X-Spam-Status: No, score=-3.048 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, NICE_REPLY_A=-0.948, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 UCusOnjjETfi; Thu, 27 Aug 2020 08:15:57 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8810F3A0DA6; Thu, 27 Aug 2020 08:15:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4BcmWx2PP0z6GDYD; Thu, 27 Aug 2020 08:15:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1598541357; bh=UupuE1ue3Q979g87GuRW2htzPgG+g8U12BsZ5cxfw0g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=hRX1GPrXCW/+i8C/YIt1WBD8TPCmFUI/E+diDXlQkRRxRUoF6rf5An5S8PjQpVQFp 9wAzrV97pRqD8Wbj2kBEnxo5u0cwFq2hjO3tyqDHVu1vIf2kZTAPeD2rQqKAaM7vBz bTDLicd/6pf/VulusKuKsCCRAGlPAhUZ+MhkLcCI=
X-Quarantine-ID: <vgpSSndWSSAG>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4BcmWw4ZtWz6G99q; Thu, 27 Aug 2020 08:15:56 -0700 (PDT)
To: mohamed.boucadair@orange.com, Vishnu Pavan Beeram <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>
References: <CA+YzgTvnv5nUZ6OYx9GkFUxDHxAFNvYsx5LrFfho3860_MLfZA@mail.gmail.com> <29904_1598531216_5F47A690_29904_16_1_7263a5d8-b9e0-4e33-9ea1-9cbab9ff0f0b@OPEXCAUBM7F.corporate.adroot.infra.ftgroup>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <2e8a3df4-9c7e-d4ab-1ac7-b539ad74fbae@joelhalpern.com>
Date: Thu, 27 Aug 2020 11:15:55 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <29904_1598531216_5F47A690_29904_16_1_7263a5d8-b9e0-4e33-9ea1-9cbab9ff0f0b@OPEXCAUBM7F.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/G_JqiEi9_e9h5PSLnQLYNLmyaOo>
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 15:15:59 -0000

RFC 7297 is an Independent Submission Informational RFC.
Looking at it, building from it, and where agreed copying the text would 
seem sensible.
Referencing it normatively would be a major problem, as it is not an 
IETF consensus document.

Yours,
Joel

On 8/27/2020 8:26 AM, mohamed.boucadair@orange.com wrote:
> Hi all,
> 
> I support this effort.
> 
> That’s said, I do think the document should leverage existing documents, 
> e.g., use https://tools.ietf.org/html/rfc7297 to define the SLOs:
> 
> 3  <https://tools.ietf.org/html/rfc7297#section-3>.  Connectivity Provisioning Profile (CPP) . . . . . . . . . . . 9  <https://tools.ietf.org/html/rfc7297#page-9>
> 
> 3.1  <https://tools.ietf.org/html/rfc7297#section-3.1>.  Customer Nodes Map  . . . . . . . . . . . . . . . . . . . 9  <https://tools.ietf.org/html/rfc7297#page-9>
> 
> 3.2  <https://tools.ietf.org/html/rfc7297#section-3.2>.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 10  <https://tools.ietf.org/html/rfc7297#page-10>
> 
> 3.3  <https://tools.ietf.org/html/rfc7297#section-3.3>.  QoS Guarantees  . . . . . . . . . . . . . . . . . . . . . 11  <https://tools.ietf.org/html/rfc7297#page-11>
> 
> 3.4  <https://tools.ietf.org/html/rfc7297#section-3.4>.  Availability  . . . . . . . . . . . . . . . . . . . . . . 11  <https://tools.ietf.org/html/rfc7297#page-11>
> 
> 3.5  <https://tools.ietf.org/html/rfc7297#section-3.5>.  Capacity  . . . . . . . . . . . . . . . . . . . . . . . . 12  <https://tools.ietf.org/html/rfc7297#page-12>
> 
> 3.6  <https://tools.ietf.org/html/rfc7297#section-3.6>.  Conformance Traffic . . . . . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.7  <https://tools.ietf.org/html/rfc7297#section-3.7>.  Overall Traffic Guarantees  . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.8  <https://tools.ietf.org/html/rfc7297#section-3.8>.  Traffic Isolation . . . . . . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.9  <https://tools.ietf.org/html/rfc7297#section-3.9>.  Flow Identification . . . . . . . . . . . . . . . . . . . 13  <https://tools.ietf.org/html/rfc7297#page-13>
> 
> 3.10  <https://tools.ietf.org/html/rfc7297#section-3.10>. Routing and Forwarding  . . . . . . . . . . . . . . . . . 14  <https://tools.ietf.org/html/rfc7297#page-14>
> 
> 3.11  <https://tools.ietf.org/html/rfc7297#section-3.11>. Activation Means  . . . . . . . . . . . . . . . . . . . . 15  <https://tools.ietf.org/html/rfc7297#page-15>
> 
> 3.12  <https://tools.ietf.org/html/rfc7297#section-3.12>. Invocation Means  . . . . . . . . . . . . . . . . . . . . 15  <https://tools.ietf.org/html/rfc7297#page-15>
> 
>       3.13  <https://tools.ietf.org/html/rfc7297#section-3.13>. Notifications . . . . . . . . . . . . . . . . . . . . . .16  <https://tools.ietf.org/html/rfc7297#page-16>
> 
> Cheers,
> 
> Med
> 
> *De :*Teas [mailto:teas-bounces@ietf.org] *De la part de* Vishnu Pavan 
> Beeram
> *Envoyé :* mercredi 19 août 2020 17:50
> *À :* TEAS WG <teas@ietf.org>
> *Cc :* TEAS WG Chairs <teas-chairs@ietf.org>
> *Objet :* [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition
> 
> All,
> 
> This is start of a *three* week poll on making
> draft-nsdt-teas-transport-slice-definition-03 a TEAS working group document.
> Please send email to the list indicating "yes/support" or "no/do not
> support". If indicating no, please state your reservations with the
> document. If yes, please also feel free to provide comments you'd
> like to see addressed once the document is a WG document.
> 
> The poll ends September 9th (extra week to account for vacation season).
> 
> Thanks,
> Pavan and Lou
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>