[Gen-art] Genart last call review of draft-ietf-sidrops-rpki-tree-validation-02

Linda Dunbar <Linda.dunbar@huawei.com> Fri, 03 August 2018 20:11 UTC

Return-Path: <Linda.dunbar@huawei.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 18734130FA8; Fri, 3 Aug 2018 13:11:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar <Linda.dunbar@huawei.com>
To: <gen-art@ietf.org>
Cc: sidrops@ietf.org, ietf@ietf.org, draft-ietf-sidrops-rpki-tree-validation.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153332707807.18413.5304119074828612207@ietfa.amsl.com>
Date: Fri, 03 Aug 2018 13:11:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/T0ZydAyp_DjIvTZgT9EPsLtCrh8>
Subject: [Gen-art] Genart last call review of draft-ietf-sidrops-rpki-tree-validation-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.27
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2018 20:11:18 -0000

Reviewer: Linda Dunbar
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 treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-sidrops-rpki-tree-validation-02
Reviewer: Linda Dunbar
Review Date: 2018-08-03
IETF LC End Date: 2018-08-10
IESG Telechat date: Not scheduled for a telechat

This draft describes one sample implementation of validating the content of
RPKI certificate Tree. The description is clear, especially clearly described
which section of RFC6487 are based for its implementation.

Major issues:

Minor issues:

Nits/editorial comments:
Section 9.1. the Hash Collisions is more of design in-complete instead of
"Security Considerations". So is the section 9.2 In addition, why the
implementation description has to be an RFC? clog up the RFCs