Re: [spring] SRV6 - SR-TE support & Flex Alg support ? and comparison and contrast of those two steering strategies

Peter Psenak <ppsenak@cisco.com> Tue, 31 March 2020 08:11 UTC

Return-Path: <ppsenak@cisco.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 240163A1DC5 for <spring@ietfa.amsl.com>; Tue, 31 Mar 2020 01:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.701
X-Spam-Level:
X-Spam-Status: No, score=-7.701 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 muffU6xAbh2p for <spring@ietfa.amsl.com>; Tue, 31 Mar 2020 01:11:55 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19F853A1DC7 for <spring@ietf.org>; Tue, 31 Mar 2020 01:11:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3413; q=dns/txt; s=iport; t=1585642315; x=1586851915; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=8XPfs+1cyL4UDQjzq+e9Ix1zDJDbpQpwfFa5Ro0fZiQ=; b=FLNFnLMez3775/pwlHeowhGrgLHqLeXp+QeFmGD3ZHdlRd98V0qFkUJa 68Fxk0BQqyLvjeqRFziOgWrc9xqMJEjnCC4Ga8yyAWVrbPeV2AmWo42vk OtkU94yTLSssRFBixZSmc5QD7w5Q5zEW8Rk8kkHz1A1ym8dS75r/r3uUi 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C1BACH+oJe/xbLJq1jAx0BAQEJAREFBQGBe4MVVAEgEiqEGokCiBCZX4FnCgEBAQ4lCgQBAYREAoJXOBMCAwEBCwEBBQEBAQIBBQRthVYMhXABAQEBAgEjDwEFTwILDgoCAh8EAwICGysRBgEMBgIBAReDCwGCSwMOIA+sSHWBMhSEJQKBEIM8gTgGBYEJKoxLgUE/gRABJ4I/Lj6CHkkBAQIBgS0BEgFCJoJLgl4EsG2CR4JWhQuGFIkcBh2CTIgxhDKMP4RRikqJGJMVgWkiZ3EzGggbFTuCbFAYDY4pBRIViE+FQz8DMAIwjlsBAQ
X-IronPort-AV: E=Sophos;i="5.72,327,1580774400"; d="scan'208";a="24917154"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Mar 2020 08:11:52 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id 02V8Bqlv028667; Tue, 31 Mar 2020 08:11:52 GMT
To: Gyan Mishra <hayabusagsm@gmail.com>, SPRING WG <spring@ietf.org>
References: <CABNhwV2RVoRqd9HPRSHMarFvmL6cJayq-igbLOSpHtcUDWkXPw@mail.gmail.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <a1433334-cf0b-dca7-fb3a-c08dd9a33f20@cisco.com>
Date: Tue, 31 Mar 2020 10:11:52 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CABNhwV2RVoRqd9HPRSHMarFvmL6cJayq-igbLOSpHtcUDWkXPw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.60.140.51, ams-ppsenak-nitro2.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/quBJ30pRNjRy75OmmiGP8c3O1_w>
Subject: Re: [spring] SRV6 - SR-TE support & Flex Alg support ? and comparison and contrast of those two steering strategies
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: Tue, 31 Mar 2020 08:12:02 -0000

Hi Gyan,

let me comment on the flex-algo aspect. Please see inline:

On 30/03/2020 23:50, Gyan Mishra wrote:
> 
> Does SRv6 support SR-TE and flex Alg?

yes, it does support both.

> 
> 
> Since SRv6 supports native traffic steering with SRH with end prefix sid 
> and end.x adjacency sid you can achieve the basic steering and ECMP 
> capability with prefix sid lose or strict hop by hop with every node 
> specified in SRH SL.
> 
> I want to confirm that SRv6 fully supports all of the  SR-TE 
> capabilities available with SR-MPLS with static lose or strict paths and 
> coloring of vpn flows.
> 
>  From the SR policy draft I did see that section 4 lists segment types 
> and does appear to support SRv6 sid.
> 
> https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-06
> 
> 
>     4
>     <https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-06#section-4>.
>     Segment Types
> 
> 
> 
>     A Segment-List is an ordered set of segments represented as <S1, S2,
>     ... Sn> where S1 is the first segment.
> 
>     Based on the desired dataplane, either the MPLS label stack or the
>     SRv6 SRH is built from the Segment-List.  However, the Segment-List
>     itself can be specified using different segment-descriptor types and
>     the following are currently defined:
> 
> 
> Flex Alg - SRv6 support?

yes.

> 
> Flex Alg is orthogonal to SR TE as it provides IGP extensions for 
> constrained SPF versus traditional RSVP or SR-TE providing the 
> extensions for cSPF - basically another method of steering which as well 
> is very powerful tool for operators.
> 
> It does appear SRv6 supports flex Alg draft below.

yes.

> 
> https://tools.ietf.org/html/draft-ietf-lsr-flex-algo-06
> 
> Abstract
> 
> IGP protocols traditionally compute best paths over the network based
>     on the IGP metric assigned to the links.  Many network deployments
>     use RSVP-TE based or Segment Routing based Traffic Engineering to
>     enforce traffic over a path that is computed using different metrics
>     or constraints than the shortest IGP path.  This document proposes a
>     solution that allows IGPs themselves to compute constraint based
>     paths over the network.  This document also specifies a way of using
>     Segment Routing (SR) Prefix-SIDs and SRv6 locators to steer packets
>     along the constraint-based paths.
> 
> 
> 
> What are the benefits of using SR-TE over flex Alg and vice versa?

you can think of them as different tools in your SR-TE tool set. You 
pick them as you need them. They can be used independently in parallel 
or can even be combined together to give you even more flexibility.

The principal difference is that SR-TE provisions point-to-point path(s) 
between two end-points, while flex-algo provides any to any paths 
between set of participating nodes.

> 
> Also can SR-TE use flex Alg steered paths as the dynamic cSPF paths?

yes

> 
> Can SR-TE use and specify flex Alg to be used for traffic steering?

yes

thanks,
Peter

> 
> 
> Kind regards
> 
> 
> Gyan
> Verizon
> Cell 301 502-1347
> -- 
> 
> Gyan  Mishra
> 
> Network Engineering & Technology
> 
> Verizon
> 
> Silver Spring, MD 20904
> 
> Phone: 301 502-1347
> 
> Email: gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>
> 
> 
>