[104640] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Splitting ARIN assignment

daemon@ATHENA.MIT.EDU (Scott Morris)
Thu May 22 12:49:28 2008

From: "Scott Morris" <swm@emanon.com>
To: "'James Kelty'" <jkelty@pandora.com>,
	<nanog@nanog.org>
Date: Thu, 22 May 2008 12:49:14 -0400
In-Reply-To: <4835A188.2000302@pandora.com>
Reply-To: swm@emanon.com
Errors-To: nanog-bounces@nanog.org

As long as your upstreams/partners are cool with that, there is no related
designation between how addresses are allocated versus how they are
announced.

In other words, TECHNICALLY you could advertise a whole bunch of /30's....
You just run the risk of being filtered and/or ridiculed along the way.  :)

But splitting the /22's from the same announcing AS shouldn't cause any
problems as long as you design your connectivity ok.

Scott 

-----Original Message-----
From: James Kelty [mailto:jkelty@pandora.com] 
Sent: Thursday, May 22, 2008 12:39 PM
To: nanog@nanog.org
Subject: Splitting ARIN assignment 

Hey all,

I'm looking for an opinion from the group. I have an ARIN /21 assignment and
a new requirement for a second data center. Rather than ask for another
assignment, I would like to advertise one /22 from one location and the
other /22 from the second location both with the same asn. My apps will work
that way, so I don't have an issue internally, but I'm looking for a broader
base opinion on that.

Thanks a lot!

-James




home help back first fref pref prev next nref lref last post