As per Relevance of the word experiment, we have this rfc below:
Network Working Group
Request for Comments: 1797
Category: Experimental April 1995
Class A Subnet
Status of this
This document defines an Experimental Protocol for the
community. This does not specify an Internet standard of any kind
Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited
There appears to be some interest in experimenting with
the class A addresses
There is some evidence that not all the routing software in use
deal correctly with subnetted class A addresses. It also
that actual use of subnetted class A addresses may be necessary
the not too distant future. It is suggested that conducting
experiment now to identify and fix any software that does
properly handle subnetted class A addresses would be useful
important
To further this experiment the IANA will temporarily designate
class A network number 39 to be used in the following way
The high order octet of the 4-octet IPv4 address is the class
network number 39. There are two cases for low order 24 bits
Case 1:
In the first case, the high order bit of these 24 bits is zero
the next 15 bits are the low order 15 bits of a
assigned Autonomous System number (AS), as registered by a
registry and listed in the RWhois database system
Using the AS number in this way allows the experiment to
underway quickly in that it automatically allocates some
to each service provider and does not require a registration step
One concern is that this might cause a run on AS numbers, since
getting an AS number you automatically get some address space
This concern should be offset by the fact that the amount
address space one gets under this plan is the same as one class
IANA [Page 1]
RFC 1797 Class A Subnet Experiment April 1995
network number (and it should be easier to get a single class
allocated than to get an AS number allocated), and that this is
limited time experiment so that these addresses will be temporary
The low order octet of the 4-octet IPv4 address is for local use
It is expected that an address of this form will be used
identify a specific publicly accessible Internet host
+--------+-+-------+--------+--------+
| 39 |0| low 15 bits AS | local |
+--------+-+-------+--------+--------+
Case 2:
In the second case, the high order bit of these 24 bits is one
and the remaining 23 bits are assigned by the IANA (
reserved for future use).
+--------+-+-------+--------+--------+
| 39 |1| variable prefix + local |
+--------+-+-------+--------+--------+
The general intent is to find a way to assign to
prefixes of differing lengths so that a variety of experiments
be conducted with the prefix/local-address boundary at
points
It is not intended that either of these address allocation schemes
the model for how subnetted class A addresses will be
allocated in the future
It is expected, to make the experiment interesting, that
providers will use these addresses for servers supplying
material via the Web or FTP
For example, if the service provider registered to use AS 690
to use this style of address to provide access to a server of
information on local host 7, the address would be
+--------+--------+--------+--------+
| 39 | 2 | 178 | 7 |
+--------+--------+--------+--------+
IANA [Page 2]
RFC 1797 Class A Subnet Experiment April 1995
The support for DNS name and address resolution should be provided
For example, if Alternet wanted to put up a database of
information using the hostname "Interesting.Alter.Net" using
address 39.2.189.7, they would need to put the name to
mapping in their name server using the A
Interesting.Alter.Net. IN A 39.2.189.7
Similarly, the address to name PTR record should be
7.189.2.39.IN-ADDR.ARPA. PTR Interesting.Alter.Net
which means that the 189.2.39 branch of the IN-ADDR tree would
delegated to Alternet for the purposes of this experiment
To support this, the 39.IN-ADDR.ARPA branch is delegated to the
to be managed at ISI. The nameserver for this branch
IN-ADDR.EP.NET (39.17.199.10). Participants in this
should contact the administrator of this nameserver to have
portion of the address space further delegated. The
for this server can be reached at .
Another aspect of the testing that should be performed is to
providers interchange addresses to test the portability of
class A addresses. It is not intended that this would be the
for actual use
For example, if AS 690 and AS 1800 want to try out routing
in each others' allocations within their AS, that should
encouraged. That is, suppose AS 690 handed some address of
addresses to AS 1800, and vice-versa. This type of testing
be necessary to see if the addresses can be made portable
larger sub-A allocations
This is experiment will be of limited duration and these
may be reassigned to other uses when the experiment is over
This experiment will begin on 1-May-95.
The current date for the termination of this experiment is 1-Dec-95.
IANA [Page 3]
RFC 1797 Class A Subnet Experiment April 1995
Security
Security issues are not discussed in this memo
Author's
Internet Assigned Numbers Authority (IANA
Information Sciences
University of Southern
4676 Admiralty Way, Suite 1001
Marina del Rey, CA 90292-6695
Phone: 1-310-822-1511
EMail: iana@isi.
IANA [Page 4]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
