Re: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 22 July 2021 09:47 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 167283A3FF7; Thu, 22 Jul 2021 02:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.494
X-Spam-Level:
X-Spam-Status: No, score=-9.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=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=UM7Ealyb; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=p36sH8Zj
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 3WOfmtjTriz0; Thu, 22 Jul 2021 02:47:23 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F043A3FF1; Thu, 22 Jul 2021 02:47:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=51965; q=dns/txt; s=iport; t=1626947242; x=1628156842; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=B1y1qypAOqE5kjwACkYYDZ0+WzfqBmjV9W5tenJoROw=; b=UM7Ealyb5FOx25Nok9inBSaZAasMktmFFImvVNFZk2Y9Td+vQgNWszfs XUgCavrtUm5Q479DYKyvXhyJlf/qSU7AMQ3OGRx8X4Xp++U8dlmFdbmcv mzK6+T9KrplH8XUqPkV2zFSX+Rb5bDk9cI7PwKVHsIGAHYKoALtYKLdUF E=;
X-IPAS-Result: =?us-ascii?q?A0B1AABRPvlgl5pdJa1aHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?UgEAQELAYEiMFF+Dkw3MQOGJIFpA4U5iGEDilePWYFCgREDVAsBAQENAQEyD?= =?us-ascii?q?wQBAYMigTUCgnYCJTcGDgIEAQEBAQMCAwEBAQEFAQEFAQEBAgEGBBQBAQEBA?= =?us-ascii?q?QEBAXKFaA2GRQEBAQQSCBMTAQE3AQ8CAQgRAwEBASEBBgchERQJCAIEAQ0FC?= =?us-ascii?q?AwHB4JPAYF+VwMvAQ6dFwGBOgKKH3iBNIEBggcBAQYEBIFKQYMfDQuCNAMGg?= =?us-ascii?q?ToBgnuEDIEZgVGDeiccgUlEgRQBQ4FhgQE+giBCAQECAYEoARIBIx4GBwmDF?= =?us-ascii?q?4IugiwQWwhiBDIZBgJGgSUZBAEuER4CD5EILYt1jTaROVsKgyWKNY4khXoSg?= =?us-ascii?q?2OLXpcelHcMgQWMM4M0kCaEfwIEAgQFAg4BAQaBdiNrcHAVO4JpUBkOjX0iD?= =?us-ascii?q?AUICYNPhRSFSnMCATUCBgsBAQMJi14BAQ?=
IronPort-PHdr: A9a23:QNdAmhFlOA1hJVdAAoVbV51GfsAY04WdBeZdwpg6jbNWf77l+Zn+b wTT5vRo2VnOW4iTq/dJkPHfvK2oX2scqY2Av3YPfN0pNVcFhMwakhZmDJuDDkv2f/z3aS0iE d4EUlJ5rDm3NEFPE5P4YFvf6nS58T8VHED5Mgx4buT4E4LflYK5zee3rpbSeA5PwjG6ZOAaE Q==
IronPort-HdrOrdr: A9a23:kpIYIK5RBHZ5/1T8RgPXwZGCI+orL9Y04lQ7vn2ZFiY1TiXIra 6TdaoguiMc0AxhJ03Jmbi7Sc69qADnhOBICOgqTPeftWzd2FdAQ7sSlrcKrweQfhEWs9QtqZ uIEJIOS+EYb2IK9/oSiTPQe71LrbX3k9HLuQ6d9QYRcegAUdAH0+4NMHfiLqQAfng+OXNWLu v52uN34x6bPVgHZMWyAXcIG8LZocfQqZ7gaRkaQzY69Qinl1qTmfzHOind+i1bfyJEwL8k/2 SAuRf+/L+fv/ayzQKZ/3PP7q5RhMDqxrJ4dYmxY4kuW3HRYzSTFcJcso65zWkISSaUmQ4Xee z30lAd1gJImijsly+O0EHQMkLboUcTAjfZuC+laD3Y0JHErPZQMbsfuWqfGSGpt3bI9esMop 6i0w+ixulqJAKFkyLn69fSURZ20kKyvHo5iOYWy2dSSI0EddZq3MAiFW5uYd099RjBmc0a+S hVfbfhzecTdUnfY2HSv2FpztDpVnMvHg2eSkxHvsCOyTBZkH1w0kNdnaUk7zk93YN4T4MB6/ XPM6xumr0LRsgKbbhlDONERcesEGTCTR/FLWrXK1X6E6MMPW7LtvfMkfoIzfDvfIZNwIo5mZ zHXl8dvWkue1j2AcnLx5FP+gClehT3Yd0s8LAX23FdgMy8eFPGC1z2dLkeqbronxxEOLyvZx +aAuMgP8Pe
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.84,260,1620691200"; d="scan'208,217";a="771907457"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Jul 2021 09:47:20 +0000
Received: from mail.cisco.com (xbe-rcd-007.cisco.com [173.37.102.22]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 16M9lKLY017899 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Thu, 22 Jul 2021 09:47:20 GMT
Received: from xfe-rcd-004.cisco.com (173.37.227.252) by xbe-rcd-007.cisco.com (173.37.102.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Thu, 22 Jul 2021 04:47:20 -0500
Received: from xfe-rcd-003.cisco.com (173.37.227.251) by xfe-rcd-004.cisco.com (173.37.227.252) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Thu, 22 Jul 2021 04:47:19 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xfe-rcd-003.cisco.com (173.37.227.251) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15 via Frontend Transport; Thu, 22 Jul 2021 04:47:19 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aPMi9/2E3P5TIt2GoRdJV5PkHvagI3A/xDHdRSRWVYYtkgC2q0FgEMa0xbAdwv9vFw3/gfYx+Dy6KVy6T0x+p6i6CtyO0e6Bbgyy4DnkzBqrbWmwKso8dg+ZmkyP4jg+dfqetVs6ECEFtEDfcJV3vtCD2k6oHeDUVCrPcxjyHafj3xbiDih9FKG4Ist7z81g8QKNDbLGwvc9gRYvxTj+xV43Bm5rcLnWfSrbZIIyESC5lCuxs88F2AJNZIYgXnmcUdJLvtz2K0uTN0nhTj0NGy4kdHkilkZndJ/m9FnLgarp9aj5sq8QLJb9xZJDNdd9w5ZWprXf+egk/lnXQ6qurA==
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=GZL+pIQqNF+Vfvl766jMDGDxcaQN5ijzpjLm159iu+s=; b=IyayAgQ1bWokkv2oV6TWAq2ZuaCokuChGk/5RddXnfZJin8BFfiQ7hhjRehF7P7AO/Zzoob6yv98oxGGhpOeWtzUGwBEt3TnYwrqGnC3ReODnhek0Q4D8oAczBFaX3k5xnsF2NFE+ZroAGRm+d9OIWB5rvhT279tjJ8qc7pSXlCo7NxuWURjUiZmbMu/vnV0pRMWg3Jo57MvIdK9T/cZEvbkCOrhAZQw7GyrJ6hD9o7IFtdZ5KVB5R/akbDoZQWjI2xNwGzeNmCsluQ2sOPUkQ5BDIHftLjyAR8jJE69zlGhmB5MKIszr0H5z4ycnJEdjzBX5KbeeTJVCqUzkFA5ag==
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=GZL+pIQqNF+Vfvl766jMDGDxcaQN5ijzpjLm159iu+s=; b=p36sH8ZjpQsIBHvLr4sHM1uaY2/6nJ+sN+xMhnB3W/0bj/K75lJWjMJBIXgjfRgomv0glrhHZkFReFI/48B+uSb84YjuHkXnwLow/pZpkUlyYFBZ41KflPLetrCq/aD+J5chUcLLufBNiTGnJW4ZKMXavU4AUKr/Ol2fU+QEmuk=
Received: from MW3PR11MB4570.namprd11.prod.outlook.com (2603:10b6:303:5f::22) by CO1PR11MB4834.namprd11.prod.outlook.com (2603:10b6:303:90::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4331.22; Thu, 22 Jul 2021 09:47:18 +0000
Received: from MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::7c01:5b00:b7b8:3e87]) by MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::7c01:5b00:b7b8:3e87%3]) with mapi id 15.20.4331.034; Thu, 22 Jul 2021 09:47:18 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Rajesh M <mrajesh@juniper.net>, Salih K A <salih@juniper.net>
CC: "draft-ietf-bess-srv6-services@ietf.org" <draft-ietf-bess-srv6-services@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)
Thread-Index: AQHXftQXRymFG5lplU6k2L+8bR3kyqtOrleAgAAFWiCAAASHoA==
Date: Thu, 22 Jul 2021 09:47:18 +0000
Message-ID: <MW3PR11MB457060C4E47053906C872C2EC1E49@MW3PR11MB4570.namprd11.prod.outlook.com>
References: <D9D76C88-0466-4AB8-8D4E-CDE10D924B74@juniper.net> <MW3PR11MB4570A0EA852747EEA4CABEDFC1E49@MW3PR11MB4570.namprd11.prod.outlook.com> <BN6PR05MB36343C68FF24E6EA211FA486BEE49@BN6PR05MB3634.namprd05.prod.outlook.com>
In-Reply-To: <BN6PR05MB36343C68FF24E6EA211FA486BEE49@BN6PR05MB3634.namprd05.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2021-07-15T11:06:24.0000000Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard
authentication-results: juniper.net; dkim=none (message not signed) header.d=none;juniper.net; dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3bd1b644-d859-4292-4b31-08d94cf5b1eb
x-ms-traffictypediagnostic: CO1PR11MB4834:
x-microsoft-antispam-prvs: <CO1PR11MB4834948B1286A894477AFB56C1E49@CO1PR11MB4834.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: pGv3ZhmzNLpMm+JyvDZpqi7poP3WOt2fgJVhAgV5ZQx8Jc/H+7aMu0CA+QJdhKeaMmt0KZzxhAnqD7ExCmGcIjGbXtwrQFnYj1LSohjadzpsGkJDTPk8Z0KkVJfERYJh55jEH+Zzh00d8DiSdIssP+yDAD4/bgKLab3eBk9ikC6p/YSgxzWykZc1C6ib/7j8Kg0aHUpR1d0XrZUP/RXuZs9RNklE0ZuO+wWDbUqLC3T4RwP2Q2+37Lh8/TniTC8h4jShcSCPB/hcJViPA5EG46i9saCKN6dhV6nLDBagN79+yy/sM5Y4UFRxb49SY9M/jmmlys4RmniEZtn2FkkIWGnytlkBJ2RSq+BlbPL+e8lema/PkJCrzdFMgeKHa3Z6bIgwujR5Qhfx0hFLj2sUxOV+kLu4pNRNzAiXLlRKLwHcgza1oX6s/PxaJs1j3iJ9HqpwwVftlHaPiXOfnkzp9qmWdMHXoDyb2MyzpePcPjktqIZ4UP6mf2LmsC+Qe5kqZ5pHq0XYLRGaSgOTlfjxaOPuhBjbsD6pOaIA018gmoMRv6euAPIj7X+2U/MGtvQqBn3CcLFs4mHTW+ucNIlkHTji6HuK/OlxcP8PeszlyFlP0KuefHF5lCEfnEiU/1l8hea7dSD8LNMmql2w9gBMUI43P5qpyAYHgEMyDaTn8p+vMdbBHEWYSrTL7aqg0PLMRfXuOl8i0TyuOwRKsx/K7Bo1IAHiAIBs1gqt2XS3blr9IZUq4d+SbOwqrA+rRGAWVAG6FkJ0GSg6WsY8vdYAIx8mGYnRUbtsCOobX0u/TLDGY6DV+Lbob4owoYvTbP5Woc4Zlgd0yPQwcEP2wL5JNw==
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; SFS:(396003)(376002)(346002)(136003)(39860400002)(366004)(33656002)(166002)(6506007)(122000001)(7696005)(8676002)(8936002)(54906003)(55016002)(4326008)(52536014)(83380400001)(966005)(86362001)(53546011)(5660300002)(2906002)(26005)(478600001)(9686003)(66446008)(38100700002)(9326002)(66946007)(66556008)(186003)(76116006)(71200400001)(316002)(110136005)(66476007)(64756008)(38070700004); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?4OznKeexuRNuioUUdzC/T5XqK2F4OlUGjGWLAyEir4rijYR97yiuL9dkPz7B?= =?us-ascii?Q?O7ugR9fAxQ0pJmebceV/KtSssmLIdeZ0fPRVxaSlphhf0UkHK58eXrQKmGnA?= =?us-ascii?Q?4eH/uHTUqra5+qPq1ZWXfQBmzEW/B26Q/G2/VQwsjDeZW1jqLbBXW0Mxrm/7?= =?us-ascii?Q?4mCRkDpZR8ZCp83cSPdcItG/B9CQXp6L+sNIMVcOaw8Q+cxgCSkliPTuGrn5?= =?us-ascii?Q?TuaE8ntJbXoTjTmVCWO4bBa61g3G/ZmRSgo4cdpD2hDmdj95kqif97l/x4+1?= =?us-ascii?Q?IeRPsTnO85NXJUTZXTyw9VL0KZP2Kd/Abicn5ZVOlm/cWCDleU49Rrhxz9D1?= =?us-ascii?Q?UfxIFFt+2SkeA2AgUhQSeo7JNYMz63kVlhAy0RuYG5RnS76SYUwdL1fH0sy6?= =?us-ascii?Q?/QnMWQfFexR3By+06V/a6+DyS6yNnJJkaW2uVVEeBhwhO41P1BU0SAea4MEO?= =?us-ascii?Q?e/zlHWhTZb6I8cYd42VL13eI64uKhTh/JeIf3jB//hGTeAeSNj8dXmqKu4Pa?= =?us-ascii?Q?cdiGYtJYu3XHXSXejEEP755mkq8jbU4U4OxwfmKyJz2O3xVUWRqwjVbDgQuv?= =?us-ascii?Q?rAAYhcpxSi3wABYbem9JsIaJPKjcDmB+csvLmCfi0c9VihfPH9U+l+exE5XB?= =?us-ascii?Q?jbo9H6/Cw2UV9Kf6yK/jjUEi3Zp8pD8vQ6p2908//5ElAiz9tBZSQ26AH9Tj?= =?us-ascii?Q?QwhOOhGEWb1H2YgFRliWX1Z14ifzzTSgl+2YbI3iLmi91nO2zflZ66QNKedD?= =?us-ascii?Q?bLgBuBJBDEaCe8ByYST7kKPQUwVYE6LyVe9Vwiv4HBNv63yb+CUN9Ex/cjaO?= =?us-ascii?Q?k3vA29s1YviKQ5pUXkza+va0bbVSeK7m7hqqVD1vyzDZiOlTRQ645FJLesZb?= =?us-ascii?Q?KX8g7VaVkmfX76Sd72eRJh09CZ4GvyeQhDPyrlvEeDeoQlsz1K4RRk/XwRO8?= =?us-ascii?Q?DSONCNNpmskK2G95mIgybmis1vg8HBNH7naG90Q4m2z1EK0shl/ZEmZ459IK?= =?us-ascii?Q?xvQSEFCI017nrzLwfwAjaMmFEXKcP7PeyXkn1fmKsmViirz8myOgO8Bk4xnk?= =?us-ascii?Q?AIxTpzlqDRpJI72Z4R6xFLGxuTBOJymdafd9Kyh5wye+XAQfUwchKwhUAsC6?= =?us-ascii?Q?V8l+yVOfIlgZW0396Q4kc2KJbb/YGBmc50WYA30WYTvWN9F37GU6cZvuHZBs?= =?us-ascii?Q?MFE9fIVfNiMdD4AQcz8RKBXYrk4zITdzLHdLIm7wxvBkks/a0HQjam1J3qNb?= =?us-ascii?Q?VSePNvuxu42LtMUP8l+CMVBNnTumRd9rKTWY0Y+nxAN9Z0+6Vth3FTAPj0PX?= =?us-ascii?Q?l1ibAGPnNjUIPj817F1Ua0dV?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR11MB457060C4E47053906C872C2EC1E49MW3PR11MB4570namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR11MB4570.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3bd1b644-d859-4292-4b31-08d94cf5b1eb
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2021 09:47:18.4644 (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: s1giZS7sfVw1Di9AKWx/yw/AYX2zt3jAXy2g7OB3wPc8o9558CtVwmUCzlo+TT4W4/kwacCEaVHEbu0cHdz/iQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR11MB4834
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xbe-rcd-007.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/zQb5FMTazEYVtOMtjCDxjfUW6p0>
Subject: Re: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)
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: Thu, 22 Jul 2021 09:47:31 -0000

