IETF Logo Mail Archive

Re: [Idr] BGP flooding and AS-PATH

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Mon, 11 March 2019 10:41 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 9B805130F39 for <idr@ietfa.amsl.com>; Mon, 11 Mar 2019 03:41:27 -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=ZK6ZE0Tr; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=i+W4CS2m
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 410MkAE3iKVG for <idr@ietfa.amsl.com>; Mon, 11 Mar 2019 03:41:25 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61BD9130F3C for <idr@ietf.org>; Mon, 11 Mar 2019 03:41:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11020; q=dns/txt; s=iport; t=1552300885; x=1553510485; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lB4IdmaqSqCPo8nMkdAVwqIF6ralqikmBt9OWop3Chk=; b=ZK6ZE0TraOK0KcqeEm7iu6HfBdJPwoGcuRzmgOatf1ezMnDvs++XGgUw u1f5nQqwVnen1DBfxwo7vNATYjQDueuEsBo9SFRINxWHxYAnRWimDnCQl 4MQkZGOPzT9vIqNHcAZploktY63ciR+n4DP1ns6XNFImRvu7m3wc9od5g o=;
IronPort-PHdr: 9a23:5M2dKRR7ebkYXvBaX2qwx3TkqNpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESUDNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOi83AM1ESHdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAADOOoZc/5tdJa1kGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDS8kLANodAQLJ4QJg0cDhFCKZIJXkjOFcxSBEANUCwEBIwmBS4J1AheEIyI0CQ0BAQMBAQcBAwJtHAyFSgEBAQQjChMBATIFAQ8CAQgRBAEBKwICAjAdCAIEDgUIgxuBEUwDFQECDKQTAooUcYEvgngBAQWEehiCDAMFgS8BiywXgUA/gVeCTIMeAQECAYEmOiuCXTGCJoxNhAiHKowlCQKHT4tUgXmFZoofgTyQXYxiAgQCBAUCDgEBBYFHOIFWcBWDJ4IKg26FFIU/cgEBgSaPFAEB
X-IronPort-AV: E=Sophos;i="5.58,467,1544486400"; d="scan'208,217";a="531443283"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Mar 2019 10:41:24 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x2BAfObX017903 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Mar 2019 10:41:24 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Mar 2019 05:41:23 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Mar 2019 05:41:22 -0500
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 11 Mar 2019 05:41:22 -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=lB4IdmaqSqCPo8nMkdAVwqIF6ralqikmBt9OWop3Chk=; b=i+W4CS2mak87xsAQEFJ8nGIjeurcJjk2WsC1XAfRsGJ+QZarcQ6PxpFp5qZxuoE8mumZ3O8Xe6QBlRF+c73yC1DQm02/rdIzbB1jzHwEzgYiaNQQBIZdg8fK8rm9KUcIoZFLE7KOS+w19M4FHfKp3uZnr3CYw1gr5GdXcX8GhXQ=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB2608.namprd11.prod.outlook.com (52.135.91.29) 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 10:41:22 +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 10:41:22 +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+27wJYHhaEaQEafQWwOZK8B4KYGNiRA
Date: Mon, 11 Mar 2019 10:41:21 +0000
Message-ID: <SN6PR11MB284547928521AD7AABD3D6AFC1480@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <CAOj+MMEH276xQscJDXaGCH3wmZZynkfP+TJD-Zxd06ZyfxU1YQ@mail.gmail.com>
In-Reply-To: <CAOj+MMEH276xQscJDXaGCH3wmZZynkfP+TJD-Zxd06ZyfxU1YQ@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: 8f0f7e9b-0d2b-4f7c-7d2c-08d6a60e1a58
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:SN6PR11MB2608;
x-ms-traffictypediagnostic: SN6PR11MB2608:
x-ms-exchange-purlcount: 1
x-microsoft-exchange-diagnostics: 1;SN6PR11MB2608;23:psc2UkRIqz+V/ExY/dQXYkpMAom4OX67Af9ys5/7YXh45NHn8ZG7Cj6Mxip9ODEL6a1o/fbQ9DDVPLG6oVLpXJNQ1KbV0cdtrmGpiJQws+lXHJR/KsHbGpY/RLlheblOqe74BkqdUgXAZg3fwb861m1kxcSCC5a0sOS6S5VCn2RhlZgj8rPA6TeAbKzf7cbdyHDLrwvgd+TTd1Du+df0rNMQpZUeqeEFOf3Svb9I7go7I7u4z7G9bdHbDzFLNZc3g3O2zirsS3FSz8peIN+tFxqNoyCAlPKsltRiESLnjnDP0DT0RUPwXqhUUNicJyFOcwnAaCfVDyxbQ7rwS6+5WURQ3KW6RLDylCG6tcJUxdsBxe9waVznc3Pdund9uS6VdNQ4gTRdMWjMFrPPqOJp9q7TmY9XPURT9yUkpm3qTdPwNcoinWtSOipJSj0SgquhAS3pwz1+cu3EDEUuEHO9HfnHvK9MBDDDeAz6eRMMpO+GFQDq19j49GyjsyXqollWr5r/BDc/JEabPd0YUGtcSROlIbwyfc2Qc2bYRlZkJ4DC725bOTsYWQpdRBXlxcLFmNdapJsR8vzYNlYZZT+31kOWC8/boK4lhh49HqweoaFy16ChtcEOqrOalU7BCJayDgi9jMFAZJ012jpVJ/OW4bFsZmymbveiK+VRt13/+EBO6bFPCtGvlHZza3agUA3aotmrJwsPHFRyO9biyqN5gCXViUUFYZtdCV/gLWdSC5/5C7fjmDszFQp48fDWAmO5WSXeFPUfCIoMO/hdKIbBmpFor0EOvtgxYxvc7HnX+ZIySzShYazPdUXcB8tGPMWqShS3wLq+viInJpTAFuiq7JYHHdtTlg7l2cInAIruuXc6JnNcS6S0OFfQalb/vOTdznOcvRb/rV6Mrk3QOx5z2smg2nl04qKaqL2mFSzgqH9ASR+0QP2YsxLvdgvxu5dXVCCDKQokL4b7VSZZaGEL+DbLaqGso1LNVHxGNcfv+qhyf51SSRSv9mJtb3bzjW+tpRyJgQeRBkqDq12qrtFZwYG4QgP1WdgXVtXP3J14vM2U/uZA1YPwEJb+pkj5jmwdOZhSSNVHoe4FnANZn3KWfofV2/zHuhoU0bXwWTMT4qLxHf1eScepDm69w1s7gC8HEo7b4vxoLDetOqQ14JhpDaWwgKltMZ1nbjSftAicefAqAd+YbuI853w8M5ghyCPWafw6bFoRUPlUxUzywlXbFxxfi//cWeAfHbOoquz3cU+GybZYbk8e/gp80vDTxTfb
x-microsoft-antispam-prvs: <SN6PR11MB260828F85B4925957E254089C1480@SN6PR11MB2608.namprd11.prod.outlook.com>
x-forefront-prvs: 09730BD177
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(396003)(39860400002)(136003)(376002)(189003)(199004)(6436002)(4326008)(53936002)(478600001)(81166006)(81156014)(9686003)(236005)(54896002)(476003)(55016002)(76176011)(99286004)(11346002)(8676002)(6306002)(7696005)(7736002)(53546011)(6506007)(486006)(186003)(102836004)(105586002)(6246003)(106356001)(446003)(74316002)(25786009)(46003)(6916009)(2906002)(606006)(9326002)(52536013)(97736004)(33656002)(71190400001)(5660300002)(14454004)(6116002)(790700001)(316002)(71200400001)(86362001)(966005)(68736007)(256004)(229853002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2608; 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: yOjAx6kXigvzpHgjmDFvY2Yfj9WoxWYPpw2LeEQBs/hGJwcDyoa+qk5hN5JqOrH8UIlYW2Am2pEnClmj6Xu96Jyhomdy0HzvNl7kjQqFdU5Iezoye96BhDBh9UBlZjP7Bi7Q/hRBpdaFiP08JRo8tfng7fkd/gD0lYbiX2XQVBtXY2LoV1QXtVE370JzfB82lzT25zctyQcP0MyMVonff/V7UmbjvVBtN+7KVR90MD2jJbkODqYZJHHVLanMWZacNVnmT/l6HuLBLdvXE4qKRbV1Xk0lA2YbmU/gebX+PHUiYi9TBXAJAT/Ai/STQExQcCO8TsvKwOZNIw3faB6ggxyc6p3Kj5wNV3paxfpobzgyJpq8f2eKgyuD+Tk/KEyIxLxS5BUmc/Ufds81kMcVZ+bERAr2J7fc0e0Gvt0AbdY=
Content-Type: multipart/alternative; boundary="_000_SN6PR11MB284547928521AD7AABD3D6AFC1480SN6PR11MB2845namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8f0f7e9b-0d2b-4f7c-7d2c-08d6a60e1a58
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2019 10:41:21.9932 (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: SN6PR11MB2608
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VdxyqToVNf2DcF0v3NNfVDrx7gU>
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 10:41:28 -0000

Hi Robert,

Please check inline below.

From: Robert Raszuk <robert@raszuk.net>
Sent: 11 March 2019 15:05
To: Ketan Talaulikar (ketant) <ketant@cisco.com>
Cc: idr@ietf. org <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.

v2.23.0 | Report a Bug | By Email