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

Ron Bonica <rbonica@juniper.net> Sat, 03 October 2020 20:33 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 142513A0822 for <lsr@ietfa.amsl.com>; Sat, 3 Oct 2020 13:33:38 -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=TsLrIa5K; dkim=pass (1024-bit key) header.d=juniper.net header.b=H2V93fU7
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 bsGLEE8hfyId for <lsr@ietfa.amsl.com>; Sat, 3 Oct 2020 13:33:36 -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 11FBD3A07CE for <lsr@ietf.org>; Sat, 3 Oct 2020 13:33:35 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 093KXW1S029282; Sat, 3 Oct 2020 13:33:32 -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=M7uVS3it4mFl101V5gu7um0U9gYQLfY58yr4MpKrNIY=; b=TsLrIa5Ka+VzYBRGsuRcL71+koNhMLBPiOBYXZsDlA1Bv6OwtAgZ1Pm/dTMgcp+lQ10J lqi5j7EM05Zr7jPOHwKELtFFHc78JPG/rocEG+XyCSqfb/AjfF18F6SXzT1ajhG7iuuY FX/k858YCXZpcTz+skVTQfxy4XFj7t2IrFyCn6bLpbGFIrhCnMfSEPc/6rpHAHpQBTL+ 1eMLPQ3LxIF23L5jNjT93X6YemYe+fe7tX/DX3BIZBHYccsGE2irUdV7RSyHvolzOWDE jhFEMZPMOWepg3ie5wrVfxPb2fxbkjXh6OyseVNzM4GE4kus0Mu2dXGU1vaTEIAhxqfp aQ==
Received: from nam12-dm6-obe.outbound.protection.outlook.com (mail-dm6nam12lp2169.outbound.protection.outlook.com [104.47.59.169]) by mx0b-00273201.pphosted.com with ESMTP id 33xq7j0dat-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 03 Oct 2020 13:33:32 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TQ25bQCJ7ZxlJI2I2tJsAFhaE9sScw0fORBBFDiLLbRWvoUG9ReTZ9DwVzk6pAIns7Zy5rj7HYwADIK6242bJDUw5qx8irntEywVXYD5HhuAqhGjMTYri28f2lNnxkmbOQ1TNC3Qho5s6b8puZaR3iCqshrnqEGvyNWnZ6q0eXFlzAT4whsKx8ST0oRVOwhkhBuFVBC3r7kK2MI2CWqRiZJ9nJbB0l3NXPBq4ChJPg6MFIUMUqff3isUyqbuj7+dGAwpr9K8MMxNowAsoJH57U1Ru8+n2qXDML7RcnmkeLvt9ge0djXs6VsAxcu4qXccs+5ed05nxpl2TVrv3WgPOA==
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=M7uVS3it4mFl101V5gu7um0U9gYQLfY58yr4MpKrNIY=; b=G62SUfaciHx0GBIA/Gj4+RSUvTvDNaVqqOGEG88HtEuBL9dg3gQtseV02+JP42q0Z/KBxiPOBTQKSexN2ZU0usWDZnPq8xj4IC3Pejz3AG4Ct97O9x4ULdm34PsRE2EKeRHr6NPtFrEpSoryWPkJph5mWy5zpXa5kTHx5k58KrUH7ueDrPcAHBCcmce9GTFpzgKgXDmNBE4HNdexpDGFo6IsF9MwBnzUIHJYo0Vyg4sTofdfR8A2gBsZR33QpBYyZar6ZScD5MloCddkxQOvOnWnjyUk6jDUuCgOlUjY2BvAvotaRlQ7jwfZ7ndl/pJ43fh53PRI+UPMg2nX5bU3lw==
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=M7uVS3it4mFl101V5gu7um0U9gYQLfY58yr4MpKrNIY=; b=H2V93fU79jxxGFsQYdw3ccllNPH4hzAhZBfr62yMVNwYUlRYlBKRexQb7hsNfi5j+iieGOIgy1EuaDIA9I9plNqCtIWnjlVq+oS8GfAZum9yd0lqKpU8pGWJ+Xb1ZdSVutry3ivP36hxvPQAoMRYmBR59jcoULHkH4ocCDmvhZc=
Received: from DM6PR05MB6348.namprd05.prod.outlook.com (2603:10b6:5:122::15) by DM5PR05MB3371.namprd05.prod.outlook.com (2603:10b6:4:45::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.20; Sat, 3 Oct 2020 20:33:30 +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.3455.016; Sat, 3 Oct 2020 20:33:30 +0000
From: Ron Bonica <rbonica@juniper.net>
To: Yingzhen Qu <yingzhen.qu@futurewei.com>, Peter Psenak <ppsenak@cisco.com>, Gyan Mishra <hayabusagsm@gmail.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>
Thread-Topic: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt
Thread-Index: AQHWlmVwC6ypd3I8xkyHSNG022ojU6l/nmSwgAGYiICAAB9mMIAA726AgADTSnCAAWzZgIAAAz2A///GWICAAVg7AIAAFmsAgACYCCA=
Date: Sat, 03 Oct 2020 20:33:30 +0000
Message-ID: <DM6PR05MB6348C6FBFD50C19C06DE719BAE0E0@DM6PR05MB6348.namprd05.prod.outlook.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> <00158dee-bb0d-6f5e-f740-b7bac61a1c74@cisco.com> <7F26707A-8137-4114-9236-D80B060E2528@futurewei.com>
In-Reply-To: <7F26707A-8137-4114-9236-D80B060E2528@futurewei.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-03T20:33:28Z; 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=88f21b67-5478-433b-8af2-b556a3f96bf2; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
authentication-results: futurewei.com; dkim=none (message not signed) header.d=none;futurewei.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [173.79.132.205]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 65080bbc-9787-4b49-f1d6-08d867db9706
x-ms-traffictypediagnostic: DM5PR05MB3371:
x-microsoft-antispam-prvs: <DM5PR05MB3371DFA20F35D7CEC3A3C77BAE0E0@DM5PR05MB3371.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9mrytJIGfe6ffx8BtizAGPfDvUrV2chCsWyiZ4UCeFTtg3fHRikqJ94ELfbH2dSvVBJXx9uAe6PG3mboDkB4F47/Mo9ANyQYbFBsoJ8Tu30NP4OwWVJ16kdm3FAa5cZbGq7KNfysosLIKbirqrZSrQtuYYIQ36oMF6lbwNywyrEgTg3pRjw5cQfoh/eW/yTm3oZ1pE+nykWGMspMz0NOZJNs7y2/mav9ag7foi3vnq01WjAA2laGiQWdDE0yK7xvqUH7sCcSgVlMV/xCQWmv7/aTTnUTuZrfhZbLNed1by+kgsxGP+pEIJcapvued529Aymko6O3MNdg0M2qTyHjD2nB/Sq/jAXFoO+sBk4EXSNpsRtdKOVg3n8iB103Cw8PpTVPw2FlmaVIwrJnRY4+LQF7ePRTvyCh5wrsPhewu65YdAZtxBxmz3qYm9mAGnz0YCy6hM1PblSNbp2IcojYZQ==
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)(376002)(39860400002)(136003)(366004)(346002)(396003)(76116006)(478600001)(110136005)(86362001)(15650500001)(8676002)(45080400002)(8936002)(2906002)(66556008)(71200400001)(66476007)(64756008)(66946007)(66446008)(9686003)(4326008)(26005)(54906003)(33656002)(55016002)(7696005)(52536014)(966005)(186003)(316002)(5660300002)(53546011)(6506007)(83380400001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: sfk2dy9pz9sddZ9VuSV2aa7sib3pZ5kOMygCcCTsSjHr1yOaXluIFIAlmlrbMjigxC+wRJX8ZOnU4gjBrh2hmgfb7xYqK8o1vc0ofMjUCS3qY8QSRAF2Ik4s+pLeBaT9WotEfHdXkFxgnNIECRoWPuNRjrKFMxLixudjk3f4MZ/pQLZ30P+7POQ6cpVh1+lbXE3R+eE03mlP8VrgRNIYshWiAhEECY8vUCIF2cGaeGir2tCQpssBkNikkJ1nYswA3T6VEyIML86h3taxKfrsvAsOXQu31xVK3Fmc8JPBJ9acU4TlPwJytZB7R45xi8lkclRR9QcGt3/DhtpdQeJwGByhiBf0ryN4aBfepd+/pYdjpXLmDxb9xYAscpkrSPhZucug/eDSqHTlU08MZYxp+WYcEoZjkkDvsFc9f/TPd9grZACQegaQYASrFGCzcCvzhw9eQd0pBVUoOWPdef48UeeJuPY4hdr2JkmC8g9LZL9OovlvbJndQLLclSC75CNdueLcvqUctOf1dgFvrJ9+qRVtfTTsErGKZgqiqiwv4dvdjw6oqRPaCgPYiaMlHiTliXcBX16K5pPprAKydPTPkeMr9kNCSBHU2WnqT/MTdlf50U8Dgjk5krMdmqRyi1rTDaS0lIlu2w25VGlmuZ/Iwg==
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: 65080bbc-9787-4b49-f1d6-08d867db9706
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Oct 2020 20:33:30.0929 (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: OfU6WTqEMNaE0lbHduSAyf+Nf/0vNVI/k4NW5kwzIiOdaTIoMlYqPskU0jBhKY24JNfFStC0olFIQBhqfYbezA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3371
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-10-03_16:2020-10-02, 2020-10-03 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 malwarescore=0 spamscore=0 clxscore=1011 priorityscore=1501 suspectscore=0 mlxlogscore=999 impostorscore=0 phishscore=0 lowpriorityscore=0 mlxscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2010030171
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/Uv6T9wSMtHGiqKRWQs-CA51zH4A>
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 20:33:38 -0000

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.outlook.com/?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Flsr&amp;data=02*7C01*7Cyingzhen.qu*40futurewei.com*7Cfe03124c6e414e067c2008d867816541*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637373152739865126&amp;sdata=WI48cEAan*2FOkDPmVXGurEAjPItNGF9p9PDQIlD1ip0g*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!X1fRln9MjimeJcREUEIydr-8IIbtNonXMs83eoXvRww6xkaQfVUdNh0kK452GP-G$
    >
    >
    >