IETF Logo Mail Archive

Re: [sidr] working group adoption call for draft-kklf-sidr-route-server-rpki-light-01

"Carlos M. Martinez" <carlosm3011@gmail.com> Fri, 06 May 2016 19:35 UTC

Return-Path: <carlosm3011@gmail.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 1422112D5E2 for <sidr@ietfa.amsl.com>; Fri, 6 May 2016 12:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzglOliTxt4D for <sidr@ietfa.amsl.com>; Fri, 6 May 2016 12:35:09 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 970E112D52C for <sidr@ietf.org>; Fri, 6 May 2016 12:35:09 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id g133so200884024ywb.2 for <sidr@ietf.org>; Fri, 06 May 2016 12:35:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=S1TYkBgNSMGV5TYGkeQ3V6u6B4jqvCHP7aLco5naBdg=; b=qxBFgG3tMMp0E7f7tcBuN/5z+ZgVREKeSJmPwR0Vy8pdAbBpXYAW2UDZgznwabp+rK tXXaftYbQs8ROfNBvJ0sHtrOjmxqkRJ5xF4oadxm4apZwN1A4qKJK+BA0pQmducbvHzR uns9dlW0foGhglFbVfDMXTU40CvcDvmDo/Bq5cbH+O1cY/Rfn/YPpZYeg1BTLHePUQE5 +VnuSLLTKsP4wB94CUDi8vjbXHmG7RBs2UpMbC/XeDkAAH2BSplq6Le45fIguq0T16gg TNVQ+Mrj7mwGOxessIE7jSkuFHg7nDapdGSmw22kQDJSVToGm9AwI9tKT+QKUdbnl2dC ysug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=S1TYkBgNSMGV5TYGkeQ3V6u6B4jqvCHP7aLco5naBdg=; b=MNHT25jATK+IeD/pVocT/ckT/CcwFsf37poLQlyOFbNMc6mpymVSEBX+xO5g99xZhs ucX2Q2YszgXTi1kyQEapFzTPRXOZNdjrM0ubrjDI2Vr3A/b+ianTeJ2UbXx3EcvLgXpQ K5q6OlnGlvJj81Lr6RfxZvQHQ6TLskWkCxzcmA83/pMJcOVFC5QHu331bOM+cjkwGRNM yXlmkK1eokZ54MGvQZxBWI6herKdgAanB/WRbmtlqMdNDaYUwW14FlBCOmVfSRudb+5Y n8RlGc6rYjlZ2/eNOZUzLJw2k0shvSmGDKtNVlWlrO1fYm4GYCihgwheR4U5OFJQd2yF RlFA==
X-Gm-Message-State: AOPr4FW2nO/3X8LD6aXca60lfVvwWW5xoU5mLDcSozfw0LYw2O++D//zYbyMZMCkXydXvg==
X-Received: by 10.13.230.193 with SMTP id p184mr13324763ywe.81.1462563308934; Fri, 06 May 2016 12:35:08 -0700 (PDT)
Received: from [190.112.54.14] ([190.112.54.14]) by smtp.googlemail.com with ESMTPSA id l128sm9689338ywd.5.2016.05.06.12.35.07 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 May 2016 12:35:08 -0700 (PDT)
References: <13075573-8AFA-41D7-B0A3-E2B94DF78E61@tislabs.com> <CAL9jLaa6rcJ42cFyJEW1XTcvMfqnLr++VE7kHgpOG1ywL4S1JA@mail.gmail.com> <alpine.WNT.2.00.1605051758070.2308@mw-PC> <m2r3dgnmns.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>, Matthias Waehlisch <m.waehlisch@fu-berlin.de>
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
Message-ID: <152abece-c6cc-4715-bbd7-a86da29e15e3@gmail.com>
Date: Fri, 06 May 2016 15:35:05 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <m2r3dgnmns.wl%randy@psg.com>
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/t6noiaqUBW1cg2wzt8rgcFwuBVw>
Cc: sidr <sidr@ietf.org>
Subject: Re: [sidr] working group adoption call for draft-kklf-sidr-route-server-rpki-light-01
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: carlos@lacnic.net
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 06 May 2016 19:35:11 -0000

Hi!

On 5/5/16 6:51 PM, Randy Bush wrote:
>>> mostly because I don't see a clear method to ensure that 'third party' has:
>>>   1) up-to-date information
>>   Same with RTR cache server.
> 
> i would not load routers from rpki caches i do not own and control

Me neither. Yet people do it. Whether they are going to be majority or
not, time will tell.

> 
>>>   2) my best interest at heart
>>   If you peer with a route server, you should establish a trust relation 
>> anyway.
> 
> in my heart i agree with chris, a prudent operator does not outsource
> security.
> 
> otoh, i also do not think a prudent operator outsources bgp, i.e. uses a
> route server.
> 
> putting the two together, if you are willing to outsource bgp to a route
> server, then outsourcing bgp security to the route server is not much of
> a leap.

Agree 100%.

> 
> chris, think of it as shooting yourself in the foot with a two-barrelled
> gun instead of one with one barrel.  :)

:-)

-C.

v2.23.0 | Report a Bug | By Email