Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt
Ron Bonica <rbonica@juniper.net> Sun, 11 October 2020 16:42 UTC
Return-Path: <rbonica@juniper.net>
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 D983A3A095F for <lsr@ietfa.amsl.com>; Sun, 11 Oct 2020 09:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.297
X-Spam-Level:
X-Spam-Status: No, score=-3.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=juniper.net header.b=B4pSmQ8a; dkim=pass (1024-bit key) header.d=juniper.net header.b=GZ2cjpv0
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 BcVOTvFH6Q6K for <lsr@ietfa.amsl.com>; Sun, 11 Oct 2020 09:42:13 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF0EB3A0EC4 for <lsr@ietf.org>; Sun, 11 Oct 2020 09:42:12 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 09BGfoc9023470; Sun, 11 Oct 2020 09:41:50 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=c+QWdqCNa1spRiODO8F0fdZN2uarj19v+ndGC+jfCz0=; b=B4pSmQ8avurRU0QX/pyJNJxfWZUsr2QE31ANBjtenZEQif8YKB/sJJn3KQuJanuahpOM uEmEUUDVkw65Bd7ktCbSvSOm9ZsbAfvApauHYDTLsgwa9PSL2XdEBxl5VtqMNE6qgeSN ag0FO1PF0NubRwCJ93m1feTzcayo5Z3ea9NeSjxwDpCRTqvVTuRnhlG8A9ETMzPSxhVF hnfesa8FDtjWivLff9CqCVe7xI42ZXJgnLq8mGyo2PyHOxcTfb+HKqmYgN8rYc+bjBmt DJbtD/bgVGaTGbqTV9T21hxxYManCZJEMdQIyyYnu2a0yHT2tiaHhJOPChUw7rmfzFLI CQ==
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp2053.outbound.protection.outlook.com [104.47.38.53]) by mx0b-00273201.pphosted.com with ESMTP id 343b79h8ce-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 11 Oct 2020 09:41:49 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JQQkMZITGSq0TnKJZpFUsCn1ZFduL5+dNrFvWfLLlaeljxivY73G8wbq4WDovB8d2gtLv0UVNfGNih6ItKQpfqK2QIu03IXYfrBQy8X9tkVD33scVXKJABaw4PTC3Aro1HXemUqE7tR9CxpbB5G7NjN69qxGm1FoyhkAIWMQ///dozzK3/9YlQQRFR9no65ITO6y+93mP3kSgIOArmT2wj62GgJmXNz6WzGzkK8PZg9TjIB+vfTfBuBotulauy5iESexuo7Qg8nT9dQDBf62n4kgKIqRyzaGLfOqaVc1B++xn5HrpFKb5Aa7xpCOMPtD7jX0xV9WXHHaIfqDw46CzQ==
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=c+QWdqCNa1spRiODO8F0fdZN2uarj19v+ndGC+jfCz0=; b=bMqmkVh5gtYpvp/EONHJhzuj6hO4Sk2V1QNQY2RzZBHf6wPc5NpFyvEyurgUCDD/X2XBkUUIAFgwdJleMoF22746nZafEbvmWOn7J5e+HDYMp9Fc+r/+YWwRb6d6MfSv2s6BmfKCtZ1E+bIfyInYDrKS4SzBNlWql5TwwVnXj9uXu1FsucA6r1e+MOE/6Xo9ceK0SHo21buigB2C2cmx6RtP7MxJRING7ftZfBif2OJMAQrC/aA5DW5hlHdXnhxBGnE5c94qBj2AgZF6922ed9Tq2cy+YC2VNJgXX3Y409lbJW0obTO0Cot2G1U0tZLjQx4medUb5SfVqKTuWbvTTA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=c+QWdqCNa1spRiODO8F0fdZN2uarj19v+ndGC+jfCz0=; b=GZ2cjpv0fASHdZ5x1g53Zktr2h/fTFy6jYtKPysiuFlRKd0fjeLWRuC2+/LAlnr7uAKahW7/JoYlRsu9A3tQPXww0n9tMseVV6Vvt7SiyOVCYR+pOo1XXLNfA+650Ct+TnkjbvAuzB8ONdheayNMoxqVJOwYEbbUCFSAr/vYNU8=
Received: from DM6PR05MB6348.namprd05.prod.outlook.com (2603:10b6:5:122::15) by DM6PR05MB5769.namprd05.prod.outlook.com (2603:10b6:5:102::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.11; Sun, 11 Oct 2020 16:41:48 +0000
Received: from DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::79ec:53dd:43c6:2782]) by DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::79ec:53dd:43c6:2782%3]) with mapi id 15.20.3477.017; Sun, 11 Oct 2020 16:41:48 +0000
From: Ron Bonica <rbonica@juniper.net>
To: Jeff Tantsura <jefftant.ietf@gmail.com>
CC: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Peter Psenak <ppsenak@cisco.com>, Yingzhen Qu <yingzhen.qu@futurewei.com>, Gyan Mishra <hayabusagsm@gmail.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt
Thread-Index: AQHWlmVwC6ypd3I8xkyHSNG022ojU6l/nmSwgAGYiICAAB9mMIAA726AgADTSnCAAWzZgIAAAz2A///GWICAAVg7AIAAFmsAgACYCCCACE1YgIAA2YqAgAC6nQCAAJ/jwIAAbpcAgAFnkDA=
Date: Sun, 11 Oct 2020 16:41:47 +0000
Message-ID: <DM6PR05MB6348E37E907E973B77CC114DAE060@DM6PR05MB6348.namprd05.prod.outlook.com>
References: <DM6PR05MB6348BE62F0F0801D4468B296AE090@DM6PR05MB6348.namprd05.prod.outlook.com> <7FC87D5B-0DA9-434C-905C-E5DD4F4EE4D8@gmail.com>
In-Reply-To: <7FC87D5B-0DA9-434C-905C-E5DD4F4EE4D8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.5.0.60
dlp-reaction: no-action
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=true; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2020-10-11T16:41:46Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=0724538e-6f99-4375-b46d-3469e55e4656; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [173.79.115.7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: de50527d-ae74-412a-1b1b-08d86e048bfa
x-ms-traffictypediagnostic: DM6PR05MB5769:
x-microsoft-antispam-prvs: <DM6PR05MB5769FAB863534FCF53075FD2AE060@DM6PR05MB5769.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TtR9PTD6qRulL6XaoY0X7GRMbRb5lm7VsaiII0VYAc9Rr3VRyTIFvgYWSojoHvqQO5RWyA6XCu9lt7PHE7aY8cKG+e/dPVxyM8KY7GaZdtLX5Ky1UTZeMDNLQpqlT2i3jk0ujc+GfzITw7ebkQgt6BsWA12ff4NSkjLcp25gtf7RIzOcktKRV3pHQhNWdRW5Nn0veOnRwEeaQDLa8BZzCmecaV5Z1anXgRZYlMW9Xid1NIsk+JYDnPasKwvBl2wOy/J0ammVpavc8w+XZfRpnVdgsaLqb02xtm5gMDiHxzvjKDolL6dqibGpQgch21PDGVQqVuGhrzh8i5RKX+CjI1jQwvZ1zG0MY0OtIqbplvGKFxQXeCnun598Dl7KJkP2FD55Y7eS/8hYLMAmNNPvhg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR05MB6348.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(346002)(376002)(136003)(39860400002)(396003)(7696005)(4326008)(15650500001)(54906003)(52536014)(45080400002)(966005)(186003)(26005)(83080400001)(9686003)(6916009)(478600001)(8936002)(2906002)(316002)(71200400001)(53546011)(83380400001)(64756008)(66556008)(66446008)(5660300002)(86362001)(66946007)(76116006)(66476007)(33656002)(6506007)(8676002)(55016002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: E/Q8QvSPTlL+2hGN8lpouNa+d6CERcfTOUWxF6z/oUK1YZQEzwEJ9ltql9miLShTkmKs8d2FDpkCcakhDzbaJ5+guHa4AboR9ig7Yol4gR3c5k8LKgHiDSEZyZOpYWXea++3k7wmiUWrOaC6h4gH+CPEgB1BCcPxjVef0JN6+8BQUjnOMFvmZs7Cmc3mXSoBiej/AG0IK7GWQgj0o8tEjBwFaGrGUONEOAs2vU4UOVfTlyi3zIoH+EpE0DG+eDezVEkli9bOAOmt7vwRfnaVzYnATVkPRfnRi915rpIKYl4u69zX5g1GHGwE6ReqOe619MZo0aA/MANTQR6sk7Iw94lhaLE1PxrmIY0Q1d0PFvncKaCOEGBXVBKoAS+RuG38181ThBGwncKSTt7RRSy1YowfE8ZZ1r/pW81oCHQlnveyXdnxP/1qJPu3+l1N3453QApujKgTL3RotyPYF9uAcDjsFaCJZCI/ypIJm/9ozxa78RNjwFvqxERGjgzX+XBT66zL5SFqgP4ggvYonLir6SquxkfouqaozVEeNmobNLMKMDKkD84MfWRQioul5TyhlFNSnvOSPlWvLT5a8xC6NG+8ZL5++Li6ElARuMM3uS73HofoOByiKu2gJ5AsjTxdOtyQ3ashtiPdhCJSyHyyiw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR05MB6348.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: de50527d-ae74-412a-1b1b-08d86e048bfa
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Oct 2020 16:41:47.9074 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2XuXkIO3u9MPmcmwNBBSofJcj+3p3xig7EytKPQ7LLJU7ASrFB56wByPjYTpGB3K/qWSQ4obDB+Y03ZrDJJNsQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB5769
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-10-11_12:2020-10-09, 2020-10-11 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 impostorscore=0 mlxscore=0 phishscore=0 bulkscore=0 adultscore=0 lowpriorityscore=0 spamscore=0 clxscore=1015 mlxlogscore=999 priorityscore=1501 malwarescore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2010110157
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/m0ndCdKacTygn8203N36QMEzzgc>
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: Sun, 11 Oct 2020 16:42:15 -0000
Jeff, I think that you mean the scope is different..... Ron Juniper Business Use Only -----Original Message----- From: Jeff Tantsura <jefftant.ietf@gmail.com> Sent: Saturday, October 10, 2020 3:14 PM To: Ron Bonica <rbonica@juniper.net> Cc: Dongjie (Jimmy) <jie.dong@huawei.com>; Peter Psenak <ppsenak@cisco.com>; Yingzhen Qu <yingzhen.qu@futurewei.com>; Gyan Mishra <hayabusagsm@gmail.com>; lsr@ietf.org Subject: Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt [External Email. Be cautious of content] Jie, The scoop is different, for SR data plane entry uniqueness is in context of SR domain (SID = value + context), while for IP it is global to the routing domain, FIB entry is a destination, nothing more. Regards, Jeff > On Oct 10, 2020, at 05:47, Ron Bonica <rbonica@juniper.net> wrote: > > Hi Jimmie, > > Inline..... > > Ron > > > Juniper Business Use Only > > -----Original Message----- > From: Dongjie (Jimmy) <jie.dong@huawei.com> > Sent: Friday, October 9, 2020 11:06 PM > To: Peter Psenak <ppsenak@cisco.com>; Ron Bonica > <rbonica@juniper.net>; Yingzhen Qu <yingzhen.qu@futurewei.com>; Gyan > Mishra <hayabusagsm@gmail.com> > Cc: lsr@ietf.org; Jeff Tantsura <jefftant.ietf@gmail.com> > Subject: RE: [Lsr] FW: New Version Notification for > draft-bonica-lsr-ip-flexalgo-00.txt > > [External Email. Be cautious of content] > > > Hi Peter, > > Thanks for your reply. It aligns with my understanding of FAD, which is just a set of constraints for path computation. Thus one Flex-Algo ID could be used with multiple different data planes. Is this understanding correct? > > [RB] I never thought about this. Is there a use-case? I think that it will work, but I would have to try it before saying for sure. > > If so, my question is about the scenario below: > > A group of nodes in a network support FA-128, a sub-group of them bind FA-128 to SR SIDs, another sub-group of them bind FA-128 to IP address. When one node compute an SR path to a destination, can it compute the path to only pass the nodes which bind FA-128 to SR SIDs, and avoid the nodes which bind FA-128 to IP address? > > [RB] I don't think so. However, you could achieve the same outcome using link colors. > > If so, how could this node know the binding of FA to different data planes on other nodes? > > Best regards, > Jie > >> -----Original Message----- >> From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Peter Psenak >> Sent: Friday, October 9, 2020 11:58 PM >> To: Dongjie (Jimmy) <jie.dong@huawei.com>; Ron Bonica >> <rbonica=40juniper.net@dmarc.ietf.org>; Yingzhen Qu >> <yingzhen.qu@futurewei.com>; Gyan Mishra <hayabusagsm@gmail.com> >> Cc: lsr@ietf.org; Jeff Tantsura <jefftant.ietf@gmail.com> >> Subject: Re: [Lsr] FW: New Version Notification for >> draft-bonica-lsr-ip-flexalgo-00.txt >> >> Hi Jimmy, >> >> >>> On 09/10/2020 04:59, Dongjie (Jimmy) wrote: >>> Hi Ron, >>> >>> Thanks for explaining the difference between IP Flex-Algo and SR >>> Flex-algo. As >> you said, the major difference is the data plane. >>> >>> If my understanding is correct, for one Flex-Algo to be used >>> correctly, the set >> of nodes need to apply consistent constraints in computation, and >> bind the FAD to the same data plane. >>> >>> Is it possible that different nodes may use the same Flex-Algo with >>> different >> data plane, e.g. some with SR-MPLS, some with SRv6, and some with >> pure IP etc., or each Flex-Algo is always associated with only one >> data plane? In the former case, should the flex-algo definition also >> indicate the data plane(s) to be used with the flex-algo? >> >> let me respond to this query, as this is not specific to Ron's draft. >> >> FAD is data plane agnostic and is used by all of them. >> >> thanks, >> Peter >> >>> >>> Best regards, >>> Jie >>> >>>> -----Original Message----- >>>> From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Ron Bonica >>>> Sent: Sunday, October 4, 2020 4:34 AM >>>> To: Yingzhen Qu <yingzhen.qu@futurewei.com>; Peter Psenak >>>> <ppsenak@cisco.com>; Gyan Mishra <hayabusagsm@gmail.com> >>>> Cc: lsr@ietf.org; Jeff Tantsura <jefftant.ietf@gmail.com> >>>> Subject: Re: [Lsr] FW: New Version Notification for >>>> draft-bonica-lsr-ip-flexalgo-00.txt >>>> >>>> Hi Yingzhen, >>>> >>>> IP Flexible Algorithms are like SR Flexible Algorithms in the >>>> following >> respects: >>>> >>>> - Links have IGP metrics, TE metrics, delay metrics and >>>> administrative colors >>>> - FADs define Flexible Algorithms >>>> >>>> More specifically, the FAD: >>>> >>>> - Indicates which metric type the Flexible Algorithm uses >>>> - Specifies constraints in terms of link colors that are included >>>> or excluded from the Flexible Algorithm. >>>> >>>> The significant difference between IP Flexible Algorithms and SR >>>> Flexible Algorithms is: >>>> >>>> - SR Flexible Algorithms bind FADs to prefix SIDs or SRv6 locators >>>> - IP Flexible Algorithms bind FADs to IPv4 or IPv6 addresses. >>>> >>>> So, IP Flexible Algorithms can be deployed in any IP network, even >>>> in the absence of SR. >>>> >>>> Ron >>>> >>>> >>>> Juniper Business Use Only >>>> >>>> -----Original Message----- >>>> From: Yingzhen Qu <yingzhen.qu@futurewei.com> >>>> Sent: Saturday, October 3, 2020 2:08 PM >>>> To: Peter Psenak <ppsenak@cisco.com>; Gyan Mishra >>>> <hayabusagsm@gmail.com>; Ron Bonica <rbonica@juniper.net> >>>> Cc: lsr@ietf.org; Jeff Tantsura <jefftant.ietf@gmail.com> >>>> Subject: Re: [Lsr] FW: New Version Notification for >>>> draft-bonica-lsr-ip-flexalgo-00.txt >>>> >>>> [External Email. Be cautious of content] >>>> >>>> >>>> Hi Peter, >>>> >>>> Using flex-algo, a SRv6 locator can be associated with a single >>>> algo, which means an IPv6 or IPv4 address can also be associated >>>> with a single algo. So my understanding is Ron's proposal is making >>>> the >> configuration of flex-algo easier? >>>> Instead of using the exclude or include list you can configure a >>>> loopback address to a flex-algo directly? >>>> >>>> Thanks, >>>> Yingzhen >>>> >>>> On 10/3/20, 2:47 AM, "Peter Psenak" <ppsenak@cisco.com> wrote: >>>> >>>> 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://urldefense.com/v3/__https://nam11.safelinks.protection.outl >>>> oo >>>> k.com/ >>>> ?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Flsr&data >>>> = >> 0 >>>> 2 >>>> >> *7C01*7Cyingzhen.qu*40futurewei.com*7Cfe03124c6e414e067c2008d86781 >>>> >> 6541*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C63737315273986 >>>> >> 5126&sdata=WI48cEAan*2FOkDPmVXGurEAjPItNGF9p9PDQIlD1ip0g*3D >>>> >> &reserved=0__;JSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!X1fRln9MjimeJcR >>>> EUEIydr-8IIbtNonXMs83eoXvRww6xkaQfVUdNh0kK452GP-G$ >>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Lsr mailing list >>>> Lsr@ietf.org >>>> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/l >>>> sr__;!!NEt6yMaO-gk!TeHgIKM4lUZhkYnt_eFt3SshGJtln8PTqhCuZtODomUQWC_H >>>> z218CE8S8XzlIxAA$ >>> >>> >> >> _______________________________________________ >> Lsr mailing list >> Lsr@ietf.org >> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/lsr >> _ >> _;!!NEt6yMaO-gk!TeHgIKM4lUZhkYnt_eFt3SshGJtln8PTqhCuZtODomUQWC_Hz218C >> E >> 8S8XzlIxAA$
- [Lsr] FW: New Version Notification for draft-boni… Ron Bonica
- Re: [Lsr] New Version Notification for draft-boni… tony.li
- Re: [Lsr] New Version Notification for draft-boni… Jia Chen
- Re: [Lsr] New Version Notification for draft-boni… Huzhibo
- Re: [Lsr] New Version Notification for draft-boni… Joel M. Halpern
- Re: [Lsr] New Version Notification for draft-boni… Huzhibo
- Re: [Lsr] New Version Notification for draft-boni… Robert Raszuk
- Re: [Lsr] New Version Notification for draft-boni… Peter Psenak
- Re: [Lsr] New Version Notification for draft-boni… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Muthu Arul Mozhi Perumal
- Re: [Lsr] New Version Notification for draft-boni… Robert Raszuk
- Re: [Lsr] New Version Notification for draft-boni… Dongjie (Jimmy)
- Re: [Lsr] New Version Notification for draft-boni… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Ron Bonica
- Re: [Lsr] New Version Notification for draft-boni… Robert Raszuk
- Re: [Lsr] New Version Notification for draft-boni… Les Ginsberg (ginsberg)
- Re: [Lsr] FW: New Version Notification for draft-… Jeff Tantsura
- Re: [Lsr] New Version Notification for draft-boni… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] New Version Notification for draft-boni… Ron Bonica
- Re: [Lsr] New Version Notification for draft-boni… Ron Bonica
- Re: [Lsr] FW: New Version Notification for draft-… Acee Lindem (acee)
- Re: [Lsr] FW: New Version Notification for draft-… Ron Bonica
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Yingzhen Qu
- Re: [Lsr] FW: New Version Notification for draft-… Jeff Tantsura
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Robert Raszuk
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Yingzhen Qu
- Re: [Lsr] FW: New Version Notification for draft-… Ron Bonica
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- [Lsr] draft-zhu-lsr-isis-sr-vtn-flexalgo-01 Huaimo Chen
- Re: [Lsr] FW: New Version Notification for draft-… Dongjie (Jimmy)
- [Lsr] 回复: draft-zhu-lsr-isis-sr-vtn-flexalgo-01 zhuyq8
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Ron Bonica
- Re: [Lsr] FW: New Version Notification for draft-… Dongjie (Jimmy)
- Re: [Lsr] FW: New Version Notification for draft-… Ron Bonica
- Re: [Lsr] FW: New Version Notification for draft-… Jeff Tantsura
- Re: [Lsr] FW: New Version Notification for draft-… Ron Bonica
- Re: [Lsr] FW: New Version Notification for draft-… Jeff Tantsura
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Acee Lindem (acee)
- Re: [Lsr] FW: New Version Notification for draft-… Jeff Tantsura
- Re: [Lsr] FW: New Version Notification for draft-… Dongjie (Jimmy)
- Re: [Lsr] FW: New Version Notification for draft-… Dongjie (Jimmy)
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Robert Raszuk
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Gyan Mishra
- Re: [Lsr] FW: New Version Notification for draft-… Dongjie (Jimmy)
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Robert Raszuk
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] FW: New Version Notification for draft-… Dongjie (Jimmy)
- Re: [Lsr] FW: New Version Notification for draft-… Dongjie (Jimmy)
- Re: [Lsr] FW: New Version Notification for draft-… Peter Psenak
- Re: [Lsr] New Version Notification for draft-boni… bruno.decraene
- Re: [Lsr] New Version Notification for draft-boni… Peter Psenak
- Re: [Lsr] New Version Notification for draft-boni… bruno.decraene
- Re: [Lsr] New Version Notification for draft-boni… Peter Psenak
- Re: [Lsr] New Version Notification for draft-boni… bruno.decraene
- Re: [Lsr] New Version Notification for draft-boni… Peter Psenak