[bess] Genart telechat review of draft-ietf-bess-evpn-vpws-11

Roni Even <ron.even.tlv@gmail.com> Sun, 09 April 2017 05:57 UTC

Return-Path: <ron.even.tlv@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 3DCB5129417; Sat, 8 Apr 2017 22:57:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: gen-art@ietf.org
Cc: draft-ietf-bess-evpn-vpws.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149171742319.3063.4555090995663652452@ietfa.amsl.com>
Date: Sat, 08 Apr 2017 22:57:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/seS0zFHIJJGP809V7Fa00j75e48>
Subject: [bess] Genart telechat review of draft-ietf-bess-evpn-vpws-11
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: Sun, 09 Apr 2017 05:57:03 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bess-evpn-vpws-??
Reviewer: Roni Even
Review Date: 2017-04-08
IETF LC End Date: 2017-03-10
IESG Telechat date: 2017-04-13

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

In section 1 second paragraph "[RFC7432] provides the ability " looks
like the reference is not a link to RFC7432.