Re: [Idr] 答复: WG adoption call for draft-xu-idr-neighbor-autodiscovery

" 徐小虎(义先) " <xiaohu.xxh@alibaba-inc.com> Tue, 17 July 2018 01:07 UTC

Return-Path: <xiaohu.xxh@alibaba-inc.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 62195130E7B; Mon, 16 Jul 2018 18:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.02
X-Spam-Level:
X-Spam-Status: No, score=-1.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alibaba-inc.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 FTXd9wqPHAjj; Mon, 16 Jul 2018 18:07:34 -0700 (PDT)
Received: from out0-156.mail.aliyun.com (out0-156.mail.aliyun.com [140.205.0.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A8D0130E52; Mon, 16 Jul 2018 18:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1531789648; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=TQRbdSzTz9F9B9aW9/npsDMFJ4bK46nwz5AqmaESR1c=; b=nk2C9TBLeoNAX+mbMj4KNkkbZEF0lqbfFhxEVpcMQvgzk/06UfnmsvyxnhKna3Izn7dlLbpaZPp0wsLhBJ64T2YbBqZuW7kjzTHXUsdwLQ2AI9GSyq0DYGZ8Z3SkE/TzkO7EOkpgu47d49tzzOkIoQGXCG+FE9q8nfFM7yaZof4=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R291e4; CH=green; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03308; MF=xiaohu.xxh@alibaba-inc.com; NM=1; PH=DW; RN=4; SR=0; TI=W4_5305839_v5ForWebDing_0A9326CB_1531789198007_o7001c125b;
Received: from WS-web (xiaohu.xxh@alibaba-inc.com[W4_5305839_v5ForWebDing_0A9326CB_1531789198007_o7001c125b]) by e01l07389.eu6 at Tue, 17 Jul 2018 09:07:25 +0800
Date: Tue, 17 Jul 2018 09:07:25 +0800
From: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
To: Idr <idr-bounces@ietf.org>, Lizhenbin <lizhenbin@huawei.com>, Susan Hares <shares@ndzh.com>
Cc: "idr@ietf.org" <idr@ietf.org>
Reply-To: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
Message-ID: <1ec22cba-dbee-4b65-8a75-a8afa213e8bb.xiaohu.xxh@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent revision 268][W4_5305839][v5ForWebDing][Safari]
MIME-Version: 1.0
References: <19AB2A007F56DB4E8257F949A2FB9858DC3B8B4C@NKGEML515-MBX.china.huawei.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F45D82A@DGGEMM532-MBX.china.huawei.com>, <CA+b+ER=UVaE61h57m3z=TpaS9-CQs8oahMu-tuA9i1521Jad9w@mail.gmail.com>
In-Reply-To: <CA+b+ER=UVaE61h57m3z=TpaS9-CQs8oahMu-tuA9i1521Jad9w@mail.gmail.com>
x-aliyun-mail-creator: W4_5305839_v5ForWebDing_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTJfNikgQXBwbGVXZWJLaXQvNjA0LjUuNiAoS0hUTUwsIGxpa2UgR2Vja28pIFZlcnNpb24vMTEuMC4zIFNhZmFyaS82MDQuNS42La
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_26954_4dfea940_5b4d414d_279798"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/PNEAIvriPknXIWbJ75uy17tjNYA>
Subject: Re: [Idr] 答复: WG adoption call for draft-xu-idr-neighbor-autodiscovery
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.27
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, 17 Jul 2018 01:07:37 -0000

Robert,

If you believe that some TLVs proposed in draft-xu-idr-neighbor-autodiscovery are unnecessary, please list them explicitly and then we can consider how to address your concerns.

It seems that you have denied your previous argument as below. It seems like a good start:)

"...Sure you can do that. But perhaps someone could just explain (s/explain/complain?) what is so difficult in configuring your TORs and SPINEs with provisioning tool ? Why in DC there is need for this automation in BGP ? "

Best regards
Xiaohu
------------------------------------------------------------------
From:Robert Raszuk <robert@raszuk.net>
Send Time:2018年7月16日(星期一) 23:33
To:Lizhenbin <lizhenbin@huawei.com>; Susan Hares <shares@ndzh.com>
Cc:idr@ietf.org <idr@ietf.org>
Subject:Re: [Idr] 答复: WG adoption call for draft-xu-idr-neighbor-autodiscovery

Hello Zhenbin,


BGP is widely used and simplifying the provisioning is important and useful. 
+
 Moreover the solution should be better to be provided by BGP's self. 
+ 
Dependency on other protocols may add unnecessary limitation.

Well I do agree with your above three comments above. But since IMO draft-xu-idr-neighbor-autodiscovery goes way over the above points opening pandora box with various TLVs, instead of keep arguing on the list I wrote a small 3 page draft which does address the core issue of BGP build in session auto setup in a fully automated way for both DCs or campus deployments - yet without any risk of taking BGP on one more wild tracks again. 


Hello Sue,

Please kindly consider the below proposal as simple candidate solution for the discussed problem at hand. 

A new version of I-D, draft-raszuk-idr-bgp-auto-session-setup-00.txt
has been successfully submitted by Robert Raszuk and posted to the
IETF repository.

Name:           draft-raszuk-idr-bgp-auto-session-setup
Revision:       00
Title:          BGP Automated Session Setup (BGP-ASS)
Document date:  2018-07-16
Group:          Individual Submission
Pages:          6
URL:            https://www.ietf.org/internet-drafts/draft-raszuk-idr-bgp-auto-session-setup-00.txt
Status:         https://datatracker.ietf.org/doc/draft-raszuk-idr-bgp-auto-session-setup/
Htmlized:       https://tools.ietf.org/html/draft-raszuk-idr-bgp-auto-session-setup-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-raszuk-idr-bgp-auto-session-setup


Abstract:
   This document proposes a solution for BGP deployments in some
   specific environments to automatically establish BGP sessions without
   need for manual peer configuration.


Kind regards,
Robert.