Re: [Idr] BGP flooding and AS-PATH

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Mon, 11 March 2019 12:23 UTC

Return-Path: <ketant@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC89124BF6 for <idr@ietfa.amsl.com>; Mon, 11 Mar 2019 05:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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=Vg7bjMKy; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=D7fLPlma
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 4U_QbpiSKMHW for <idr@ietfa.amsl.com>; Mon, 11 Mar 2019 05:23:47 -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 436241200B3 for <idr@ietf.org>; Mon, 11 Mar 2019 05:23:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17110; q=dns/txt; s=iport; t=1552307027; x=1553516627; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=q6/aOgqiCWeva9cJUSmLRZnaJpXU5itpfAejYtbkQ6w=; b=Vg7bjMKyd80BtpYK2s9DwhZ9t4kMZ1pel7Hr1bDpRZxil9XC5WZ1Wk6M r9anlqAFAlCXA2RXDSUvcVUyV5WpeXZXpWmNz0EPazzsGdIwL0oNth4p1 ToAyu3+I7VU2aAklxllED7BUSBWQWKEyTQ22fht71q7MMrGmFM9kMzHw8 g=;
IronPort-PHdr: 9a23:4J7ehx9KM02lCv9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+/bR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVc2IFUT9MNbhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAAAgUoZc/4QNJK1kGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDS8kLANodAQLJ4QJg0cDhFCKZIJXkjOFcxSBEANUCwEBIwmBS4J1AheEIyI0CQ0BAQMBAQcBAwJtHAyFSgEBAQQjChMBATIFAQ8CAQgRBAEBKAMCAgIwFAkIAgQOBQiDG4ERTAMVAQIMpBMCihRxgS+CeAEBBYR6GIIMAwWBLwGLLBeBQD+BV4JMgx4BAQIBgSY6FRYJglQxgiaMTYQIhyqLTVgJAodPi1SBeYVmih+BPIwKhFOMYgIEAgQFAg4BAQWBRziBVnAVgyeCCoNuhRSFP3IBAYEmjxQBAQ
X-IronPort-AV: E=Sophos;i="5.58,467,1544486400"; d="scan'208,217";a="245170237"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Mar 2019 12:23:46 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x2BCNj3J027613 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Mar 2019 12:23:46 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Mar 2019 07:23:45 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Mar 2019 08:23:44 -0400
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 11 Mar 2019 07:23:43 -0500
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=q6/aOgqiCWeva9cJUSmLRZnaJpXU5itpfAejYtbkQ6w=; b=D7fLPlmaW/0/Fu056H8AAEoprV23Pa0/ghb81Izmnbp5AL6Ga7DmNTmmgkCC3jhSetAn3VVd4C00jPW+Mhy1uWpYhrGjVC2UzynzYTRMA6V2WylNLAJDVIJ2a6kyFESsY+N/wxOobIK6vLina1CHI4hQPmJT94/XgwFC3u3hiiY=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB3406.namprd11.prod.outlook.com (52.135.110.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.19; Mon, 11 Mar 2019 12:23:43 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::117:6d33:4c0a:a1b3]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::117:6d33:4c0a:a1b3%3]) with mapi id 15.20.1686.021; Mon, 11 Mar 2019 12:23:43 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Robert Raszuk <robert@raszuk.net>
CC: "idr@ietf. org" <idr@ietf.org>
Thread-Topic: BGP flooding and AS-PATH
Thread-Index: AQHU1+27wJYHhaEaQEafQWwOZK8B4KYGNiRAgAAX0oCAAAhfIA==
Date: Mon, 11 Mar 2019 12:23:43 +0000
Message-ID: <SN6PR11MB2845EED04F5684DA0618D860C1480@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <CAOj+MMEH276xQscJDXaGCH3wmZZynkfP+TJD-Zxd06ZyfxU1YQ@mail.gmail.com> <SN6PR11MB284547928521AD7AABD3D6AFC1480@SN6PR11MB2845.namprd11.prod.outlook.com> <CAOj+MMGZQOosfLus46QB9_h-2YeiDx4T-28=tpK2R7sLSmCHVA@mail.gmail.com>
In-Reply-To: <CAOj+MMGZQOosfLus46QB9_h-2YeiDx4T-28=tpK2R7sLSmCHVA@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=ketant@cisco.com;
x-originating-ip: [2001:420:c0e0:1002::d9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d1ab96ee-c2ad-4d78-4642-08d6a61c66c9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:SN6PR11MB3406;
x-ms-traffictypediagnostic: SN6PR11MB3406:
x-ms-exchange-purlcount: 1
x-microsoft-exchange-diagnostics: 1;SN6PR11MB3406;23:eVbxg444JeGjEiG3iyvrUdlncxvL+5pUHPClP6F4K2HxahBBP2FLGiJfRIxhb2DwdJm//WO0oOsuHH9G9oJVTjEwgGIFa2uCOlKMoaxyqPdtO1GDRHlyEcNoSsE6gZqCAEhCOpcrqvvWUE10md2nICf+sVei5GMzt/euaowRsKdi0RqOjOhDCtIHddqtgbCSjHibWlC20PjqlIBOCcuLbHodiPzE1qp9kQ6mB5ANTR1IZ76f+kgP5DIuflNdBiLg7tvpDa+ayUQjUWkLCbx/jeet2ds+qn7Wai9iciJC8QDurl3w7Sbntoo0h9QRnsXxQuQG3a884GlheuujpvP9otcV1aV9Zu0xZtzKV6YfSWLB9LPwc/ugH6rcvOJy0s56ShSeLlX5nWKxxkZBXSRnvdt3T9cbLkprEoBgcvzJJ1Z0kyzmYnZya24kLGOIlQ+Nbyh9gF0EecRKPVRlz9fCe4AiN9A15mfk3DMs9MgYPXBddMjsQQki3aRf8f/VMeHVeM8Z7KJJR0gh23G9U5Ps2rdBuMp7raKnfJDn7UKtgqmM8DoomVRTSJV3forFlEDRzHfZLFvINAnIBLUJ0ezwUdR/6PXmTwwVsJZiFcn3mFohr4E3lTnnk4XoJ4cK/5oDfPguFDzrnJYHkXZm9Q+8jLZD0djkkTNYDo3hFhbyrHuFRy0B5IKqscqFmKdj5Em6VGO/y6kCSSpQuwqcw69vjwAcC1G0jYpdCxTvzXGVtrccixjiL6jlnV0pfdS8LMaSM+IB/xQevGFRmNg28tdWet3QUPEq+YEZmDQzZWM2BE66XUxrhyMpYGVOAs50k84FjW7SmZwLQL/Tw5OYExcRwHdx2F+YgGBgLvq8YypaZuuYI2Kq9wAM95trfZTLQPmKqyek2S/OV+PUK8usdRz0i5QRFlG3BG2FFHJiuyqJNjeUczfgiFhCmAVUff/c69a2nZnhSrKJ8bifPNrqAUBpLUJNLuPjIZIRuTGlK8VsC9x521mZfDmTWwfBHnwWlGvgKtX1QD2UON0NWwNm0AgfZeAsADZVaneYVdLKOyaHseW5wXhObvkODIh1d8hfaBvL5/mNzerX8kgsd8doxRvAWHlqN02dOFMT/dGONH2LFa4XaaCXV2EY34DQJFqysAQaJgKvsamddbgBedNw8AE89p/e50e7TxmRa6xshjp5ZV+z+A9eqGDmv0R4qbljJjlyXPdLoJ++Sbmkbnrvrzd5gZ7Sz+i88GjgXY9vYDDyppA1Hk91XmicIi/3g5S7l307
x-microsoft-antispam-prvs: <SN6PR11MB340622CB2D2242D58168F21AC1480@SN6PR11MB3406.namprd11.prod.outlook.com>
x-forefront-prvs: 09730BD177
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(136003)(346002)(39860400002)(376002)(189003)(199004)(76176011)(2906002)(14444005)(8936002)(68736007)(229853002)(106356001)(105586002)(53936002)(478600001)(256004)(46003)(6116002)(790700001)(74316002)(55016002)(71200400001)(71190400001)(14454004)(236005)(9686003)(54896002)(6306002)(486006)(316002)(7736002)(6246003)(53546011)(476003)(6436002)(6506007)(966005)(606006)(446003)(11346002)(102836004)(33656002)(81166006)(99286004)(8676002)(81156014)(86362001)(4326008)(5660300002)(186003)(25786009)(52536013)(97736004)(6916009)(7696005); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3406; H:SN6PR11MB2845.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-message-info: zXrH013q0uLew+ptE1awsE+qQlqBj5R+PACf0+7NgRZANWS3D8hUxtMrp4SBTHUnCfiJonXzQNHey/0vwLIcIqB4Dzfvledz/4yWVQCY0bbqpuTul53wPhWI5jjeADxXk7o0+Uaz7a63PhYB33a5EIu121nCne2MV+ZITJDPLQvZmwGYPY2NaLLMbpbN4I2PIpOpy6DewLUZ1/Il080oKOaLaFqRmuK5ldnYodzCBnjWdlspDz/vAE0UdphsgirsWi1tV+ISpWdny3j1g2tceNLxMqB2q/cLBj9nPMpDkWOIDsnSXOj5TDGQbg1+YwVpGlhawR3PYVVoj94bY2irD88rEYG3d1oiBmUV841bsY73+zkIHu+f4yjP/E3c/iV2DmfHq4bZRG4RiPOFWq27WdR56ssIzeaiv6i+6mVSSU4=
Content-Type: multipart/alternative; boundary="_000_SN6PR11MB2845EED04F5684DA0618D860C1480SN6PR11MB2845namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d1ab96ee-c2ad-4d78-4642-08d6a61c66c9
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2019 12:23:43.1544 (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: SN6PR11MB3406
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Gk96eXAETgsHC8mzTXEpcSy5PLw>
Subject: Re: [Idr] BGP flooding and AS-PATH
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2019 12:23:50 -0000

Agreed, Robert. Will capture this in the next update and thanks for your review and for pointing this out.

Thanks,
Ketan

From: Robert Raszuk <robert@raszuk.net>
Sent: 11 March 2019 17:08
To: Ketan Talaulikar (ketant) <ketant@cisco.com>
Cc: idr@ietf. org <idr@ietf.org>
Subject: Re: BGP flooding and AS-PATH

Hi Ketan,

I was not talking about TORs .. they will get all info just fine.

I was talking about same stage peers as they can have same AS number and with eBGP there may be a bit of challenge to get BGP updates accepted orignated by same level device.

And I was only waiting for you to mention allowas-in or as-overwrite knobs ;)

Can you reflect those options in the draft? Or at least in any other way address this scenario ?

Kind regards,
R.

On Mon, Mar 11, 2019, 11:41 Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>> wrote:
Hi Robert,

Please check inline below.

From: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>
Sent: 11 March 2019 15:05
To: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>
Cc: idr@ietf. org <idr@ietf.org<mailto:idr@ietf.org>>
Subject: BGP flooding and AS-PATH

Dear authors of draft-ketant-idr-bgp-ls-bgp-only-fabric,

I would like to ask for a small clarification on how in the quoted RFC7938 design are you going to propagate topology information between peers configured with the same AS number ? Say between devices belonging to tier 1 stage or to a sets in tier 2 stages ?

Do you assume that those switches just do not need to be aware of each other's presence say for TE purposes ?
[KT] This isn’t necessary in the use-cases where controller is doing the TE computations. E.g. a TOR can delegate end to end TE computation (from itself all the way over the DCI/WAN to a remote node) to the controller.

Specifically I am curious how are you going to accomplish it in the cases where no AS-PATH removing controller is involved as described here:


"An internal software component on any of the BGP routers

(e.g. TE module) can also receive the entire BGP network

topology information from its local BGP process."

[KT] This is a different variant of the TE use-case where the TOR itself can do TE computation. In this case, you are correct about the topology flooding via the controller when using the ASN scheme in https://tools.ietf.org/html/rfc7938#section-5.2.1 . For this use-case, there are other options and designs though (incl private AS for unique assignment to TORs, allowAS-in, etc.) to make this possible.



Thanks,

Ketan

Thx a lot,
R.