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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Tue, 31 March 2020 09:15 UTC

Return-Path: <ketant@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 86B793A1E71 for <spring@ietfa.amsl.com>; Tue, 31 Mar 2020 02:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.7
X-Spam-Level:
X-Spam-Status: No, score=-7.7 tagged_above=-999 required=5 tests=[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 header.b=PyafMkuq; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=GY7WnHT3
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 PSobGzgurZCU for <spring@ietfa.amsl.com>; Tue, 31 Mar 2020 02:15:55 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C797C3A1E6F for <spring@ietf.org>; Tue, 31 Mar 2020 02:15:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5592; q=dns/txt; s=iport; t=1585646155; x=1586855755; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=C7Ms9Z+QGjXSGb/50Ogq+OpsWce+UYCUStBOIGq0Gh8=; b=PyafMkuqz5FwViswHAtUkaXc1vU/HIDzWQpR6bqvawQbtpkWYh4abypW FsY14QprdPwHe1WdB5sSau55AfId52L5aAl9wBsMO/KJzq2O3m0M0Jiba ANofTtMN/uirr1IoNyGI62QPrk9AeOe5QR24d+IhvxIbkMvy22U4rrRF9 Y=;
IronPort-PHdr: 9a23:mXAMJhZviQp5njW0Fm1CKXn/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20Q6bRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavpYjAzGthqX15+9Hb9Ok9QS47z
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AqCQA+CYNe/5hdJa1jAxwBAQEBAQcBAREBBAQBAYF7gVRQBWxYIAQLKgqEEINFA4ppToIRiWyOMYFCgRADVAoBAQEMAQEYDQgCBAEBg39FAheCHCQ4EwIDAQELAQEFAQEBAgEFBG2FVgyFcAEBAQECAQEBEBERDAEBLAwLAgICAQgRAQMBAQECAh8EAwICAhkGBgsUAQIGCAIEARIIEweDBYJLAw4gAQ6iLQKBOYhidYEyFIJrAQEFgTMCg10NC4IMAwYFgQkqjDEagUE/gRABR4IfLj6CHkkBAQIBgS0BEgEjBRAKBRQNgksygiyQfp8uRQqCPYdhhhSEZIRbgkyIMZBxhFGKSokYgjiQNQIEAgQFAg4BAQWBaSJncXAVO4JsUBgNjh0MBRIVgzuFFIVBdAIwd4xUAYEPAQE
X-IronPort-AV: E=Sophos;i="5.72,327,1580774400"; d="scan'208";a="746681858"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Mar 2020 09:15:54 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 02V9FsBt015637 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 31 Mar 2020 09:15:54 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 31 Mar 2020 04:15:54 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 31 Mar 2020 05:15:53 -0400
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 31 Mar 2020 05:15:53 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=G/TUxbXGx9vvy1y3vP9lpQu/f5iStIyKUrSbVxOgcdij4Kl/yRpnrs31SVXrh3/uSRm0P493hFLAMhFnefzqiIFztzmobTbu7Evh3YTZuexAvT8HVhoLkFpCoBXCf5a2EsP1dxS2gfw5ne/3gRAquGfuFXfAHkfiq8UPc5+eVcaQSyLGB7kr7tGwZ7VesFZdgmMEW6Y5I8EWUs6+/gv3Oz6X4q0II7Gs1t5WrEH+vjTAKhTSHEyqBwopw3b+mgZ+K/pfCewTwKLnEvcWlzAkKz1TpJONDqyyb66NTvi1ulgwpkPSobepwSsZbfHtxrgdXnb+7U+Hdknav1CUe7+yFg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=C7Ms9Z+QGjXSGb/50Ogq+OpsWce+UYCUStBOIGq0Gh8=; b=SV7vH9sWWv0ic54v1u6P2f0BhDWxhM9QXNmCMXxkxOdnEgKWnDhKCFiyRuVqalTDNUoJswG16COAoQRiBXYXRPpUSN4/q5tdQ10d3pUTYDEa9j96+DweW5dvurKUDvQiz51rLRfomQtuzMcjPc33VqLFEka9SgxHw68c7TEeGlyLBj/vNYBg90xVDXGoa+DSHiZ0nNAX/uAtOXgpj2T+xbKbniFgJyBomBlq0UcWkYpA7EcI8NPVbu4u21WC1RXpahVinsGe6oxE/oMPi3V2Yb5Of9XyG4Pw8d99f/QRcaUR0aftyjmDMSYxyBBHrcWMr00gW+Ie9mV9cxYpOUAjLg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=C7Ms9Z+QGjXSGb/50Ogq+OpsWce+UYCUStBOIGq0Gh8=; b=GY7WnHT3AhoV7aFPCikHfGWvHb8e65IegF91cZtxjBBikcKOJwxZRuuNa613sR9MwCsgOenOfenHjIWfq2VAkfRmOtMVb6hbWLZpCVZBPKSHizZbnpVZi/ngY4PorrjjoFTfO4EwXSKCRroi/0oPqJbRfEdnxujVmQ1ntBqTGyQ=
Received: from MW3PR11MB4570.namprd11.prod.outlook.com (2603:10b6:303:5f::22) by MW3PR11MB4586.namprd11.prod.outlook.com (2603:10b6:303:5e::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.20; Tue, 31 Mar 2020 09:15:52 +0000
Received: from MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::dc3d:f0de:21ec:cf87]) by MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::dc3d:f0de:21ec:cf87%7]) with mapi id 15.20.2856.019; Tue, 31 Mar 2020 09:15:52 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>, Gyan Mishra <hayabusagsm@gmail.com>, SPRING WG <spring@ietf.org>
Thread-Topic: [spring] SRV6 - SR-TE support & Flex Alg support ? and comparison and contrast of those two steering strategies
Thread-Index: AQHWBt1stcERmTb2x0+BKERyaB1nUKhiWlYAgAARUwA=
Date: Tue, 31 Mar 2020 09:15:51 +0000
Message-ID: <MW3PR11MB4570FFE64C1AD31B6ECEEF73C1C80@MW3PR11MB4570.namprd11.prod.outlook.com>
References: <CABNhwV2RVoRqd9HPRSHMarFvmL6cJayq-igbLOSpHtcUDWkXPw@mail.gmail.com> <a1433334-cf0b-dca7-fb3a-c08dd9a33f20@cisco.com>
In-Reply-To: <a1433334-cf0b-dca7-fb3a-c08dd9a33f20@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ketant@cisco.com;
x-originating-ip: [72.163.220.7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e18c9098-d16f-44bb-71e5-08d7d5541c17
x-ms-traffictypediagnostic: MW3PR11MB4586:
x-microsoft-antispam-prvs: <MW3PR11MB4586836F36747ABB4AD9DB9AC1C80@MW3PR11MB4586.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3173;
x-forefront-prvs: 0359162B6D
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW3PR11MB4570.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(366004)(136003)(376002)(346002)(396003)(39860400002)(26005)(52536014)(7696005)(86362001)(53546011)(186003)(5660300002)(6506007)(71200400001)(66946007)(478600001)(2906002)(64756008)(66476007)(66446008)(966005)(8936002)(8676002)(81156014)(316002)(66556008)(110136005)(76116006)(9686003)(33656002)(81166006)(55016002); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: ckz4N+mvoujKkW5WUawKkej3CYCOySGBkuqubSjn3PUhqlfQzTEgp9RGmICoddOauuo2BhJGgp4BKrhbiO+EsJuDWDjYtRgj1fGc9DCw4cuhHBXpKbvKWfJs9btb74KldMaBBKCD5gLGsD4KQ+Jyh2U+lgL+Mb+hvPv2qMLdT/orUSdDr/rYQ1jG/1a3uFC0ttWVB/TGI+uOsF8AE0SzvLuJS53lW73gJe/3rx76s343e+caL1cRXcoCIkiktn4aAh3Lqs3DtPcrExTeikFXSw82CekOSKFO+m+6YoX4gEZhyGPA+VjauevVM1rYkfZDHs5dtBddwOAR0hsnh7Bv5zzYF9cYMZVlsBYnoQZ7G7s2fMUb2cgM1d/IJMOglmyfGx1AOHiAk/2BWkanAmWsOJV3m+uEsHSzDIGuuWN4kSAWYaG5cppXNm+2U3D8jeKdgpsUtIwQU11hlC0xmeU/quLLerwJYLIlq40TybKdhU0mjehvZZMD1YzAiFB39neEg+zpNN1N67wu+E0SDn02TQ==
x-ms-exchange-antispam-messagedata: nFf7Q4BbvCJ7TR8+sIkmt3VYDr3A86B3Kk6sQt5kpno56zMErNpAjK38oIRiShVO3aVd0Jn7ypYEqs+hAY0NVi5O5IOdNSQdmJ2qz4dlpU8yB1cVDmsEcD5/b4dzgrvaW+04h+AQScrXikDoDE/ALQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e18c9098-d16f-44bb-71e5-08d7d5541c17
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Mar 2020 09:15:51.9142 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: pZASvMyPxdDEfUYJNZrWLflOVSdWUKui02slwa8AXWW6itYs0eCANChzVjlci5/BG+vH0t5By264Uhh+um587Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW3PR11MB4586
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/9rymt6cD00sFVw1UpbWEGs9kp2g>
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 09:15:58 -0000

Hi Gyan,

To add to what Peter has clarified, SR Policy architecture also supports SRv6 (as you've pointed out in the references) - loose and strict paths as well as steering for colored BGP routes.

Thanks,
Ketan

-----Original Message-----
From: spring <spring-bounces@ietf.org> On Behalf Of Peter Psenak
Sent: 31 March 2020 13:42
To: Gyan Mishra <hayabusagsm@gmail.com>; SPRING WG <spring@ietf.org>
Subject: Re: [spring] SRV6 - SR-TE support & Flex Alg support ? and comparison and contrast of those two steering strategies

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-0
> 6
> 
> 
>     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>
> 
> 
> 

_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring