the Internet Backbone

Jim Fleming JimFleming at unety.net
Sat Apr 6 20:42:46 UTC 1996


On Saturday, April 06, 1996 6:10 AM, Michael Dillon[SMTP:michael at memra.com] wrote:
@On Sat, 6 Apr 1996, Jim Browning wrote:
@
@> Perhaps there needs to be a "Global Service Provider" or "Tier/Level 0" 
@> designation for those with International 'backbone circuits' and routers at 
@> meet points in other countries??
@
@I think we just need to recognize that there are Tier 1 providers in other 
@countries. Maybe we should replace the term "national" with 
@"broad geographic regions encompassing a signficant percentage of a 
@continent". Then providers like EUNet would qualify as Tier 1 providers
@although, like MCI, they also provide Tier 3 ISP services.
@
@If Sprint, MCI, ANS, Alternet/UUNET, PSI and AGIS/Net99 are the Tier 1 
@providers in North America, what networks would qualify as Tier 1in Europe
@and the Asia-Pacific region?
@
@Michael Dillon                                    Voice: +1-604-546-8022
@Memra Software Inc.                                 Fax: +1-604-546-3049
@http://www.memra.com                             E-mail: michael at memra.com
@
@
@

You can also use the terms "Galaxy" Provider and "StarGate" Providers if you like...:-)

A StarGate Provider has to be willing and able to manage a 32 bit address space....

None of the current carriers even comes close at this point...

<HTML>
<HEAD>
<TITLE>Galaxy/StarGate Reference Page</TITLE>
</HEAD>
<BODY BGCOLOR=#F0F0F0>
<CENTER>
<H1>Galaxy/StarGate Reference Page</H1>
<H3>C+ at nIP (CAT-NIP) Version</H3>
<H4>Jim Fleming - Unir Corporation</H4>
</CENTER>
<HR>
The Galaxy/StarGate system is being developed and tested to satisfy
the following needs, goals and objectives:
<UL>
<LI>Increase the Number of Available IP Addresses by a Factor of 2,048</LI>
<LI>Preserve and Co-Exist with Existing Networks, Servers and PCs</LI>
<LI>Provide Better Service Via Limited Hierarchical Routing</LI>
<LI>Accommodate a new DNS-Based Router Administration System</LI>
<LI>Focus Software Changes in Routers, not PCs and Servers</LI>
<LI>Accommodate Efficient Algorithms without Impacting Packet Transport</LI>
<LI>Evolve away from the IP Options Encoding Format</LI>
</UL>
<P>
<HR>
<H3>Introduction</H3>
The Internet Protocol (IP) is at the heart of the Internet.
Most packets of data that are sent via the Internet have a standard
format as shown below.
The IP Header is used to store information that allows a packet to be
routed to various locations.
<P>
The IP Header consists of a fixed part and an optional variable length
section. Both parts are always multiples of 32 bit words. Most packets
only contain a 20 byte header.
<P>
The IP Options part of an IP Header contains a variety of variable
length components that largely assist in tracing network routes and
in forcing packets to take a certain route.
<CENTER>
<H2>IP Packet Layout</H2>
<TABLE BORDER=1 CELLPADDING=2>
<TR>
	<TABLE BORDER=1 CELLPADDING=2 BGCOLOR=#FFD0D0>
	<TR ALIGN=CENTER>
	<TD COLSPAN=2>
	IP Header
	</TD>
	</TR>
	<TR>
	<TD ALIGN=CENTER WIDTH=180>
	Fixed Part<BR>(Five 32-Bit Words)<BR>20 Bytes
	</TD>
	<TD ALIGN=CENTER WIDTH=80>
	IP Options<BR>(0 to 40 bytes)
	</TD>
	</TABLE>
	<TD ALIGN=CENTER WIDTH=400>
DATA<BR>
Encoded using various protocols
	</TD>
	</TR>
