Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)

Jeffrey Haas <> Fri, 27 January 2017 21:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 40BCC129983; Fri, 27 Jan 2017 13:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.101
X-Spam-Status: No, score=-5.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iSmpB7jUop-r; Fri, 27 Jan 2017 13:33:38 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 6B664129985; Fri, 27 Jan 2017 13:33:38 -0800 (PST)
Received: by (Postfix, from userid 1001) id 65D141E32B; Fri, 27 Jan 2017 16:38:33 -0500 (EST)
Date: Fri, 27 Jan 2017 16:38:33 -0500
From: Jeffrey Haas <>
To: Susan Hares <>
Message-ID: <>
References: <01b801d27105$45702bc0$d0508340$>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01b801d27105$45702bc0$d0508340$>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <>
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Jan 2017 21:33:39 -0000

Sue and authors,

On Tue, Jan 17, 2017 at 04:04:18PM -0500, Susan Hares wrote:
> This begins a 2 week WG Last Call for draft-ietf-idr-shutdown-02.txt
> (1/17/2017 to 1/31/2017).  Section 7 of this document lists the
> implementations that have been created for this BGP functionality.   These
> include: ExaBGP, pmacct, OpenBGPD, Wireshark (packet analyzer), and tcpdump

While working through the likely changes in our BGP implementation, the
following thought occurred while looking at the relevant RFC 4486 sub-codes
and triggers.

RFC 4486 defines two administrative actions that seem applicable to this

         2        Administrative Shutdown
         4        Administrative Reset

The draft covers code point 2.

I believe the draft should cover both administrative sub-codes.  It also
permits two slightly different work flows:

run clear bgp neighbor reason "You have a bgp wedgie and I'm trying to clear it"

set protocols bgp group external neighbor shutdown reason "De-peered with prejudice"

The first allows a reset reason to be passed along that may be transient.

The second permits a reason to persist in subsequent attempts when that BGP
speaker tries to re-connect.

Beyond the above point, I find the document to be of good quality.

-- Jeff