Re: [sidr] Burstiness of BGP updates

Robert Raszuk <robert@raszuk.net> Fri, 18 November 2011 15:01 UTC

Return-Path: <robert@raszuk.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 DA9621F0C3E for <sidr@ietfa.amsl.com>; Fri, 18 Nov 2011 07:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wCnbBFh58uHa for <sidr@ietfa.amsl.com>; Fri, 18 Nov 2011 07:01:54 -0800 (PST)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 85C9E1F0C34 for <sidr@ietf.org>; Fri, 18 Nov 2011 07:01:54 -0800 (PST)
Received: (qmail 1960 invoked by uid 399); 18 Nov 2011 15:01:53 -0000
Received: from unknown (HELO ?10.0.1.3?) (203.69.99.16) by mail1310.opentransfer.com with ESMTP; 18 Nov 2011 15:01:53 -0000
X-Originating-IP: 203.69.99.16
Message-ID: <4EC67362.5050608@raszuk.net>
Date: Fri, 18 Nov 2011 16:01:54 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Tony Tauber <ttauber@1-4-5.net>
References: <D7A0423E5E193F40BE6E94126930C49308E9E35567@MBCLUSTER.xchange.nist.gov> <4EC32EBE.6030106@riw.us> <7309FCBCAE981B43ABBE69B31C8D21391A45A20633@EUSAACMS0701.eamcs.ericsson.se> <E2D346C7800D704DB41ED19D90434DA6320C15DF93@ESESSCMS0358.eemea.ericsson.se> <4EC33E88.9090505@riw.us> <7309FCBCAE981B43ABBE69B31C8D21391A45A20649@EUSAACMS0701.eamcs.ericsson.se> <4EC459F0.9070200@riw.us> <CAL9jLabyymUZJRk44Z00UeQsxinN5D-05-7_htmRanYwi7ysvQ@mail.gmail.com> <4EC462E9.7090103@riw.us> <m2wraz4j68.wl%randy@psg.com> <4EC4684B.3030204@riw.us> <m2ty634ie7.wl%randy@psg.com> <855A62C6-6654-4FA8-8644-B7B044C76148@verisign.com> <m2k46z4f1d.wl%randy@psg.com> <4EC48834.9060805@riw.us> <m2hb2346uq.wl%randy@psg.com> <09683D2C-A35A-4083-93D4-0E47B2106D83@apnic.net> <CAGQUKcd1nos+XfBzaSKrBu=oeNWGaMnA-AVa207GTr48pbrc2Q@mail.gmail.com> <4EC66C5F.7040302@raszuk.net> <CAGQUKcftCirgR_4_nuB54sNDDuHpJkURqU1spZ_SNkTH7WwokA@mail.gmail.com>
In-Reply-To: <CAGQUKcftCirgR_4_nuB54sNDDuHpJkURqU1spZ_SNkTH7WwokA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Burstiness of BGP updates
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.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: <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: Fri, 18 Nov 2011 15:01:59 -0000

Hi Tony,

> I'm not sure what "legal" thing you refer to.

Oh apologies .. I was under impression that we all following IETF alias 
as well as participate in global NOG/RIPE events.

As far as ietf alias see below:

-------- Original Message --------
Subject: Lawsuit against IETF/SIDR/RPKI? (fwd)
Date: Thu, 17 Nov 2011 12:06:48 -0500 (EST)
From: Paul Wouters <paul@xelerance.com>
To: ietf@ietf.org

Anyone have more info on this?

Paul

---------- Forwarded message ----------
Date: Thu, 17 Nov 2011 10:34:54
From: Vesna Manojlovic <becha@xs4all.nl>
To: p2p-sec@lists.puscii.nl
Subject: Lawsuit against IETF/SIDR/RPKI?
X-Spam-Flag: NO

You've heard it here first ;-)

But it's still only a rumor...

(does any of you have more news about it?)

Aparently, few big carriers in the States are preparing a lawasuit 
against RPKI creators, since they are funded by US government, _and_ are 
mandating the system that the ISPs will need to implement... so - 
anti-trust suit?

Conflict of interests? etc...

I could only find some "old news" about this:
http://www.networkworld.com/news/2010/121510-feds-internet-routing-security.html

That's why it is very important to continue with the development of the
alternatives to the routing security...

BTW, I got a ticket for 28c3, so -- see you there!

Ciao,
Vesna