</TR>
</TABLE>
</CENTER>
<HR>
<H3>Standard IP Headers</H3>
The details of the standard IP Header are shown below.
Headers without additional IP Options are 20 bytes (5 32-Bit Words) long.
The Header Length field indicates the number of 32-Bit words
in the IP Header. The maximum value of 15 (1111) allows for
up to 60 (15x4) bytes in the header. 
<P>
The IP Options section is restricted to 40 bytes since the
first 20 bytes are fixed and pre-allocated.
This has been viewed as a limitation in some systems and makes
the IP Options field a candidate for long-term replacement.
<P>
The Galaxy/StarGate system design is based on the recognition
that some of the IP Header fields can be used
for a short period of time and reconstructed if necessary without
lose of information.
<P>
There are three fields which are <I>borrowed</I> for the Galaxy/StarGate system:
<UL>
<LI>4-Bit Version</LI>
<LI>4-Bit Header Length</LI>
<LI>16-Bit Header Checksum</LI>
</UL>
The entire first byte is borrowed to carry the Galaxy addressing information.
The 16-Bit checksum field is used to carry the StarGate addresses.
These fields can be restored from information in the other IP Header fields.
<CENTER>
<H2>IP Header</H2>
<H4>Fixed Part - (Five 32-Bit Words) 20 Bytes</H4>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=660 BGCOLOR=#FFD0D0>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 1
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=78 BGCOLOR=#D0D0FF>
4-Bit<BR>Version<BR><B>0100 = 4</B>
</TD>
<TD ALIGN=CENTER WIDTH=76 BGCOLOR=#D0D0FF>
4-Bit<BR>Header<BR>Length
</TD>
<TD ALIGN=CENTER WIDTH=159>
8-Bit Type of Service<BR>(TOS)
</TD>
<TD ALIGN=CENTER WIDTH=320>
16-Bit<BR>Total Length (in bytes)
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 2
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=320>
16-Bit<BR>Identification
</TD>
<TD ALIGN=CENTER WIDTH=60>
3-Bit<BR>Flags
</TD>
<TD ALIGN=CENTER WIDTH=260>
13-Bit<BR>Fragment Offset
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 3
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=160>
8-Bit<BR>Time to Live (TTL)
</TD>
<TD ALIGN=CENTER WIDTH=159>
8-Bit<BR>Protocol
</TD>
<TD ALIGN=CENTER WIDTH=319 BGCOLOR=#D0FFD0>
16-Bit<BR>Header Checksum
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 4
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=638>
32-Bit<BR>Source IP Address
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 5
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=638>
32-Bit<BR>Destination IP Address
</TD>
</TR>
</TABLE>
	</TD>
</TR>
</TABLE>
</CENTER>
<HR>
<H3>C+ at nIP - The Key to Upgrading</H3>
In the goals stated at the top of the page, an emphasis has been
placed on simplicity.
This will allow software in existing routers and host systems
to be easily changed without a large impact on performance.
<P>
The first byte of the IP Header can be used to allow a smooth
transition.
As shown below, the high bit of the first byte can be set to a
one as an indicator that the Enhanced IP Header format is being used.
Once this bit is set, the remaining 7 bits can be freely used.
<P>
As shown, Bit 6 can be used as a flag to indicate whether
IP Options information follows the 20 Byte fixed IP Header.
If the bit is a 0, then no options follow and if 1, options are
present. This knowledge must be preserved, because to rebuild
the IP Header Length, the IP Options area has to be scanned to
determine the size. Bit 6 indicates whether the scan is necessary.
<CENTER>
<H2>C+ at nIP Byte</H2>
<TABLE BORDER=1 CELLPADDING=2 BGCOLOR=#D0D0FF>
<TR>
<TD ALIGN=CENTER COLSPAN=8>
<B>C+ at nIP Byte Definition</B>
</TD>
</TR>
<TR>
<TD ALIGN=CENTER>7</TD>
<TD ALIGN=CENTER>6</TD>
<TD ALIGN=CENTER>5</TD>
<TD ALIGN=CENTER>4</TD>
<TD ALIGN=CENTER>3</TD>
<TD ALIGN=CENTER>2</TD>
<TD ALIGN=CENTER>1</TD>
<TD ALIGN=CENTER>0</TD>
</TR>
<TD ALIGN=CENTER>
<B>1</B>
</TD>
<TD ALIGN=CENTER>
Options<BR><B>X</B>
</TD>
<TD ALIGN=CENTER COLSPAN=3>
Source Galaxy<BR><B>SSS</B>
</TD>
<TD ALIGN=CENTER COLSPAN=3>
Destination Galaxy<BR><B>DDD</B>
</TD>
</TR>
<TR>
</TABLE>
Options: 0 = No Options, 1 = Options Appended
</CENTER>
<P>
The remaining 6 bits of the C+ at nIP Byte are used to encode the
Source Galaxy and Destination Galaxy.
Each 3 bit field supports up to 8 different Galaxies.
Galaxy 0 is reserved for the Legacy Internet.
The other Galaxies are listed below.
<HR>
<H3>Enhanced IP Headers</H3>
In order to meet the goals and objectives stated at the top of this
page, a new IP Header format is used to encode Galaxy and StarGate
information.
As shown below, a 3-Bit Galaxy value and 8-Bit StarGate value can
be overlaid on to fields in a standard IP header.
The modified packet can be <I>tunneled</I> to another network
where the fields can be restored before it is delivered to
its final destination.
<P>
The addition of the 3-Bit Galaxy and 8-Bit StarGate addresses adds
11 bits to the 32 bit IP addresses. This results in an increase
of 2,048 available IP address spaces.
<CENTER>
<H2>Galaxy/StarGate IP Header</H2>
<H4>Fixed Part - (Five 32-Bit Words) 20 Bytes</H4>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=660 BGCOLOR=#FFD0D0>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 1
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=159 BGCOLOR=#D0D0FF>
8-Bit<BR>C+ at nIP Byte<BR><B>1 X SSS DDD</B>
</TD>
<TD ALIGN=CENTER WIDTH=159>
8-Bit Type of Service<BR>(TOS)
</TD>
<TD ALIGN=CENTER WIDTH=320>
16-Bit<BR>Total Length (in bytes)
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 2
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=320>
16-Bit<BR>Identification
</TD>
<TD ALIGN=CENTER WIDTH=60>
3-Bit<BR>Flags
</TD>
<TD ALIGN=CENTER WIDTH=260>
13-Bit<BR>Fragment Offset
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 3
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=160>
8-Bit<BR>Time to Live (TTL)
</TD>
<TD ALIGN=CENTER WIDTH=159>
8-Bit<BR>Protocol
</TD>
<TD ALIGN=CENTER WIDTH=159 BGCOLOR=#D0FFD0>
8-Bit<BR>Source StarGate
</TD>
<TD ALIGN=CENTER WIDTH=159 BGCOLOR=#D0FFD0>
8-Bit<BR>Destination StarGate
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 4
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=638>
32-Bit<BR>Source IP Address
</TD>
</TR>
</TABLE>
	</TD>
