Re: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06

mohamed.boucadair@orange.com Tue, 05 July 2022 10:46 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 8DB87C15CF4B; Tue, 5 Jul 2022 03:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RCxTY4amy0bu; Tue, 5 Jul 2022 03:46:37 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FC17C15CF4E; Tue, 5 Jul 2022 03:46:37 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr20.francetelecom.fr (ESMTP service) with ESMTPS id 4LcfVg47tBz1yJ9; Tue, 5 Jul 2022 12:46:35 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1657017995; bh=yEObHsMbS+MaXX/eBDaiK8Do7GbC/xaEn8qLb5Gv2ks=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=pF7+x3uJO4vCcs16MmK00GjwxNjGdcjmuZoW9K72Me5EhxWkTKZXfjXChMxlVyL4G 9o+0qJRB3ILmPBIOd5yy4Y5spwPXAeehhY4H+YI96Hnl4gXBVS/B583wUqL0iacmy/ zcKQ2mQK1yoBilUiOab7CDAn8UFLdV+d0Icgq/lRLvD5Y/spWeI3gp/eS2r/ygl1t7 33w2u9htCISAEy6HA97ETrR8FNo6hYyKktRYnEhqd3vHsstE63n5jqoy4oEsgL14ES ddCfcYJQyFZt/l5TWjSkdxluhLsYyGMzk1kmFWsc7l65lJnEggC6m+XnUqRoqFuCIy nMD+f7Rtg9JfA==
From: mohamed.boucadair@orange.com
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Vishnu Pavan Beeram' <vishnupavan@gmail.com>, 'TEAS WG' <teas@ietf.org>
CC: 'TEAS WG Chairs' <teas-chairs@ietf.org>
Thread-Topic: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06
Thread-Index: AQIPgl1IfzhnbIOfA7nB0cCPfKDP/ALKUxnYAfHHO0Ss28oYsIAABvhQ
Content-Class:
Date: Tue, 05 Jul 2022 10:46:25 +0000
Message-ID: <32635_1657017995_62C41681_32635_103_1_d26cdedca9f54d0c818fa7941be8bdb0@orange.com>
References: <CA+YzgTs4Z5eEKQfWs19chLxq1bHN0oiRDPfkqWJROsUrNXFnWw@mail.gmail.com> <02ae01d88e6c$003d0200$00b70600$@olddog.co.uk> <14414_1657013372_62C4047C_14414_18_30_f2df4840030942c19ddec193900e1387@orange.com> <04e701d89058$21be21a0$653a64e0$@olddog.co.uk>
In-Reply-To: <04e701d89058$21be21a0$653a64e0$@olddog.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-07-05T10:45:12Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=523da7a9-0511-41f5-af99-4ac4e6ca248f; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: multipart/alternative; boundary="_000_d26cdedca9f54d0c818fa7941be8bdb0orangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/8k24zlz0eV0AcIDOSKyndnAnSCc>
Subject: Re: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 05 Jul 2022 10:46:41 -0000

Re-,

Looks like a good plan.

Thanks, Adrian.

Cheers,
Med

De : Adrian Farrel <adrian@olddog.co.uk>
Envoyé : mardi 5 juillet 2022 12:15
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; 'Vishnu Pavan Beeram' <vishnupavan@gmail.com>; 'TEAS WG' <teas@ietf.org>
Cc : 'TEAS WG Chairs' <teas-chairs@ietf.org>
Objet : RE: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06

That’s a reasonable argument, Med. Thanks.

Might be nice to include a statement of intent in the Abstract/Introduction along the lines of “This document is intended to provide motivation and support for work on YANG models for the IETF Network Slice Service interface. As such, it might not be necessary to advance it to publication as an RFC.”

Cheers,
Adrian

From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
Sent: 05 July 2022 10:30
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Vishnu Pavan Beeram' <vishnupavan@gmail.com<mailto:vishnupavan@gmail.com>>; 'TEAS WG' <teas@ietf.org<mailto:teas@ietf.org>>
Cc: 'TEAS WG Chairs' <teas-chairs@ietf.org<mailto:teas-chairs@ietf.org>>
Subject: RE: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06

Hi Adrian, all,

(focusing on this specific comment below)

As you known, adopting does not mean that the document will make it to the RFC stage. IMO, this document is a good ** support document **. As such, it falls under https://www.ietf.org/about/groups/iesg/statements/support-documents/ and the WG may decide to let it expire when it serves its purposes or not.

The merit I see in formally adopting is to have a WG reference to assess the slice service model against a set of cases and capture consensus about any missing attributes that need to be reflected in the service model itself.

Cheers,
Med

De : Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> De la part de Adrian Farrel
Envoyé : dimanche 3 juillet 2022 01:33
À : 'Vishnu Pavan Beeram' <vishnupavan@gmail.com<mailto:vishnupavan@gmail.com>>; 'TEAS WG' <teas@ietf.org<mailto:teas@ietf.org>>
Cc : 'TEAS WG Chairs' <teas-chairs@ietf.org<mailto:teas-chairs@ietf.org>>
Objet : Re: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06

Hi,

(Not late with this review!)

I only have one question about supporting the adoption of this document
and that is to wonder whether the work is overtaken by events. We
already have work progressing developing and specifying the IETF Network
Slice Service Interface YANG model in draft-ietf-teas-ietf-network-
slice-nbi-yang. That YANG model is surely based on discussions that
arise from this work, and I am not doubting the value of those
discussions. But I don't quite understand why we need to pursue this I-D
towards an RFC when it's principal purpose is surely to shape the
content of the YANG model. Have I missed the purpose of this draft?

_________________________________________________________________________________________________________________________

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.