Re: [bess] Comments on draft-ietf-bess-evpn-pref-df

"Satya Mohanty (satyamoh)" <satyamoh@cisco.com> Mon, 30 September 2019 17:28 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 AA6EE12001E; Mon, 30 Sep 2019 10:28:32 -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, 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, 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=V9Ye9JAs; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=OKa4XWyg
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 gnhHhxlwNKX4; Mon, 30 Sep 2019 10:28:29 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ECA312004D; Mon, 30 Sep 2019 10:28:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19867; q=dns/txt; s=iport; t=1569864509; x=1571074109; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=qmAfJT7rw3pc4rNnL7uAcphSJHDAKjVU0GluNUMnW54=; b=V9Ye9JAsz5MlBCv3+bkFK6tP7/SWugFsXiqicEo06Ac6O+ru2ZsfB90q /jQ5QJ/GKjqTv0BNjPFkUuy+Wb5fZQtt8vPKnm3vkCirY9KsY4hUWXD15 wLJyLMjhOa5PzYlplgIhSqrLb+5KP/YRjUTmVm4IEMpkymoZiGyMagDvv 4=;
IronPort-PHdr: 9a23:vsgvmxWzOgEtdUad8YT7AgqaurDV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtankhFdhTXVpi/1mwMFNeH4D1YFiB6nA=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+BwBMOpJd/5RdJa1mHAEBAQQBAQwEAQGBZ4EcL1ADbVYgBAsqhCKDRwOKWk2BaiWJZ4kwhF+CUgNUCQEBAQwBAS0CAQGEQAIXgywjOBMCAwEDAgMBAQQBAQECAQUEbYUtDIVLAQEBAQMSEQQGEwEBOA8CAQgRAwECKwICAh8RHQgBAQQBEiKDAAGBHU0DHQECowcCgTiIYXV/M4J9AQEFhQENC4IXCYE0jA4YgUA/gTgME4FOfj6CGoJKgm0ygiaPZYUtiSiOKEEKgiKRCYQCG4I3h06PMY4hiiKOfQIEAgQFAg4BAQWBaSKBWHAVZQGCQVAQFIFPg3OKU3SBKY95AQE
X-IronPort-AV: E=Sophos;i="5.64,568,1559520000"; d="scan'208,217";a="347873358"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Sep 2019 17:28:28 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x8UHSR52008479 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 30 Sep 2019 17:28:27 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 30 Sep 2019 12:28:27 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 30 Sep 2019 12:28:26 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 30 Sep 2019 12:28:26 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EzP9i4LBfvE8YP6QOlHngZfDjZuMy+aeM+WpPYZ6Re+EwSOy2nHieyorFr0n+Hc9gNncMYgUtYelNl4/2Xs/fPHXdY4+iV1QbOE4iulvWnO9gMewUWh0uq5serUrJNQMVzNWjWsM5dFsfewZxsUQPn1bHYV9eNTJHpYtfC5aPzcuUxdYSljCksKGBQ1LGtUVMi9NcgqhEWRFqoRxyKX/5YGtJY1Zc1wWusozrffOBLMgVwk7TDlYjkE+HN3IeLiuzJlXs2b0N2YF386yGDFimgH/NmMEh7ren/cqpaBlAKLQputKNiwdTlKtMpXLc3Ts8hEkHm8MiYWqbAASvQO7GA==
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=qmAfJT7rw3pc4rNnL7uAcphSJHDAKjVU0GluNUMnW54=; b=U4cBqboxUVhWBM1TOopZA9ZCgqvPiKjyGSD7+GsiGMR6pzrJNMA4Fl59aLDEmztAvdj12ka/v/1mS9MjobplqFlmWSDJq87TtPjwwoAPqYYBiLmbVcZQRez3C7A9jmZOzGe3zJqlm47Twvlq8p42FsvxY776FnaKL00ODPbJlsraUw0LTrjwBoh2A6bI08lHiwb3Vr5raH3JS4g2T/pUAkLPu5AFrxCzcGyZmPUUuV83rZEiug6y6XEFdZjeM2iOuGs3CDO3TVqKGRYW/x/vdXKDyZBCC/DVlLT0BG4Ux5tL84+HD7wRrutyOdUu96gty2YpLLJlnVtIbFgsuiAqMw==
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=qmAfJT7rw3pc4rNnL7uAcphSJHDAKjVU0GluNUMnW54=; b=OKa4XWygq0VOW44lSTddULyjydOspD9x7onrW+oF8ZjRrxatRfXznuXXW+/3B1HqE4Pm7KfcXW1/xYwwMaj5ebh2NDeVGlE1lsVhNnyF9PAl/n43AUiuLwicHhGUpJEvLeDzjsFUJStt1lGsV79gNxX/HaegSiSxFyL3uFRzcks=
Received: from SN6PR11MB3102.namprd11.prod.outlook.com (52.135.126.204) by SN6PR11MB3326.namprd11.prod.outlook.com (52.135.111.76) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Mon, 30 Sep 2019 17:28:25 +0000
Received: from SN6PR11MB3102.namprd11.prod.outlook.com ([fe80::e9f7:8614:fad4:b268]) by SN6PR11MB3102.namprd11.prod.outlook.com ([fe80::e9f7:8614:fad4:b268%5]) with mapi id 15.20.2305.017; Mon, 30 Sep 2019 17:28:25 +0000
From: "Satya Mohanty (satyamoh)" <satyamoh@cisco.com>
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, "slitkows.ietf@gmail.com" <slitkows.ietf@gmail.com>, "draft-ietf-bess-evpn-pref-df@ietf.org" <draft-ietf-bess-evpn-pref-df@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Comments on draft-ietf-bess-evpn-pref-df
Thread-Index: AdV1p77phYo3FgjZSc+woeKyumxlRABH2m+AACyoeIA=
Date: Mon, 30 Sep 2019 17:28:25 +0000
Message-ID: <2C5B9075-1042-4474-B646-0E1028F3CA4F@cisco.com>
References: <045c01d575a8$71a5bb60$54f13220$@gmail.com> <48058166-E2F2-46D4-9C69-91FA2400F5A3@nokia.com>
In-Reply-To: <48058166-E2F2-46D4-9C69-91FA2400F5A3@nokia.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:30d:1254:d4c3:469:7f53:d58b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 55b1508e-0ea3-4e09-bf1d-08d745cb99d4
x-ms-traffictypediagnostic: SN6PR11MB3326:
x-microsoft-antispam-prvs: <SN6PR11MB33261F3B7A132CCDDE33CD0ED4820@SN6PR11MB3326.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01762B0D64
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(396003)(366004)(136003)(346002)(189003)(199004)(2906002)(6246003)(2501003)(6486002)(316002)(2201001)(7736002)(36756003)(110136005)(229853002)(296002)(46003)(446003)(11346002)(6306002)(54896002)(2616005)(476003)(486006)(6512007)(33656002)(256004)(99286004)(71190400001)(66556008)(66446008)(66476007)(64756008)(102836004)(478600001)(76116006)(91956017)(66946007)(6436002)(71200400001)(25786009)(5660300002)(76176011)(9326002)(6116002)(8936002)(86362001)(186003)(8676002)(53546011)(14454004)(6506007)(81156014)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3326; H:SN6PR11MB3102.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: y8ZADl/fpcsYEz68EukhCrRpa/NSbzg1MQyMuq7Hht9NNaHhnpSOr0qJcE2JQV+csmWGyZ3/K8hsrL2M65RwLWn3YspReaTNZ5ylBtlKgErXtHBFcrGF+VLY0bkBZioi7J3t5cT8ohdsvyeEt6kjhN65vyd+pZDgP4mj3Pvjwl2EETnVXUQ9tPwO81SueQYt3JsJ3R6WcpMu6R7KoGBd9IqBH3mO8GFl3l4IKYDgP75hQjpClLWGMSYf74fKjIe4ePm7dhJSN6MjZH0WwYMYyuCOgQia9EPPUFdz2J71xV356gR7vX+Ps/rJlimy1XD/EzXsZuIMi16XgbwmW3UOjnavpc7ILzFPFTVPrB6uqUobvKmgoPO6cBNJ6nlauSpYqw+DNA4E7oF1ZnwztH0hfK2EwU59md8xNb9Si69XAA4=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_2C5B907510424474B6460E1028F3CA4Fciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 55b1508e-0ea3-4e09-bf1d-08d745cb99d4
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Sep 2019 17:28:25.6179 (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: eSp9Cqj4x8lvqjpidijLD03zKs3biNM8AlYTIRVMbRc+bqw97JGWMRkoBCqBzylUeUMqMcAlK5/hTQ04LUm5Mg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB3326
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.28, xch-rcd-018.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/o-wJmK9TJ2iulB_jXwn3Fre8Q-w>
Subject: Re: [bess] Comments on draft-ietf-bess-evpn-pref-df
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: Mon, 30 Sep 2019 17:28:33 -0000

Hi Stephane,

An alternative way to guarantee precedence per vlan (i.e. the most granular) rather than the vlan-range in the vlan-based service models, could be by using the DF extcom in the per EVI AD route instead of the procedures in Section 4.2 relevant to the vlan range.

But this may not be required in a real deployment and specification of precedence per a vlan-range is probably sufficient.

So, I agree with Jorge regarding his observation of vES.

Best,
--Satya

From: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>
Date: Sunday, September 29, 2019 at 4:10 AM
To: "slitkows.ietf@gmail.com" <slitkows.ietf@gmail.com>, "draft-ietf-bess-evpn-pref-df@ietf.org" <draft-ietf-bess-evpn-pref-df@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Subject: Re: Comments on draft-ietf-bess-evpn-pref-df
Resent-From: <alias-bounces@ietf.org>
Resent-To: <jorge.rabadan@nokia.com>, <senthil.sathappan@nokia.com>, <prz@juniper.net>, <wlin@juniper.net>, "jdrake@juniper.net" <jdrake@juniper.net>, <sajassi@cisco.com>, <satyamoh@cisco.com>
Resent-Date: Sunday, September 29, 2019 at 4:09 AM

Hi Stephane,

Please see in-line.

If you think we should add some text making my comments below more explicit, I’d be happy to do it.
Thank you.
Jorge

From: "slitkows.ietf@gmail.com" <slitkows.ietf@gmail.com>
Date: Saturday, September 28, 2019 at 4:57 AM
To: "draft-ietf-bess-evpn-pref-df@ietf.org" <draft-ietf-bess-evpn-pref-df@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Subject: Comments on draft-ietf-bess-evpn-pref-df
Resent-From: <alias-bounces@ietf.org>
Resent-To: <jorge.rabadan@nokia.com>, <senthil.sathappan@nokia.com>, <prz@juniper.net>, <wlin@juniper.net>, <jdrake@juniper.net>, <sajassi@cisco.com>, <satyamoh@cisco.com>
Resent-Date: Saturday, September 28, 2019 at 4:57 AM

Hi Authors,

I had a look on your draft and I have some concerns/questions that I would like to discuss.
I like the fact of being able to tune the pref DF election per VLAN range, however:

-          Don’t you think that using a local configuration may open to inconsistent configurations resulting in issues ?
[JORGE] We discussed quite a few times whether we should signal the vlan ranges for which you desire high_pref or low_pref. We ended up coming to the conclusion that it is better/simpler (and already supported) to define virtual ethernet segments for ranges of vlans and then have the default high_pref that is defined in the spec. That is less prone to errors. E.g. on a given port, define two ranges: vlan (1-2k) --> vES-1 and [(2k+1)-4k] -->vES-2. On a given PE, vES-1 and vES-2 have different pref values.


-          How does the high_or_low works if I have more than 2 links in the ES ? (multihoming with 4 links with 4 levels of preference ?)
[JORGE] if you want 4 levels of preference so that each of the 4 PEs is DF for a range of vlans, the easiest way as discussed above is to define 4 vESes. The high_or_low is an easy way of having load balancing if you have only 2 PEs in the ES and you really want to define only one ES.

Thanks,

Stephane