[bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-etree-13: (with COMMENT)

Mirja Kühlewind <ietf@kuehlewind.net> Mon, 11 September 2017 12:51 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-bess-evpn-etree@ietf.org, aretana@cisco.com, Thomas Morin <thomas.morin@orange.com>, bess-chairs@ietf.org, thomas.morin@orange.com, bess@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150513427770.9608.8875211941036474000.idtracker@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 05:51:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/EwIx9bD4JqfZ-6Ak5gQ97kUEwnI>
Subject: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-etree-13: (with COMMENT)

Mirja Kühlewind has entered the following ballot position for
draft-ietf-bess-evpn-etree-13: 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-bess-evpn-etree/



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

Mostly editorial comment:
Reading sections 3 and 4 it not clear to me if this is providing an actual
implementation specification or just reasoning. If the former is indented I
would recommend to use more active and normative language. Also I would
recommend to have section 5 before 3 and 4 because they use these new
flags/fields.

[bess] Mirja Kühlewind's No Objection on draft-ie… Mirja Kühlewind