[bess] Deborah Brungard's No Objection on draft-ietf-bess-evpn-df-election-framework-07: (with COMMENT)

Deborah Brungard <db3546@att.com> Wed, 09 January 2019 21:18 UTC

Return-Path: <db3546@att.com>
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 5671D130EAB; Wed, 9 Jan 2019 13:18:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Deborah Brungard <db3546@att.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-bess-evpn-df-election-framework@ietf.org, Stephane Litkowski <stephane.litkowski@orange.com>, bess-chairs@ietf.org, stephane.litkowski@orange.com, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154706871734.5193.9907519907870786879.idtracker@ietfa.amsl.com>
Date: Wed, 09 Jan 2019 13:18:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/j7C3Yrv-6UOLX4hcC8id2_NT7YA>
Subject: [bess] Deborah Brungard's No Objection on draft-ietf-bess-evpn-df-election-framework-07: (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: Wed, 09 Jan 2019 21:18:37 -0000

Deborah Brungard has entered the following ballot position for
draft-ietf-bess-evpn-df-election-framework-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-bess-evpn-df-election-framework/



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

I can be swayed either way on the update discussion. I usually prefer to be
conservative with using "update" so the reader of the original RFC does not
have to parse many updates to understand what is applicable when
implementing the original RFC. While others view it as applying to the
new RFC and its relationship with the original. What's important (to me)
is to clearly describe the update in the abstract for the reader to decide
to read or not.