[bess] Spencer Dawkins' No Objection on draft-ietf-bess-mvpn-expl-track-12: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Thu, 25 October 2018 02:13 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 1ECBA126BED; Wed, 24 Oct 2018 19:13:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-bess-mvpn-expl-track@ietf.org, bess-chairs@ietf.org, stephane.litkowski@orange.com, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154043363712.6859.3409038768870954064.idtracker@ietfa.amsl.com>
Date: Wed, 24 Oct 2018 19:13:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/r-sYnXLR5G18_YM88zVWzFzPG3I>
Subject: [bess] Spencer Dawkins' No Objection on draft-ietf-bess-mvpn-expl-track-12: (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, 25 Oct 2018 02:13:57 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-bess-mvpn-expl-track-12: 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:


Keeping in mind that reading multicast specifications now is like reading the
denser MPLS specifications 10-15 years ago, even with the forest of unfamiliar
terms in the Introduction, you manage to explain clearly what the problems
being addressed are. Thank you for that effort.

I support Mirja's Discuss, specifically because if this ever goes wrong, the
people writing this spec probably know the most about what to do about it. If
you can provide guidance, it will probably be better guidance than operators
will get from anyone else.

(And please take this as a compliment!)