RFC 2529 on Transmission of IPv6 Packets over IPv4
RFC Editor <rfc-ed@ISI.EDU> Wed, 10 March 1999 00:55 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22763 for ietf-123-outbound.10@ietf.org; Tue, 9 Mar 1999 19:55:03 -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 TAA22241 for <all-ietf@ietf.org>; Tue, 9 Mar 1999 19:31:25 -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 QAA07342; Tue, 9 Mar 1999 16:31:25 -0800 (PST)
Message-Id: <199903100031.QAA07342@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2529 on Transmission of IPv6 Packets over IPv4
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 09 Mar 1999 16:31:24 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2529: Title: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels Author(s): B. Carpenter, C. Jung Status: Proposed Standard Date: March 1999 Mailbox: brian@hursley.ibm.com, cmj@3Com.com Pages: 10 Characters: 21049 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-ipngwg-6over4-02.txt URL: ftp://ftp.isi.edu/in-notes/rfc2529.txt This memo specifies the frame format for transmission of IPv6 [IPV6] packets and the method of forming IPv6 link-local addresses over IPv4 domains. It also specifies the content of the Source/Target Link-layer Address option used in the Router Solicitation, Router Advertisement, Neighbor Solicitation, and Neighbor Advertisement and Redirect messages, when those messages are transmitted on an IPv4 multicast 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.