Deborah Brungard's No Objection on draft-ietf-rtgwg-enterprise-pa-multihoming-08: (with COMMENT)

Deborah Brungard via Datatracker <noreply@ietf.org> Tue, 25 June 2019 18:12 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 92911120B3E; Tue, 25 Jun 2019 11:12:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Deborah Brungard via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-rtgwg-enterprise-pa-multihoming@ietf.org, Ron Bonica <rbonica@juniper.net>, rtgwg-chairs@ietf.org, rbonica@juniper.net, rtgwg@ietf.org
Subject: Deborah Brungard's No Objection on draft-ietf-rtgwg-enterprise-pa-multihoming-08: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Deborah Brungard <db3546@att.com>
Message-ID: <156148636958.31241.4782066670825152870.idtracker@ietfa.amsl.com>
Date: Tue, 25 Jun 2019 11:12:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/aJOAjkzIPszxKtdSIFQjFEDUKX0>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2019 18:12:50 -0000

Deborah Brungard has entered the following ballot position for
draft-ietf-rtgwg-enterprise-pa-multihoming-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-rtgwg-enterprise-pa-multihoming/



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

Much thanks for a very comprehensive document!

Similar to Alvaro's (F),  I find a couple of sentences confusing.

I think it would be very helpful to clarify the scope of this document (in
this document), especially as Alvaro notes, the same working group
is progressing a PS document with another solution.

Examples:

- Abstract: I find the sentence "attempts..complete" solution a bit in conflict.
"Attempts" - either it does or doesn't. "complete" is questionable as it is focused
on a set of use cases. Suggest:

This document attempts to define a complete solution to this problem
/s/
This document examines currently available mechanisms for providing a solution
to this problem for a broad range of enterprise topologies.

- Section 4:
"The method described in the current document is functionally equivalent, but it is
intended to be easier to understand for enterprise network operators."
I don't find the justification "easier to understand for enterprise network operators" to be
convincing. Especially if there is already a PS document being progressed in the same working
group. Hopefully the PS document will also be easy to understand for both operators and vendors.
Suggest a better qualifier, even simply:
but it is intended to be easier to understand for enterprise network operators
/s/
but it is based on application of existing mechanisms for the described scenarios