IETF Logo Mail Archive

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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 12 July 2018 02:02 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 05F65130FCF; Wed, 11 Jul 2018 19:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 ZkfrAbkNj7K7; Wed, 11 Jul 2018 19:02:55 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12E94130DE3; Wed, 11 Jul 2018 19:02:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27164; q=dns/txt; s=iport; t=1531360975; x=1532570575; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=znuwrmcTLhkAX+/AfwJrWnUlc2oama+lgmmI6dhI0Xk=; b=YXApJchvCv9OmN9ZLTjnNOMYe7/dLrtx2fLUuHei0LSDrzkfucYb/94R n2hG3LQse0GJNLbQfXfJW+8ixdgra8iAtAhI23400nGdPh2idfpQ+No4Q 10TJSZ4mC4vCN1jN8Z3GvqJqd5ADo7WlwCO9HPQnH8qLt7I/PccFHTdCP s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CrAADytUZb/5RdJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYJTdmN/KAqDcIgEjDeCC3WCNYUMhSyFFoI6FIFmCyOESQIXgiYhNBgBAgEBAgEBAm0cDIU2AQEBAQMdBgpMEAIBBgIRBAEBIQcDAgICHxEUCQgBAQQBDQUIgxmBG0wDFQ+OTZtIgS6HEg2DAx0FiH6BVz+BEIJcNYJWQwIDAYEpARIBVYJLglUCh2SRSCsJAoYIhGGBMIMEjWmKOE+GZAIRFIEkHThhcXAVgySLFYU+b4otgR+BGgEB
X-IronPort-AV: E=Sophos;i="5.51,341,1526342400"; d="scan'208,217";a="141426623"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jul 2018 02:02:54 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id w6C22ssC019631 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 12 Jul 2018 02:02:54 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 11 Jul 2018 21:02:53 -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.1320.000; Wed, 11 Jul 2018 21:02:53 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>, Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>
CC: draft-xu-idr-neighbor-autodiscovery <draft-xu-idr-neighbor-autodiscovery@ietf.org>, "aretana.ietf" <aretana.ietf@gmail.com>, John Scudder <jgs@juniper.net>
Thread-Topic: WG adoption call for draft-xu-idr-neighbor-autodiscovery
Thread-Index: AdQSJcQmPylai0FFTx6TtuTV7fzVrQGuD1+AACmX65A=
Date: Thu, 12 Jul 2018 02:02:53 +0000
Message-ID: <e918a522bbbe4598be0c0e56252ff3fb@XCH-ALN-008.cisco.com>
References: <013701d41227$579d2d10$06d78730$@ndzh.com> <a628c5ad-93d6-4107-8f70-ed794b4ca581.xiaohu.xxh@alibaba-inc.com>
In-Reply-To: <a628c5ad-93d6-4107-8f70-ed794b4ca581.xiaohu.xxh@alibaba-inc.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.65.34.111]
Content-Type: multipart/alternative; boundary="_000_e918a522bbbe4598be0c0e56252ff3fbXCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/8R4SlRp8-lJ4IMxZeCgN3XS0WlI>
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: Thu, 12 Jul 2018 02:02:59 -0000

+1 and support as co-author.

Thanks,
Ketan

From: 徐小虎(义先) <xiaohu.xxh@alibaba-inc.com>
Sent: 11 July 2018 06:41
To: Susan Hares <shares@ndzh.com>; idr <idr@ietf.org>
Cc: draft-xu-idr-neighbor-autodiscovery <draft-xu-idr-neighbor-autodiscovery@ietf.org>; Ketan Talaulikar (ketant) <ketant@cisco.com>; aretana.ietf <aretana.ietf@gmail.com>; John Scudder <jgs@juniper.net>
Subject: Re: WG adoption call for draft-xu-idr-neighbor-autodiscovery


Hi all,

I support the adoption as a coauthor.

The following is my answer to co-chair's questions:


1)      Does BGP need to have an autodiscovery mechanism for peers within Data Centers?



Yes. it's needed in large-scale data centers where BGP is deployed as a underlay routing protocol.



2)      Does this mechanism work for other deployments?



Yes, it works for other deployments such as metro area networks where BGP is deployed as a underlay routing protocol as well.



3)      If so, should be passed in BGP Hello message?

Or should it be a part of another protocol (e.g. LLDP, BFD, etc).



Yes, it seems straightforward to extend BGP itself rather than extending other protocol to realize the BGP peer discovery purpose.


4)      Does this interact with any of the LSVR work?



Yes, this interact with the LSVR work.



Best regards,

Xiaohu
------------------------------------------------------------------
From:Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Send Time:2018年7月3日(星期二) 01:08
To:idr <idr@ietf.org<mailto:idr@ietf.org>>
Cc:draft-xu-idr-neighbor-autodiscovery <draft-xu-idr-neighbor-autodiscovery@ietf.org<mailto:draft-xu-idr-neighbor-autodiscovery@ietf.org>>; 徐小虎(义先) <xiaohu.xxh@alibaba-inc.com<mailto:xiaohu.xxh@alibaba-inc.com>>; Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; aretana.ietf <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>>; John Scudder <jgs@juniper.net<mailto:jgs@juniper.net>>
Subject:WG adoption call for draft-xu-idr-neighbor-autodiscovery

Greetings:

This begins a 2 week WG adoption call for draft-xu-idr-neighbor-autodiscovery (July 2 – July 16).

https://datatracker.ietf.org/doc/draft-xu-idr-neighbor-autodiscovery/

The authors of this draft should send their IPR statements in response to this email.  I hope the authors will ihelp their vacationing co-authors to respond by July 7th.

The WG should consider the following:

1)      Does BGP need to have an autodiscovery mechanism for peers within Data Centers?

2)      Does this mechanism work for other deployments?



3)      If so, should be passed in BGP Hello message?

Or should it be a part of another protocol (e.g. LLDP, BFD, etc).


4)      Does this interact with any of the LSVR work?

I want to thank the authors for their patience while we sorted through some of the WG LC for other drafts.  We decided to wait until some of those discussion were cleared up prior to starting a new WG Adoption call.


Susan Hares

v2.23.0 | Report a Bug | By Email