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

Matthew Walster <matthew@walster.org> Fri, 27 January 2017 23:21 UTC

Return-Path: <matthew@walster.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 DE0A0129AB1; Fri, 27 Jan 2017 15:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no 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 UGd2TnpZ3vI5; Fri, 27 Jan 2017 15:21:43 -0800 (PST)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21101129AB0; Fri, 27 Jan 2017 15:21:42 -0800 (PST)
Received: from mail-wm0-f43.google.com ([74.125.82.43]:34901) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:matthew@walster.org) (TLS1.0:RSA_AES_128_CBC_SHA1:16) id 1cXFpo-0000Np-RX (Exim 4.72) (return-path <matthew@walster.org>); Fri, 27 Jan 2017 23:21:36 +0000
Received: by mail-wm0-f43.google.com with SMTP id r126so138120076wmr.0; Fri, 27 Jan 2017 15:21:40 -0800 (PST)
X-Gm-Message-State: AIkVDXIEC9hEhmPQRjqQyviSNZyn+ycKoVH6s8CloSX0rThgtagDaXKJqeXxyJmsshbxZO8AqjSOCLJTmm0ILA==
X-Received: by 10.223.130.46 with SMTP id 43mr9351754wrb.41.1485559300632; Fri, 27 Jan 2017 15:21:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.164.9 with HTTP; Fri, 27 Jan 2017 15:21:19 -0800 (PST)
In-Reply-To: <20170127213832.GA20988@pfrc.org>
References: <01b801d27105$45702bc0$d0508340$@ndzh.com> <20170127213832.GA20988@pfrc.org>
From: Matthew Walster <matthew@walster.org>
Date: Fri, 27 Jan 2017 15:21:19 -0800
X-Gmail-Original-Message-ID: <CADLW2vwFPikHb9=+V7oQ-HTQPu+s1S5e_B0x8yai8wLB-4z6Tw@mail.gmail.com>
Message-ID: <CADLW2vwFPikHb9=+V7oQ-HTQPu+s1S5e_B0x8yai8wLB-4z6Tw@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary=001a114b3774683aba05471bba65
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/YJPgIdtZg7DrY4PliefkrPm6Kas>
Cc: idr@ietf.org, draft-ietf-idr-shutdown@ietf.org, Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] 2 week WG LC for draft-ietf-idr-shutdown-02 (1/17 to 1/31/2017)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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, 27 Jan 2017 23:21:45 -0000

On 27 January 2017 at 13:38, Jeffrey Haas <jhaas@pfrc.org> wrote:

> I believe the draft should cover both administrative sub-codes.


​While I'm hesitant to consider this a perfect idea due to the fact that
there are mechanisms within BGP to make this a non-disrupting event not in
such explicit need of notification​ similar to a shut down event, such as
graceful restart, end-of-rib markers etc, there is the possibility of a
reset occurring and the BGP session not restoring as intended with a
notification from the remote side or indeed a TCP reset should the speaker
not be willing/ready to accept the new connection. At which point, it would
be good to have the shut down communication message to reference the
intended action, reference a contact point etc.

I'd support a widening of the draft to include the additional code point
(Cease/Administrative Shutdown and Cease/Administrative Reset).

Indeed, could not all Cease sub-codes use this method? For instance:

         1        Maximum Number of Prefixes Reached


The notification could provide a link to a filter update site, or an email
address for the NOC to take further actions... Or to indicate whether or
not the connection is moved into an error state with no future connections
allowed until the error is cleared by an operator.

         3        Peer De-configured


Likewise, this could be supplemented with a message when the session is
being deconfigured and moved to another router.

         6        Other Configuration Change


This has always been difficult to interpret, and has very recently been
something I've been butting up against. A vendor supplied string detailing
the exact change mechanism that caused this would be welcome.

There is obvious scope-creep at this point, I would like to suggest either
the draft considered as-is or to allow all Cease sub-codes to have shutdown
communication possible.

The rest of the draft itself seems well written, easy to understand, and
even unamended would be a welcome addition to the internet operators
toolkit.

Matthew Walster