[sidr] RPKI Repo concerns WAS Re: Interim Meeting Dates/Locations (Proposed)

Terry Manderson <terry.manderson@icann.org> Wed, 28 March 2012 06:22 UTC

Return-Path: <terry.manderson@icann.org>
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 84E3921F86F3 for <sidr@ietfa.amsl.com>; Tue, 27 Mar 2012 23:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.54
X-Spam-Level:
X-Spam-Status: No, score=-106.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNvoui4Z7sxN for <sidr@ietfa.amsl.com>; Tue, 27 Mar 2012 23:22:33 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id 1514821F86DD for <sidr@ietf.org>; Tue, 27 Mar 2012 23:22:33 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Tue, 27 Mar 2012 23:22:31 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Matt Lepinski <mlepinski@bbn.com>, "sidr@ietf.org" <sidr@ietf.org>
Date: Tue, 27 Mar 2012 23:22:30 -0700
Thread-Topic: RPKI Repo concerns WAS Re: [sidr] Interim Meeting Dates/Locations (Proposed)
Thread-Index: Ac0MZ+COw2NxfUU7Q1iC63zkT2zavAAQ0ajH
Message-ID: <CB98EB46.239C3%terry.manderson@icann.org>
In-Reply-To: <4F723D2A.6080007@bbn.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3415796550_10091091"
MIME-Version: 1.0
Subject: [sidr] RPKI Repo concerns WAS Re: Interim Meeting Dates/Locations (Proposed)
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: Wed, 28 Mar 2012 06:22:33 -0000

Hi Matt,

On 28/03/12 8:20 AM, "Matt Lepinski" <mlepinski@bbn.com> wrote:
> 
> I see your point here. However, I am personally very grateful to Rob for
> his BitTorrent experiment. I believe that the choke point of the global
> RIR repositories is a vital challenge in RPKI deployment.

Excellent - so we have a defined, and succinct problem statement.
"The choke point of the global RIR repositories is a vital challenge in RPKI
deployment."

> I think the
> working group would benefit from spending significant bandwidth thinking
> about this challenge and I see Rob's presentation as a very reasonable
> way to get the ball rolling.

It's a thought process. And I don't mind seeing the idea thrown "out there"
with a speculative solution. My comments were in parallel with the time /
form / agenda of the proposed interim meetings, and the idea that some
(many?) will be churning additional resources from their own companies to
participate and in that participate remotely with all the obvious foibles
that brings.

> 
> That is, this particular topic has been completely dormant on the

Sorry, has this been previously raised on the ML? I couldn't find anything
in a quick scan of the archives. Do you have a pointer?

> mailing list in the past months. Therefore, doing any kind of concrete
> experiment and presenting it to the working group as a possible approach
> for getting around the global-repository choke-point seems like a
> valuable way to spur work/discussion on this topic.
> 

I appreciate experimentation as a valuable precursor to discussion, but more
than anything I would love to see some requirements fleshed out in working
group form first.

Cheers
Terry