Review of draft-ietf-sidr-bgpsec-ops-12

Roni Even <roni.even@mail01.huawei.com> Thu, 15 December 2016 13:05 UTC

Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D69C5129DA8; Thu, 15 Dec 2016 05:05:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roni Even <roni.even@mail01.huawei.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-sidr-bgpsec-ops-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.39.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148180713687.27658.2938123182879685300.idtracker@ietfa.amsl.com>
Date: Thu, 15 Dec 2016 05:05:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zSuRn51e5xdisOHFZt3s1g7hRe8>
Cc: draft-ietf-sidr-bgpsec-ops.all@ietf.org, ietf@ietf.org, sidr@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2016 13:05:37 -0000

Reviewer: Roni Even
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Please resolve these comments along with any other Last Call comments
you may receive.
Document: draft-ietf-sidr-bgpsec-ops-12
Reviewer: Roni Even
Review Date:2016-12-15
IETF LC End Date: 2016–12-22
IESG Telechat date:  

Summary: This draft is almost ready for publication as a BCP RFC.


Major issues:

Minor issues:


Nits/editorial comments:

I think the document need an editorial review, a lot of text in
passive language, for example third paragraph in section 1
"BGPsec needs to be spoken only by an AS's eBGP speaking, AKA border,
routers, and is designed so that it can be used to protect 
announcements which are originated by resource constrained edge 
routers." is written in passive language and it is also a long
sentence.