IETF Logo Mail Archive

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

Gaurav Dawra <gdawra.ietf@gmail.com> Fri, 13 July 2018 05:03 UTC

Return-Path: <gdawra.ietf@gmail.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 91B3A12777C; Thu, 12 Jul 2018 22:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dNt1iSOBe1eX; Thu, 12 Jul 2018 22:03:12 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12829124D68; Thu, 12 Jul 2018 22:03:12 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id j8-v6so26104662lfb.4; Thu, 12 Jul 2018 22:03:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gSJjWbHHFWcKeJSpQLh/Ma0FyaMzUXaFsT0RShofrEU=; b=GUYV6hUufYCyluaa0KTcHN02/h2dJhDGny5TZdF/oiwtpFuY+ing/RVfFvMIMdpFqT ogA/5eelLTRz7oj1OT0IpeqVao/LfSMl7I6MwlVAWtXEYYvGNQvHwFxB8EpQQX4XlddQ qn5sRvcFi3grjdBHWApQDpBuAuM4TJkM8f78ev5VX9zPs/NpcgBd7dzg1EYc9Snh4gNP two8aVihgP4NZYq34MRLQ7X8feNR4sFzDy+GxK9A+bE4fiRaf9MmHJlWf3ZUW/GQzFoy aceXkbL+fZWhtP6kW0sqWZnLz99xC/4QNIDVUhFcPyBvUJS9Zw8YwwnKIixgEd5fouqq p0Jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gSJjWbHHFWcKeJSpQLh/Ma0FyaMzUXaFsT0RShofrEU=; b=Hli3TZXR7Qcg4NOIHG37lpT6hmUdoVm8CyVRb/nuOvybigQ6DbbZZzh8kT9I4ExdGd RTFouYmfJgLEboZF4vvISurqfhXiNsZw463NrIDusK5VuNba2GRmSG5KJdgIE1t49Z5Y ekN42j7SvXy9mXYd/Tm1DDFP4Is39oZ+nMYfhEAqN/1ouYPNzkhkS4XX1lZI7h4OGYry p1IJ+7Ih2XpKDk+2o2mNgT4eb4oleQQ1lnmkNpQyWofASygxlUYLBgahqobMHkpZQQBo 0qaQ3bZ9Qrhf3mKvL6CDDpcW3K1mHayEy++vVAw21MWIMk1MawK4gf1mEz8WlZ5dVtWs Uhgg==
X-Gm-Message-State: AOUpUlGb/9SFTWTsscWkPtVSwtWaTDg7pGysCbut6+bSargQ6SypbxB5 Ap6XbMb1nVggXcEE0ey4QB7xUt+cz/MMUuElgIDkeg==
X-Google-Smtp-Source: AAOMgpfCrY6cSxQy4Ey7aRDmy7duO0Wg/uCnKPEzyxVVFQv0ugZFfh/rpYa6kou/JMPTA/s7z6F4yVicg9RA1nQj/lM=
X-Received: by 2002:a19:e40d:: with SMTP id b13-v6mr3923568lfh.141.1531458190105; Thu, 12 Jul 2018 22:03:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ab3:d68:0:0:0:0:0 with HTTP; Thu, 12 Jul 2018 22:03:09 -0700 (PDT)
In-Reply-To: <E0D48054-CE8E-44AE-AD22-D95F56CAF603@gmail.com>
References: <013701d41227$579d2d10$06d78730$@ndzh.com> <E0D48054-CE8E-44AE-AD22-D95F56CAF603@gmail.com>
From: Gaurav Dawra <gdawra.ietf@gmail.com>
Date: Thu, 12 Jul 2018 22:03:09 -0700
Message-ID: <CAMOQah9YexwZz5Ww_CEQU7oX6w_0xSFPiiA0VtyBiW6p4+hRAw@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: idr wg <idr@ietf.org>, draft-xu-idr-neighbor-autodiscovery@ietf.org
Content-Type: multipart/alternative; boundary="00000000000068e6f80570da6536"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/fAp9yV3u0uNzYYeozNvzGovivaI>
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: Fri, 13 Jul 2018 05:03:15 -0000

Hi,

While I think having a BGP neighbor auto-discovery protocol would be useful
in DCs.
There is a potential scaling issue to process hello messages as a number of
BGP sessions scale increases.
Proper handling of proposed hello messages needs to be addressed first.

Cheers,

Gaurav

>
> On Mon, Jul 2, 2018 at 10:08 AM, Susan Hares <shares@ndzh.com> wrote:
>
>> 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
>>
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>
>>
>

v2.23.0 | Report a Bug | By Email