Re: [Teas] The TEAS WG has placed draft-gcdrb-teas-5g-network-slice-application in state "Candidate for WG Adoption"

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Fri, 03 February 2023 06:49 UTC

Return-Path: <gengxuesong@huawei.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 7FDA1C151531; Thu, 2 Feb 2023 22:49:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 5PpCpii_32-D; Thu, 2 Feb 2023 22:49:32 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74156C15152B; Thu, 2 Feb 2023 22:49:32 -0800 (PST)
Received: from lhrpeml100004.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4P7R3q2B3Rz6823d; Fri, 3 Feb 2023 14:45:11 +0800 (CST)
Received: from canpemm100010.china.huawei.com (7.192.104.38) by lhrpeml100004.china.huawei.com (7.191.162.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Fri, 3 Feb 2023 06:49:28 +0000
Received: from canpemm500010.china.huawei.com (7.192.105.118) by canpemm100010.china.huawei.com (7.192.104.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Fri, 3 Feb 2023 14:49:26 +0800
Received: from canpemm500010.china.huawei.com ([7.192.105.118]) by canpemm500010.china.huawei.com ([7.192.105.118]) with mapi id 15.01.2375.034; Fri, 3 Feb 2023 14:49:26 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "draft-gcdrb-teas-5g-network-slice-application@ietf.org" <draft-gcdrb-teas-5g-network-slice-application@ietf.org>, "teas-chairs@ietf.org" <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>
CC: JACQUENET Christian INNOV/NET <christian.jacquenet@orange.com>
Thread-Topic: [Teas] The TEAS WG has placed draft-gcdrb-teas-5g-network-slice-application in state "Candidate for WG Adoption"
Thread-Index: AQHZLyUsSwyRax1i2Eq33Xi/Y06kPa67PA0AgAGS6eA=
Date: Fri, 03 Feb 2023 06:49:26 +0000
Message-ID: <e9e8e5c5a75f4fd4b49fec662db4a723@huawei.com>
References: <167447644950.24917.1729181856143737512@ietfa.amsl.com> <12036_1675347082_63DBC48A_12036_450_1_7420f5a646c4492eaaeca0c12f6d3e7a@orange.com>
In-Reply-To: <12036_1675347082_63DBC48A_12036_450_1_7420f5a646c4492eaaeca0c12f6d3e7a@orange.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.43]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/DM5GpfMMU5Y5_r51KMVZItsB7Kw>
Subject: Re: [Teas] The TEAS WG has placed draft-gcdrb-teas-5g-network-slice-application in state "Candidate for WG Adoption"
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: Fri, 03 Feb 2023 06:49:37 -0000

Hi Mohamed,

Thanks very much for reviewing the document and giving detailed comments.
The authors are still working together on modifying the document. I think lots of your concerns may be solved in the next version, including the logical connection among different parts and moving some detailed specification to annex. Other comments you have given in the document will also be carefully considered. 
Hopefully there will be an updated version very soon.

Best
Xuesong

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: Thursday, February 2, 2023 10:11 PM
> To: draft-gcdrb-teas-5g-network-slice-application@ietf.org;
> teas-chairs@ietf.org; teas@ietf.org
> Cc: JACQUENET Christian INNOV/NET <christian.jacquenet@orange.com>
> Subject: RE: [Teas] The TEAS WG has placed
> draft-gcdrb-teas-5g-network-slice-application in state "Candidate for WG
> Adoption"
> 
> Hi all,
> 
> Thanks to the authors for the effort put into this document.
> 
> Please find below some quick comments about this draft:
> 
> * pdf:
> https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-gcdrb-te
> as-5g-network-slice-application-01-rev%20Med.pdf
> * doc:
> https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-gcdrb-te
> as-5g-network-slice-application-01-rev%20Med.doc
> 
> The flow of the draft is really hard to follow and the reasoning is not always
> that intuitive. I guess this is justified as this I-D is a merge (?) of many other
> documents.
> 
> The document can be enhanced by removing implementation details (including
> the digression on virtualization) and focus on the claimed scope: analyze the
> mapping between the 5G slice vs underlying transport slices + assess to what
> extent the Ep information as specified by the 3GPP is sufficient to trigger the
> provision of (transport) slices.
> 
> That's said, I support adopting this document assuming major rewrite effort
> will be needed to align with the intended scope + more focus on the gap
> analysis. The document can be even more better if it exercise the data models
> out there to assess if a 5G slice request can trigger ietf network slice service
> and attachment circuits service requests.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Teas <teas-bounces@ietf.org> De la part de IETF Secretariat
> > Envoyé : lundi 23 janvier 2023 13:21 À :
> > draft-gcdrb-teas-5g-network-slice-application@ietf.org; teas-
> > chairs@ietf.org; teas@ietf.org Objet : [Teas] The TEAS WG has placed
> > draft-gcdrb-teas-5g-network- slice-application in state "Candidate for
> > WG Adoption"
> >
> >
> > The TEAS WG has placed draft-gcdrb-teas-5g-network-slice-
> > application in state Candidate for WG Adoption (entered by Oscar de
> > Dios)
> >
> > The document is available at
> > https://datatracker.ietf.org/doc/draft-gcdrb-teas-5g-network-
> > slice-application/
> >
> > Comment:
> > Pending IPR Call.
> >
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
> 
> ________________________________________________________________
> _________________________________________________________
> 
> 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.