Re: [sidr] sidrSlides for "RPKI Over BitTorrent" presentation

Wes Hardaker <wjhns1@hardakers.net> Thu, 24 May 2012 13:36 UTC

Return-Path: <wjhns1@hardakers.net>
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 10ADA21F8681 for <sidr@ietfa.amsl.com>; Thu, 24 May 2012 06:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 lkfA0-EQQi42 for <sidr@ietfa.amsl.com>; Thu, 24 May 2012 06:36:52 -0700 (PDT)
Received: from mail.hardakers.net (unknown [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id A21ED21F8683 for <sidr@ietf.org>; Thu, 24 May 2012 06:36:52 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:62d8:19ff:fed4:c8b6]) by mail.hardakers.net (Postfix) with ESMTPSA id 24CC4BC0; Thu, 24 May 2012 06:36:52 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: heasley <heas@shrubbery.net>
References: <20120326173305.D1CB96E71B3@minas-ithil.hactrn.net> <0lehqanzja.fsf@wjh.hardakers.net> <20120524131831.GG35070@shrubbery.net>
Date: Thu, 24 May 2012 06:36:51 -0700
In-Reply-To: <20120524131831.GG35070@shrubbery.net> (heasley's message of "Thu, 24 May 2012 13:18:31 +0000")
Message-ID: <0lwr41lmz0.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: sidr@ietf.org, Rob Austein <sra@hactrn.net>
Subject: Re: [sidr] sidrSlides for "RPKI Over BitTorrent" presentation
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, 24 May 2012 13:36:53 -0000

heasley <heas@shrubbery.net> writes:

>> This sure smells to me like a solution in need of multicast (or, more
>> accurately, "deployed multicast") with a fall back to something like
>> bittorrent for bootstrapping or when you've missed session data and
>> can't recover.  Multicast as a data stream would be much more efficient
>> is collecting updates, although there are still issues that would need
>> to be worked through like "how do you know you heard everything".  Oh,
>> and it only works if you multicast deployed to your site of course.
>
> please, we do not want multicast as the only solution.  does your noc know
> how to debug multicast forwarding problems?

I didn't say only :-) . In fact, I pointed at bittorrent as a backup.  I
simply said it would be more efficient when sending out *new* changes.
-- 
Wes Hardaker
SPARTA, Inc.