As per Relevance of the word identifier, we have this rfc below:
Network Working Group I.
Request for Comments: 2497 The NetBSD
See Also: 1201 January 1999
Category: Standards
Transmission of IPv6 Packets over ARCnet
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
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
1.
This memo specifies a frame format for transmission of IPv6 [IPV6]
packets and the method of forming IPv6 link-local and
autoconfigured addresses on ARCnet networks. It also specifies
content of the Source/Target Link-layer Address option used by
Router Solicitation, Router Advertisement, Neighbor Solicitation
Neighbor Advertisement and Redirect messages described in [DISC],
when those messages are transmitted on an ARCnet
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL
in this document are to be interpreted as described in RFC 2119
[KWORD].
2. Frame
IPv6 packets are link layer fragmented and reassembled according
[PHDS]. A brief but sufficient discussion of this
method can be found in [ARCIPV4].
The protocol ID (System Code in ARCnet terminology) assigned to IPv
is C4 hexadecimal
Souvatzis Standards Track [Page 1]
RFC 2497 IPv6 Datagrams on ARCnet January 1999
3. Maximum Transmission
The maximum IPv6 packet length possible using this
method is 60480 octets. Since this length is impractical because
its worst case transmission time of several seconds, all
implementations on a given ARCnet network should agree on a
value
The default MTU for IPv6 [IPV6] packets on an ARCnet is 9072 octets
In the presence of a router, this size MAY be changed by a
Advertisement [DISC] containing an MTU option. If a
Advertisement is received with an MTU option specifying an MTU
than 60480, or larger than a manually configured value less
60480, that MTU option may be logged to system management but MUST
otherwise ignored
If no router is available, the local MTU MUST be left at 9072 or
be manually configured to the same different value on all
stations
Implementations MAY accept arriving IPv6 datagrams which are
than their configured maximum transmission unit. They are
required to discard such datagrams. If they can not handle
datagrams, they MAY log the event to the system administration,
MUST otherwise silently discard them
4. Stateless Auto-
If a node has an EUI-64 which is not used to form the
Identifier for any other interface, it SHOULD use that EUI-64 to
the Interface Identifier for its ARCnet interface. If that EUI-64
in use for another interface attached to a different link, it MAY
used for the ARCnet interface as well
The Interface Identifier is then formed from the EUI-64
complementing the "Universal/Local" (U/L) bit, which is the next
to-lowest order bit of the first octet of the EUI-64.
When a node has no EUI-64 available for forming its ARCnet
Identifer, it MUST form that identifier as specified in [AARCH],
Appendix A, section "Links with Non-Global Identifier". That is,
8 bit manually configured ARCnet address is appended to the 56
bits
For example, for an ARCnet interface with the configured address
49 hexadecimal this results in the following identifier
Souvatzis Standards Track [Page 2]
RFC 2497 IPv6 Datagrams on ARCnet January 1999
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|0000000000000000|0000000000000000|0000000000000000|0000000001001001|
+----------------+----------------+----------------+----------------+
Note that this results in the universal/local bit set to "0"
indicate local scope
An IPv6 address prefix used for stateless auto-configuration [ACONF
of an ARCnet interface MUST have a length of 64 bits
5. Link-Local
The IPv6 link-local address [AARCH] for an ARCnet interface is
by appending the Interface Identifier, as defined above, to
prefix FE80::/64.
10 bits 54 bits 64
+----------+-----------------------+----------------------------+
|1111111010| (zeros) | Interface Identifier |
+----------+-----------------------+----------------------------+
6. Address Mapping --
The procedure for mapping IPv6 addresses into ARCnet link-
addresses is described in [DISC]. The Source/Target link
Address option has the following form when the link layer is ARCnet
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|ARCnet address | |
+---------------+ -+
| |
+- 5 octets of padding -+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option fields
Type 1 for Source Link-layer address
2 for Target Link-layer address
Length 1 (in units of 8 octets).
ARCnet address The 8 bit ARCnet address, in canonical bit order
Souvatzis Standards Track [Page 3]
RFC 2497 IPv6 Datagrams on ARCnet January 1999
7. Address Mapping --
As ARCnet only provides 1 multicast address (00 hexadecimal),
IPv6 multicast addresses MUST be mapped to this address
8. Security
The method of derivation of Interface Identifiers from
addresses is intended to preserve local uniqueness when possible
However, there is no protection from duplication through accident
forgery
9.
Big parts of the new version of this memo are either based
[ETHIPV6] or on Matt Crawford's review of an earlier version
10.
[AARCH] Hinden, R. and S. Deering, "IP Version 6
Architecture", RFC 2373, July 1998.
[ACONF] Thomson, S. and T. Narten, "IPv6 Stateless
Autoconfiguration", RFC 2462, December 1998.
[ARCIPV4] Provan, D., "Transmitting IP Traffic over ARCNET Networks",
RFC1201, Novell, Inc., February 1991.
[DISC] Narten, T., Nordmark, E. and W. Simpson, "
Discovery for IP Version 6 (IPv6)", RFC 2461,
1998.
[ETHIPV6] Crawford, M., "Transmission of IPv6 Packets over
Networks", RFC 2464, December 1998.
[EUI64] "64-Bit Global Identifier Format Tutorial", http://stan
dards.ieee.org/db/oui/tutorials/EUI64.html
[IPV6] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[KWORD] Bradner, S., "Key words for use in RFCs to
Requirement Levels", BCP 14, RFC 2119, March 1997.
[PHDS] Novell, Inc., "ARCNET Packet Header Definition Standard",
Novell Part Number 100-00721-001, November 1989.
Souvatzis Standards Track [Page 4]
RFC 2497 IPv6 Datagrams on ARCnet January 1999
11. Author's
Ignatios
The NetBSD
Stationenweg 29
D-53332
Phone (work): +49 (228) 734316
EMail: is@netbsd.
Souvatzis Standards Track [Page 5]
RFC 2497 IPv6 Datagrams on ARCnet January 1999
12. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Souvatzis Standards Track [Page 6]
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
