Mailing List Archive

Hi,

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. :)

--
miguel a.l. paraz <map@iphil.net> | pgp key id: 0x43F0D011
iphil communications, makati city, philippines | <http://www.iphil.net>











- - - - - - - - - - - - - - - - -

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. :)

Each continent is served by only one registry, correct?

I guess I should have been more clear. What I am wondering is anyone doing
what is described in RFC 1518, section 5.7?

Thanks!

-BD

- - - - - - - - - - - - - - - - -

On Friday, January 10, 1997 4:03 AM, Bradley Dunn[SMTP:bradley@dunn.org] wrote:
@ 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. :)
@
@ 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.

===================

8 Galaxy Registries
X:X:x.x.x.x
256 - Stargate Registries per Galaxy
X:X:x.x.x.x
256 - Continental Registries per Stargate
X:X:X.x.x.x
256 - Island Registries per Continent
X:X:X.X.x.x

Weighted Sum using double weights downstream
8+512+1024+2048 = 3592

Percentage Calculations
8/3592 = .002227
512/3592 = .142538
1024/3592 = .285077
2048/3592 = .570155

Revenue Percentages to Various Registries
57.0155% to Island Registry
28.5077% to Continental Registry
14.2538% to Stargate Registry
00.2227% to Galaxy Registry

======== EXAMPLE - Based on Lease Rate of $2 per IP Address per Year

Typical Class C scenario
256 IP address x $2 - $512/year Gross Revenue from Customer

$512 x 57.0155% = $291.919360 to Island Registry
$512 x 28.5077% = $145.959424 to Continental Registry
$512 x 14.2538% = $41.609601 to Stargate Registry
$512 x 00.2227% = $1.14 to Galaxy Registry

Theoretical Total Potential Gross Revenues

Island Registries handle /16 allocations (16 bit address space to manage)
$291.92 x 256 = $74,731.36 Gross Revenue for Island Registry

Continental Registries handle /8 allocations (24 bit address space to manage)
$145.96 x 65,536 = $9,565,634.56 Gross Revenue for Continental Registry

Stargate Registries handle /0 allocations (32 bit address16 space to manage)
$41.61 x 16,777,216 = $698,099,957.76 Gross Revenue to Stargate Registry

Galaxy Registries handle /-8 allocations (40 bit address space to manage)
$1.14 x 4,294,967,296 = $4,896,262,717.44 Gross Revenue to Galaxy Registry

=============================================================


--
Jim Fleming
UNETY Systems, Inc.
Naperville, IL

e-mail:
JimFleming@unety.net
JimFleming@unety.net.s0.g0 (EDNS/IPv8)

- - - - - - - - - - - - - - - - -

At 2:20 PM +0000 1/10/97, Miguel A.L. Paraz wrote:
>Hi,
>
>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. :)
>
>--
Miguel,

You have just given me even more ammunition for my argument that the IETF
needs to update RFC1149, "Standard for the Transmission of IP Datagrams
over Avian Media." Previously, I have been concerned that it ignored the
use of security mechanisms available in the transmission system, such as
audit trails left on windshields, rooftops, statues, etc.

But your comment reminds me that RFC1149 is not as general as claimed, but
is really pigeon-centric and oriented to metropolitan area transmission.
Clearly, Antarctica would make use of penguin-based transmission over much
wider areas.

Howard



- - - - - - - - - - - - - - - - -

...
>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.

Sigh.

Already you're requiring us to use
# config t
ip galazy-subnet-zero
ip stargate-subnet-zero
^Z

E


>===================

>8 Galaxy Registries
> X:X:x.x.x.x
> 256 - Stargate Registries per Galaxy
> X:X:x.x.x.x
> 256 - Continental Registries per Stargate
> X:X:X.x.x.x
> 256 - Island Registries per Continent
> X:X:X.X.x.x

>Weighted Sum using double weights downstream
>8+512+1024+2048 = 3592

>Percentage Calculations
>8/3592 = .002227
>512/3592 = .142538
>1024/3592 = .285077
>2048/3592 = .570155

>Revenue Percentages to Various Registries
> 57.0155% to Island Registry
> 28.5077% to Continental Registry
> 14.2538% to Stargate Registry
> 00.2227% to Galaxy Registry

>======== EXAMPLE - Based on Lease Rate of $2 per IP Address per Year

>Typical Class C scenario
> 256 IP address x $2 - $512/year Gross Revenue from Customer

> $512 x 57.0155% = $291.919360 to Island Registry
> $512 x 28.5077% = $145.959424 to Continental Registry
> $512 x 14.2538% = $41.609601 to Stargate Registry
> $512 x 00.2227% = $1.14 to Galaxy Registry

>Theoretical Total Potential Gross Revenues

>Island Registries handle /16 allocations (16 bit address space to manage)
>$291.92 x 256 = $74,731.36 Gross Revenue for Island Registry

>Continental Registries handle /8 allocations (24 bit address space to manage)
>$145.96 x 65,536 = $9,565,634.56 Gross Revenue for Continental Registry

>Stargate Registries handle /0 allocations (32 bit address16 space to manage)
>$41.61 x 16,777,216 = $698,099,957.76 Gross Revenue to Stargate Registry

>Galaxy Registries handle /-8 allocations (40 bit address space to manage)
>$1.14 x 4,294,967,296 = $4,896,262,717.44 Gross Revenue to Galaxy Registry

>=============================================================


>--
>Jim Fleming
>UNETY Systems, Inc.
>Naperville, IL

>e-mail:
>JimFleming@unety.net
>JimFleming@unety.net.s0.g0 (EDNS/IPv8)

- - - - - - - - - - - - - - - - -