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

"Satya Mohanty (satyamoh)" <satyamoh@cisco.com> Thu, 12 July 2018 02:08 UTC

Return-Path: <satyamoh@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 B7862130E7F; Wed, 11 Jul 2018 19:08:12 -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_MED=-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 eqKYI59CLT8I; Wed, 11 Jul 2018 19:08:10 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA39E127332; Wed, 11 Jul 2018 19:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12896; q=dns/txt; s=iport; t=1531361289; x=1532570889; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=uqwTJEy3cPmmJeBPRHNO9RmgxiO9qIFhK01duRC2ru0=; b=SosnEY0PCJsRJHURdWED6mWpd3+/WX5u97K3LIOZbBlX0YAS47CLst7b Xg5nrpCGMkNzlOu0oGcn5WdXbxDBmUvhDl6gpvdcE6wa/hQMsHnasCZGj H2APN4oxV/qqGWybWRGC0d7m/NTf6TdG0PBB/xS8DpqkC6oN8Fe9bOSm8 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CTAgDYtkZb/4UNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYJTdmN/KAqDcJQ7gWckdYxtEYIxglSCToFmCyOESQIXgiYhNxUBAgEBAgEBAm0cDIU2AQEBAQMdBlYQAgEIDgMDAQIrAgICMB0IAQEEAQ0FgyABgRtkD6oVgS6EW4VHHQWIfoFXP4EQJwyCKTWDGQIDAYEpARIBP4JhMYIkAohQiR+HaAkChgiEYYQ8jWGKOIczAhETAYEkMyJhcXAVZQGCPgmLDIU+b4otgR+BGgEB
X-IronPort-AV: E=Sophos;i="5.51,341,1526342400"; d="scan'208,217";a="422584822"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jul 2018 02:08:09 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w6C288fN012609 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 12 Jul 2018 02:08:08 GMT
Received: from xch-rtp-012.cisco.com (64.101.220.152) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 11 Jul 2018 22:08:08 -0400
Received: from xch-rtp-012.cisco.com ([64.101.220.152]) by XCH-RTP-012.cisco.com ([64.101.220.152]) with mapi id 15.00.1320.000; Wed, 11 Jul 2018 22:08:08 -0400
From: "Satya Mohanty (satyamoh)" <satyamoh@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>
Thread-Topic: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery
Thread-Index: AdQSJcQmPylai0FFTx6TtuTV7fzVrQHRkMiA
Date: Thu, 12 Jul 2018 02:08:08 +0000
Message-ID: <A4C8928D-2899-40F4-9465-38CF27ED9C27@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-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.102.175]
Content-Type: multipart/alternative; boundary="_000_A4C8928D289940F4946538CF27ED9C27ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-z0x5XSYTBndmgE_iGHXqON6xD0>
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:08:13 -0000

Support as Contributor.

Thanks,
--Satya

From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
Date: Monday, July 2, 2018 at 10:10 AM
To: "idr@ietf.org" <idr@ietf.org>
Cc: "draft-xu-idr-neighbor-autodiscovery@ietf.org" <draft-xu-idr-neighbor-autodiscovery@ietf.org>
Subject: [Idr] 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?



  1.  If so, should be passed in BGP Hello message?

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


  1.  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