Re: [Sidr] Architecture document: narrowing the scope

Danny McPherson <danny@tcb.net> Mon, 10 March 2008 23:48 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 38F7928C164; Mon, 10 Mar 2008 16:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.699
X-Spam-Level:
X-Spam-Status: No, score=-100.699 tagged_above=-999 required=5 tests=[AWL=-0.262, 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 Q+9UgxM2tcic; Mon, 10 Mar 2008 16:48:42 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DE983A6AFC; Mon, 10 Mar 2008 16:48:42 -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 DEE493A6AFC for <sidr@core3.amsl.com>; Mon, 10 Mar 2008 16:48:41 -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 aY2EIHMIOSKY for <sidr@core3.amsl.com>; Mon, 10 Mar 2008 16:48:41 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 3FB863A67A3 for <sidr@ietf.org>; Mon, 10 Mar 2008 16:48:41 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 4792F268037; Mon, 10 Mar 2008 17:46:21 -0600 (MDT)
Received: from dhcp-1587.ietf71.ietf.org (division.aa.arbor.net [152.160.38.65]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Mon, 10 Mar 2008 17:46:21 -0600 (MDT) (envelope-from danny@tcb.net)
Message-Id: <D38AE639-2669-44BF-8544-8FBF8D2BE3BD@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: Stephen Kent <kent@bbn.com>
In-Reply-To: <p06240516c3fb6e75c7b9@[10.150.134.25]>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 10 Mar 2008 17:46:05 -0600
References: <alpine.LRH.1.00.0803110039560.26663@netcore.fi> <p06240516c3fb6e75c7b9@[10.150.134.25]>
X-Mailer: Apple Mail (2.919.2)
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

On Mar 10, 2008, at 5:22 PM, Stephen Kent wrote:

> 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.

But RPKI provides an infrastructure *to enable those*, OR a static
route filter, or any of a number of other things.  Listing the array
of things that might be done and implying that SIDR itself provides
that capability is misleading.

-danny

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