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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Wed, 04 July 2018 05:34 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 48F06130EA3; Tue, 3 Jul 2018 22:34:38 -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 sUnypdbUi8cd; Tue, 3 Jul 2018 22:34:36 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D1CA130DEF; Tue, 3 Jul 2018 22:34:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10756; q=dns/txt; s=iport; t=1530682476; x=1531892076; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=oSA/eLOcqpn6z97x/F7ZSf7ox1Bj+hoR61ptUM2Qob0=; b=ibpUhIHjJUTyRYQfg1XyD5guPff1WcEsTen35+Cw7/YFw0bhwplwUphi FI16wYe8cpCKahSnCPYBbarcA8O8v7EY0ggg2t5gL1X6J5U+N+T2It7ia 4eZ49YkQKkQGSLdN+lWlnWE4m+q3Pvy84qg/0PzJVCrPd63OyTcJ5pZUl 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ChAACFWzxb/4gNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYJTdmJ/KAqDb4gEjECCB3WHPoUqgkGCVII6FIFmCyOESQIXggMhNBgBAgEBAgEBAm0cDIU2AQEBBB0QTBACAQYCDgMEAQEtAgIfER0IAQEEAQ0FCIMZgRtMAxUPjFmbQgiCGocWDYEugRgdBYhtgVY/gQ+CWjWCVkICAwGBKQESAYMcglkCh2iROCsJAoYEhF+BMIMDjV+KNU+GXgIREwGBJB04YXFwFYMkixSFPm+OZ4EfgRoBAQ
X-IronPort-AV: E=Sophos;i="5.51,306,1526342400"; d="scan'208,217";a="138407998"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jul 2018 05:34:35 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w645YY4K010820 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 4 Jul 2018 05:34:34 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 4 Jul 2018 00:34:34 -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, 4 Jul 2018 00:34:34 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-xu-idr-neighbor-autodiscovery@ietf.org" <draft-xu-idr-neighbor-autodiscovery@ietf.org>, "'徐小虎(义先)'" <xiaohu.xxh@alibaba-inc.com>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, 'John Scudder' <jgs@juniper.net>
Thread-Topic: WG adoption call for draft-xu-idr-neighbor-autodiscovery
Thread-Index: AdQSJcQmPylai0FFTx6TtuTV7fzVrQBMr82A
Date: Wed, 04 Jul 2018 05:34:34 +0000
Message-ID: <d6089640c7494b61a706833989dd9250@XCH-ALN-008.cisco.com>
References: <013701d41227$579d2d10$06d78730$@ndzh.com>
In-Reply-To: <013701d41227$579d2d10$06d78730$@ndzh.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.82.219]
Content-Type: multipart/alternative; boundary="_000_d6089640c7494b61a706833989dd9250XCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/bPQu385CD1-DD5PCm-jvBEs6H3s>
Subject: Re: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 04 Jul 2018 05:34:39 -0000

Hello,

I am not aware of any IPR related to this draft.

Thanks,
Ketan

From: Susan Hares <shares@ndzh.com>
Sent: 02 July 2018 22:39
To: idr@ietf.org
Cc: draft-xu-idr-neighbor-autodiscovery@ietf.org; 'ÐìС»¢(ÒåÏÈ)' <xiaohu.xxh@alibaba-inc.com>; Ketan Talaulikar (ketant) <ketant@cisco.com>; aretana.ietf@gmail.com; 'John Scudder' <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 ¨C 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