Re: [GROW] A new bgpdump tool

Yasuhiro Ohara <yasu@nttv6.jp> Mon, 09 March 2015 04:52 UTC

Return-Path: <yasu@nttv6.jp>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6CE1A1B2E for <grow@ietfa.amsl.com>; Sun, 8 Mar 2015 21:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.496
X-Spam-Level: **
X-Spam-Status: No, score=2.496 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 6B0YbyUqIUy4 for <grow@ietfa.amsl.com>; Sun, 8 Mar 2015 21:52:09 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [115.69.231.228]) by ietfa.amsl.com (Postfix) with ESMTP id EBC511A1F70 for <grow@ietf.org>; Sun, 8 Mar 2015 21:52:08 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [IPv6:2402:c800:ff06:6::f]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 09B8A4E600; Mon, 9 Mar 2015 13:52:08 +0900 (JST)
Received: from localhost (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTPSA id A383D3AC84; Mon, 9 Mar 2015 13:52:07 +0900 (JST)
Date: Mon, 09 Mar 2015 13:51:07 +0900
Message-Id: <20150309.135107.1363168067214153689.yasu@nttv6.jp>
To: kemp@network-services.uoregon.edu
From: Yasuhiro Ohara <yasu@nttv6.jp>
In-Reply-To: <54F9F1F8.5020700@network-services.uoregon.edu>
References: <20150306.142705.1611674823609985976.yasu@nttv6.jp> <1425655141369.1718@nist.gov> <54F9F1F8.5020700@network-services.uoregon.edu>
Organizaton: NTT Communications
X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/6rrZ9thJ77Y-eYOPvPlc3emZky0>
Cc: grow@ietf.org
Subject: Re: [GROW] A new bgpdump tool
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2015 04:52:11 -0000

Hi John,

... I'm not sure yet if I'm following here.

I agree there are two perspectives, at least.
One is to compare the growth (time difference) of a
certain ISP's full-route routing table. Another is to
compare routing tables from different ISPs at a
certain time. However, I'm not sure what's the benefit
of comparing routing tables from two ISPs of different times.

The regexp is a great idea (I wonder why I couldn't think of it
myself from the first place). Even though I'm not sure if I can
implement all of them until the next IETF, I will work on it.

Thanks.

Best regards,
Yasu

From: John Kemp <kemp@network-services.uoregon.edu>
Subject: Re: [GROW] A new bgpdump tool
Date: Fri, 06 Mar 2015 10:29:12 -0800
Message-ID: <54F9F1F8.5020700@network-services.uoregon.edu>

> 
> Yasuhiro,
> 
> We are sort of at two ends of the spectrum here.
> If we are just talking about a simple tool, I guess the
> point I was making was that somehow you probably want to
> consider that there is a time domain.
> 
> For example, if your tool is parsing out ribs.  If it
> could also read those back in, and then do "comm" kinds
> of comparisons, then you could compare two ribs from different
> times.  IE what is common, what is in both, what is only in
> 1 vs. 2, or 2 vs. 1.
> 
> Or a kind of regexp feature might be nice.  You probably
> want ASPATH regexp to add to the prefix matching, as well
> as next-longest/next-shortest matching....
> 
> /jgk
> 
> On 3/6/15 7:19 AM, Sriram, Kotikalapudi wrote:
>>> Yes, I'm interested in route leaks. Now I'm wondering what kind of
>>> functions are beneficial in a BGP dump tool to help people check or
>>> find the route leaks. Please let me know if you have some idea.
>> 
>> Some additional references related to determining AS relations, routing policies, 
>> and route leak detection/mitigation:
>> 
>> "Valley-free violation in Internet routing - Analysis based on BGP Community data"
>> http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6363987&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6363987 
>> 
>> "AS Relationships, Customer Cones, and Validation"
>> http://www.caida.org/~amogh/papers/asrank-IMC13.pdf 
>> 
>> "A Survey of Interdomain Routing Policies"
>> https://www.cs.bu.edu/~goldbe/papers/survey.pdf
>> 
>> "Methods for Detection and Mitigation of BGP Route Leaks"
>> https://tools.ietf.org/html/draft-sriram-route-leak-detection-mitigation-00
>> (to be presented in the IDR WG meeting in Dallas)
>> 
>> Sriram
>> 
>> 
>> 
>