[bess] Francesca Palombini's No Objection on draft-ietf-bess-evpn-optimized-ir-09: (with COMMENT)

Francesca Palombini via Datatracker <noreply@ietf.org> Thu, 21 October 2021 12:24 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B8AB13A0A73; Thu, 21 Oct 2021 05:24:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-bess-evpn-optimized-ir@ietf.org, bess-chairs@ietf.org, bess@ietf.org, Matthew Bocci <matthew.bocci@nokia.com>, matthew.bocci@nokia.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <163481904972.28046.2219435173262767712@ietfa.amsl.com>
Date: Thu, 21 Oct 2021 05:24:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Xy87bTcqmCG-RsID3MxHU2P7Qgc>
Subject: [bess] Francesca Palombini's No Objection on draft-ietf-bess-evpn-optimized-ir-09: (with COMMENT)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2021 12:24:10 -0000

Francesca Palombini has entered the following ballot position for
draft-ietf-bess-evpn-optimized-ir-09: 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/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-optimized-ir/



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

Thanks for the work on this document.

I strongly support John's DISCUSS and COMMENT points, especially:

* overuse of abbreviations and the assumptions that the reader is familiar with
all concepts and terms used make the document really hard to read for
non-expert in the field. I'll also point out that having a terminology section
with expansion but with no references is not as useful as one with proper
descriptions and references.

* there are several occurrences of SHOULD in the document that left me
wondering in which cases it is acceptable to not go with the recommended
behavior. Again, John has pointed out 2 of them I believe, but I would suggest
to check all normative SHOULD as only a couple were put in context. Also note
that even if the context might be obvious to the authors and wg, it would help
the reader with one more sentence clarifying it.

Francesca