Allocation of IP Addresses

I may be opening a can of worms, and if so, I believe it is one which needs
to be opened. If this topic has been beaten to death in the past, then I
apologize, however as it is a rapidly evolving topic, it warrants repeated
discussion and evaluation. My fundamental questions are:

1. Is InterNIC consistently applying objective criteria in its evaluation
of requests for the allocation of IP address blocks?
2. If so, what are the criteria?

The INTERNIC IP ALLOCATION GUIDELINES FOR INTERNET SERVICE PROVIDERS states
that "allocation is based on the ISP's 3 - 6 month requirement and other
information the InterNIC deems necessary". There is no detail provided (in
any document I have found) of what other information InterNIC deems to be
necessary.

I find an apparent conflict between established policy and its actual
implementation on a day-to-day basis. CIDR dictates that addresses should
be aggregated into the largest blocks possible, and that the publishing of
extraneous routes be eliminated. In keeping with this, and because of
often discussed operational considerations, the minimum size of blocks
routed at the NAPs is growing larger and larger. To ease participation at
the national level, you must ensure to the fullest extent possible that
your address space is routable as a single block. In order to accomplish
this, you must obtain either:

A. a single allocation capable of supporting planned growth, or
B. incremental allocations of *contiguous* blocks

InterNIC's current CIDR allocation practice does not support either of
these options. Due to the shortage of *available* IP addresses (there are
of course millions of allocated but unused addresses floating around),
InterNIC is using a "slow start" approach which provides incremental
increases in total address space, with no guarantee that future increments
will be contiguous. This means that the only way to maintain efficient
routing is to engage in repeated renumbering of customer addresses to
consolidate into increasingly larger blocks.

How many times is it reasonable to ask a customer to renumber? Once is
certainly reasonable. Twice is questionable. More than that and I would
suspect the customer would renumber all right, but as part of shifting to a
different ISP.

The day to day implementation of policy by the InterNIC has increasingly
critical impact on our industry, to the point of controlling who has the
opportunity to succeed and who does not. IMHO, it is imperative that:

1. this function be performed in an understandable manner,
2. objective criteria be consistently applied
3. the criteria in use be publicly available, and
4. there be defined mechanisms for the 'appeal' of decisions made in the
processing of allocation requests.

Recent experience and observation leads me to conclude that these
imperatives are perhaps not being met. Am I all wet???

I may be opening a can of worms, and if so, I believe it is one which needs
to be opened. If this topic has been beaten to death in the past, then I
apologize, however as it is a rapidly evolving topic, it warrants repeated
discussion and evaluation. My fundamental questions are:

1. Is InterNIC consistently applying objective criteria in its evaluation
of requests for the allocation of IP address blocks?
2. If so, what are the criteria?

The INTERNIC IP ALLOCATION GUIDELINES FOR INTERNET SERVICE PROVIDERS states
that "allocation is based on the ISP's 3 - 6 month requirement and other
information the InterNIC deems necessary". There is no detail provided (in
any document I have found) of what other information InterNIC deems to be
necessary.

I find an apparent conflict between established policy and its actual
implementation on a day-to-day basis. CIDR dictates that addresses should
be aggregated into the largest blocks possible, and that the publishing of
extraneous routes be eliminated. In keeping with this, and because of
often discussed operational considerations, the minimum size of blocks
routed at the NAPs is growing larger and larger. To ease participation at
the national level, you must ensure to the fullest extent possible that
your address space is routable as a single block. In order to accomplish
this, you must obtain either:

This is because the internic is not the one saying /18 or smaller, NSP
are doing that. Why should the internic get involved?

A. a single allocation capable of supporting planned growth, or
B. incremental allocations of *contiguous* blocks

InterNIC's current CIDR allocation practice does not support either of
these options. Due to the shortage of *available* IP addresses (there are
of course millions of allocated but unused addresses floating around),
InterNIC is using a "slow start" approach which provides incremental
increases in total address space, with no guarantee that future increments
will be contiguous. This means that the only way to maintain efficient
routing is to engage in repeated renumbering of customer addresses to
consolidate into increasingly larger blocks.

Yes, well there is no other way of doing it. The days of starting a ISP
out of your house and in a few years be a Sprint is falling away. ISP's
will just need to get space from there upstream provider and renumber.

