RFC-Ref is not longer maintained; use RFC browser at: http://zvon.org/comp/r/ref-RFC.html
RFC 3053:IPv6 Tunnel Broker
RFC-Ref

Internet


Click on the red underlined text to get to the source

... IPv6 networks started mainly using the transport facilities offered by the current Internet. This led to the development of several techniques to manage IPv6 over IPv4 ...
... network is built using manually configured tunnels over the Internet. The main drawback of this approach is the overwhelming management load for network administrators ...
... link layer. It does not solve the problem of connecting an isolated user to the global IPv6 Internet; ...
... wide area network with no native IPv6 support (e.g., the IPv4 Internet), to communicate with other such IPv6 domains ...
... IPv6 sites, and especially isolated IPv6 hosts on the IPv4 Internet, that want to easily connect to an existing IPv6 network; ...
... 6to4 relays, 6to4 sites can also reach sites on the IPv6 Internet. ...
... Tunnel Broker service within the Internet. It does not specify any protocol but details the general architecture of the proposed approach. It also outlines a set of ...


... IPv6 ISPs, providing IPv6 connectivity to users already connected to the IPv4 Internet. In the emerging IPv6 Internet it is expected that many tunnel ...
... IPv6 connectivity to users already connected to the IPv4 Internet. In the emerging IPv6 Internet it is expected that many tunnel brokers will be available so that the user will just have to pick one. The list ...
... IPv6) router connected to the global Internet. Upon receipt of a configuration order coming from the TB, it creates, modifies or deletes ...
... (host or router) connected to the IPv4 Internet. Approaching the TB, the client should be asked first of all to provide its identity ...
... IPv6 addresses and associated DNS names even though it is connected to the Internet via a dial-up link and gets dynamically assigned IPv4 addresses ...
... Obviously this is not an optimal solution especially for users accessing the Internet through short-lived and dynamically addressed IPv4 connections ...
... point or tearing down his IPv4 connection to the Internet). The drawback of this policy mechanism is that it also requires a software upgrade on the client ...
... Moreover, keeping track of the tunnel configuration even after the user has disconnected from the IPv4 Internet may be worth the extra cost. In this way, in fact, when the user reconnects to the Internet ...
... IPv4 Internet may be worth the extra cost. In this way, in fact, when the user reconnects to the Internet, possibly using a different IPv4 address, he could just restart ...
... security issues could be elegantly overcome by defining a new MIME (Multipurpose Internet Mail Extension) content- type (e.g., application/tunnel) [4 ...


... multicast islands within the unicast Internet) or an IPsec tunnel. ...


... confidentiality may occur whenever a dial-up user disconnects from the Internet without tearing down the tunnel previously established through the TB. In fact, the TS ...


... Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, RFC 2045draft ...
... Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, RFC 2045draft, November 1996. ...
... Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046draft ...
... Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401(-> 4301prop), November 1998. ...


... Copyright (C) The Internet Society (2001). All Rights Reserved. ...
... document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of ...
... the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for ...
... Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be ...
... developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than ...
... The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. ...
... This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ...
... "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION ...


... Funding for the RFC Editor function is currently provided by the Internet Society. ...



Google
Web
RFC-Ref