Re: [Sidr] Architecture document: narrowing the scope

Stephen Kent <kent@bbn.com> Mon, 10 March 2008 23:24 UTC

Return-Path: <sidr-bounces@ietf.org>
X-Original-To: ietfarch-sidr-archive@core3.amsl.com
Delivered-To: ietfarch-sidr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10AC43A6AED; Mon, 10 Mar 2008 16:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.869
X-Spam-Level:
X-Spam-Status: No, score=-100.869 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFYT4rmmW1qW; Mon, 10 Mar 2008 16:24:51 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 420E73A67B2; Mon, 10 Mar 2008 16:24:51 -0700 (PDT)
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6FE53A6AAD for <sidr@core3.amsl.com>; Mon, 10 Mar 2008 16:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L+-naN2r79SG for <sidr@core3.amsl.com>; Mon, 10 Mar 2008 16:24:49 -0700 (PDT)
Received: from mx12.bbn.com (mx12.bbn.com [128.33.0.81]) by core3.amsl.com (Postfix) with ESMTP id 1A8C83A6A92 for <sidr@ietf.org>; Mon, 10 Mar 2008 16:24:49 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15] helo=[10.150.134.25]) by mx12.bbn.com with esmtp (Exim 4.60) (envelope-from <kent@bbn.com>) id 1JYrK8-0005v4-5B; Mon, 10 Mar 2008 19:22:28 -0400
Mime-Version: 1.0
Message-Id: <p06240516c3fb6e75c7b9@[10.150.134.25]>
In-Reply-To: <alpine.LRH.1.00.0803110039560.26663@netcore.fi>
References: <alpine.LRH.1.00.0803110039560.26663@netcore.fi>
Date: Mon, 10 Mar 2008 19:22:37 -0400
To: Pekka Savola <pekkas@netcore.fi>
From: Stephen Kent <kent@bbn.com>
Cc: sidr@ietf.org
Subject: Re: [Sidr] Architecture document: narrowing the scope
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sidr-bounces@ietf.org
Errors-To: sidr-bounces@ietf.org

Pekka,

I agree that a title with a narrow scope is appropriate, but I 
believe that you suggested revision is too narrow. The RPKI is 
broader in scope than just route origination, as Geoff noted. For 
example, the SBGP and soBGP proposals,  which were debated 
extensively in RPSEC, both address path validation and both rely on 
the sort of PKI that is being covered in this document. I think some 
additional wordsmithing on the title and abstract is needed.

Steve
_______________________________________________
Sidr mailing list
Sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr