Re: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03

Gyan Mishra <hayabusagsm@gmail.com> Sat, 27 March 2021 03:46 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3CB13A1C5B for <lsr@ietfa.amsl.com>; Fri, 26 Mar 2021 20:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 8YlvWHYCQ7pz for <lsr@ietfa.amsl.com>; Fri, 26 Mar 2021 20:46:45 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 AABA53A1C58 for <lsr@ietf.org>; Fri, 26 Mar 2021 20:46:45 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id d8so1842252plh.11 for <lsr@ietf.org>; Fri, 26 Mar 2021 20:46:45 -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=hwVU+1famlYAxOmxk+6LUkAHl+MyrUiNsF6hPFpeoqs=; b=qgnuBBTcDtIepj9EyHcRDRiAtfVsHu6SmztsnDr7IQUwa3gFV4Y9WJAukrLuywLchu mUvCYQ9yJO4LHzRwa+ruklcRlSgnS+wSmqnTSGuqNJvzmwjdxeADvAyO3qvLC4dsOyjY mKcGHCeSWrsA8YQANLsqkukNAplEj5DHMdTuemCDIqdRKF52l0Ob+k5rSYoErv+r8wNc Ercj1/A41o/DPDXkMhMTiG2wNrIQ5XjdQ4wmIwwqjVRokdFO1ajzj9aDT10Wm4teokAb QJR7zVQNntGIGc11VoSyw9AuimCqW7YVkmMQLGHaZEiL47kCGrHVBl52aoumJszREddk HBNw==
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=hwVU+1famlYAxOmxk+6LUkAHl+MyrUiNsF6hPFpeoqs=; b=JQWgMn6ZWGpqcUHhy/nhrQ4kHoTjH6nJFe31c/8tE4T+5xF/SBH3EgUFjpbD25NICS XSn6E59bUh6Eqa/DDQLWWyfuPsOfDOayfGIgocrwQT/JykU8r/AbxvwcJlWHRdTNlEyQ PJBYPbkesYhFuVUUUYupR2HjeQfEvCZjUlXZ6XckfzxCPALnJ5DzVErQI+vdCCvs2tCi w9TcI47rkwTHLbFa1X/rBOozg7jqmDBPqzI+fvXUgPU8tk751nwW0ySBlk0Vmq3VitGX dS22WltAHB8/821FKRbBJT+aTRVZt7kK+1IgJBWRA8Z5vIFJDHXLEXyF8e1sC9qpapV0 Cwmw==
X-Gm-Message-State: AOAM532CEaIVM+aTtAhorynQMWPavz6qX3ZFfHWP43mFZDE3t5HobnJt 4YbNPDW0HfUKXANiZ6GrorEpZVL1UzY34df8kxQyvXQrJ/HO3g==
X-Google-Smtp-Source: ABdhPJypBzHv2mIulvd2iXtCCsNHGZ/mzi7kpDBWkqZ/YX//LT53NBjDC2GWnDa3aYFGgjS9z4oOD5H8b9b4LFZn/l8=
X-Received: by 2002:a17:902:fe09:b029:e4:951e:2d2e with SMTP id g9-20020a170902fe09b02900e4951e2d2emr18816494plj.22.1616816804347; Fri, 26 Mar 2021 20:46:44 -0700 (PDT)
MIME-Version: 1.0
References: <04A60BCD-4D9C-4210-A213-4D3876595114@cisco.com>
In-Reply-To: <04A60BCD-4D9C-4210-A213-4D3876595114@cisco.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 26 Mar 2021 23:46:33 -0400
Message-ID: <CABNhwV0s95JVw9Ye_Ko1A3zXvUVF2SmoRaQpF0NB6r4R7rFOuQ@mail.gmail.com>
To: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Cc: "lsr@ietf.org" <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004a443305be7c7f16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/e16yjDkFtbG1203fNNrHXWBdS7g>
Subject: Re: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Mar 2021 03:46:51 -0000

Hi Acee

As an operator, I  support adoption of the draft and would like to provide
answers to your questions.

