[Idr] Alissa Cooper's Discuss on draft-ietf-idr-rfc8203bis-07: (with DISCUSS and COMMENT)

Alissa Cooper via Datatracker <noreply@ietf.org> Thu, 08 October 2020 00:10 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 747F33A0A08; Wed, 7 Oct 2020 17:10:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-idr-rfc8203bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, Susan Hares <shares@ndzh.com>, aretana.ietf@gmail.com, shares@ndzh.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <160211580198.31310.1253552691445772469@ietfa.amsl.com>
Date: Wed, 07 Oct 2020 17:10:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ly6EZDuucJZovDbRLxqKq8dwETY>
Subject: [Idr] Alissa Cooper's Discuss on draft-ietf-idr-rfc8203bis-07: (with DISCUSS and COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 08 Oct 2020 00:10:03 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-idr-rfc8203bis-07: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


"If a Shutdown Communication longer than 128 octets is sent to a BGP
   speaker that implements [RFC8203], then that speaker will treat it as
   an error, the consequence of which is a log message.  For this
   reason, operators would be wise to keep shutdown communications to
   less than 128 octets when feasible."

I have a similar question to what Éric asked. Doesn't the above mostly undercut
the value of doing this bis at all? If operators can't expect longer messages
to be understood, will they implement some kind of policy logic or heuristics
to decide when to try to send them and when not? Otherwise, under what
circumstances will they send them?

Was it considered to instead add a new subcode to the BGP Cease NOTIFICATION
subcode registry to capture this case (admin reset or shutdown with long
shutdown message)? That way at least those who want to use it can differentiate
between recipients that don't support RFC 8203, those that do, and those that
support longer communications. I'm not at all steeped in BGP so I'm happy to
drop this if it's unworkable, but I wanted to ask.


For the IESG: it would be good to discuss a bit if there is some process we can
use to avoid this kind of oversight (that occurred with RFC 8203) in the
future. i18ndir didn't exist when it was published, but even if it had I'm not
sure we would have caught this.