Re: [sidr] rpki-tree-validation vs. madi-sidr-rp

Declan Ma <madi@zdns.cn> Thu, 30 June 2016 05:13 UTC

Return-Path: <madi@zdns.cn>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9756112D9CF for <sidr@ietfa.amsl.com>; Wed, 29 Jun 2016 22:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KT7AAaM1sCyT for <sidr@ietfa.amsl.com>; Wed, 29 Jun 2016 22:13:34 -0700 (PDT)
Received: from gw1.turbomail.org (gw1.turbomail.org [159.8.83.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1755F12D9C6 for <sidr@ietf.org>; Wed, 29 Jun 2016 22:13:33 -0700 (PDT)
X-TM-DID: e05ed950eee8fc20771b4dbf4ae8d59d
Content-Type: text/plain; charset=gb2312
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Declan Ma <madi@zdns.cn>
In-Reply-To: <0891ea5b-6a68-581d-7f5c-0e6f71fe76d2@bbn.com>
Date: Thu, 30 Jun 2016 13:09:02 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E95FB6AF-2BF6-448A-8FF1-80CBCAAE577C@zdns.cn>
References: <0891ea5b-6a68-581d-7f5c-0e6f71fe76d2@bbn.com>
To: sidr <sidr@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/RH7B9c1uV1IjJ_80vPeEfazulLE>
Subject: Re: [sidr] rpki-tree-validation vs. madi-sidr-rp
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 05:13:37 -0000

Hi, all,

Speaking as the co-author of ‘Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties’,

In addition to the clarification made by Steve, I would like to deliver a clear message here that this draft is intended to make the RP requirements well framed, which are segmented with orthogonal functionalities in different sections.

As such, those ‘functional components’ could be crafted and distributed across the operational timeline of an RP software . 

We would appreciate your comments on this document.

Di
ZDNS


> 在 2016年6月29日,02:19,Stephen Kent <kent@bbn.com> 写道:
> 
> Although I was not present at the BA SIDR meeting, I did participate remotely for one of the sessions. I recall the discussion of the I-D that tries to collect all of the RP requirements in one place, with cites to the sources of these requirements. It part, I recall folks at the mic arguing that this I-D was redundant relative to the existing WG document on tree validation. I don't think this is an accurate comparison of the two docs, although I agree that there is overlap between them.
> 
> RPKI tree validation describes how the RIPE RP software works. It includes references to 6 SIDR RFCs to explain why the software performs certain checks. The RP requirements doc cites 11 SIDR RFCs, plus the BGPsec (router cert) profile. Thus it appears that the requirements doc tries to address a wider set of RFCs relevant to RP requirements. More importantly, the requirements doc is generic, while the tree validation doc is expressly a description of one RP implementation. Thus it is an example of how that implementation tries to meet the RP requirements, not a general characterization of RP requirements.
> 
> 
> Thus I think it appropriate to proceed with both docs.
> 
> Steve
> 
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr