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

Mirja Kühlewind <ietf@kuehlewind.net> Mon, 19 February 2018 13:45 UTC

Return-Path: <ietf@kuehlewind.net>
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 7433B1242F7; Mon, 19 Feb 2018 05:45:41 -0800 (PST)
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-usage@ietf.org, aretana.ietf@gmail.com, bess-chairs@ietf.org, martin.vigoureux@nokia.com, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151904794146.18699.5332623354542357293.idtracker@ietfa.amsl.com>
Date: Mon, 19 Feb 2018 05:45:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/opejbmOPhwSgwwdMe9dJkeOqfBk>
Subject: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-usage-08: (with COMMENT)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 19 Feb 2018 13:45:41 -0000

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



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

Possible nit:
sec 9.1.3: "It is worth noting that unless: a) control or management plane
   learning is performed through the entire EVI or b) all the EVI-
   attached devices signal their presence when they come up (GARPs or
   similar), unknown unicast flooding must be enabled."
  Is this "must be enabled" or "must not be enabled"?