I would like to start by stating that as this is an informational document,
 as nothing new is proposed other then the recommendation to use MT for VTN
provisioning as a component of the 5G network slicing solutions, the
benefit is that this concept can be used immediately as other NS features
are still being developed.

The solution for network slicing resource isolation is multi faceted
involves Enhanced VPN+ provisioning, resource SIDs for provisioning
underlay resources, SR-TE Per VPN or flow path steering to meet NS SLO
requirements, as well as a method to isolate IGP resources for a VTN.

MT is a component of the entire NS solution so there is really nothing to
market as it’s not the only component used to provision the VTN.

As their is a need for providing a viable means of provisioning IGP
underlay resources VTN network slice and the ability to provide forwarding
plane isolation via topological RIB without consuming tremendous control
plane resources per instance as with MI.

This draft does fill the gap of a means of forwarding plane isolation on
shared infrastructure even though it does have scalability considerations.

As other ideas of IGP forwarding plane isolation come about we are open to
other solutions as well.

As their are scalability concerns in section 5 that should be expanded,
when MT should be used to support VTN and when should not. Agreed.

I would deploy in a limited fashion taking into account the scalability
concerns.

Enhanced VPN  VPN+ scalability issue are described in detail in this draft
below.  Lots of variables related to how many slices based on services
which will eventually scale up but I think MT may suffice well in the
beginning stages.

https://tools.ietf.org/html/draft-dong-teas-enhanced-vpn-vtn-scalability-01


There are many drafts and solutions in the works across many different WGs
that are working on development of solution as to how network slicing and
SLO can be realized  by operators for 5G services.

Of these drafts below there are a number of Enhanced VPN Framework VPN+
 related drafts that are critical to the provisioning of various components
of network slicing.

https://datatracker.ietf.org/doc/html/draft-ietf-teas-enhanced-vpn-07

https://datatracker.ietf.org/doc/draft-dong-teas-enhanced-vpn-vtn-scalability/

https://tools.ietf.org/html/draft-drake-bess-enhanced-vpn-06

https://tools.ietf.org/html/draft-ietf-spring-resource-aware-segments-02

Kind Regards

Gyan

On Thu, Mar 25, 2021 at 2:21 PM Acee Lindem (acee) <acee=
40cisco.com@dmarc.ietf.org> wrote:

> Speaking as WG chair:
>
>
>
> There has been considerable support for this document. However, there has
> also been objections to the document. The objections are either that there
> is nothing to standardize given that all pieces exist and that the MT isn’t
> a viable option for VTNs since it isn’t scalable.
>
>
>
> Since most of the draft’s support is from “friends and family”, I’d like
> to know of the WG members who supported it, would you really want to market
> it as a VTN solution? Those of you who operate networks, would you actually
> consider deploying it?
>
>
>
> In any case, section 5 needs to be expanded on the scalability and where
> using MTs to support VTNs would make sense and where it wouldn’t.
>
>
>
> Thanks,
> Acee
>
>
>
>
>
> *From: *Lsr <lsr-bounces@ietf.org> on behalf of "Acee Lindem (acee)"
> <acee=40cisco.com@dmarc.ietf.org>
>
>
> *Date: *Tuesday, March 2, 2021 at 6:28 PM
> *To: *"lsr@ietf.org" <lsr@ietf.org>
> *Subject: *[Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT)
> for Segment Routing based Virtual Transport Network” -
> draft-xie-lsr-isis-sr-vtn-mt-03
>
>
>
> This information draft describes how MT could be used for VTN
> segmentation. The authors have asked for WG adoption.
>
>
>
> This begins a three week LSR Working Group Adoption Poll for “Using IS-IS
> Multi-Topology (MT) for Segment Routing based Virtual Transport Network” -
> draft-xie-lsr-isis-sr-vtn-mt-03. I’m giving it three weeks due to the IETF
> next week. Please register your support or objection on this list prior to
> the end of the adoption poll on 3/24/2020.
>
>
>
> Thanks,
>
> Acee
>
>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
-- 

<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*