RFC - 3053

IPv6 Tunnel Broker

Original:	ftp://ftp.isi.edu/in-notes/rfc3053.txt
Authors:	A. Durand [SUN Microsystems, Inc], P. Fasano [CSELT S.p.A.], I. Guardini [CSELT S.p.A.], D. Lento [TIM]
Date:	January 2001
Category:	Informational

---

Referred by:	4 RFC
Refers to:	11 RFC

---

Status

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract

The IPv6 global Internet as of today uses a lot of tunnels over the existing IPv4 infrastructure. Those tunnels are difficult to configure and maintain in a large scale environment. The 6bone has proven that large sites and Internet Service Providers (ISPs) can do it, but this process is too complex for the isolated end user who already has an IPv4 connection and would like to enter the IPv6 world. The motivation for the development of the tunnel broker model is to help early IPv6 adopters to hook up to an existing IPv6 network (e.g., the 6bone) and to get stable, permanent IPv6 addresses and DNS names. The concept of the tunnel broker was first presented at Orlando's IETF in December 1998. Two implementations were demonstrated during the Grenoble IPng & NGtrans interim meeting in February 1999.

---