[Idr] Updates to draft-xu-idr-neighbor-autodiscovery

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Tue, 23 October 2018 03:11 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 8B7321288BD for <idr@ietfa.amsl.com>; Mon, 22 Oct 2018 20:11:24 -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_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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
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 hO6dgSR41wi9 for <idr@ietfa.amsl.com>; Mon, 22 Oct 2018 20:11:22 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6006130E57 for <idr@ietf.org>; Mon, 22 Oct 2018 20:11:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2859; q=dns/txt; s=iport; t=1540264282; x=1541473882; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=QynhbJ58qVyCpEZgAG786CMwkp+jsGbkRxxugS6JaLw=; b=eABSJuDc5Jdnl/oKmu/0Uyo3g76tIpWc69wmk/+HKEEsoD8c0u+GqTTg u3Pq+r69yWlFUERhWNN1EXM6LSWW7D3K/RF5cqrE8nSsrzhQtwA4LDt6I 2//CWwcb9TzFVZY6NsPZlQt0FuxeocDdf4AJo8WeIKDYBxAZUUSSk+6XQ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFAAA+kM5b/4sNJK1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBVS9mfygKjAOMHYINlxWBegsBARgNhEcChRUhNA0NAQMBAQIBAQJtHAELhToBAQYBODQXBgEZBAEBHzcLHQkBBBMIgxqCAQ+nV4QwAgxAhSiLUheBQT+BEYYtAQECAQEWhyECiFyVbAkCgVmFB4oIH4FSTIQniWmJJYMziV4CERSBJh04gVVwFRohgmwJixCFPQFvjEeBHwEB
X-IronPort-AV: E=Sophos;i="5.54,414,1534809600"; d="scan'208";a="189459116"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2018 03:11:20 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w9N3BKoS029023 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Tue, 23 Oct 2018 03:11:20 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 22 Oct 2018 22:11:20 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1395.000; Mon, 22 Oct 2018 22:11:19 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Updates to draft-xu-idr-neighbor-autodiscovery
Thread-Index: AdRqfg7CwT+yIlHWRWelXPmtk6vIsQ==
Date: Tue, 23 Oct 2018 03:11:19 +0000
Message-ID: <7ed1feee03204b9f86100bacc3e36347@XCH-ALN-008.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.41.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.19, xch-aln-009.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ncQt_4MMpRGi6dfGtkoX1VG8-bk>
Subject: [Idr] Updates to draft-xu-idr-neighbor-autodiscovery
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: Tue, 23 Oct 2018 03:11:25 -0000

Hi All,

An update to the BGP Neighbor Discovery draft has been posted with the following key changes:

1) Added Applicability & Requirements sections in the draft to provide context and clarity on its objectives.

2) Updates to the Neighbor TLV and Adjacency FSM for more clarity and details based on the feedback received at the last IETF.

3) Improved scalability aspects by not requiring TLVs to be exchanged in periodic hellos.

4) Other editorial changes and explanation for procedures and interactions with base BGP protocol machinery.

Would appreciate review and feedback from the WG.

Thanks,
Ketan

-----Original Message-----
From: Idr <idr-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 22 October 2018 19:03
To: i-d-announce@ietf.org
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-xu-idr-neighbor-autodiscovery-10.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing WG of the IETF.

        Title           : BGP Neighbor Discovery
        Authors         : Xiaohu Xu
                          Ketan Talaulikar
                          Kunyang Bi
                          Jeff Tantsura
                          Nikos Triantafillis
	Filename        : draft-xu-idr-neighbor-autodiscovery-10.txt
	Pages           : 33
	Date            : 2018-10-22

Abstract:
   BGP is being used as the underlay routing protocol in some large-
   scaled data centers (DCs).  Most popular design followed is to do
   hop-by-hop external BGP (EBGP) session configurations between
   neighboring routers on a per link basis.  The provisioning of BGP
   neighbors in routers across such a DC brings its own operational
   complexity.

   This document introduces a BGP neighbor discovery mechanism that
   greatly simplifies BGP operations in such DC and other networks by
   automatic setup of BGP sessions between neighbor routers using this
   mechanism.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-xu-idr-neighbor-autodiscovery/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-xu-idr-neighbor-autodiscovery-10
https://datatracker.ietf.org/doc/html/draft-xu-idr-neighbor-autodiscovery-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-xu-idr-neighbor-autodiscovery-10


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr