End of life: 'sh ip bgp' collection on route-views.routeviews.org

	Folks,

	We're planning to end of life collection of 'sh ip bgp'
	RIBs from route-views.routeviews.org. We will of course
	keep the data we have. 

	Please let us know if you are still using these data. 

	Thanks,

	Dave

>> We're planning to end of life collection of 'sh ip
bgp'
>> RIBs from route-views.routeviews.org. We will of
course
>> keep the data we have. 
>> 
>> Please let us know if you are still using these
data. 

researchers do use rib shots.

it's feb 32nd 2012, and i want r-v's rib, i go back to 2008
and run in
all the updates since the last snap?  and this is viable,
let alone
reliable?

randy

On Thu, Mar 27, 2008 at 06:21:41AM +0900, Randy Bush wrote:
> 
> >> We're planning to end of life collection of
'sh ip bgp'
> >> RIBs from route-views.routeviews.org. We will
of course
> >> keep the data we have. 
> >> 
> >> Please let us know if you are still using
these data. 
> 
> researchers do use rib shots.
> 
> it's feb 32nd 2012, and i want r-v's rib, i go back to
2008 and run in
> all the updates since the last snap?  and this is
viable, let alone
> reliable?

	Randy,

	Its the Cisco 'sh ip bgp' format RIBs that we're planning
	to end-of-life, not the MRT format RIBs. Is that still a
	problem? In addition, we're looking at whether we can
	generate the 'sh ip bgp' format RIBs from the MRT format
	RIBs in the event someone has tools that take that format
	as input. 

	One important issue is that rv2.routeviews.org (where
	many of the MRT format RIBs are generated) has a
	different peer set than route-views.routeviews.org (where
	the 'sh ip bgp' RIBs come from).  I'm working on trying
	to regularize those now.

	In any event, please let me know if the end-of-life of
	the 'sh ip bgp' format RIBs is a problem.

	Thanks,

	Dave

On Thu, Mar 27, 2008 at 06:21:41AM +0900, Randy Bush wrote:
> 
> >> We're planning to end of life collection of
'sh ip bgp'
> >> RIBs from route-views.routeviews.org. We will
of course
> >> keep the data we have. 
> >> 
> >> Please let us know if you are still using
these data. 
> 
> researchers do use rib shots.
> 
> it's feb 32nd 2012, and i want r-v's rib, i go back to
2008 and run in
> all the updates since the last snap?  and this is
viable, let alone
> reliable?

	Parsing the MRT rib snapshots is much easier and more
predictable for an automated fashion than some CLI interface
that
can (and does) change unpredictably over time.

	The MRT data is far more valuable because it is easier to
automate analysis.

	- Jared


-- 
Jared Mauch  | pgp key available via finger from jaredpuck.nether.net
clue++;      | http://puck.nether.net
/~jared/  My statements are only mine.

On Thu, Mar 27, 2008 at 10:42:36AM -0400, Jared Mauch
wrote:
> 
> On Thu, Mar 27, 2008 at 06:21:41AM +0900, Randy Bush
wrote:
> > 
> > >> We're planning to end of life collection
of 'sh ip bgp'
> > >> RIBs from route-views.routeviews.org. We
will of course
> > >> keep the data we have. 
> > >> 
> > >> Please let us know if you are still using
these data. 
> > 
> > researchers do use rib shots.
> > 
> > it's feb 32nd 2012, and i want r-v's rib, i go
back to 2008 and run in
> > all the updates since the last snap?  and this is
viable, let alone
> > reliable?
> 
> 	Parsing the MRT rib snapshots is much easier and more
> predictable for an automated fashion than some CLI
interface that
> can (and does) change unpredictably over time.
> 
> 	The MRT data is far more valuable because it is easier
to
> automate analysis.
	
	Jarad,

	Thanks for the feedback. That was our sense as well, but
	I know that (in the past, anyway) some folks had built
	tools that used 'sh ip bgp' format input data. We didn't
	want to break those. As I mentioned to Randy, we're
	thinking we can generate 'sh ip bgp' format from MRT data
	(but there is still the "peer partity" issue;
we're
	working that now). 

	One other note on all of this. Part of the reason we
	wanted to take down the screen scraping to get the 'sh ip
	bgp' stuff is that route-views.routeviews.org is under
	quite a bit of CPU and memory stress. While we're in the
	process of trying to upgrade that box, resources are
	tight and it would be useful if we could free up the
	resources used in collecting that data.

	Dave