RFC 2470 (rfc2470) - Page 1 of 11
Transmission of IPv6 Packets over Token Ring Networks
Alternative Format: Original Text Document
Network Working Group M. Crawford
Request for Comments: 2470 Fermilab
Category: Standards Track T. Narten
IBM
S. Thomas
TransNexus
December 1998
Transmission of IPv6 Packets over Token Ring Networks
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
1. Introduction
This memo specifies the MTU and frame format for transmission of IPv6
packets on Token Ring networks. It also specifies the method of
forming IPv6 link-local addresses on Token Ring networks and the
content of the Source/Target Link-layer Address option used the
Router Solicitation, Router Advertisement, Redirect, Neighbor
Solicitation and Neighbor Advertisement messages when those messages
are transmitted on a Token Ring network.
Implementors should be careful to note that Token Ring adaptors
assume addresses are in non-canonical rather than canonical format,
requiring that special care be taken to insure that addresses are
processed correctly. See [CANON] for more details.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [KWORD].
2. Maximum Transmission Unit
IEEE 802.5 networks have a maximum frame size based on the maximum
time a node may hold the token. This time depends on many factors
including the data signaling rate and the number of nodes on the
ring. Because the maximum frame size varies, implementations must
Crawford, et. al. Standards Track