Hi Rajesh,

I think there might be some confusion here with the mix-up between a draft which is past WGLC and an individual draft? Would it be possible to keep their discussions on separate threads?

However, since I am an author on both, I would like to clarify is that "the rules" are merely being used as an example in the BGP CAR draft : https://datatracker.ietf.org/doc/html/draft-dskc-bess-bgp-car-02#section-3

Whether we form WG consensus on codifying this preference as a "default" still remains to be seen. Irrespective, when it comes to such things there might be operators that would like to have some policy control.

If we just focus on the SR Policy based steering then we have the following in SR Policy draft (https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-policy-13#section-8.4) that I had pointed to below. This indicates a preference for steering over SR Policy using color extended community.

Thanks,
Ketan

From: Rajesh M <mrajesh@juniper.net>
Sent: 22 July 2021 14:44
To: Ketan Talaulikar (ketant) <ketant@cisco.com>om>; Salih K A <salih@juniper.net>
Cc: draft-ietf-bess-srv6-services@ietf.org; spring@ietf.org; bess@ietf.org
Subject: RE: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

Hi Ketan,

As per CAR draft - For Intent service Route (IGP Flex-Algo first then BGP CAR then SR Policy):

So below must be the rules right ?
BGP next hop is not reachable return (just for reachability).
Resolve SRv6 Service SID for forwarding(To find IGP flex algo).if successfully resolves then return.
Resolve BGP next hop for forwarding either by CAR or by SR-policy (in case above is not success).

Thanks
Rajesh





Juniper Business Use Only
From: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>
Sent: Thursday, July 22, 2021 2:25 PM
To: Salih K A <salih@juniper.net<mailto:salih@juniper.net>>; Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>
Cc: draft-ietf-bess-srv6-services@ietf.org<mailto:draft-ietf-bess-srv6-services@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>; bess@ietf.org<mailto:bess@ietf.org>
Subject: RE: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[External Email. Be cautious of content]

Hi Salih,

Could you please check the following regarding the choice/fallback when using SR Policy based steering?

https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-policy-13#section-8.4<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-policy-13*section-8.4__;Iw!!NEt6yMaO-gk!UVtxbzzcrG5uslNvEdjH34VnBanX7PHCCU487ZgaxyKBxCr8lhxEKIxQD-4i7eL9$>
https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-policy-13#section-8.8<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-policy-13*section-8.8__;Iw!!NEt6yMaO-gk!UVtxbzzcrG5uslNvEdjH34VnBanX7PHCCU487ZgaxyKBxCr8lhxEKIxQD9V3qgJv$>

Thanks,
Ketan

From: Salih K A <salih@juniper.net<mailto:salih@juniper.net>>
Sent: 22 July 2021 14:02
To: Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org<mailto:ketant=40cisco.com@dmarc.ietf.org>>; Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>
Cc: draft-ietf-bess-srv6-services@ietf.org<mailto:draft-ietf-bess-srv6-services@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>; bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

Hi Ketan,

1 clarification query:

With flex algo and SRTE policies, service routes can carry color extended communities.
Now for the ingress, how to decide whether to resolve over SRv6 Service SID (to choose flex algo) OR over BGP Protocol next hop (to choose SRTE)?
In a domain both can be present & operators may want fallbacks as well if one is not available. So, I think it's better to clarify that to avoid ambiguity.

Thanks,
Salih
From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> on behalf of "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org<mailto:ketant=40cisco.com@dmarc.ietf.org>>
Date: Thursday, July 22, 2021 at 1:19 PM
To: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>
Cc: "draft-ietf-bess-srv6-services@ietf.org<mailto:draft-ietf-bess-srv6-services@ietf.org>" <draft-ietf-bess-srv6-services@ietf.org<mailto:draft-ietf-bess-srv6-services@ietf.org>>, "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Subject: Re: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[External Email. Be cautious of content]

Resending with individual email addressed trimmed

From: Ketan Talaulikar (ketant)
Sent: 22 July 2021 13:13
To: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>; Rajesh M <mrajesh=40juniper.net@dmarc.ietf.org<mailto:mrajesh=40juniper.net@dmarc.ietf.org>>; Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>; gdawra.ietf@gmail.com<mailto:gdawra.ietf@gmail.com>; Clarence Filsfils (cfilsfil) <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>; robert@raszuk.net<mailto:robert@raszuk.net>; bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
Cc: spring@ietf.org<mailto:spring@ietf.org>; bgp@ans.net<mailto:bgp@ans.net>; Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>; bess@ietf.org<mailto:bess@ietf.org>; Srihari Sangli <ssangli@juniper.net<mailto:ssangli@juniper.net>>
Subject: RE: SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

Hi Rajesh,

My apologies for the delay in my response. However, some of my co-authors and other WG members have already clarified this point. Let me try to summarize.

The draft covers two SRv6 based mechanisms for the transport of services between SRv6 PEs. (1) using SR Policy based steering (i.e. for service routes with Color Extended Communities) using the H.encap construct along with a list of SRv6 segments  and the other (2) using H.encap with just the SRv6 Service SID in the IPv6 DA.

As mentioned in the draft, it is required to verify the reachability of the SRv6 Service SID before the mechanism (2) can be used. This is an explicit clarification for verification of reachability. In an MPLS-VPN scenario, if the egress PE NH's IP route is reachable at the ingress PE but without an MPLS label, such a path cannot be used. This is semantically similar.

The mechanism (1) is different since the routing to the egress PE is via SR Policy and hence the requirement for verification of reachability of the SRv6 Service SID is not there.

There is no mandate for the setting of the NH since that is left to deployment design.

I hope this helps in addition to the various clarifications already provided by others.

Thanks,
Ketan

From: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>
Sent: 22 July 2021 12:09
To: Rajesh M <mrajesh=40juniper.net@dmarc.ietf.org<mailto:mrajesh=40juniper.net@dmarc.ietf.org>>; Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>; Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; gdawra.ietf@gmail.com<mailto:gdawra.ietf@gmail.com>; Clarence Filsfils (cfilsfil) <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>; robert@raszuk.net<mailto:robert@raszuk.net>; bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
Cc: spring@ietf.org<mailto:spring@ietf.org>; bgp@ans.net<mailto:bgp@ans.net>; Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>; bess@ietf.org<mailto:bess@ietf.org>; Srihari Sangli <ssangli@juniper.net<mailto:ssangli@juniper.net>>
Subject: RE: SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

Could Authors respond to this ?



Juniper Business Use Only
From: Rajesh M <mrajesh=40juniper.net@dmarc.ietf.org<mailto:mrajesh=40juniper.net@dmarc.ietf.org>>
Sent: Monday, July 19, 2021 7:28 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>; Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>; Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; gdawra.ietf@gmail.com<mailto:gdawra.ietf@gmail.com>; Clarence Filsfils (cfilsfil) <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>; robert@raszuk.net<mailto:robert@raszuk.net>; bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
Cc: spring@ietf.org<mailto:spring@ietf.org>; bgp@ans.net<mailto:bgp@ans.net>; Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>; bess@ietf.org<mailto:bess@ietf.org>; Srihari Sangli <ssangli@juniper.net<mailto:ssangli@juniper.net>>
Subject: RE: SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[External Email. Be cautious of content]

Hi All,

For best effort service, flex algo - Resolve SRv6 Service SID for forwarding.
For SR-TE, CAR/CT - Resolve BGP next hop for forwarding.

There is no unification here, it's better to unify.
Any other solution is OK.

Thanks
Rajesh



Juniper Business Use Only
From: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Sent: Monday, July 19, 2021 7:17 PM
To: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>; Rajesh M <mrajesh=40juniper.net@dmarc.ietf.org<mailto:mrajesh=40juniper.net@dmarc.ietf.org>>; Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; gdawra.ietf@gmail.com<mailto:gdawra.ietf@gmail.com>; Clarence Filsfils (cfilsfil) <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>; robert@raszuk.net<mailto:robert@raszuk.net>; bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
Cc: spring@ietf.org<mailto:spring@ietf.org>; bgp@ans.net<mailto:bgp@ans.net>; Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>; bess@ietf.org<mailto:bess@ietf.org>; Srihari Sangli <ssangli@juniper.net<mailto:ssangli@juniper.net>>
Subject: Re: SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[External Email. Be cautious of content]

Hi Rajesh,

The draft is written so that the next-hop address MAY be covered by the locator, but there are cases in which the next-hop address is not part of the locator prefix, and there are implementations already allowing that, so I don't agree the document should mandate what you are suggesting.

Thanks.
Jorge

From: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>
Date: Monday, July 19, 2021 at 3:24 PM
To: Rajesh M <mrajesh=40juniper.net@dmarc.ietf.org<mailto:mrajesh=40juniper.net@dmarc.ietf.org>>, Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>, gdawra.ietf@gmail.com<mailto:gdawra.ietf@gmail.com> <gdawra.ietf@gmail.com<mailto:gdawra.ietf@gmail.com>>, Clarence Filsfils (cfilsfil) <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>, robert@raszuk.net<mailto:robert@raszuk.net> <robert@raszuk.net<mailto:robert@raszuk.net>>, bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>, Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Cc: spring@ietf.org<mailto:spring@ietf.org> <spring@ietf.org<mailto:spring@ietf.org>>, bgp@ans.net<mailto:bgp@ans.net> <bgp@ans.net<mailto:bgp@ans.net>>, Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>, bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>>, Srihari Sangli <ssangli@juniper.net<mailto:ssangli@juniper.net>>
Subject: RE: SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)
Hi Authors,

