Routing Policy and http://rs.arin.net/ip-allocation.html

Jason L. Weisberger jweis at softaware.com
Wed May 6 19:58:01 UTC 1998


Anyways to address the actual question:

I haven't dealt with anyone other than Sprint filtering space longer than
/19 in the 206.0.0.0/8 but in the past I had issues with both UUnet and
Agis filtering errant /24's and /23's out of 204.0.0.0/8.

I've been very clearly telling all my customers that while I will route
their IP space for them, as long as its allocated to them - I will not be
responsible for anything that we know Sprint may or may not filter on any
given day. It generally works well, they take space from me and we
resubmit their space to whomever the governing body is/was at the time.

For customers that really have a need we push as hard as we can to get
them their own /19 so they'll not have to renumber but we know the issues
involved with this.

jlw


On Wed, 6 May 1998, Bryan Fullerton wrote:

> Date: Wed, 6 May 1998 13:26:12 -0400
> From: Bryan Fullerton <bryanf at samurai.com>
> To: Stephen Schmidt <steve at eagle.ais.net>, Mike Tancsa <mike at sentex.net>
> Cc: nanog at merit.edu
> Subject: Re: Routing Policy and http://rs.arin.net/ip-allocation.html
> 
> On Wed, May 06, 1998 at 11:51:38AM -0500, Stephen Schmidt <steve at eagle.ais.net> wrote:
> > > For the first time we have had to deal with  Sprint's routing policy as
> > > defined by http://www.sprint.net/filter.htm.  Here is the situation.  
> > > 
> > > One of our dialup customers wants to access his website in the
> > > 206.116.31.0/24 network at another provider.  PSI is advertising it as a
> > > /24.  According to Sprint's routing policy, they do not honour anything
> > > longer than a /19 in 206.0.0.0/8 . 
> > 
> > It's interesting that PSI routes it at all.  While IP ownership (note the
> > NON-PORTABLE below) and routing aren't necessarily interconnected, I
> > suggest contacting the block's owner and seeing if they know it's
> > alternately routed.  If they wish, they can request that PSI un-route this
> > block.  However, that would break whomever is using it.  The user should
> > re-number into PSI space, and this issue will go away.  If the user is
> > multi-homed, they should investigate the adivisibility of getting a CIDR
> > block which they can announce as an aggregate.
> > 
> > My $0.02
> > ___
> > iSTAR Internet Inc. (NETBLK-ISTAR0005)
> >    250 Albert Street, Suite 202
> >    Ottawa, Ontario K1P 6M1
> >    Canada
> [snip]
> 
> PSI bought iSTAR earlier this year, so it's not really surprising that
> they're routing these networks.
> 
> Bryan
> 
> -- 
> bryanf at samurai.com     Home      "You know, sometimes I just want to
> bryanf at canoe.ca        Work       be a chicken." - Master FehHead
> bryanf at icomm.ca        http://www.icomm.ca        http://www.feh.net
> 

--
Jason Weisberger
Chief Technology Officer
SoftAware, Inc. - 310/305-0275

"Let us cross over the river, and rest under the shade of the trees."
-Thomas Jonathan "Stonewall" Jackson





More information about the NANOG mailing list