Re: [Idr] BGP Auto-Discovery Protocol State Requirements

Jeffrey Haas <jhaas@pfrc.org> Tue, 23 March 2021 16:22 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 C52303A00E5 for <idr@ietfa.amsl.com>; Tue, 23 Mar 2021 09:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 DyPHnakbVGJ6 for <idr@ietfa.amsl.com>; Tue, 23 Mar 2021 09:22:38 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C48263A02BE for <idr@ietf.org>; Tue, 23 Mar 2021 09:22:23 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 5CFCF1E447; Tue, 23 Mar 2021 12:44:05 -0400 (EDT)
Date: Tue, 23 Mar 2021 12:44:05 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Raszuk <robert@raszuk.net>
Cc: "Fomin, Sergey (Nokia - US/Mountain View)" <sergey.fomin@nokia.com>, "idr@ietf.org" <idr@ietf.org>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Message-ID: <20210323164404.GH31047@pfrc.org>
References: <20210319144657.GO29692@pfrc.org> <CAOj+MME8GB4jo_q3kHm1jx6E60GCHeU-pz0eYy_96BJ+ak7_Bw@mail.gmail.com> <20210319152832.GP29692@pfrc.org> <BYAPR08MB549328E3379E94589DC3CE0885649@BYAPR08MB5493.namprd08.prod.outlook.com> <20210323120515.GA31047@pfrc.org> <CAOj+MMGY+sMHr29Uw4bFct9kxoBnp=fJDULVjvFQL1UxC3JYtQ@mail.gmail.com> <20210323150837.GB31047@pfrc.org> <CAOj+MMES0hiWdVy=B_HnYmobtyOR87LBrnCwEEFcJAGLwud+=Q@mail.gmail.com> <20210323160251.GE31047@pfrc.org> <CAOj+MMFj3wu_PHTRSzKA=XXFc6KiJ7M+5mYLgTzZxOmNZHAwmQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOj+MMFj3wu_PHTRSzKA=XXFc6KiJ7M+5mYLgTzZxOmNZHAwmQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/bC0JvmD1-x-g3DyoVTR7XdY8c8o>
Subject: Re: [Idr] BGP Auto-Discovery Protocol State Requirements
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 23 Mar 2021 16:22:44 -0000

On Tue, Mar 23, 2021 at 04:58:08PM +0100, Robert Raszuk wrote:
> > The position I have been taking is figuring out what is required for BGP
> > auto-configuration.  Data center is the specific scenario we are solving
> > for
> > right now.  The working group may take on non-data center cases as future
> > work.  The analysis discussion is being used to refine what state is
> > required for each of the scenarios.
> 
> 
> And I think this is where the confusion is coming from.
> 
> The document is about DC but it includes lots of additional baggage which
> in view of number of people is not required for the DC auto discovery.

You, and the rest of the working group, are explicitly solicited to provide
your feedback on what *is* required for BGP auto-discovery for a DC context.[1]

The draft provides a framework for how the requirements are analyzed in
terms of:
- What BGP needs for a session to come up.
- How a discovering peer can choose whether it wants to peer with the
  discovered thing.
- What the transport requirements are for the discovery protocol.
- What the security considerations are for your desired properties.

Please provide your requirements with those things addressed.

-- Jeff

[1] As a member of the design team, you were requested to do this prior to
publication.  You didn't.