Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

Peter Psenak <ppsenak@cisco.com> Sat, 03 October 2020 09:47 UTC

Return-Path: <ppsenak@cisco.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 CC5523A0977 for <lsr@ietfa.amsl.com>; Sat, 3 Oct 2020 02:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.813
X-Spam-Level:
X-Spam-Status: No, score=-9.813 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.213, RCVD_IN_DNSWL_BLOCKED=0.001, 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 xyRk1aTa5Q9m for <lsr@ietfa.amsl.com>; Sat, 3 Oct 2020 02:47:52 -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 82E0D3A0976 for <lsr@ietf.org>; Sat, 3 Oct 2020 02:47:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3098; q=dns/txt; s=iport; t=1601718471; x=1602928071; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=xysBOEb0ey7HDG2Vieibi9w4sSCcsVEB9gzB3Y/f68Y=; b=GnjOqqFTjHjQWArwfYasq4KNsPUcqCtTcG10IHrw14EOF1ky5MirFavb P1GNzssXW5UZ0GW+FLwLtarT7Zhs4G2lArGME1MKkGW7oV4AWV34AJ1qB 8JlSngkhnbKhaUdmWzCtZ3hcrMe/b0+Qqpf5eTmSBIfJNwr8QLJbaRb9z k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BbAAD6R3hf/xbLJq1gGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBQIFPgxpVASASLIQ9iQKICS6cJAsBAQEPLwQBAYRKAoI3JjgTAgMBAQsBAQUBAQECAQYEbYVohXIBAQEBAgEjFTYJAhALGAICJgICVwYBDAYCAQGDIgGCXCCmRHaBMoVUgz+BPAaBDiqJH4QtgUE/gTiCaT6CXASEdIJgBJAfCYJViH6bU4JxgxOXQgUHAx+DDooChRKOe5MToDyBayMNgUozGggbFTuCaVAZDZxoPwMwAjUCBgoBAQMJjkgBAQ
X-IronPort-AV: E=Sophos;i="5.77,331,1596499200"; d="scan'208";a="30086407"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Oct 2020 09:47:47 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTP id 0939llKe021953; Sat, 3 Oct 2020 09:47:47 GMT
To: Yingzhen Qu <yingzhen.qu@futurewei.com>, Gyan Mishra <hayabusagsm@gmail.com>, Ron Bonica <rbonica@juniper.net>
Cc: "lsr@ietf.org" <lsr@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>
References: <160138654056.12980.329207214151594381@ietfa.amsl.com> <DM6PR05MB63482DBC001DD56BEF6F7311AE320@DM6PR05MB6348.namprd05.prod.outlook.com> <CAKz0y8w5VOf_=baG6UCP8Q9s=VLM2ghT2jhiF5FZNN4JXB23eA@mail.gmail.com> <DM6PR05MB63485389C261CA2E0C08DE50AE330@DM6PR05MB6348.namprd05.prod.outlook.com> <0f85212d-fac7-47ea-a608-4f53061cbf02@Spark> <DM6PR05MB63480E863599BBC810BF334AAE300@DM6PR05MB6348.namprd05.prod.outlook.com> <CABNhwV2+jhjAfxq5FzaukdhCOqXvGCkv75xYWcStN=SCrpni4Q@mail.gmail.com> <f4fdff8b-fe11-cb75-3cd7-7766baedf730@cisco.com> <CB2F6A55-B231-4A2D-821C-D3F2ABE6649E@futurewei.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <00158dee-bb0d-6f5e-f740-b7bac61a1c74@cisco.com>
Date: Sat, 03 Oct 2020 11:47:46 +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: <CB2F6A55-B231-4A2D-821C-D3F2ABE6649E@futurewei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.60.140.51, ams-ppsenak-nitro2.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/RDSG4ifHuvfnLWEK462nT1vcVk0>
Subject: Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt
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, 03 Oct 2020 09:47:54 -0000

Hi Yingzhen,

On 02/10/2020 22:15, Yingzhen Qu wrote:
> Hi Peter,
> 
> My understanding of flex-algo is that for traffic destined to a prefix on a particular algo, it can only be routed on routers belong to that algo, which also means only routers in that algo calculates how to reach that prefix and install it into the routing table. It seems to me that using flex-algo (section 12 of the draft) it's possible to have a loopback address associated with only one algo, please correct me if I'm missing or misunderstood something.

you are right. That is exactly what is being done for flex-algo with 
SRv6 - locator is associated with a single algo only. The proposal uses 
the same concept.

thanks,
Peter

> 
> Thanks,
> Yingzhen
> 
> On 10/2/20, 9:43 AM, "Lsr on behalf of Peter Psenak" <lsr-bounces@ietf.org on behalf of ppsenak=40cisco.com@dmarc.ietf.org> wrote:
> 
>      Gyan,
> 
>      On 02/10/2020 18:30, Gyan Mishra wrote:
>      > All,
>      >
>      > With SRv6 and IP based flex algo a generic question as it applies to
>      > both. Is it possible to have within a single IGP domain different sets
>      > of nodes or segments of the network running different algorithms.
> 
>      absolutely.
> 
>      > From
>      > both drafts it sounds like all nodes have to agree on same algorithm
>      > similar to concept of metric and reference bandwidth all have to have
>      > the same style metric and play to the same sheet of music.
> 
>      all participating nodes need to agree on the definition of the flex-algo
>      and advertise the participation. That's it.
> 
>      > If there was
>      > a way to use multiple algorithms simultaneously based on SFC or services
>      > and instantiation of specific algorithm based on service to be
>      > rendered.  Doing so without causing a routing loop or sub optimal
>      > routing.
> 
>      you can certainly use multiple algorithms simultaneously and use algo
>      specific paths to forward specific traffic over it. How that is done
>      from the forwarding perspective depends in which forwarding plane you
>      use. Flex-algo control plane is independent of the forwarding plane.
> 
> 
>      >I thought with flex algo that there exists a feature that on
>      > each hop there is a way to specify which algo to use hop by hop similar
>      > to a hop by hop policy based routing.
> 
>      no, there is no hop-by-hop classification, that is problematic and does
>      not scale for high speeds. Classification is done at the ingress only.
> 
>      thanks,
>      Peter
> 
>      >
> 
>      _______________________________________________
>      Lsr mailing list
>      Lsr@ietf.org
>      https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr&amp;data=02%7C01%7Cyingzhen.qu%40futurewei.com%7C51dd940ab25d4ea19b1b08d866f23b6a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637372537869296887&amp;sdata=R%2FI%2BAUkcw12FmgDtsh%2FBOL7zLjPF%2BwwRpqwnE2Ndv%2Fg%3D&amp;reserved=0
> 
> 
>