IETF Logo Mail Archive

Re: [sidr] RPKI <-> allocation consistency

Stephen Kent <kent@bbn.com> Tue, 28 August 2012 04:23 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 7CAA721E803F for <sidr@ietfa.amsl.com>; Mon, 27 Aug 2012 21:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.529
X-Spam-Level:
X-Spam-Status: No, score=-106.529 tagged_above=-999 required=5 tests=[AWL=0.070, 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 5dHMaJAyLkRU for <sidr@ietfa.amsl.com>; Mon, 27 Aug 2012 21:23:07 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 0795421E8039 for <sidr@ietf.org>; Mon, 27 Aug 2012 21:23:07 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:36914 helo=fritz.local) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1T6DKT-000AL4-O5; Tue, 28 Aug 2012 00:23:06 -0400
Message-ID: <503C47A8.7030700@bbn.com>
Date: Tue, 28 Aug 2012 00:23:04 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Eric Osterweil <eosterweil@verisign.com>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F555CB@Hermes.columbia.ads.sparta.com> <D857A4BB-E484-45A4-A09F-FB8FAF2215AC@tcb.net> <C5B88834-3A10-41F7-A4F3-2B7C9B540197@verisign.com> <50389897.3040503@bbn.com> <97856400-9F70-4AEC-AF91-A0673A6D716D@verisign.com>
In-Reply-To: <97856400-9F70-4AEC-AF91-A0673A6D716D@verisign.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: sidr@ietf.org
Subject: Re: [sidr] RPKI <-> allocation consistency
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: Tue, 28 Aug 2012 04:23:07 -0000

Eric,

It seems likely that not all RPs will have the same view of INR 
allocation, e.g., due to differences
in when RPs fetch data from repositories. This seems analogous to the 
transient inconsistencies that
ISPs see today if they use IRR or other INR data sources, for similar 
reasons.

I think Rob Austein has referred to the repository system as being 
"loosely consistent," a reasonable target for a large scale, distributed 
database with entries maintained by a large group of folks.

Steve

v2.23.0 | Report a Bug | By Email