As per Relevance of the word experimental, we have this rfc below:
Network Working Group R.
Request for Comments: 1897 Ipsilon
Category: Experimental J.
January 1996
IPv6 Testing Address
Status of this
This document specifies an Experimental protocol for the
community. This memo does not specify an Internet standard of
kind. Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited
1.0
This document describes an allocation plan for IPv6 addresses to
used in testing IPv6 prototype software. These addresses
temporary and will be reclaimed in the future. Any IPv6 system
these addresses will have to renumber at some time in the future
These addresses will not to be routable in the Internet other
for IPv6 testing
The addresses described in this document are consistent with the IPv
Addressing Architecture [ARCH]. They may be assigned to
manually, with IPv6 Auto Address Allocation [AUTO], or with DHCP
IPv6 [DHCPv6].
Hinden & Postel Experimental [Page 1]
RFC 1897 IPv6 Testing Address Allocation January 1996
2.0 Address
The address format for the IPv6 test address is consistent with
provider-based unicast address allocation [PRVD] which is as follows
| 3 | 5 bits | 16 bits | 8 | 24 bits | 8 | 64 bits |
+---+----------+----------+---+------------+---+----------------+
|010|RegistryID|ProviderID|RES|SubscriberID|RES|Intra-Subscriber
+---+----------+----------+---+------------+---+----------------+
The specific allocation of each field of the test address format
as follows
| 3 | 5 bits | 16 bits | 8 | 24 bits | 8 | 16 bits|48 bits
+---+----------+----------+---+------------+---+--------+-------+
| | |Autonomous| | IPv4 | | Subnet | Intf. |
|010| 11111 | System |RES| Network |RES| | |
| | | Number | | Address | | Address| ID |
+---+----------+----------+---+------------+---+--------+-------+
where
010
This is the Format Prefix used to identify provider-
unicast addresses
11111
This is a Registry ID reserved by the IANA. The initial use
addresses in this Registry ID for IPv6 testing is temporary
All users of these addresses will be required to renumber
some time in the future
Autonomous System
This is the current autonomous system number assigned to
provider providing internet service to the an IPv6
organization. For example for IPv6 testers receiving
service from BBN Barrnet would use autonomous system number 189.
This would be coded in the autonomous system field of
address as follows
0000 0000 1011 1101 (binary
Hinden & Postel Experimental [Page 2]
RFC 1897 IPv6 Testing Address Allocation January 1996
The values for the autonomous system number of an organization'
provider can be obtained from that provider, or can be looked
in the "whois" database maintained by the internic.net
This field is reserved and must be set to zero
IPv4 Network
This is based on the current IPv4 routable address for
subscriber which the interface is connected. It is formed
taking the high order 24 bits of the IPv4 address. For
for an IPv4 address (in IPv4 syntax):
IPv4
------------
39.11.22.1
the value to put in this field of IPv6 address is
IPv4 Format
------------ ------
39.11.22 270B16
This technique for generating values for this field only
for subscribers which have IPv4 subscriber prefixes less
equal to 24 bits long. There may be subscribers using IPv
addresses with longer subscriber prefixes, but this conflict
expected to be very rare. Subscribers with subscriber
larger than 24 bits should use the remaining bits in the IPv
prefix as the high order bits in the Subnet Address field
This field is reserved and must be set to zero
Subnet
The Subnet ID identifies a specific physical link on which
interface is located. There can be multiple subnets on the
physical link. A specific subnet can not span multiple
links. The assignment of values for this field is left to
individual subscriber. One possible algorithm to
values for this field is to use the bits in the IPv4
which identify the IPv4 subnet
Hinden & Postel Experimental [Page 3]
RFC 1897 IPv6 Testing Address Allocation January 1996
Interface
This is the unique identifier of the interface on the link
usually the 48-bit IEEE 802 MAC address of the interface
available
4.0
[ARCH] Hinden, R., and S. Deering, Editors, "IP Version 6
Addressing Architecture", RFC 1884, Ipsilon Networks,
PARC, December 1995.
[AUTO] Thomson, S., "IPv6 Stateless Address Autoconfiguration",
Work in Progress
[DHCP6] Bound, J., "Host Configuration Protocol for IPv6",
in Progress
[PROV] Rekhter, Y., and P. Lothberg, "An IPv6 Provider-
Unicast Address Format", Work in Progress
5.0 Security
Security issues are not discussed in this memo
6.0 Authors'
Robert M.
Ipsilon Networks, Inc
2191 E. Bayshore Road, Suite 100
Palo Alto, CA 94303
Phone: +1 415 846 4604
Fax: +1 415 855 1414
EMail: hinden@ipsilon.
Jon
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292-6695
Phone: +1 310 822 1511
Fax: +1 310 823 6714
EMail: postel@isi.
Hinden & Postel Experimental [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
