IETF Logo Mail Archive

Re: [Lsr] draft-ketant-idr-bgp-ls-bgp-only-fabric

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

Return-Path: <ketant@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B255B130F3E; Mon, 11 Mar 2019 03:11:54 -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=YQJiQ85V; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ixB8Oiqb
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 wiS302p7Sqhr; Mon, 11 Mar 2019 03:11:51 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A8B8130F3C; Mon, 11 Mar 2019 03:11:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12110; q=dns/txt; s=iport; t=1552299111; x=1553508711; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Du36xVwe4JY4y0gjhglIJ4R+Ny+UJqmZhvQ8bCgrHII=; b=YQJiQ85VlWReuBridc4P6ZSfxDpL6PBcQk5CQCM9Banf7/g+dXdtDOxO jV7w2bT3Szg1o7pB0E2SwoG2DvJ2qfduJS+RFIqaTIDFMw04xaqxH5Zsp cG/O9gziyISiYqc9MPCFYNIWomF7ZT+cIiD2tEDUhDcpNBaCKOOM995b9 Q=;
IronPort-PHdr: 9a23:1ecS3RVCfBemiAuA/mcu+Hkk9MnV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSANSJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtank5EdhLUkNN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAACbM4Zc/4gNJK1kGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDS8kLANodAQLJ4QJg0cDhFCKZIJXkjOFc4EkA1QLAQEshEACF4QjIjQJDQEBAwEBBwEDAm0cDIVKAQEBBCMKEwEBNwEPAgEIEQQBASsCAgIwHQgCBA4FCIMbgRFMAxUBAqQbAooUcYEvgngBAQWEehiCDAiBLwGLLBeBQD+BEUaCTIUDgwgxgiaMTYQIhyqMJQkCkyOBeYVmg0mGVoE8nT8CBAIEBQIOAQEFgUc4gVZwFYMnggoMF4NLilNygSiPFAEB
X-IronPort-AV: E=Sophos;i="5.58,467,1544486400"; d="scan'208,217";a="243877739"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Mar 2019 10:11:50 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x2BABoGE015859 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Mar 2019 10:11:50 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Mar 2019 05:11:49 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Mar 2019 05:11:48 -0500
Received: from NAM04-BN3-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; Mon, 11 Mar 2019 06:11:48 -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=Du36xVwe4JY4y0gjhglIJ4R+Ny+UJqmZhvQ8bCgrHII=; b=ixB8OiqbTPWUbPFgMf3UmwBVhRpMKXf97jwl2iZ3PJ9DBgL079OJAOhoB/O7YgH9I0mvrsQW/uBpSpKqoMgdoAzEymIoCQkyV6MJE2pIITsRfQvyAKuOtYdyfHisfmdS4WXV77WhVLCVaWHGE+WroVNL3O3UmOCkGR5o2QuTLjs=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB2960.namprd11.prod.outlook.com (52.135.124.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.21; Mon, 11 Mar 2019 10:11:47 +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:11:47 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Robert Raszuk <robert@raszuk.net>
CC: "idr@ietf. org" <idr@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: draft-ketant-idr-bgp-ls-bgp-only-fabric
Thread-Index: AQHU11u2Esy9S6n3LkKjkXKzoMZcmKYGM+Dw
Date: Mon, 11 Mar 2019 10:11:47 +0000
Message-ID: <SN6PR11MB28455D5C90231EA6DC2D9239C1480@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <CAOj+MMFp9=56e8v3V-nhDJyvTVrwY1YwDa5LQCyfgVnJMjgz9Q@mail.gmail.com>
In-Reply-To: <CAOj+MMFp9=56e8v3V-nhDJyvTVrwY1YwDa5LQCyfgVnJMjgz9Q@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: fc854fcd-7fb1-4d27-4d18-08d6a609f8d8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:SN6PR11MB2960;
x-ms-traffictypediagnostic: SN6PR11MB2960:
x-microsoft-exchange-diagnostics: 1;SN6PR11MB2960;23:9pJpf2pwetlwiu7a8yXqLFJwshwx6w0vM8oi5X4SCqvCcg0qyV9LVCkfNaqbThsofh8empMvZS31qajGVZH4YgdCc7ppjMQsTAc9SYNRTmAzOJppv/bGS7UHuRF3Gtw7DkjHns/SaGT5SoIezQnY1JSRsa8wsnxqNuZonKPXQLH/Jvm+jkRoQaDZtk4T8WmIFSzzPF7nv4GMLMI4aBhVtwSRq/9Ao5C5foZHF7sbJqOW/dt67J0Fdwwa81kAR0UP3+WPVMuVxWVzqQSU6r7VOexF1oSPKveq319Zg3aUq5ooE1R7JY1G20EPj5jsuU8NeU2aSHJee/7UGzzSVRD4Qgi6XnvuoQv+6sFDWW2+l6djffrcs7tZNo2/N2dOAPt8fUSxEuMGvcabnMZn4F8Qi5e/TGQ7zckCzWv5M86GM9jCmb+Vt8aBXis90VHYjMywg0fyIkMynwJ8HSOAMwbyuhvxm6daL02gOwXWR803purQEXCGan8h6UHOe+58NB/L184IMB0F7TH3d/bBbNrg+/aaO9D4ZFxMgGON5Y+W9A4EPZ3rQi5gn7KeTr/x3pYQtnO7lKowRwsAko3g2V7DfXKD3AnRg1Hvazxfer0C4bpFq/5xuryRYGutulj4NGfCtPX/3eS5IdV/kOBVaFYKOgIbD7lXZkkQ/cip4YR7fu/ujqbtDZH8J3Z+JPfYl0aMQ8zQCLuH3vvmBApMiQBy6nBUxThvK0/G1pfpodt+doxyQMcSrXf7I80+Dq/9q6rUkcbqwMS0sJmEP3XXE3XlJ1r6vHh3DrBDBAdgV53vEmYilQmMjiYkQB0iYxjCab/SDsSmeFVksjpmurwvDB4hEPWOTHEbYd/bSTFQcxd5lzgb+MwI7SmcL4eOk1tZ2qrHMkdROyeX7LqN/JwNe15SM4CBPznCeVqJbADaHogY3udzmxnLZ0qZbKnNLc0cFFPWVgEE2ISmhu75H2OGaPAnL0CdpS7VvW795mkBgXPoBd9WiclLbwUd7VXV80T076RqEq/l54jrcWbLiCg2y3epu6Jy1K88u3CjoBhqjoxtSyfKkU/Rmb5Pzh2sU1loN5X6UI5Cg3R0Eg49uxNAKdDaaX6Jpsq2EEqX6eOI45HImZJWGxq3Jell/6b998P9dkNWxSCsOrSIbPXBuYLPLfNAmt8sbyIrJj/O961O9cRUCBFygjTjGPKtTDKAJkUPy2S8Zeal6CNHJz5T7/2KjYrD5gGBW0klj0fv+BnDMdY0qm/k5KdeiCre9Y7zEK4V/PwwLHnMGUD8joO20VOpMWR4Ig==
x-microsoft-antispam-prvs: <SN6PR11MB2960A41FDF0380E71386F362C1480@SN6PR11MB2960.namprd11.prod.outlook.com>
x-forefront-prvs: 09730BD177
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(136003)(346002)(366004)(39860400002)(199004)(189003)(71190400001)(71200400001)(33656002)(9326002)(9686003)(316002)(229853002)(53936002)(25786009)(6246003)(476003)(4326008)(52536013)(5660300002)(46003)(68736007)(66574012)(14454004)(11346002)(446003)(2906002)(54906003)(561944003)(55016002)(6306002)(54896002)(6436002)(8936002)(256004)(7696005)(6506007)(53546011)(99286004)(76176011)(478600001)(86362001)(102836004)(186003)(6916009)(105586002)(81156014)(81166006)(106356001)(790700001)(6116002)(8676002)(486006)(7736002)(74316002)(97736004); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2960; H:SN6PR11MB2845.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: 8yMibDEYsYn4lfI6Dq/Ffc4o82An2oRHYsQ7f8uRm4IMchSgnkjcu+MNwe7EXd5mGRSaTEWoiogJin1Cum5V2h+JGKS1hsvPb8+PjwkqIEYqc8b4Eh9Tx2F5vk8fc1PAhLqMZoDxAPPhlLyusVKjDMi3AVjTaZzgJFnQzQaJ/oB0/tLq6EQKkWTJqmaMiPDihE2kIP9wPW2k9zMwthygCJQ+A2sckMyDsjHYMYubKH1uguQPi4fqY8uAJHsSZ8gY3rQ25dc5HAxjUq8kKak7jj+/Ai2Tt8yUPODsVswKFu/MISBQSXCDlVYTyJ4htCObxdG5p5wxkEolRhK2dVi0d1yahtZVz4IHSED4tN1YQOYNRy306tdUkqsnJNsZ+82UJGPwmT0UayfoCt5fVNf8DZkPb2EzqPpqd/86zUdrMm0=
Content-Type: multipart/alternative; boundary="_000_SN6PR11MB28455D5C90231EA6DC2D9239C1480SN6PR11MB2845namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fc854fcd-7fb1-4d27-4d18-08d6a609f8d8
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2019 10:11:47.8134 (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: SN6PR11MB2960
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/KVIoGeJR5eMdVJs-4UQk3dmmf5M>
Subject: Re: [Lsr] draft-ketant-idr-bgp-ls-bgp-only-fabric
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2019 10:11:55 -0000

Hi Robert,

Please check inline below.

From: Robert Raszuk <robert@raszuk.net>
Sent: 10 March 2019 21:40
To: Ketan Talaulikar (ketant) <ketant@cisco.com>
Cc: idr@ietf. org <idr@ietf.org>; lsr@ietf.org
Subject: draft-ketant-idr-bgp-ls-bgp-only-fabric

Hi Ketan,

I have read your proposal of defining topology flooding in BGP with interest.

It seems like a pretty brilliant twist to take pieces defined in other documents with their original intention for sending IGP information (LSDB or TED) over BGP extension and now use all of those without IGP at all :).
[KT] RFC7752 did always have “direct” and “static” protocols – so it was not just IGPs. We extended to include BGP protocol for describing Peering topology for the EPE use-case with draft-ietf-idr-bgpls-segment-routing-epe

But I have just one question here perhaps to the WG or ADs.

Almost all normative references used in this draft clearly state that they were defined for carrying information present in ISIS & OSPF protocols as rather a courtesy of transporting them over TCP with BGP envelope between network and controller.

Can we now just "reuse" verbatim all of those defined codepoints as well as redefine use of BGP-LS SAFI as a new link state p2p network topology transport just like that ?
[KT] The BGP-LS SAFI is still used to report link-state information. This draft describes how it can be done even when no IGP is running and we are instead running BGP protocol (in RFC7938 hop-by-hop routing design). Each router here is setting up a BGP-LS session with a controller or a centralized BGP speaker to report the router’s own node properties, links, prefixes, etc. The objective is build a link-state topology at the controller for specific use-cases like topology discovering and TE with SR as described in Sec 6 of the draft.

At min I would like to see some analysis included in this draft of running native link state protocol possibly with dynamic flooding optimization vs running BGP as the only routing protocol with using BGP as topology discovery transport before we proceed further on this document.
[KT] I am not sure I see the contrast here. Personally, I support the dynamic flooding optimization work in LSR. There are already DC networks deployed with RFC7938 design. All this draft is introducing is topology discovery and other use-cases in the latter.

Thanks,
Ketan

Kind regards,
Robert.

v2.23.0 | Report a Bug | By Email