Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?

Joe Touch <touch@isi.edu> Sun, 05 June 2011 22:20 UTC

Return-Path: <touch@isi.edu>
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 E84BB21F84E5 for <sidr@ietfa.amsl.com>; Sun, 5 Jun 2011 15:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Dhc7hDvTrZPb for <sidr@ietfa.amsl.com>; Sun, 5 Jun 2011 15:20:30 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by ietfa.amsl.com (Postfix) with ESMTP id 3555721F84E4 for <sidr@ietf.org>; Sun, 5 Jun 2011 15:20:29 -0700 (PDT)
Received: from [172.20.0.222] (pc2.kyotoint1-unet.ocn.ne.jp [211.123.99.34]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p55MJt7O007481 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sun, 5 Jun 2011 15:20:07 -0700 (PDT)
Message-ID: <4DEC010B.1090107@isi.edu>
Date: Sun, 05 Jun 2011 15:19:55 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <4DAF44AC.8060408@isi.edu> <F0FABE61-FC1D-45ED-A21D-ED7A1228A997@isi.edu> <01eb01cc0325$6e4fd260$4001a8c0@gateway.2wire.net> <4DB592B3.3090805@isi.edu> <033e01cc05a8$0a82f160$4001a8c0@gateway.2wire.net> <4DB9A456.3060709@isi.edu> <BANLkTikg18FV5H0bOdOfWMzpTcm_B__EVQ@mail.gmail.com> <017b01cc13ff$0cb6da40$4001a8c0@gateway.2wire.net> <BANLkTink82qvhge6rRhqt5+h-2mEkKBMhA@mail.gmail.com> <m21uzwr3tw.wl%randy@psg.com> <BANLkTimPnMfE1ii=6uwAckoFY0yUU=w43g@mail.gmail.com> <BANLkTinu8pxxCj4cdJzbS3z5h=8=s+U3Gw@mail.gmail.com> <D1D8138DDF34B34B8BC68A11262D10790F6233E006@EUSAACMS0701.eamcs.ericsson.se> <Pine.WNT.4.64.1106031624560.2148@SMURPHY-LT.columbia.ads.sparta.com> <D1D8138DDF34B34B8BC68A11262D10790F6233E04A@EUSAACMS0701.eamcs.ericsson.se> <D1D8138DDF34B34B8BC68A11262D10790F6233E0E3@EUSAACMS0701.eamcs.ericsson.se> <BANLkTikqeHdq15P7yC1A6owtrKGBWQsKkQ@mail.gmail.com> <1F1804CA-BC0D-4231-B83B-1F3DAE29CDC1@isi.edu> <BANLkTikN2tBkqV8ETawx29WqmnOsPn7m9Q@mail.gmail.com>
In-Reply-To: <BANLkTikN2tBkqV8ETawx29WqmnOsPn7m9Q@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p55MJt7O007481
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "stephen.farrell@cs.tcd.ie" <stephen.farrell@cs.tcd.ie>, Sandra Murphy <Sandra.Murphy@sparta.com>, "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?
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: Sun, 05 Jun 2011 22:20:32 -0000

Hi, all,

On 6/4/2011 5:56 PM, Christopher Morrow wrote:
> On Sat, Jun 4, 2011 at 10:02 AM, Joe Touch<touch@isi.edu>  wrote:
>> So basically the problem is that:
>>
>> - routers don't all support IPsec for the control plane
>>
>> - servers don't yet implement AO
>
> routers don't yet support AO either :( at least not in juniper 10.x
> code nor cisco 12.2(S) or 15 code...
> (or not that I've seen and been able to configure, though at least 1
> of the 2 there say 'coming RSN!')

One other thing to keep in mind is whether this doc (and to some extent, 
the IETF as a whole) should follow or lead.

If we're followers, then the answer is clear - watch what the hackers 
implement.

If we're leaders, we should focus on the goal state, recognizing that 
all issued requirements are - at best - goals anyway.

>> Yes, servers will support AO, if for no other reason than they support BGP and MD5 now.
>
> agreed, some heat is required to make this happen (heat == 'gosh I'd
> love my Oracle/fbsd/linux server(s) to be able to run quagga to my new
> and old IOS boxes...')

Again, follow vs. lead. If we're leading, then we should recognize that 
we're talking about a very small amount of resources need to accomplish 
this task. I'm already working with the funding agencies and a few 
companies with similar 'rfp' processes to access those resources. If 
anyone wants to help with any resources, please let me know.

Joe