How many times is it reasonable to ask a customer to renumber? Once is
certainly reasonable. Twice is questionable. More than that and I would
suspect the customer would renumber all right, but as part of shifting to a
different ISP.

As many as it takes, This is just something you are going to need to deal
with. We started with small blocks and had to renumber several times so
far. It is just part of growing, until you are a large NSP connected to
all the NAPs you will just need to start will small blocks and renumber
over and over until you get /18 or smaller.

The day to day implementation of policy by the InterNIC has increasingly
critical impact on our industry, to the point of controlling who has the
opportunity to succeed and who does not. IMHO, it is imperative that:

1. this function be performed in an understandable manner,
2. objective criteria be consistently applied
3. the criteria in use be publicly available, and
4. there be defined mechanisms for the 'appeal' of decisions made in the
processing of allocation requests.

Recent experience and observation leads me to conclude that these
imperatives are perhaps not being met. Am I all wet???

This is not something that the internic need to be involved with, one day
a NSP is filtering a /19 and larger the next something different. It is
not the InterNIC job to get involved with that. ISPs should just get
space from there upstream provider.

Nathan Stratton CEO, NetRail, Inc. Your Gateway to the World!

A. a single allocation capable of supporting planned growth, or
B. incremental allocations of *contiguous* blocks

InterNIC's current CIDR allocation practice does not support either of
these options.

Here's an idea. Let new ISP's reserve large blocks (say /16's) in 65/8,
66/8, .... but don't let them actually use these addresses on the global
Internet. Then, the ISP can run a Network Address Translation gateway and
give their customers 65/8 addresses while still using a chunk from their
provider's block. And they can switch providers without forcing their
customers to renumber. Then, after they have demonstrated that they
should be given a /16, open up the block they were given in 65/8 for use
without the NAT.

Of course, there is one little problem with this....

bash$ whois 65
Air Force Logistics Command (ASN-LOGNET) LOGNET-AS 65
IANA (RESERVED-7) Reserved 64.0.0.0 - 95.0.0.0

bash$ whois 96
Army Finance and Accounting Office (ASN-JTELS) JTELS-BEN1-AS 96
IANA (RESERVED-8) Reserved 96.0.0.0 - 126.0.0.0

How did these guys get such big chunks of address space reserved?

The day to day implementation of policy by the InterNIC has increasingly
critical impact on our industry, to the point of controlling who has the
opportunity to succeed and who does not. IMHO, it is imperative that:

1. this function be performed in an understandable manner,
2. objective criteria be consistently applied
3. the criteria in use be publicly available, and
4. there be defined mechanisms for the 'appeal' of decisions made in the
processing of allocation requests.

Recent experience and observation leads me to conclude that these
imperatives are perhaps not being met. Am I all wet???

I think that the fundamental problem here is that the Internic is
fundamentally clueless about important issues such as global routing and
*BUSINESS* issues. They are behaving a lot like a government bureaucracy
or a regulatory agency.

I don't really see how this can be fixed with the current system of
having a US government agency writing a contract with a private US
company to provide a fundamental international infrastructure service!

Michael Dillon Voice: +1-604-546-8022
Memra Software Inc. Fax: +1-604-546-3049
http://www.memra.com E-mail: michael@memra.com

[give ISP's blocks out of 65/8, 96/8?]

Of course, there is one little problem with this....

bash$ whois 65
Air Force Logistics Command (ASN-LOGNET) LOGNET-AS 65
IANA (RESERVED-7) Reserved 64.0.0.0 - 95.0.0.0

bash$ whois 96
Army Finance and Accounting Office (ASN-JTELS) JTELS-BEN1-AS 96
IANA (RESERVED-8) Reserved 96.0.0.0 - 126.0.0.0

How did these guys get such big chunks of address space reserved?

IANA: Internet Assigned Numbers Authority. The address space is theirs to
delegate in the first place. 64/8-126/8 is old Class-A space that is
"reserved indefinitely" according to RFC1466 (May '93).

// Matt Zimmerman Chief of System Management NetRail, Inc.
// mdz@netrail.net sales@netrail.net
// (703) 524-4800 [voice] (703) 524-4802 [data] (703) 534-5033 [fax]

Look one more time, AS65 is reserved for Air Force and AS96 for the Army,
the blocks are reserved for the IANA.

Nathan Stratton CEO, NetRail, Inc. Your Gateway to the World!