idnits 2.17.1 draft-ietf-ngtrans-6to4-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3056 5 Title: Connection of IPv6 Domains via IPv4 Clouds 6 Author(s): B. Carpenter, K. Moore 7 Status: Standards Track 8 Date: February 2001 9 Mailbox: brian@icair.org, moore@cs.utk.edu 10 Pages: 23 11 Characters: 54902 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-ngtrans-6to4-07.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3056.txt 18 This memo specifies an optional interim mechanism for IPv6 sites to 19 communicate with each other over the IPv4 network without explicit 20 tunnel setup, and for them to communicate with native IPv6 domains 21 via relay routers. Effectively it treats the wide area IPv4 network 22 as a unicast point-to-point link layer. The mechanism is intended as 23 a start-up transition tool used during the period of co-existence of 24 IPv4 and IPv6. It is not intended as a permanent solution. 26 The document defines a method for assigning an interim unique IPv6 27 address prefix to any site that currently has at least one globally 28 unique IPv4 address, and specifies an encapsulation mechanism for 29 transmitting IPv6 packets using such a prefix over the global IPv4 30 network. 32 The motivation for this method is to allow isolated IPv6 domains or 33 hosts, attached to an IPv4 network which has no native IPv6 support, 34 to communicate with other such IPv6 domains or hosts with minimal 35 manual configuration, before they can obtain natuve IPv6 36 connectivity. It incidentally provides an interim globally unique 37 IPv6 address prefix to any site with at least one globally unique 38 IPv4 address, even if combined with an IPv4 Network Address 39 Translator (NAT). 41 This document is a product of the Next Generation Transition Working 42 Group of the IETF. 44 This is now a Proposed Standard Protocol. 46 This document specifies an Internet standards track protocol for 47 the Internet community, and requests discussion and suggestions 48 for improvements. Please refer to the current edition of the 49 "Internet Official Protocol Standards" (STD 1) for the 50 standardization state and status of this protocol. Distribution 51 of this memo is unlimited. 53 This announcement is sent to the IETF list and the RFC-DIST list. 54 Requests to be added to or deleted from the IETF distribution list 55 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 56 added to or deleted from the RFC-DIST distribution list should 57 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 59 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 60 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 61 help: ways_to_get_rfcs. For example: 63 To: rfc-info@RFC-EDITOR.ORG 64 Subject: getting rfcs 66 help: ways_to_get_rfcs 68 Requests for special distribution should be addressed to either the 69 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 70 specifically noted otherwise on the RFC itself, all RFCs are for 71 unlimited distribution.echo 72 Submissions for Requests for Comments should be sent to 73 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 74 Authors, for further information.