RFC 2464 on IPv6 Packets over Ethernet

RFC Editor <rfc-ed@ISI.EDU> Thu, 03 December 1998 00:35 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id TAA04603 for ietf-123-outbound.10@ietf.org; Wed, 2 Dec 1998 19:35: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 SAA02707 for <all-ietf@ietf.org>; Wed, 2 Dec 1998 18:35: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 PAA08631; Wed, 2 Dec 1998 15:35:47 -0800 (PST)
Message-Id: <199812022335.PAA08631@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2464 on IPv6 Packets over Ethernet
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 02 Dec 1998 15:35:46 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2464:

        Title:	    Transmission of IPv6 Packets over Ethernet
		    Networks
	Author(s):  M. Crawford
	Status:     Proposed Standard
	Date:       December 1998
        Mailbox:    crawdad@fnal.gov
	Pages:      7
        Characters: 12725
        Obsoletes:  1972
        I-D Tag:    draft-ietf-ipngwg-trans-ethernet-04.txt


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

This document specifies the frame format for transmission of IPv6
packets and the method of forming IPv6 link-local addresses and
statelessly autoconfigured addresses on Ethernet networks.  It also
specifies the content of the Source/Target Link-layer Address option
used in Router Solicitation, Router Advertisement, Neighbor
Solicitation, Neighbor Advertisement and Redirect messages when
those messages are transmitted on an Ethernet.

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/rfc2464.txt"><ftp://ftp.isi.edu/in-notes/rfc2464.txt>