IETF Logo Mail Archive

Re: [sidr] pCNT & prepending

Stephen Kent <kent@bbn.com> Thu, 28 July 2011 16:59 UTC

Return-Path: <kent@bbn.com>
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 DC99E11E80F9 for <sidr@ietfa.amsl.com>; Thu, 28 Jul 2011 09:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.57
X-Spam-Level:
X-Spam-Status: No, score=-106.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5J8-7r6scO2 for <sidr@ietfa.amsl.com>; Thu, 28 Jul 2011 09:59:40 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 5877D11E8106 for <sidr@ietf.org>; Thu, 28 Jul 2011 09:59:40 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:56411 helo=[130.129.18.170]) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1QmTvp-000Lle-Qv; Thu, 28 Jul 2011 12:59:33 -0400
Mime-Version: 1.0
Message-Id: <p06240802ca5744407d5d@[130.129.18.170]>
In-Reply-To: <CA56FC4F.5AC4E%dougm.tlist@gmail.com>
References: <CA56FC4F.5AC4E%dougm.tlist@gmail.com>
Date: Thu, 28 Jul 2011 12:57:37 -0400
To: Doug Montgomery <dougm.tlist@gmail.com>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] pCNT & prepending
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 28 Jul 2011 16:59:41 -0000

At 11:53 AM -0400 7/28/11, Doug Montgomery wrote:
>...
>
>One could think of having RS's somehow announce/declare themselves (e.g.,
>an RPKI object/flag) ... But I will point out that if I am unscrupulous I
>will just announce myself and proceed.

yes, but if you do so, then there is a signed record of that, if we 
follow Roque's suggestion and include an EKU in the router cert.  If 
contracts for resource allocation include language that prohibits 
using the RPKI to make false assertions about RS-ness, then this 
could be a basis for revocation ...

(As someone who is going through the resource allocation process with 
an RIR, I know that there are already a lot of criteria that I have 
promised to not violate, and that provide a basis for termination of 
my allocation, so this could be added to that list :-).)

Steve

v2.23.0 | Report a Bug | By Email