[bess] Opsdir last call review of draft-ietf-bess-evpn-vpls-seamless-integ-05

Linda Dunbar <ldunbar@huawei.com> Tue, 18 December 2018 23:26 UTC

Return-Path: <ldunbar@huawei.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 92BC8131260; Tue, 18 Dec 2018 15:26:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar <ldunbar@huawei.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-bess-evpn-vpls-seamless-integ.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154517556254.5530.14577483027370675798@ietfa.amsl.com>
Date: Tue, 18 Dec 2018 15:26:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Coy6PXLQHJW9yZF7jSLyrgXW9Sw>
Subject: [bess] Opsdir last call review of draft-ietf-bess-evpn-vpls-seamless-integ-05
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: Tue, 18 Dec 2018 23:26:03 -0000

Reviewer: Linda Dunbar
Review result: Ready

Reviewer: Linda Dunbar
Review result: Ready with comments

I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

The draft describes the procedures for EVPN PEs to handle traffic from VPLS
PEs, to enable smooth transition from VPLS network to EVPN network. The
procedures are written very clear, (although I am not sure why it is a Standard
Track document as the document is mainly in describing the procedures of PEs
that support both EVPN & VPLS).

Question to the authors:

Page 8 Section 3.2: why set up the PW if keep it operationally down?

Best Regards,
Linda Dunbar