</TR>
<TR>
	<TD ALIGN=CENTER WIDTH=20>
Word 5
	</TD>
	<TD>
<TABLE BORDER=1 CELLPADDING=2 WIDTH=640>
<TR>
<TD ALIGN=CENTER WIDTH=638>
32-Bit<BR>Destination IP Address
</TD>
</TR>
</TABLE>
	</TD>
</TR>
</TABLE>
</CENTER>
<HR>
<CENTER>
<H2>Galaxy Assignments</H2>
<TABLE BORDER=1 CELLPADDING=5 BGCOLOR=#D0D0FF>
<TR>
<TD>0</TD>
<TD>Legacy Internet, R&D, Education, Etc.</TD>
</TR>
<TR>
<TD>1</TD>
<TD>North America (U.S., Mexico, Canada)</TD>
</TR>
<TR>
<TD>2</TD>
<TD>South America including Central America
</TR>
<TR>
<TD>3</TD>
<TD>England, Europe and Russia</TD>
</TR>
<TR>
<TD>4</TD>
<TD>Asia and the Pacific Rim</TD>
</TR>
<TR>
<TD>5</TD>
<TD>Africa and the Middle East</TD>
</TR>
<TR>
<TD>6</TD>
<TD>Australia and New Zealand</TD>
</TR>
<TR>
<TD>7</TD>
<TD>Islands, Boats, Spaceships, etc.</TD>
</TR>
</TABLE>
</CENTER>
<HR>
<H2>The Legacy Internet - G:0 S:0</H2>
For some period of time, the existing Internet (or Legacy Internet) will
be used by people and companies that desire basic global connectivity.
Despite people's claims about exhausting the IPv4 Internet Addresses,
there are many addresses which are not efficiently allocated and will
be reclaimed as resources become scarce.
<P>
Galaxy 0 (G:0) and StarGate 0 (S:0)
have been allocated for use by the Legacy Internet.
As traffic builds using the IPv8 format of the Galaxy/StarGate system,
studies can be conducted on which IPv4 addresses can be reassigned
to multiple Galaxies and StarGates.
<HR>
</BODY>
</HTML>

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

e-mail: JimFleming at unety.net




More information about the NANOG mailing list