Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming
"Satya Mohanty (satyamoh)" <satyamoh@cisco.com> Wed, 27 March 2019 18:47 UTC
Return-Path: <satyamoh@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DBA3120368 for <bess@ietfa.amsl.com>; Wed, 27 Mar 2019 11:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=U+2QcYWz; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=UXkX6ABm
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 hMrtf8ICSGet for <bess@ietfa.amsl.com>; Wed, 27 Mar 2019 11:47:28 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECDB612035D for <bess@ietf.org>; Wed, 27 Mar 2019 11:47:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=30593; q=dns/txt; s=iport; t=1553712448; x=1554922048; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=TiDxw7Lc/ZYQkQzMSiRBtOg3SggVI0mKP2leWdYJR9s=; b=U+2QcYWzxHliPA0HcVyB3Ipm9E6oPzvFr/VfOQfTt65mJYhYsxZHYXb4 p8JsHKgAQHuhClP2QCrSV9wL3scQrHmX/Pne0Eg79wOlqbR6yufD3jIUG WRu4onsvZ1qVB2aK2hkr5Hjy36lNMcSp+YcXOghSDxcvzHzqgU5X/FKsy 8=;
IronPort-PHdr: 9a23:58jdHxd1QBn+6H1XUls4kIqvlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dCUmDc1HU19N9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAD9xJtc/4oNJK1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ4vUANodAQLJ4QOg0cDhFKKWoJXiTiNVoEugSQDVA0BASUHhEACF4UXIjQJDQEBAwEBCQEDAm0cDIVKAQEBBCMKEwEBNwEPAgEIEQMBAQEhBwMCAgIfERQJCAIEDgWDIgGBEUwDFQECDJ8fAooUcYEvgngBAQWBNQKDTg0LggwDBYEvAYsxF4FAP4ERJx+BTlAuPoIaRwEBA4EaWwkNCYJUMYImjHyEIodKjBA2CQKHaogcgz8aggOSCYoegiaEcYE8i3UCBAIEBQIOAQEFgU04KIEucBU7KgGCQYIKg26FFIU/coEojk0BAQ
X-IronPort-AV: E=Sophos;i="5.60,277,1549929600"; d="scan'208,217";a="251263819"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Mar 2019 18:47:21 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x2RIlLu4016923 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 27 Mar 2019 18:47:21 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 27 Mar 2019 13:47:20 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 27 Mar 2019 13:47:20 -0500
Received: from NAM01-SN1-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.1473.3 via Frontend Transport; Wed, 27 Mar 2019 14:47:19 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TiDxw7Lc/ZYQkQzMSiRBtOg3SggVI0mKP2leWdYJR9s=; b=UXkX6ABmBL3Vxw9yxdlqqlhdNSN6jpza/MVKe8kdpibAjpTABrD6ytsQ5TqheCGpvIFI23ufct03pstvohYRLpsW3vUaVWFxWTa5RqpMzsXrFttcf4cDvyCfBXQhHA/fXYRLoBsiJKYkB5l5QYxKHWxP9NDRa4kB4TbKyRvGWRY=
Received: from BYAPR11MB3094.namprd11.prod.outlook.com (20.177.227.76) by BYAPR11MB3832.namprd11.prod.outlook.com (20.178.239.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.15; Wed, 27 Mar 2019 18:47:18 +0000
Received: from BYAPR11MB3094.namprd11.prod.outlook.com ([fe80::85e9:66ea:d05a:41e4]) by BYAPR11MB3094.namprd11.prod.outlook.com ([fe80::85e9:66ea:d05a:41e4%6]) with mapi id 15.20.1730.019; Wed, 27 Mar 2019 18:47:18 +0000
From: "Satya Mohanty (satyamoh)" <satyamoh@cisco.com>
To: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
CC: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] BDF Election in EVPN VPWS Single-Active Multihoming
Thread-Index: AQHU4KHAKrFWHhn7rU6BVZMyO+QSvqYXsqSAgAA44ICAAAm4AIAABuIA//+2LQCABENcAIADbr2A
Date: Wed, 27 Mar 2019 18:47:18 +0000
Message-ID: <9D3DC208-1CEF-4A69-850B-EBBFD33529A8@cisco.com>
References: <CAKz0y8zPKgTc7ctDgthOuUyag-zM8xV-P=nAC0js9HKOKYSnJA@mail.gmail.com> <C2C58125-48AC-45A1-ACFA-EAEFC6364433@nokia.com> <CAKz0y8zMQ+T=c9KkX0soefBoqEgmZ02tjAO56cUoqUUSr5cCdA@mail.gmail.com> <AM0PR07MB3844FE2F40F789D8F476FB0FF7430@AM0PR07MB3844.eurprd07.prod.outlook.com> <CAKz0y8ySkDq2Q-H_FqTirGvdT5i_C0eYyrntdkTA6SVFQzEcMA@mail.gmail.com> <AE6D95F3-7474-4652-8FAB-E69EDF33B3C4@cisco.com> <CAKz0y8x+eXR0Z_R4y-7R9=3XH-z5GxG9nDqbUcf+T9A23D5jvA@mail.gmail.com>
In-Reply-To: <CAKz0y8x+eXR0Z_R4y-7R9=3XH-z5GxG9nDqbUcf+T9A23D5jvA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=satyamoh@cisco.com;
x-originating-ip: [2001:420:c0c0:1005::169]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c2393fcd-07b2-4001-b717-08d6b2e4a3a4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BYAPR11MB3832;
x-ms-traffictypediagnostic: BYAPR11MB3832:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB3832437798447B1E24229D2CD4580@BYAPR11MB3832.namprd11.prod.outlook.com>
x-forefront-prvs: 0989A7979C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(136003)(376002)(366004)(39860400002)(396003)(199004)(189003)(8676002)(5070765005)(46003)(478600001)(6436002)(7736002)(440504004)(9326002)(14454004)(99286004)(105586002)(606006)(6506007)(106356001)(93886005)(97736004)(517774005)(68736007)(2906002)(54906003)(966005)(71200400001)(83716004)(71190400001)(316002)(25786009)(8936002)(256004)(4326008)(790700001)(6116002)(6486002)(14444005)(33656002)(86362001)(81166006)(81156014)(76176011)(6512007)(53936002)(6246003)(6916009)(53546011)(186003)(54896002)(11346002)(6306002)(236005)(82746002)(5660300002)(2616005)(229853002)(102836004)(476003)(486006)(36756003)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3832; H:BYAPR11MB3094.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: R2fHM0l22lS0etX3Qgg2ZvfpuSP+t811RNJFpObrBX9rhcJU5QdPM3ECVf8qKYEG+YWIUe4y4pwPLDQNSvYHVt/2abreYXtnoEoAqovxeVLKzuBgbx/pYUF3W/jWSfFLOkCUp2398+s2SyCHNHAH+Q3SIOCHNJF35X/7NsoK1OrYmbjFSHqbfOCfC0wIpay2PgcSRS8sQrEA3CEYDsNZVAJTVNrYLCnm7NaSDj3b31ATbjeOaezFoMoa7bhTnrmYjIzLpoyVwQRTLMUwOqEhTUkBSm7uCP/ntcSimzMc/JHAQGGO93OYeMRhPCG74WIOw0oMP68DifETbq3RPDAwtLZ8/yuMSLj7fZy/3SAtV0tU43jifzuKtdXv3VlzLuxWWNh/YgYkWiZ7jQCpKlAn44OtBC4oWWPuw1tqHRX0NDU=
Content-Type: multipart/alternative; boundary="_000_9D3DC2081CEF4A69850BEBBFD33529A8ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c2393fcd-07b2-4001-b717-08d6b2e4a3a4
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Mar 2019 18:47:18.5651 (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-Transport-CrossTenantHeadersStamped: BYAPR11MB3832
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.28, xch-rcd-018.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/2quVlQTMsiw9jux-wciiftsmBAs>
Subject: Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2019 18:47:30 -0000
Hi Muthu, As you mentioned it is straightforward to calculate the BDF in the default DF Algorithm by taking the current DF out of reckoning. It is my personal view that since this is self-evident it need not be explicitly stated. But I will let others decide. Thanks, --Satya From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Date: Monday, March 25, 2019 at 8:22 AM To: "Satya Mohanty (satyamoh)" <satyamoh@cisco.com> Cc: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, "bess@ietf.org" <bess@ietf.org> Subject: Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming Hi Satya, draft-ietf-bess-evpn-df-election-framework also does not describe how the BDF is to be calculated for the default DF election algo. Am I missing something? I think my question still holds: Though it is straightforward to calculate the BDF by eliminating the DF from the candidate list, would an implementation calculating the BDF that way for the default DF election algo interoperate without any problem? Would it be better to update draft-ietf-bess-evpn-df-election-framework on how the BDF is to be calculated in general for any DF election algo (including the default DF election algo)? [Satya] IMHO opinion, much as it appears obvious, we cannot say for certain that in every future DF algorithm (that may come into existence), the BDF computation will always be as simple as taking the current DF (PE) out of reckoning and doing the recomputation. Regards, Muthu Best, --Satya On Sat, Mar 23, 2019 at 2:46 AM Satya Mohanty (satyamoh) <satyamoh@cisco.com<mailto:satyamoh@cisco.com>> wrote: Hi Muthu, Yes, the BDF is as per what you have mentioned. https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-framework-09 formally defines it. Thanks, --Satya From: BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of Muthu Arul Mozhi Perumal <muthu.arul@gmail.com<mailto:muthu.arul@gmail.com>> Date: Friday, March 22, 2019 at 11:41 AM To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>> Cc: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>> Subject: Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming Thanks, Jorge. Need another clarification. RFC 7432 does not describe how to calculate the BDF for the default DF algo. Though it is straightforward to calculate the BDF by eliminating the DF from the candidate list, would an implementation calculating the BDF that way for the default DF algo interoperate without any problem? Regards, Muthu On Fri, Mar 22, 2019 at 11:45 PM Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>> wrote: Hi, Well, everyone has to support the default DF Alg, based on RFC7432. So that one for sure. And in addition there are others that have been implemented. For instance, Pref DF election has been implemented by multiple vendors. Thanks, Jorge ________________________________ From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com<mailto:muthu.arul@gmail.com>> Sent: Friday, March 22, 2019 10:41 To: Rabadan, Jorge (Nokia - US/Mountain View) Cc: bess@ietf.org<mailto:bess@ietf.org> Subject: Re: [bess] BDF Election in EVPN VPWS Single-Active Multihoming Hi Jorge, I didn't mean using different algorithms for electing the DF and BFD. I am just asking which algorithm is most widely implemented/used for electing the DF *and* BDF for EVPN VPWS single-active multihoming. Regards, Muthu On Fri, Mar 22, 2019 at 7:47 PM Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>> wrote: The implementations I know use the same DF Alg for DF election _and_ backup DF Election. And I don’t see why you would use something different? In other words, if you use e.g., Pref based DF Alg, use it for DF and BDF elections. Only that the BDF election excludes the DF from the candidate list. Thx Jorge From:BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of Muthu Arul Mozhi Perumal <muthu.arul@gmail.com<mailto:muthu.arul@gmail.com>> Date: Friday, March 22, 2019 at 4:23 AM To: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>> Subject: [bess] BDF Election in EVPN VPWS Single-Active Multihoming While RFC 8214 doesn't recommend any DF election algorithm capable of electing the BDF in EVPN VPWS single-active multihoming for deciding the backup PE, any feedback on what is(are) the widely implemented/supported DF election algorithm(s) by vendors? Regards, Muthu
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Muthu Arul Mozhi Perumal
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Rabadan, Jorge (Nokia - US/Mountain View)
- [bess] BDF Election in EVPN VPWS Single-Active Mu… Muthu Arul Mozhi Perumal
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Muthu Arul Mozhi Perumal
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Muthu Arul Mozhi Perumal
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Satya Mohanty (satyamoh)
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Muthu Arul Mozhi Perumal
- Re: [bess] BDF Election in EVPN VPWS Single-Activ… Satya Mohanty (satyamoh)