Re: [RPSEC] BGP Security Requirements v08

Stephen Kent <kent@bbn.com> Fri, 20 July 2007 14:35 UTC

Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBtZV-0000Uc-5K; Fri, 20 Jul 2007 10:35:09 -0400
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1IBtZT-0000Oh-D0 for rpsec-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 10:35:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBtZT-0000OS-3W for rpsec@ietf.org; Fri, 20 Jul 2007 10:35:07 -0400
Received: from mx11.bbn.com ([128.33.0.80]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBtZS-0000CS-S8 for rpsec@ietf.org; Fri, 20 Jul 2007 10:35:07 -0400
Received: from dhcp89-089-071.bbn.com ([128.89.89.71]) by mx11.bbn.com with esmtp (Exim 4.60) (envelope-from <kent@bbn.com>) id 1IBtZS-0003aW-4Q; Fri, 20 Jul 2007 10:35:06 -0400
Mime-Version: 1.0
Message-Id: <p06240505c2c66fd32428@[128.89.89.71]>
In-Reply-To: <200707200246.l6K2kOPa055104@harbor.brookfield.occnc.com>
References: <200707200246.l6K2kOPa055104@harbor.brookfield.occnc.com>
Date: Fri, 20 Jul 2007 09:59:02 -0400
To: curtis@occnc.com
From: Stephen Kent <kent@bbn.com>
Subject: Re: [RPSEC] BGP Security Requirements v08
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Sandy Murphy <sandy@tislabs.com>, rpsec@ietf.org, Russ White <riw@cisco.com>
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=subscribe>
Errors-To: rpsec-bounces@ietf.org

At 10:46 PM -0400 7/19/07, Curtis Villamizar wrote:
>In message <p06240505c2c52c906079@[128.89.89.71]>
>Stephen Kent writes:
>> 
>>  The ROA scheme has a specific purpose, i.e., allowing a resource
>>  holder to express an globally-verifiable authorization to originate a
>>  route to the holder's prefix(es). ROAs ought not be criticized for
>>  not doing something that they are not intended to do.
>> 
>>  Steve
>
>
>ROA should be criticized for a major ommission relative to an existing
>scheme it is expecting to replace.  But we're off topic.
>
>Curtis

Perhaps more accurately, we're talking about this in the wrong WG.

Steve


_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec