Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing

Gyan Mishra <hayabusagsm@gmail.com> Sat, 15 May 2021 07:09 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF8883A1B8D for <spring@ietfa.amsl.com>; Sat, 15 May 2021 00:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 428adkaSIIot for <spring@ietfa.amsl.com>; Sat, 15 May 2021 00:09:36 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFB263A1B8B for <spring@ietf.org>; Sat, 15 May 2021 00:09:36 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id m190so931291pga.2 for <spring@ietf.org>; Sat, 15 May 2021 00:09:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=e1vhCB2/CoCgk/F91Z73yKwFdO41frlNaFRrDaJiWxA=; b=Vo/aM/SyHPaZDQhqh8MusgOIKRFA1EN0F4tVe27vfBYL7vSUpjQgYusu0vrQNJ5boZ 5NY2rznRZftxv2+l+ad5MT2520so2PUIMu1TqUDDu4yY1Zf7IU5gIY2SWksBjcQYArv9 x+KeAS7ufgOzwxYtph9kAFoUC1Ex73IdU9bdy69V5Ig8226ZdCHvB6kUBxvghgs0JLyr xe6qgTzf+Lfdjn0p3DdCiyPlJeCRb3l9Hrt+V0NYAok/yc1GrYcnIjQQb6QD8UioMaNk MEwgxBRkwzlMZRMHMBjOjQVZoMu8pWUc6cMI4adLbASEqTWHHkGCKPNWkJfAXADCu0cE DZIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e1vhCB2/CoCgk/F91Z73yKwFdO41frlNaFRrDaJiWxA=; b=GURLju6CtsV+iEByouKOmzR+T6VhEABrtg4oGt4lhbJtAiut5B9q3TKat2yRCjbh4g bLYjCCzoku7d6gCYP7RNnVIAhmJsiRVP3QIQdiaSak2qFdjmb6/fDJ3qWj5JxxQOnDRw 18fz7ORcw0Cq8mtEyVvbhbYMmYAwFLwavl0jwt+Clk66slCHqwvWupswbaiVR0lG753P nDTbcwvZ0w4Ao8fIWuUZRRay1Bbrhz7/rzNHM8sdUQoJ62JxaezF5ysCDCegnldCnTSe VWxo+oMSnE4w+0d+Ox52ipy+HCUrNTy5qlNKJsgP9tRQorK3r0ECxg6CNp3+cL+S8X95 Jumw==
X-Gm-Message-State: AOAM530faifPFYzGHjZYfkrcegsLOnlMZA19+fNpjX9mntqLAyqSjXO4 +ZdFSJr1WpXQ2V7Ol6zgCYEW0kxEOh6vKWf/2VU=
X-Google-Smtp-Source: ABdhPJy8TFuahYDbR+C7taJfx48QjagD9r+f4rAHCFIO7BZAcUKRPtOiyaBIEn/XK1eJ0608S9wnK+tECa29pJ4pLEk=
X-Received: by 2002:aa7:8750:0:b029:28e:d3b9:cdec with SMTP id g16-20020aa787500000b029028ed3b9cdecmr50319790pfo.20.1621062575518; Sat, 15 May 2021 00:09:35 -0700 (PDT)
MIME-Version: 1.0
References: <61a99ced69074e269918557dd05d89ee@huawei.com> <0D0FAEF3-44BB-46B7-83ED-982C3ED65BB9@chinatelecom.cn> <821fe091a4da47ff8c94bc34829283fc@huawei.com>
In-Reply-To: <821fe091a4da47ff8c94bc34829283fc@huawei.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 15 May 2021 03:09:24 -0400
Message-ID: <CABNhwV2yr77=JPUMwUwETUqvLAVFy21rtsTxDzJ92nmPspNcqA@mail.gmail.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: "spring@ietf.org" <spring@ietf.org>, "xiechf@chinatelecom.cn" <xiechf@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="000000000000f8fc3c05c2590a60"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/zmHCs7rs15N5N9KQjRtaLwa-W7M>
Subject: Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 May 2021 07:09:42 -0000

Hi Jimmy

I read the draft and support  the principles defined in instantiation of
E2E network slice and method of mapping a VPN+ overlay to VTN underlay
underpinning & resources provisioning via resource sid VTN ID across
multiple domains E2E using a list of VTN BSIDs for per domain hop path
steering.

This draft will be very useful for 5G E2E multi domain network slicing VTN
provisioning and E2E concatenation of SR-TE BSID per domain hop BSID list
E2E path instantiation.

Kind Regards

Gyan


On Fri, May 14, 2021 at 10:45 AM Dongjie (Jimmy) <jie.dong@huawei.com>
wrote:

> Hi Chongfeng,
>
>
>
> Thanks for your valuable comments. The term “IETF network slice” was
> chosen by the network slicing design team in TEAS WG, after many discussion
> in both the design team and the WG.  This document tries to align with the
> terminology there.
>
>
>
> I also agree that the terms in different SDOs needs to be aligned, or the
> relationship and mapping between different terms could be defined.
>
>
>
> Best regards,
>
> Jie
>
>
>
> *From:* xiechf@chinatelecom.cn [mailto:xiechf@chinatelecom.cn
> <xiechf@chinatelecom.cn>]
> *Sent:* Friday, May 14, 2021 5:18 PM
> *To:* Dongjie (Jimmy) <jie.dong@huawei.com>
> *Cc:* spring@ietf.org
> *Subject:* Re: [spring] A new draft on Segment Routing for End-to-End
> IETF network slicing
>
>
>
> Hi,Jie,
>
> I think this work is useful and support its progress in spring or other
> WGs. However, I have some concerns about the term of "IETF slicing”, from
> the perspective of operator, the terms of “IETF slicing” and “3GPP slicing”
> may be confusing, there should be a universal set of terms of slicing
> across different SDOs, even they may cover different sections or layers of
> the network system.  What’s your opinion?
>
>
>
> Best regards
>
> Chongfeng
>
>
>
> 2021年5月14日 下午4:10,Dongjie (Jimmy) <jie.dong@huawei.com> 写道:
>
>
>
> Hi WG,
>
>
>
> Recently we published a new draft on Segment Routing for End-to-End IETF
> Network Slicing:
>
>
>
>
> https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-network-slicing
>
>
>
> It introduces the new SRv6 behaviors and SR-MPLS BSIDs to enable the
> mapping and concatenation of multi-domain IETF network slices. This
> document is aligned with the framework for end-to-end IETF network slicing
> as described in draft-li-teas-e2e-ietf-network-slicing.
>
>
>
> Your review and comments are welcome.
>
>
>
> Best regards,
>
> Jie
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*