I agree this is a broad topic and am cc'ing the wg list.
Can you expand more on why "Options (1) and (2) will not support
independent routing policies"? I can see that the campus would need
to cooperate on developing GENI-needed policies. Is that what you
We do plan to get some addresses from ARIN, although not for every
GENI component. There is no timeline yet. Our assumption has been
that, in general, if you were deploying something you would provide
addresses for it (your 'option 1' below) and we would assist you to
work with your IT dept on getting appropriate policies in place.
Perhaps this is simple-minded, but if it won't work it I'd like to
I think the goal of collecting parameters we need to register is a
good one. Is there anything other than IP addresses and AS numbers?
On Dec 1, 2008, at 3:42 PM, Joseph B. Evans wrote:
> GpENI is going to need IP space for its control and management
> plane, and perhaps for parts of the data path as well. I assume
> projects in other clusters are going to come up against this as well.
> GpENI is looking into a few options, (1) using KU or KANREN space,
> (2) using Internet2 space, (3) getting GpENI space from ARIN, or (4)
> getting space through a coordinated request to ARIN from the GPO.
> Note that eventually, we will also likely want to have at least one
> AS number for GENI. Options (1) and (2) will not support
> independent routing policies, and (3) is unlikely to be successful.
> So the question is, is the GPO pursuing IP space for the whole of
> GENI, and if so, what is the timeline? If not, well, I'd recommend
> that it should.
> There is some urgency to this, since renumbering will be
> increasingly irritating as the systems grow.
> I've copied the Substrate WG co-chairs because I think this is a
> general substrate issue.
> Joseph B. Evans, Ph.D. <evans@...>
> Distinguished Professor, Electrical Engineering & Computer Science
> Director, Information & Telecommunications Technology Center
> University of Kansas