IETF Logo Mail Archive

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

mohamed.boucadair@orange.com Thu, 27 August 2020 12:27 UTC

Return-Path: <mohamed.boucadair@orange.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 95E2D3A0C81; Thu, 27 Aug 2020 05:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 xWILrM1nKGGM; Thu, 27 Aug 2020 05:26:59 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8A1C3A0C7F; Thu, 27 Aug 2020 05:26:58 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 4Bchmx0g3cz31MM; Thu, 27 Aug 2020 14:26:57 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1598531217; bh=3e5xfEaZAuTPC/OVTkwDafspJ8hUMctVCsknnYQU+sc=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=cXoMZPE4TfgzXsqV3399w1awq+FOkCCZMam22qq9FLp01b7IACrcvvQseFrbnDmlx Q4k3wxloXxIjl7qpGqRvNz82TCnFNvGReX20NUpqaaE9P222BL7qagDY9AhNE7eaha TrRG8Wj/bhD7l+BOEWYOL9mBtF9RE/xNNFkhjriCSiEG8R4Zh+5OIoRi/H/ioMy+vq 1qkXqcMHTclynWkPQiXvU6a/aAfrB5nS055eLP9Tj0XLA5EQVAUrGOcUiTCdkj6hdN C9TGO4oACXgVdyFTiSNPXbY43YC0tdAUGpktOzIk+nQOTR1feacCpPz8kNTnALL6dl d5sOwQqyOza1Q==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.98]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 4Bchmw6kRgzBrLp; Thu, 27 Aug 2020 14:26:56 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>
CC: TEAS WG Chairs <teas-chairs@ietf.org>
Thread-Topic: [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition
Thread-Index: AQHWdkB6bHfLwx85fEKuznlDJELZi6lL7KZQ
Date: Thu, 27 Aug 2020 12:26:54 +0000
Message-ID: <29904_1598531216_5F47A690_29904_16_1_7263a5d8-b9e0-4e33-9ea1-9cbab9ff0f0b@OPEXCAUBM7F.corporate.adroot.infra.ftgroup>
References: <CA+YzgTvnv5nUZ6OYx9GkFUxDHxAFNvYsx5LrFfho3860_MLfZA@mail.gmail.com>
In-Reply-To: <CA+YzgTvnv5nUZ6OYx9GkFUxDHxAFNvYsx5LrFfho3860_MLfZA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_7263a5d8b9e04e339ea19cbab9ff0f0bOPEXCAUBM7Fcorporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/2w8iHNb-9nf8sZlNh_LUtxhAV-M>
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 12:27:01 -0000

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.

v2.23.0 | Report a Bug | By Email