[bess] Genart last call review of draft-ietf-bess-evpn-usage-07
Roni Even <ron.even.tlv@gmail.com> Thu, 08 February 2018 14:01 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 C021F12DA09; Thu, 8 Feb 2018 06:01:57 -0800 (PST)
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-usage.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151809851776.17200.16974667997126761449@ietfa.amsl.com>
Date: Thu, 08 Feb 2018 06:01:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/UwLhrH69hraaTA6ydDiT8grYHqQ>
Subject: [bess] Genart last call review of draft-ietf-bess-evpn-usage-07
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: Thu, 08 Feb 2018 14:01:58 -0000
Reviewer: Roni Even Review result: Ready with Nits 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 treat these comments just like any other last call comments. For more information, please see the FAQ at <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. Document: draft-ietf-bess-evpn-usage-?? Reviewer: Roni Even Review Date: 2018-02-08 IETF LC End Date: 2018-02-09 IESG Telechat date: 2018-02-22 Summary: The document is ready for publication as an Informational RFC Major issues: Minor issues: Nits/editorial comments: In section 3.1 toward the end "For example, we can use ingress replication for on EVI100" no need for "for on"