RFC 3053: IPv6 Tunnel Broker

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…

Read RFC 3053 on the RFC Editor

Outgoing relationships (10 related RFCs)

Informative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Informative reference — RFC 2401: Security Architecture for the Internet Protocol
Informative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Informative reference — RFC 2136: Dynamic Updates in the Domain Name System (DNS UPDATE)
Informative reference — RFC 2571: An Architecture for Describing SNMP Management Frameworks
Informative reference — RFC 2575: View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
Informative reference — RFC 2574: User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
Informative reference — RFC 2529: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels
Informative reference — RFC 1933: Transition Mechanisms for IPv6 Hosts and Routers
Informative reference — RFC 2137: Secure Domain Name System Dynamic Update

Incoming relationships (7 related RFCs)

Normatively referenced by — RFC 4925: Softwire Problem Statement
Normatively referenced by — RFC 3904: Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks
Normatively referenced by — RFC 7123: Security Implications of IPv6 on IPv4 Networks
Informatively referenced by — RFC 6343: Advisory Guidelines for 6to4 Deployment
Informatively referenced by — RFC 6180: Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
Informatively referenced by — RFC 6751: Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44)
Informatively referenced by — RFC 6964: Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)