Re: [mpls] Closed: draft-saad-mpls-miad-usecases

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 19 May 2022 09:36 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B01C159A28; Thu, 19 May 2022 02:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 WYUGj4gM074n; Thu, 19 May 2022 02:36:19 -0700 (PDT)
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 ECCE6C15952A; Thu, 19 May 2022 02:36:18 -0700 (PDT)
Received: from fraeml701-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4L3l5g0fj1z6H7dT; Thu, 19 May 2022 17:33:11 +0800 (CST)
Received: from kwepemi500015.china.huawei.com (7.221.188.92) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Thu, 19 May 2022 11:36:14 +0200
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi500015.china.huawei.com (7.221.188.92) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 19 May 2022 17:36:12 +0800
Received: from kwepemi500017.china.huawei.com ([7.221.188.110]) by kwepemi500017.china.huawei.com ([7.221.188.110]) with mapi id 15.01.2375.024; Thu, 19 May 2022 17:36:12 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, "draft-saad-mpls-miad-usecases@ietf.org" <draft-saad-mpls-miad-usecases@ietf.org>
CC: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>
Thread-Topic: [mpls] Closed: draft-saad-mpls-miad-usecases
Thread-Index: AQHYaOAV5pVE71/kFkesQtBy7mM4Z60l7nAA
Date: Thu, 19 May 2022 09:36:12 +0000
Message-ID: <e2a927d0300b44b5a3df0f79ec1e6d2a@huawei.com>
References: <d119d6c9-92d2-9989-2ed0-34daeabc0326@pi.nu> <4703edad-e333-8a14-6ec7-f8eeffbba0d1@pi.nu>
In-Reply-To: <4703edad-e333-8a14-6ec7-f8eeffbba0d1@pi.nu>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/akIEcX8M9sfmgwK6L100nIFfetE>
Subject: Re: [mpls] Closed: draft-saad-mpls-miad-usecases
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2022 09:36:21 -0000

Hi Loa, 

Sorry for the late response to this thread. For the record, I support the adoption of this document. It is a good starting point to document the possible use cases of miad/mna.

I used to made some comments on the terminology alignment (e.g. align with TEAS for network slicing terms), this should be easy to fix in following revisions. 

Section 3 of this document talks about the co-existence of use cases. In addition to the co-existence of the new use cases, my suggestion is to also add the use cases which require the co-existence of existing MPLS mechanisms and the new functions. 

For example, the encapsulation of BIER in MPLS is defined in RFC 8296. The co-existence of BIER and the new functions such as IOAM in MPLS data plane needs to be considered. 

Best regards,
Jie

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
> Sent: Monday, May 16, 2022 12:46 PM
> To: mpls@ietf.org; draft-saad-mpls-miad-usecases@ietf.org
> Cc: mpls-chairs@ietf.org; pals-chairs@ietf.org
> Subject: [mpls] Closed: draft-saad-mpls-miad-usecases
> 
> Working Group, authors,
> 
> This working group adoption poll is closed.
> 
> We have a new working group document. Can the authors please post
> 
> draft-ietf-mpls-mna-usecases-00
> 
> /Loa
> 
> For the wg chairs
> 
> On 2022-04-28 12:54, Loa Andersson wrote:
> > Working Group,
> >
> > This is to start a two week poll on adopting poll on
> > draft-saad-mpls-miad-usecases as a MPLS working group document.
> >
> > Please send your comments (support/not support) to the mpls working
> > group mailing list (mpls@ietf.org). Please give a technical motivation
> > for your support/not support, especially if you think that the
> > document should not be adopted as a working group document.
> >
> > There are no IPR disclosures against this document.
> >
> > All the authors and the contributor have stated on the MPLS wg mailing
> > list that they are unaware of any IPRs that relates to this document.
> >
> > The working group adoption poll ends May 14, 2022.
> >
> > /Loa
> >
> 
> --
> Loa Andersson                        email: loa@pi.nu
> Senior MPLS Expert                          loa.pi.nu@gmail.com
> Bronze Dragon Consulting             phone: +46 739 81 21 64
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls