RFC 2470 on IPv6 over Token Ring

RFC Editor <rfc-ed@ISI.EDU> Fri, 04 December 1998 01:05 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id UAA07286 for ietf-123-outbound.10@ietf.org; Thu, 3 Dec 1998 20:05:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06563 for <all-ietf@ietf.org>; Thu, 3 Dec 1998 19:37:45 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA02994; Thu, 3 Dec 1998 16:37:47 -0800 (PST)
Message-Id: <199812040037.QAA02994@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2470 on IPv6 over Token Ring
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 03 Dec 1998 16:37:47 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2470:

        Title:	    Transmission of IPv6 Packets over Token Ring
		    Networks
	Author(s):  M. Crawford, T. Narten, S. Thomas
	Status:     Proposed Standard
	Date:       December 1998
        Mailbox:    crawdad@fnal.gov, narten@raleigh.ibm.com,
		    stephen.thomas@transnexus.com
	Pages:      11
        Characters: 21677
        Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-ietf-ipngwg-trans-tokenring-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2470.txt


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.

This document is a product of the IPNG Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2470.txt"><ftp://ftp.isi.edu/in-notes/rfc2470.txt>