IETF Logo Mail Archive

[Bgp-autoconf] "BGP Logical Link Discovery Protocol (LLDP) Peer Discovery" Requirements

"Acee Lindem (acee)" <acee@cisco.com> Thu, 27 February 2020 19:11 UTC

Return-Path: <acee@cisco.com>
X-Original-To: bgp-autoconf@ietfa.amsl.com
Delivered-To: bgp-autoconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 473323A097B for <bgp-autoconf@ietfa.amsl.com>; Thu, 27 Feb 2020 11:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=OlUXfD/r; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=fthSg6Nr
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 7zziwxiZbYNt for <bgp-autoconf@ietfa.amsl.com>; Thu, 27 Feb 2020 11:11:50 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C757D3A0978 for <bgp-autoconf@ietf.org>; Thu, 27 Feb 2020 11:11:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14419; q=dns/txt; s=iport; t=1582830709; x=1584040309; h=from:to:subject:date:message-id:mime-version; bh=4yv95Z8ALOqsSABBHunmdki+aZF/jDOueT6hJ0XUuIk=; b=OlUXfD/rHAgrGqWw4xXowUNZUG65EgPqDAEaF9u7RkXqhDotfNFHRUx/ BDqk9SmPvV7h5mpVl74AbRRaNddERjCu7+/HYxjbD34V7tkrB8Z3xPKhQ wffd+9EFfRvrxZynjQMkFONzBL6FFBGLNPw9Ws9EVAGRT2rtB+nHL/l3u o=;
IronPort-PHdr: 9a23:mRHjpRPMXt1o+hi8tYgl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEuKg/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDOIdJSwdDjMwXmwI6B8vQAEb2IdbhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYEADVE1he/4cNJK1mg2YvUAVsWCAECyqEFINGA4pnTpVDhGKCUgNUCQEBAQwBAS0CBAEBhFmBcSQ4EwIDDQEBBQEBAQIBBQRthTcMhXwRChMBASYSEQFKAgQwJwQBLQeDBAGBfU0DLgGlHgKBOYhidYEygn8BAQWCRIJIGIIMCYE4jCUaggCBEScgimYygiyNTIMZhXCZRQqCPJZlHJsujnCbRwIEAgQFAg4BAQWBaSKBWHAVZQGCQVAYDZIQilV0gSmOCgEB
X-IronPort-AV: E=Sophos;i="5.70,493,1574121600"; d="scan'208,217";a="486765202"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Feb 2020 19:11:48 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 01RJBmS2024171 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 27 Feb 2020 19:11:48 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; Thu, 27 Feb 2020 13:11:47 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 27 Feb 2020 14:11:45 -0500
Received: from NAM12-MW2-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; Thu, 27 Feb 2020 13:11:45 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eyOUS79Mol/EWIK0xycFMl81Q76Iz18O/PeRohCLYQk9P+hi9Qd/nbYHoR1HrHRWnhccrBx4l2/Da+B0r8VGrv622yS4dQynYg6tFm2oOwrm37K60JBFxmIViphEHujsO6F/dXqFQkDU6v0+EbNhC7DX3+skS3GFm3d6CjHcix8ro7uIauJ5lCMacpj5VJizIabGt+ftSeuGtNHW7uYOBNn2ti1bNDHDPEXscobBxrPgedx+a1wqw7GluTdTXXLhf1EQbL2MT7/5GU+2M+fW2S1Fxx/lhm1ibbLRa8kX4OGFSh4Qq3NmXUI8vyCkRRzqw8bZk9hs0h6jN23ENJMllQ==
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=4yv95Z8ALOqsSABBHunmdki+aZF/jDOueT6hJ0XUuIk=; b=LQLimjG+ir/WDATw60HQ4Lw4sAT6MvWfAwbnWeuUrVUIsi7BSVOuXYNCLnxmzd2DrRDWg6C9jQoGLkEBWihCPySF6MpSrJ2nNnDPV51oi52tUmZikGVEVOx47Jd2fo9LVV3L8OHqP/KgHAwUWMNpPp24XxancnLeABoDutjOVyyQltdeKGZy9ZuE772M+IiaKgf6zWNLrSFXNdHzP+BFVhnGIpUvVAPrlsd1IYh/S/grYRdPf7WnhOvAC5jBpOSVaul6J/Pqa+be/cINzzLVyaq/lOxZodspE5Xlb8/I76NK+UMYXgZDsBxoaKeVg+i9EQLZNFb35blFD61Vlr/FCw==
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=4yv95Z8ALOqsSABBHunmdki+aZF/jDOueT6hJ0XUuIk=; b=fthSg6Nrl5aKR+V/G3dg8uak4HVDo6sjyC6xHzLX/n1uHdh3VwqBuMX9YRd7PzUEImN7SwJ3d4NbcKhGLLW2+qzCRZjc/EMVQOGaDWNyI+4eVfRkoW/xOaDwFybRbINf6t0vh5bL3sD24FoIoDi0aGbO8p5Q2pCtKBNDBOgn9Zg=
Received: from MN2PR11MB3805.namprd11.prod.outlook.com (2603:10b6:208:f4::12) by MN2PR11MB4694.namprd11.prod.outlook.com (2603:10b6:208:266::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.21; Thu, 27 Feb 2020 19:11:44 +0000
Received: from MN2PR11MB3805.namprd11.prod.outlook.com ([fe80::b8f0:38a8:919c:f261]) by MN2PR11MB3805.namprd11.prod.outlook.com ([fe80::b8f0:38a8:919c:f261%6]) with mapi id 15.20.2750.021; Thu, 27 Feb 2020 19:11:44 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
Thread-Topic: "BGP Logical Link Discovery Protocol (LLDP) Peer Discovery" Requirements
Thread-Index: AQHV7aG/+8evezylP02ccOxoFCZBNA==
Date: Thu, 27 Feb 2020 19:11:43 +0000
Message-ID: <18ABC497-4F9C-45CB-8AFF-42B48C90A54B@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.22.0.200209
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1007::68]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fb3bd69a-d969-4084-5fa0-08d7bbb8e251
x-ms-traffictypediagnostic: MN2PR11MB4694:
x-microsoft-antispam-prvs: <MN2PR11MB4694B1A0FBB126F90C1E9488C2EB0@MN2PR11MB4694.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 03264AEA72
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(39860400002)(376002)(136003)(366004)(396003)(189003)(199004)(8676002)(6512007)(316002)(186003)(5660300002)(110136005)(6506007)(71200400001)(66446008)(81166006)(64756008)(76116006)(66476007)(66946007)(2906002)(36756003)(8936002)(86362001)(2616005)(81156014)(478600001)(66556008)(33656002)(6486002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4694; H:MN2PR11MB3805.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: VZ8L2Yec2NAY8ZwaYwGHWxXQhqH0f3D+h73qeDOHp5Y5UuzmaM6YMnssQ+XX9rflMmeZ+rwi2j3PGSwFLCEcGNd5HHvp8OZiLrgyQv3Gg9RY7+4acjQ05YzFYraTwIzKOuTMLtzFIWLhmMg1KMVy2ss92as1hCNhfWHqMkTUnYfxRIiJebcy3s+5s1i21H2jAdoHSUsFP/4BFJlEnIlCrzA2XZJm44s0KorBskU94z4kqXaaJatonhm8qOLDAZbCuKrWvOra3KJ+O4gxICHgHtYP+Kpefk2BjAEpav7V8mZpc8xhkQJUdu3oA40flphTK7mCsfcTQOsalv3mL/kZxxax9mOqFlsJ0hGPrCSH1dm/Haj34mQwBjPllhXOXCExakvZM6SbHfjDHEkzJ86mXkaJbtzxz8eFzh7NEWseR1XEkXaUEA9SwFC8PyQQQxc9
x-ms-exchange-antispam-messagedata: +Dn+07ez7E/h5L2YKwhrZRmw/4BeeVieFxZf9hyUj0/zVteMOHna0K7MgMyntYFKH+0nWUVY/YIvqiHQF8GuR5UCERs+UZeHniPgdLcWaORpPKRuFkAAt5bhP+d8grTzvLc4u2AsRC8fYGzKwFlMGpSyCG81bgtdV7GqbGxRh28=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_18ABC4974F9C45CB8AFF42B48C90A54Bciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fb3bd69a-d969-4084-5fa0-08d7bbb8e251
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2020 19:11:44.0175 (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: 6KFAdYW38oaC1vWxvIFJ4zb15ffmxgpvDDbu199Rqs761qL2d00QeLey5wktbwUX
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4694
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/b9L8egBlsV-fyepKOoWqDhPGNKA>
Subject: [Bgp-autoconf] "BGP Logical Link Discovery Protocol (LLDP) Peer Discovery" Requirements
X-BeenThere: bgp-autoconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP autoconfiguration design team discussion list <bgp-autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bgp-autoconf/>
List-Post: <mailto:bgp-autoconf@ietf.org>
List-Help: <mailto:bgp-autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 19:11:58 -0000

As I see them, the primary requirement driving our draft are:


1.       Make use of a currently implemented and deployed DC switch protocol to reduce the cost and complexity of the draft. Adoption of this draft would certainly not preclude adopting more elaborate procedures for other requirements.

2.       Allow discovery of BGP IPv4 or IPv6 peering addresses and ASes for directly connected switches in a data center.

3.       Allow discovery of the switches session group-id which could be leverage to determine the role that Jeff alluded to in the conference call. This would also be used to self-configure and verify the fabric topology.

The secondary requirements fulfilled by the draft are:


1.       Discovery of the neighbor’s BGP identifier for possible consistency checking or to avoid connection collisions.

2.       Discovery of BGP authentication parameters.

3.       Discovery parameters relating to the BGP peer session (e.g., the local address Sub-TLV).

I’d like to stress the first requirement that our draft fulfills that differentiates it from all of the other proposals. A minimal solution that meets the requirements is better than an over-engineered solution that isn’t required.

Thanks,
Acee

v2.23.0 | Report a Bug | By Email