Please respond.

Thanks
Rajesh



Juniper Business Use Only
From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> On Behalf Of Rajesh M
Sent: Thursday, July 15, 2021 4:36 PM
To: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; gdawra.ietf@gmail.com<mailto:gdawra.ietf@gmail.com>; Clarence Filsfils (cfilsfil) <cfilsfil@cisco.com<mailto:cfilsfil@cisco.com>>; robert@raszuk.net<mailto:robert@raszuk.net>; bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>; jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>
Cc: spring@ietf.org<mailto:spring@ietf.org>; bgp@ans.net<mailto:bgp@ans.net>; Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>; bess@ietf.org<mailto:bess@ietf.org>
Subject: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[External Email. Be cautious of content]

Hi All,

As per this draft, this is how resolution must work.

1)For Non Intent service Route:
if BGP next hop is not reachable return.
Resolve SRv6 Service SID for forwarding.

2)For Intent service Route (IGP Flex-Algo first then BGP CAR then SR Policy):
BGP next hop is not reachable return.
Resolve SRv6 Service SID for forwarding(To find IGP flex algo).if successfully resolves then return.
Resolve BGP next hop for forwarding (in case above is not success).


Using Service SID (overlay),for resolution is definitely not recommended.

Instead in case of srv6, we always resolve on BGP nexthop. This will be in line with BGP legacy.
In case of best effort/flex algo we must mandate user to set corresponding locator as BGP nexthop for srv6 routes.
I think this is a reasonable mandate.

Thanks
Rajesh


Juniper Business Use Only