RE: Continental aggregation?

@ On Fri, 10 Jan 1997, Miguel A.L. Paraz wrote:
@ > Bradley Dunn wrote:
@ > > Is anyone currently aggregating at the continental boundary?
@ >
@ > Like, how? There isn't a single continent served by a only one provider,
@ > with the possible exception of Antarctica. :slight_smile:
@ Each continent is served by only one registry, correct?

It seems to me that there is a flaw in the way the IPv4 address space is
viewed with respect to registries. Rather than try to decide what is an
ISP or an upstream provider or for that matter a registry, would it not
be easier to just agree that...

  "Anyone or any organiztion who has been allocated a continguous
  block of IPv4 addresses with at least 16 bits of variable bits is
  considered to be a *registry* for that block and all addresses
  in that block. Those addresses can be loaned or leased as that
  *registry* sees fit subject to the terms and conditions of any
  agreements that organization may have with one or more superior
  registries whom allocated the block from a larger continguous block."

It seems to me that it is a historic fact and a historic mistake that IP
addresses have been allocated to many types of organizations without
those organizations understanding the *registry* duties that go with
such an allocation. For example. companies that have been allocated a /8
should be encouraged to be registries for that /8 or to pass the block to
a company that *is* willing to perform registry services for the block.

Registry services consist of:
  Operation of a IN-ADDR.ARPA Name Server
  Maintenance of Global IN-ADDR.ARPA Records
  Registry to Registry Coordination
  Network Engineering Assistance
  Routing Agreement Negotiations
  General Clerical Matters of Registries

Registry services have nothing to do with being an NSP, an ISP, an IAP,
an IPP, a webmaster, a geek, a guru, or a god.

If somehow, IPv4 addresses can be placed in the hands of *registries*
then the Internet can get on with the business of cleaning up the address
space. In many cases, the same organization that currently claims "ownership"
of an IPv4 address block could be considered to be a registry, but there should
be a recognition that the registry services are separate from the other missions
and operations of the organization.

Also, the block of IP addresses that more or less defines a registry, should
stay with the registry. The registry can of course be sold or consolidated with
a larger registry, but the registry function for that block could remain as an
autonimous entity.

As food for thought, I have included some notes on how registries can be
organized in a hierarchy. Even though registries do not necessarily allocate
on octet (byte) boundaries, they could be organized on those boundaries
for administrative and revenue flow purposes.

The following is only an example, for illustrative purposes.

@@@@@@@@@@ IPv8 Registry Revenue Notes @@@@@@@@@@@@

IPv8 addresses are 43 bits. They are 11 (3+8) bits larger than an IPv4 address.
This provides two levels of hierarchy above the IPv4 addresses.

The 3 bit field is called the Galaxy ID.
The 8 bit field is called the Stargate ID.

IPv8 addresses with a 0:0:x.x.x.x format are converted IPv4
addresses. IPv4 packets can be viewed as IPv8 packets
with an implied 0 in the Galaxy and Stargate fields.