Moving from 6bone to IPv6 Internet
draft-savola-v6ops-6bone-mess-01

Document Type Expired Internet-Draft (individual)
Author Pekka Savola 
Last updated 2002-11-07
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-savola-v6ops-6bone-mess-01.txt

Abstract

Currently, IPv6 Internet is, globally considered, inseparable from the 6bone network. The 6bone has been built as a tighly meshed tunneled topology. As the number of participants has grown, it has become an untangible mess, hindering the real deployment of IPv6 due to low quality of connections. This memo discusses the nature and the state of 6bone/IPv6 Internet, points out problems and outlines a few ways to start fixing them; also, some rough operational guidelines for different-sized organizations are presented. The most important issues are: not offering transit to everyone and real transit operators being needed to take a more active role.

Authors

Pekka Savola (psavola@funet.fi)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)