nanog mailing list archives
Re: BGP Peering Info
From: Leo Bicknell <bicknell () ufp org>
Date: Wed, 14 Jul 1999 09:13:44 -0400
On Tue, Jul 13, 1999 at 11:43:03PM -0500, Michael P. Lucking wrote:
Cable & Wireless USA http://infopage.cw.net/Routing/addbgpinfo.html
Interesting statement #1: What routes do you want to hear from us? Backbone Routes (2 routes) Customer Routes (approximately 11,500 routes) Full Routes (approximately 35,000 routes)
Sprint http://www.sprint.net/maint/bgprequest.cgi
Interesting statement #2: Option Number of Routes CPU/Mem. Requirement No Routes 1 (default) 2501/3000 or equivalent Partial Routes 20,000 2501/3000 or equivalent with 16+meg memory Full Routes 45,000 4000 or equivalent with 64+meg of memory I'm not trying to point out an error, although they should be updated. It's just amazing how quickly things get out of date and don't get updated. -- Leo Bicknell - bicknell () ufp org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request () tmbg org, www.tmbg.org
Current thread:
- BGP Peering Info Mark Cobb (Jul 13)
- Re: BGP Peering Info Michael P. Lucking (Jul 13)
- Re: BGP Peering Info batz (Jul 14)
- Re: BGP Peering Info Leo Bicknell (Jul 14)
- Re: BGP Peering Info Daniel Golding (Jul 14)
- Re: BGP Peering Info Phillip Vandry (Jul 14)
- <Possible follow-ups>
- Re: BGP Peering Info Rich Sena (Jul 13)
- Re: BGP Peering Info Michael P. Lucking (Jul 13)