As per Relevance of the word multicast, we have this rfc below:
Network Working Group R. Hinden, Ipsilon
Request for Comments: 1884 S. Deering, Xerox
Category: Standards Track
December 1995
IP Version 6 Addressing
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
This specification defines the addressing architecture of the
Version 6 protocol [IPV6]. The document includes the IPv6
model, text representations of IPv6 addresses, definition of IPv
unicast addresses, anycast addresses, and multicast addresses, and
IPv6 nodes required addresses
Hinden & Deering Standards Track [Page 1]
RFC 1884 IPv6 Addressing Architecture December 1995
Table of
1. Introduction................................................3
2. IPv6 Addressing.............................................3
2.1 Addressing Model........................................4
2.2 Text Representation of Addresses........................4
2.3 Address Type Representation.............................5
2.4 Unicast Addresses.......................................7
2.4.1 Unicast Address Example.............................8
2.4.2 The Unspecified Address.............................9
2.4.3 The Loopback Address................................9
2.4.4 IPv6 Addresses with Embedded IPv4 Addresses.........9
2.4.5 NSAP Addresses......................................10
2.4.6 IPX Addresses.......................................10
2.4.7 Provider-Based Global Unicast Addresses.............10
2.4.8 Local-use IPv6 Unicast Addresses....................11
2.5 Anycast Addresses.......................................12
2.5.1 Required Anycast Address............................13
2.6 Multicast Addresses.....................................14
2.6.1 Pre-Defined Multicast Addresses.....................15
2.7 A Node's Required Addresses.............................17
REFERENCES.....................................................18
SECURITY CONSIDERATIONS........................................18
DOCUMENT EDITOR'S ADDRESSES....................................18
Hinden & Deering Standards Track [Page 2]
RFC 1884 IPv6 Addressing Architecture December 1995
1.0
This specification defines the addressing architecture of the
Version 6 protocol. It includes a detailed description of
currently defined address formats for IPv6 [IPV6].
The editors would like to acknowledge the contributions of
Francis, Jim Bound, Brian Carpenter, Deborah Estrin, Peter Ford,
Gilligan, Christian Huitema, Tony Li, Greg Minshall, Erik Nordmark
Yakov Rekhter, Bill Simpson, and Sue Thomson
2.0 IPv6
IPv6 addresses are 128-bit identifiers for interfaces and sets
interfaces. There are three types of addresses
Unicast: An identifier for a single interface. A packet
to a unicast address is delivered to the
identified by that address
Anycast: An identifier for a set of interfaces (
belonging to different nodes). A packet sent to
anycast address is delivered to one of the
identified by that address (the "nearest" one
according to the routing protocols' measure
distance).
Multicast: An identifier for a set of interfaces (
belonging to different nodes). A packet sent to
multicast address is delivered to all
identified by that address
There are no broadcast addresses in IPv6, their function
superseded by multicast addresses
In this document, fields in addresses are given a specific name,
example "subscriber". When this name is used with the term "ID"
identifier after the name (e.g., "subscriber ID"), it refers to
contents of the named field. When it is used with the term "prefix
(e.g., "subscriber prefix") it refers to all of the address up to
including this field
In IPv6, all zeros and all ones are legal values for any field
unless specifically excluded. Specifically, prefixes may
zero-valued fields or end in zeros
Hinden & Deering Standards Track [Page 3]
RFC 1884 IPv6 Addressing Architecture December 1995
2.1 Addressing
IPv6 Addresses of all types are assigned to interfaces, not nodes
Since each interface belongs to a single node, any of that node'
interfaces' unicast addresses may be used as an identifier for
node
An IPv6 unicast address refers to a single interface. A
interface may be assigned multiple IPv6 addresses of any
(unicast, anycast, and multicast). There are two exceptions to
model. These are
1) A single address may be assigned to multiple physical
if the implementation treats the multiple physical interfaces
one interface when presenting it to the internet layer. This
useful for load-sharing over multiple physical interfaces
2) Routers may have unnumbered interfaces (i.e., no IPv6
assigned to the interface) on point-to-point links to
the necessity to manually configure and advertise the addresses
Addresses are not needed for point-to-point interfaces
routers if those interfaces are not to be used as the origins
destinations of any IPv6 datagrams
IPv6 continues the IPv4 model that a subnet is associated with
link. Multiple subnets may be assigned to the same link
2.2 Text Representation of
There are three conventional forms for representing IPv6 addresses
text strings
1. The preferred form is x:x:x:x:x:x:x:x, where the 'x's are
hexadecimal values of the eight 16-bit pieces of the address
Examples
FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
1080:0:0:0:8:800:200C:417
Note that it is not necessary to write the leading zeros in
individual field, but there must be at least one numeral
every field (except for the case described in 2.).
2. Due to the method of allocating certain styles of IPv
addresses, it will be common for addresses to contain
strings of zero bits. In order to make writing
Hinden & Deering Standards Track [Page 4]
RFC 1884 IPv6 Addressing Architecture December 1995
containing zero bits easier a special syntax is available
compress the zeros. The use of "::" indicates multiple
of 16-bits of zeros. The "::" can only appear once in
address. The "::" can also be used to compress the
and/or trailing zeros in an address
For example the following addresses
1080:0:0:0:8:800:200C:417A a unicast
FF01:0:0:0:0:0:0:43 a multicast
0:0:0:0:0:0:0:1 the loopback
0:0:0:0:0:0:0:0 the unspecified
may be represented as
1080::8:800:200C:417A a unicast
FF01::43 a multicast
::1 the loopback
:: the unspecified
3. An alternative form that is sometimes more convenient
dealing with a mixed environment of IPv4 and IPv6 nodes
x:x:x:x:x:x:d.d.d.d, where the 'x's are the hexadecimal
of the six high-order 16-bit pieces of the address, and the 'd'
are the decimal values of the four low-order 8-bit pieces of
address (standard IPv4 representation). Examples
0:0:0:0:0:0:13.1.68.3
0:0:0:0:0:FFFF:129.144.52.38
or in compressed form
::13.1.68.3
::FFFF:129.144.52.38
2.3 Address Type
The specific type of an IPv6 address is indicated by the leading
in the address. The variable-length field comprising these
bits is called the Format Prefix (FP). The initial allocation
these prefixes is as follows
Hinden & Deering Standards Track [Page 5]
RFC 1884 IPv6 Addressing Architecture December 1995
Allocation Prefix Fraction
(binary) Address
------------------------------- -------- -------------
Reserved 0000 0000 1/256
Unassigned 0000 0001 1/256
Reserved for NSAP Allocation 0000 001 1/128
Reserved for IPX Allocation 0000 010 1/128
Unassigned 0000 011 1/128
Unassigned 0000 1 1/32
Unassigned 0001 1/16
Unassigned 001 1/8
Provider-Based Unicast Address 010 1/8
Unassigned 011 1/8
Reserved for Geographic
Based Unicast Addresses 100 1/8
Unassigned 101 1/8
Unassigned 110 1/8
Unassigned 1110 1/16
Unassigned 1111 0 1/32
Unassigned 1111 10 1/64
Unassigned 1111 110 1/128
Unassigned 1111 1110 0 1/512
Link Local Use Addresses 1111 1110 10 1/1024
Site Local Use Addresses 1111 1110 11 1/1024
Multicast Addresses 1111 1111 1/256
Note: The "unspecified address" (see section 2.4.2),
loopback address (see section 2.4.3), and the IPv6
with Embedded IPv4 Addresses (see section 2.4.4), are
out of the 0000 0000 format prefix space
This allocation supports the direct allocation of provider addresses
local use addresses, and multicast addresses. Space is reserved
NSAP addresses, IPX addresses, and geographic addresses.
remainder of the address space is unassigned for future use.
can be used for expansion of existing use (e.g., additional
addresses, etc.) or new uses (e.g., separate locators
identifiers). Fifteen percent of the address space is
Hinden & Deering Standards Track [Page 6]
RFC 1884 IPv6 Addressing Architecture December 1995
allocated. The remaining 85% is reserved for future use
Unicast addresses are distinguished from multicast addresses by
value of the high-order octet of the addresses: a value of
(11111111) identifies an address as a multicast address; any
value identifies an address as a unicast address. Anycast
are taken from the unicast address space, and are not
distinguishable from unicast addresses
2.4 Unicast
The IPv6 unicast address is contiguous bit-wise maskable, similar
IPv4 addresses under Class-less Interdomain Routing [CIDR].
There are several forms of unicast address assignment in IPv6,
including the global provider based unicast address, the
based unicast address, the NSAP address, the IPX
address, the site-local-use address, the link-local-use address,
the IPv4-capable host address. Additional address types can
defined in the future
IPv6 nodes may have considerable or little knowledge of the
structure of the IPv6 address, depending on the role the node
(for instance, host versus router). At a minimum, a node
consider that unicast addresses (including its own) have no
structure
| 128 bits |
+-----------------------------------------------------------------+
| node address |
+-----------------------------------------------------------------+
A slightly sophisticated host (but still rather simple)
additionally be aware of subnet prefix(es) for the link(s) it
attached to, where different addresses may have different values
n
| n bits | 128-n bits |
+------------------------------------------------+----------------+
| subnet prefix | interface ID |
+------------------------------------------------+----------------+
Still more sophisticated hosts may be aware of other
boundaries in the unicast address. Though a very simple router
have no knowledge of the internal structure of IPv6
Hinden & Deering Standards Track [Page 7]
RFC 1884 IPv6 Addressing Architecture December 1995
addresses, routers will more generally have knowledge of one or
of the hierarchical boundaries for the operation of
protocols. The known boundaries will differ from router to router
depending on what positions the router holds in the
hierarchy
2.4.1 Unicast Address
An example of a Unicast address format which will likely be common
LANs and other environments where IEEE 802 MAC addresses
available is
| n bits | 80-n bits | 48 bits |
+--------------------------------+-----------+--------------------+
| subscriber prefix | subnet ID | interface ID |
+--------------------------------+-----------+--------------------+
Where the 48-bit Interface ID is an IEEE-802 MAC address. The use
IEEE 802 MAC addresses as a interface ID is expected to be
common in environments where nodes have an IEEE 802 MAC address.
other environments, where IEEE 802 MAC addresses are not available
other types of link layer addresses can be used, such as E.164
addresses, for the interface ID
The inclusion of a unique global interface identifier, such as
IEEE MAC address, makes possible a very simple form of auto
configuration of addresses. A node may discover a subnet ID
listening to Router Advertisement messages sent by a router on
attached link(s), and then fabricating an IPv6 address for itself
using its IEEE MAC address as the interface ID on that subnet
Another unicast address format example is where a site
organization requires additional layers of internal hierarchy.
this example the subnet ID is divided into an area ID and a
ID. Its format is
| s bits | n bits | m bits | 128-s-n-m bits |
+----------------------+---------+--------------+-----------------+
| subscriber prefix | area ID | subnet ID | interface ID |
+----------------------+---------+--------------+-----------------+
This technique can be continued to allow a site or organization
add additional layers of internal hierarchy. It may be desirable
use an interface ID smaller than a 48-bit IEEE 802 MAC address
allow more space for the additional layers of internal hierarchy
These could be interface IDs which are administratively created
Hinden & Deering Standards Track [Page 8]
RFC 1884 IPv6 Addressing Architecture December 1995
the site or organization
2.4.2 The Unspecified
The address 0:0:0:0:0:0:0:0 is called the unspecified address.
must never be assigned to any node. It indicates the absence of
address. One example of its use is in the Source Address field
any IPv6 datagrams sent by an initializing host before it has
its own address
The unspecified address must not be used as the destination
of IPv6 datagrams or in IPv6 Routing Headers
2.4.3 The Loopback
The unicast address 0:0:0:0:0:0:0:1 is called the loopback address
It may be used by a node to send an IPv6 datagram to itself. It
never be assigned to any interface
The loopback address must not be used as the source address in IPv
datagrams that are sent outside of a single node. An IPv6
with a destination address of loopback must never be sent outside
a single node
2.4.4 IPv6 Addresses with Embedded IPv4
The IPv6 transition mechanisms include a technique for hosts
routers to dynamically tunnel IPv6 packets over IPv4
infrastructure. IPv6 nodes that utilize this technique are
special IPv6 unicast addresses that carry an IPv4 address in
low-order 32-bits. This type of address is termed an "IPv4-
compatible IPv6 address" and has the format
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+
A second type of IPv6 address which holds an embedded IPv4 address
also defined. This address is used to represent the addresses
IPv4-only nodes (those that *do not* support IPv6) as IPv6 addresses
This type of address is termed an "IPv4-mapped IPv6 address" and
the format
Hinden & Deering Standards Track [Page 9]
RFC 1884 IPv6 Addressing Architecture December 1995
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address |
+--------------------------------------+----+---------------------+
2.4.5 NSAP
This mapping of NSAP address into IPv6 addresses is as follows
| 7 | 121 bits |
+-------+---------------------------------------------------------+
|0000001| to be defined |
+-------+---------------------------------------------------------+
The draft definition, motivation, and usage are under study [NSAP].
2.4.6 IPX
This mapping of IPX address into IPv6 addresses is as follows
| 7 | 121 bits |
+-------+---------------------------------------------------------+
|0000010| to be defined |
+-------+---------------------------------------------------------+
The draft definition, motivation, and usage are under study
2.4.7 Provider-Based Global Unicast
The global provider-based unicast address is assigned as described
[ALLOC]. This initial assignment plan for these unicast addresses
similar to assignment of IPv4 addresses under the CIDR scheme [CIDR].
The IPv6 global provider-based unicast address format is as follows
| 3 | n bits | m bits | o bits | 125-n-m-o bits |
+---+-----------+-----------+-------------+--------------------+
|010|registry ID|provider ID|subscriber ID| intra-subscriber |
+---+-----------+-----------+-------------+--------------------+
Hinden & Deering Standards Track [Page 10]
RFC 1884 IPv6 Addressing Architecture December 1995
The high-order part of the address is assigned to registries,
then assign portions of the address space to providers, who
assign portions of the address space to subscribers, etc
The registry ID identifies the registry which assigns the
portion of the address. The term "registry prefix" refers to
high-order part of the address up to and including the registry ID
The provider ID identifies a specific provider which assigns
subscriber portion of the address. The term "provider prefix"
to the high-order part of the address up to and including
provider ID
The subscriber ID distinguishes among multiple subscribers
to the provider identified by the provider ID. The term "
prefix" refers to the high-order part of the address up to
including the subscriber ID
The intra-subscriber portion of the address is defined by
individual subscriber and is organized according to the
local internet topology. It is likely that many subscribers
choose to divide the intra-subscriber portion of the address into
subnet ID and an interface ID. In this case the subnet ID
a specific physical link and the interface ID identifies a
interface on that subnet
2.4.8 Local-use IPv6 Unicast
There are two types of local-use unicast addresses defined.
are Link-Local and Site-Local. The Link-Local is for use on a
link and the Site-Local is for use in a single site. Link-
addresses have the following format
| 10 |
| bits | n bits | 118-n bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
Link-Local addresses are designed to be used for addressing on
single link for purposes such as auto-address configuration,
discovery, or when no routers are present
Routers MUST not forward any packets with link-local
addresses
Hinden & Deering Standards Track [Page 11]
RFC 1884 IPv6 Addressing Architecture December 1995
Site-Local addresses have the following format
| 10 |
| bits | n bits | m bits | 118-n-m bits |
+----------+---------+---------------+----------------------------+
|1111111011| 0 | subnet ID | interface ID |
+----------+---------+---------------+----------------------------+
Site-Local addresses may be used for sites or organizations that
not (yet) connected to the global Internet. They do not need
request or "steal" an address prefix from the global Internet
space. IPv6 site-local addresses can be used instead. When
organization connects to the global Internet, it can then form
addresses by replacing the site-local prefix with a
prefix
Routers MUST not forward any packets with site-local source
outside of the site
2.5 Anycast
An IPv6 anycast address is an address that is assigned to more
one interface (typically belonging to different nodes), with
property that a packet sent to an anycast address is routed to
"nearest" interface having that address, according to the
protocols' measure of distance
Anycast addresses are allocated from the unicast address space,
any of the defined unicast address formats. Thus, anycast
are syntactically indistinguishable from unicast addresses. When
unicast address is assigned to more than one interface, thus
it into an anycast address, the nodes to which the address
assigned must be explicitly configured to know that it is an
address
For any assigned anycast address, there is a longest address prefix
that identifies the topological region in which all
belonging to that anycast address reside. Within the
identified by P, each member of the anycast set must be advertised
a separate entry in the routing system (commonly referred to as
"host route"); outside the region identified by P, the
address may be aggregated into the routing advertisement for
P
Note that in, the worst case, the prefix P of an anycast set may
the null prefix, i.e., the members of the set may have no
locality. In that case, the anycast address must be advertised as
Hinden & Deering Standards Track [Page 12]
RFC 1884 IPv6 Addressing Architecture December 1995
separate routing entry throughout the entire internet, which
a severe scaling limit on how many such "global" anycast sets may
supported. Therefore, it is expected that support for global
sets may be unavailable or very restricted
One expected use of anycast addresses is to identify the set
routers belonging to an internet service provider. Such
could be used as intermediate addresses in an IPv6 Routing header,
cause a packet to be delivered via a particular provider or
of providers. Some other possible uses are to identify the set
routers attached to a particular subnet, or the set of
providing entry into a particular routing domain
There is little experience with widespread, arbitrary use of
anycast addresses, and some known complications and hazards
using them in their full generality [ANYCST]. Until more
has been gained and solutions agreed upon for those problems,
following restrictions are imposed on IPv6 anycast addresses
o An anycast address MUST NOT be used as the source address of
IPv6 packet
o An anycast address MUST NOT be assigned to an IPv6 host,
is, it may be assigned to an IPv6 router only
2.5.1 Required Anycast
The Subnet-Router anycast address is predefined. It's format is
follows
| n bits | 128-n bits |
+------------------------------------------------+----------------+
| subnet prefix | 00000000000000 |
+------------------------------------------------+----------------+
The "subnet prefix" in an anycast address is the prefix
identifies a specific link. This anycast address is
the same as a unicast address for an interface on the link with
interface identifier set to zero
Packets sent to the Subnet-Router anycast address will be
to one router on the subnet. All routers are required to support
Subnet-Router anycast addresses for the subnets which they
interfaces
Hinden & Deering Standards Track [Page 13]
RFC 1884 IPv6 Addressing Architecture December 1995
The subnet-router anycast address is intended to be used
applications where a node needs to communicate with one of a set
routers on a remote subnet. For example when a mobile host needs
communicate with one of the mobile agents on it's "home" subnet
2.6 Multicast
An IPv6 multicast address is an identifier for a group of nodes.
node may belong to any number of multicast groups.
addresses have the following format
| 8 | 4 | 4 | 112 bits |
+------ -+----+----+---------------------------------------------+
|11111111|flgs|scop| group ID |
+--------+----+----+---------------------------------------------+
11111111 at the start of the address identifies the address
being a multicast address
+-+-+-+-+
flgs is a set of 4 flags: |0|0|0|T
+-+-+-+-+
The high-order 3 flags are reserved, and must
initialized to 0.
T = 0 indicates a permanently-assigned ("well-known")
multicast address, assigned by the global
numbering authority
T = 1 indicates a non-permanently-assigned ("transient")
multicast address
scop is a 4-bit multicast scope value used to limit the scope
the multicast group. The values are
0
1 node-local
2 link-local
3 (unassigned
4 (unassigned
5 site-local
6 (unassigned
7 (unassigned
8 organization-local
9 (unassigned
A (unassigned
Hinden & Deering Standards Track [Page 14]
RFC 1884 IPv6 Addressing Architecture December 1995
B (unassigned
C (unassigned
D (unassigned
E global
F
group ID identifies the multicast group, either permanent
transient, within the given scope
The "meaning" of a permanently-assigned multicast address
independent of the scope value. For example, if the "NTP
group" is assigned a permanent multicast address with a group ID
43 (hex), then
FF01:0:0:0:0:0:0:43 means all NTP servers on the same node
the sender
FF02:0:0:0:0:0:0:43 means all NTP servers on the same link
the sender
FF05:0:0:0:0:0:0:43 means all NTP servers at the same site
the sender
FF0E:0:0:0:0:0:0:43 means all NTP servers in the internet
Non-permanently-assigned multicast addresses are meaningful
within a given scope. For example, a group identified by the non
permanent, site-local multicast address FF15:0:0:0:0:0:0:43 at
site bears no relationship to a group using the same address at
different site, nor to a non-permanent group using the same group
with different scope, nor to a permanent group with the same
ID
Multicast addresses must not be used as source addresses in IPv
datagrams or appear in any routing header
2.6.1 Pre-Defined Multicast
The following well-known multicast addresses are pre-defined
Reserved Multicast Addresses: FF00:0:0:0:0:0:0:0
FF01:0:0:0:0:0:0:0
FF02:0:0:0:0:0:0:0
FF03:0:0:0:0:0:0:0
FF04:0:0:0:0:0:0:0
FF05:0:0:0:0:0:0:0
FF06:0:0:0:0:0:0:0
Hinden & Deering Standards Track [Page 15]
RFC 1884 IPv6 Addressing Architecture December 1995
FF07:0:0:0:0:0:0:0
FF08:0:0:0:0:0:0:0
FF09:0:0:0:0:0:0:0
FF0A:0:0:0:0:0:0:0
FF0B:0:0:0:0:0:0:0
FF0C:0:0:0:0:0:0:0
FF0D:0:0:0:0:0:0:0
FF0E:0:0:0:0:0:0:0
FF0F:0:0:0:0:0:0:0
The above multicast addresses are reserved and shall never
assigned to any multicast group
All Nodes Addresses: FF01:0:0:0:0:0:0:1
FF02:0:0:0:0:0:0:1
The above multicast addresses identify the group of all IPv6 nodes
within scope 1 (node-local) or 2 (link-local).
All Routers Addresses: FF01:0:0:0:0:0:0:2
FF02:0:0:0:0:0:0:2
The above multicast addresses identify the group of all IPv6 routers
within scope 1 (node-local) or 2 (link-local).
DHCP Server/Relay-Agent: FF02:0:0:0:0:0:0:
The above multicast addresses identify the group of all IPv6
Servers and Relay Agents within scope 2 (link-local).
Solicited-Node Address: FF02:0:0:0:0:1:XXXX:
The above multicast address is computed as a function of a node'
unicast and anycast addresses. The solicited-node multicast
is formed by taking the low-order 32 bits of the address (unicast
anycast) and appending those bits to the 96-bit prefix FF02:0:0:0:0:1
resulting in a multicast address in the
FF02:0:0:0:0:1:0000:0000
FF02:0:0:0:0:1:FFFF:
For example, the solicited node multicast address corresponding
the IPv6 address 4037::01:800:200E:8C6C is FF02::1:200E:8C6C. IPv
addresses that differ only in the high-order bits, e.g., due
multiple high-order prefixes associated with different providers
Hinden & Deering Standards Track [Page 16]
RFC 1884 IPv6 Addressing Architecture December 1995
will map to the same solicited-node address thereby reducing
number of multicast addresses a node must join
A node is required to compute and support a Solicited-Node
addresses for every unicast and anycast address it is assigned
2.7 A Node's Required
A host is required to recognize the following addresses
identifying itself
o Its Link-Local Address for each
o Assigned Unicast
o Loopback
o All-Nodes Multicast
o Solicited-Node Multicast Address for each of its
unicast and anycast
o Multicast Addresses of all other groups which the host belongs
A router is required to recognize the following addresses
identifying itself
o Its Link-Local Address for each
o Assigned Unicast
o Loopback
o The Subnet-Router anycast addresses for the links it
interfaces
o All other Anycast addresses with which the router has
configured
o All-Nodes Multicast
o All-Router Multicast
o Solicited-Node Multicast Address for each of its
unicast and anycast
o Multicast Addresses of all other groups which the
belongs
The only address prefixes which should be predefined in
implementation are the
o Unspecified
o Loopback
o Multicast Prefix (FF
o Local-Use Prefixes (Link-Local and Site-Local
o Pre-Defined Multicast
o IPv4-Compatible
Implementations should assume all other addresses are unicast
specifically configured (e.g., anycast addresses).
Hinden & Deering Standards Track [Page 17]
RFC 1884 IPv6 Addressing Architecture December 1995
[ALLOC] Rekhter, Y., and T. Li, "An Architecture for IPv6
Address Allocation", RFC 18XX, cisco Systems,
1995.
[ANYCST] Partridge, C., Mendez, T., and W. Milliken, "
Anycasting Service", RFC 1546, BBN, November 1993.
[CIDR] Fuller, V., Li, T., Varadhan, K., and J. Yu, "Supernetting
an Address Assignment and Aggregation Strategy", RFC 1338,
BARRNet, cisco, Merit, OARnet, June 1992.
[IPV6] Deering, S., and R. Hinden, Editors, "Internet Protocol
Version 6 (IPv6) Specification", RFC 1883, Xerox PARC
Ipsilon Networks, December 1995.
[MULT] Deering, S., "Host Extensions for IP multicasting", STD 5,
RFC 1112, Stanford University, August 1989.
[NSAP] Carpenter, B., Editor, "Mechanisms for OSIN SAPs, CLNP
TP over IPv6", Work in Progress
SECURITY
Security issues are not discussed in this document
DOCUMENT EDITOR'S
Robert M. Hinden Stephen E.
Ipsilon Networks, Inc. Xerox Palo Alto Research
2191 E. Bayshore Road, Suite 100 3333 Coyote Hill
Palo Alto, CA 94303 Palo Alto, CA 94304
USA
Phone: +1 415 846 4604 Phone: +1 415 812 4839
Fax: +1 415 855 1414 Fax: +1 415 812 4471
EMail: hinden@ipsilon.com EMail: deering@parc.xerox.
Hinden & Deering Standards Track [Page 18]
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
