Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Verio Decides what parts of the internet to drop

  • From: Alex P. Rudnev
  • Date: Sat Dec 04 17:20:05 1999

Btw, 
          it's crazy idea. I know a lot of 128-191.* networks with /19 and even
          /24 prefixes, and they should be routed independently.





On Thu, 2 Dec 1999 doug@safeport.com wrote:

> Date: Thu, 02 Dec 1999 15:46:15 -0500
> From: doug@safeport.com
> To: nanog@merit.edu
> Subject: Verio Decides what parts of the internet to drop
> 
> 
> IMHOTS
> 
> Apparently for their convenience Verio has decided what parts of the Internet I
> can get to. With no notification. This was (eventually) posted to the BSDI
> mailing list when some of us were cut from access to the site we need to
> maintain our OS.
> 
> For this I pay them.
> 
> Doug Denault
> --------------
> 
> "John A." wrote:
> > 
> > Heres a little more light on the subject.  This is a message we recieved
> > from Verio explaining why anybody that goes through their network can't
> > get to bsdi.  Because of this message, we are considering moving to a
> > different backbone.
> > 
> > John A.
> > Provide.Net
> > Ypsilanti, MI
> > 
> > >Date: Wed, 1 Dec 1999 01:15:07 +0000
> > >From: Wade Moeller <wmoeller@noc.verio.net>
> > >To: smike@provide.net
> > >Cc: Case Updates <updates@vanwebserv.verio.net>
> > >Subject: [v-666704] Routing to BSDI.com
> > >X-Mailer: Mutt 0.95.1i
> > >X-Disclaimer: My opinions are mine, and not those of anyone else.
> > >
> > >Hello there.  I am writing in regards to case #666704.  You have
> > >opened this ticket complaining that you cannot reach bsdi.com.  I am
> > >going to explain to you exactly what is happening and who needs to
> > >fix this.
> > >
> > >What is happening:
> > >       Cray Computer Corp. split up their Class B into two /17 networks
> > >and gave routing control over those IPs to 2 different ISPs.  Below
> > >are the routes being announced and the IP delegation from ARIN.
> > >
> > >First half of the Class B:
> > >BGP routing table entry for 134.195.0.0/17, version 15625171
> > >Paths: (7 available, best #3)
> > >  Advertised to peer-groups:
> > >     internal pop rr-pop
> > >  1 3404
> > >    165.117.56.98 (metric 33) from 165.117.1.145 (165.117.1.145)
> > >      Origin incomplete, metric 4294967294, localpref 100, valid,
> > >internal
> > >      Community: 1:1000 2548:183 2548:666 3706:153
> > >
> > >Second half of the Class B:
> > >BGP routing table entry for 134.195.128.0/17, version 15624883
> > >Paths: (19 available, best #13)
> > >  Advertised to peer-groups:
> > >     internal pop rr-pop
> > >  1 10487
> > >    165.117.56.98 (metric 33) from 165.117.1.145 (165.117.1.145)
> > >      Origin IGP, metric 4294967294, localpref 100, valid, internal
> > >      Community: 1:1000 2548:183 2548:666 3706:153
> > >
> > >Arin Delegation:
> > >Cray Computer Corporation (NET-CRAYCOS)
> > >   P.O. Box 17500
> > >   Colorado Springs, CO 80935
> > >
> > >   Netname: CRAYCOS
> > >   Netnumber: 134.195.0.0
> > >
> > >Verio has a BGP policy where we limit what announcements we will
> > >listen to when they are advertised to use.  This is keep the size of
> > >the routing table in check.  The policy is as follows:
> > >
> > >0.0.0.0-127.255.255.255 Verio will listen to no announcements less
> > >then a /20
> > >128.0.0.0-191.255.255.255 Verio will listen to no announcement less
> > >then a /16
> > >192.0.0.0-223.255.255.255 Verio will listen to no announcement less
> > >then a /24.
> > >
> > >We have modeled this after the allocation boundaries in use by ARIN,
> > >IE ARIN will not give out a /17 in the 128.0.0.0-191.255.255.255 IP
> > >space.
> > >
> > >Therefore we are ignoring the two /17 announcements since we will only
> > >accept them as a single /16 announcement.
> > >
> > >This is the current Verio policy and this is the future Verio policy.
> > >There has been much discussion of this policy and it is still in place
> > >so it will not be changing in the foreseeable future.
> > >
> > >Who needs to fix this:
> > >       As you can see the routes for each net-block is going through
> > >BBNPlanet (AS1) and then onto Colorado Internet Cooperative
> > >Association (AS3404) and Simple Network Communications, Inc.
> > >(AS10487).  Those last two companies need to consolidate their
> > >announcements so that they are able to announce the entire /16.
> > >Alternatively they may ask BBNPlanet to aggregate the the /17s into
> > >one /16 which we will listen to.  These are the only 2 actions that
> > >will let Verio's routers see those networks and route to them.
> > >
> > >If you have any further questions please do not hesitate to ask.
> > >
> > >--
> > >Wade Moeller                                      Network Tech I
> > >wmoeller@noc.verio.net                 (800)551-1630
> > >Here an OS, there an OS....I need more computers.
> -- 
> Douglas Denault
> support@safeport.com
> Voice: 301-469-8766
>   Fax: 301-469-0601
> 
> 

Aleksei Roudnev,
(+1 415) 585-3489 /San Francisco CA/






Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.