[Idr] Éric Vyncke's No Objection on draft-ietf-idr-rfc8203bis-07: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Fri, 02 October 2020 13:50 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 2F1173A1636; Fri, 2 Oct 2020 06:50:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke 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>, shares@ndzh.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.18.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <160164662616.20358.6818615634618021035@ietfa.amsl.com>
Date: Fri, 02 Oct 2020 06:50:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/nnRqpsMQSXNl1U0DJ9-gdVeJ0uI>
Subject: [Idr] Éric Vyncke's No Objection on draft-ietf-idr-rfc8203bis-07: (with 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: Fri, 02 Oct 2020 13:50:26 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-idr-rfc8203bis-07: No Objection

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:
https://datatracker.ietf.org/doc/draft-ietf-idr-rfc8203bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for this short and easy to read document.

Non-blocking comment/question: I really wonder what is the use of this document
(message of 0-255 octets) vs. RFC 8203 (message of 0-127 octets) especially
when using the same code points... 128 octets is already a long message in
ASCII (less of course in UTF-8) and there is no way to know whether the
receiving BGP speaker supports this document. I.e., except within a domain,
there is little use of this document. What did I get wrong ?

Regards

-éric