IETF Logo Mail Archive

[Idr] 回复： 回复： 回复： WG adoption call for draft-xu-idr-neighbor-autodiscovery

" 徐小虎(义先) " <xiaohu.xxh@alibaba-inc.com> Tue, 17 July 2018 16: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 E2D4D130F29; Tue, 17 Jul 2018 09:07:02 -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=unavailable 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 2ZTN6LGVghJK; Tue, 17 Jul 2018 09:07:00 -0700 (PDT)
Received: from out0-137.mail.aliyun.com (out0-137.mail.aliyun.com [140.205.0.137]) (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 B8021130E81; Tue, 17 Jul 2018 09:06:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1531843613; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=pfSiQ41WaLlxV9+9vetY6m35MMSrABK09YIR+H5GE90=; b=GLBwjJxtIM5POOCA6kEOtIMouZYURkLLBcN3ZhEnkffRvFZaY+HIow4bL8HM5Sv68zi9+AWhlJJLYqjjNmxeM0LsMk2Ora26v10/9JMGzcMzfsXxlOcWWKZOe2YphnrQ3zoYbzO/MpiE5eUMyo8Ji7IwntI+ZQ0NxHznVbTzp38=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R301e4; CH=green; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03311; MF=xiaohu.xxh@alibaba-inc.com; NM=1; PH=DW; RN=9; SR=0; TI=dingding_ios.COREAPI779197df43144cd98cb8c94267ed202d;
Received: from WS-web (xiaohu.xxh@alibaba-inc.com[dingding_ios.COREAPI779197df43144cd98cb8c94267ed202d]) by e01l04447.eu6 at Wed, 18 Jul 2018 00:06:48 +0800
Date: Wed, 18 Jul 2018 00:06:48 +0800
From: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
To: "rraszuk@gmail.com" <rraszuk@gmail.com>
Cc: Idr <idr-bounces@ietf.org>, "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, Susan Hares <shares@ndzh.com>, Eric C Rosen <erosen@juniper.net>, Nikos Triantafillis <ntriantafillis@gmail.com>, Keyur Patel <keyur@arrcus.com>, "draft-xu-idr-neighbor-autodiscovery@ietf.org" <draft-xu-idr-neighbor-autodiscovery@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Message-ID: <8faf0094-c7ad-466c-a74a-10a109c9bbfa.xiaohu.xxh@alibaba-inc.com>
X-Priority: 0
X-Mailer: [Alimail-Mailagent revision 268]
MIME-Version: 1.0
In-Reply-To: <CA+b+ERmoCA7XMWuh35Mx4GDC-sKAbtPrSz+1WyQ4DJFbsGqGFw@mail.gmail.com>
References: <013701d41227$579d2d10$06d78730$@ndzh.com> <6ACB426F-D10D-43E2-BC12-2D41D0CCE88A@arrcus.com> <CA+R4MGeh=+e4FvPfeGzd-4UnxuPiwHHEMEKuieXZOTitVYHm2A@mail.gmail.com> <CA+b+ERmAHwKY8x0jH6Pk9Svu1BQFDxrG2ozQO97VHWV=jXtHqA@mail.gmail.com> <CA+R4MGcoer=tAVCPPYTsXp-DtiO1cxArxJA=iAMsJ_A_LmzrhA@mail.gmail.com> <20401d8c-4591-0507-776f-a154bc968245@juniper.net> <006401d41d30$b3e0b1f0$1ba215d0$@ndzh.com> <009a01d41d31$d4c96b40$7e5c41c0$@ndzh.com> <b6d6905f2b904a21bfb8e59d8e760199@XCH-ALN-008.cisco.com> <B17A6910EEDD1F45980687268941550F36779D63@MISOUT7MSGUSRCD.ITServices.sbc.com> <66faeea6-b4c4-4ef6-84a7-3bdc4737a6eb.xiaohu.xxh@alibaba-inc.com> <4d995b1c-ee92-46e2-a8e8-c5adc412e717.xiaohu.xxh@alibaba-inc.com>, <CA+b+ERmoCA7XMWuh35Mx4GDC-sKAbtPrSz+1WyQ4DJFbsGqGFw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_7938_523f6940_5b4e1418_298013"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0qQnvoL1pdNErg_C5l4-U3ZArIY>
Subject: [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 16:07:15 -0000

LOL





来自钉钉专属商务邮箱------------------------------------------------------------------
发件人：Robert Raszuk<robert@raszuk.net>
日　期：2018年07月17日 23:35:17
收件人：徐小虎(义先)<xiaohu.xxh@alibaba-inc.com>
抄　送：Idr<idr-bounces@ietf.org>; Ketan Talaulikar (ketant)<ketant=40cisco.com@dmarc.ietf.org>; Susan Hares<shares@ndzh.com>; Eric C Rosen<erosen@juniper.net>; Nikos Triantafillis<ntriantafillis@gmail.com>; Keyur Patel<keyur@arrcus.com>; draft-xu-idr-neighbor-autodiscovery@ietf.org<draft-xu-idr-neighbor-autodiscovery@ietf.org>; idr@ietf.org<idr@ietf.org>
主　题：Re: [Idr] 回复： 回复： WG adoption call for draft-xu-idr-neighbor-autodiscovery

By the way, in addition to automate and simplify the use of BGP as IGP in MSDC, the BGP peer auto-discovery mechanism as described in this draft has the potential to be applicable to BGP-SR-TE and LSVR as well. 

Sorry for touching the LSVR cheese unintentionally:)


​And that is precisely the fundamental issue not a feature to be proud about here. You do not turn BGP into link state protocol because you like to apply LSVR or BGP-SR-TE in the DCs. 

Its completely upside down. 

That's why my draft ​https://tools.ietf.org/html/draft-raszuk-idr-bgp-auto-session-setup-00 is a simple and short honesty check. Is this discussion about helping to bring the BGP sessions up in some env. or it is rather a black box which bringing BGP discovery is just a label on it and content will explode in no time when its shipped ? 

Thx,
R.

v2.23.0 | Report a Bug | By Email