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

Jeffrey Haas <> Thu, 18 March 2021 18:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3CA783A31DF for <>; Thu, 18 Mar 2021 11:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ePLAmT-WtJkQ for <>; Thu, 18 Mar 2021 11:58:08 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3413D3A31D9 for <>; Thu, 18 Mar 2021 11:58:08 -0700 (PDT)
Received: by (Postfix, from userid 1001) id 6C8F71E409; Thu, 18 Mar 2021 15:19:36 -0400 (EDT)
Date: Thu, 18 Mar 2021 15:19:36 -0400
From: Jeffrey Haas <>
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <>
Subject: Re: [Idr] BGP Auto-Discovery Protocol State Requirements
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 18 Mar 2021 18:58:10 -0000

Further off-list conversation with Tony Przygienda offer a related
observation on the BGP Session State: They serve as the "offer", and the
management of its lifetime is to a large extent the critical detail covered
by the "retry" behavior.

This potentially creates an option between 1 and 2 below.  A BGP
Auto-Discovery listener that is implementing "discover at OPEN" mostly needs
the hint that "something has changed" for the parameters that may be
discovered at OPEN.

A version/generation or similar field in the auto-discovery protocol would
suit this purpose and permit a "discover at OPEN" BGP Speaker to minimize
the load upon the auto-discovered device.  

This would permit the entire set of BGP Session Protocol State to be omitted
from the protocol, as long as "discover at OPEN" was acceptable.  It also
addresses the consistency issue noted in section 3.6 of the
autconf-considerations draft.


Note that the majority of proposals analyzed for BGP auto-configuration in
Appendix A published some subset of the state in the BGP Session Protocol
State requirements.  Authors of those proposals may wish to comment on their
reasoning for that state in their protocol.

-- Jeff

On Tue, Mar 16, 2021 at 05:02:03PM -0400, Jeffrey Haas wrote:
> Once you have the capability of bringing up a BGP session, you have to
> decide if you even want to.  There are at least two design choices, each
> with specific consequences:
> 1. The implementation is willing to determine if a peer is acceptable or not
>    based on the information exchanged in the BGP OPEN message.  Call this
>    "discover at OPEN".  A further implication of this mode is the
>    implementation must be willing to service incoming sessions that may drop
>    just so they can figure out if they find each other mutually agreeable.
>    This becomes a scaling discussion.
> 2. The implementation wants to know the properties of its potential peer to
>    decide if it wants even try to bring up a session.  This enables "peer
>    selection".
>    The good property is that the peer sending such messages doesn't have to
>    service sessions only to immediately drop them.
>    The bad property is that this increases disclosure of some BGP
>    information to parties that may not eventually be permitted to peer.
>    (Security consideration.)