API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 3964
[ACTIVE]

Security Considerations for 6to4

Metadata

Publisher
IETF
Doc Type
Informational
Pages
41
Abstract
The IPv6 interim mechanism 6to4 (RFC3056) uses automatic IPv6-over-IPv4 tunneling to interconnect IPv6 networks. The architecture includes 6to4 routers and 6to4 relay routers, which accept and decapsulate IPv4 protocol-41 ("IPv6-in-IPv4") traffic from any node in the IPv4 internet. This characteristic enables a number of security threats, mainly Denial of Service. It also makes it easier for nodes to spoof IPv6 addresses. This document discusses these issues in more detail and suggests enhancements to alleviate the problems. This memo provides information for the Internet community.
Publication Date
2004-12-01
Status Note
Informational
DOI
10.17487/RFC3964
Link
https://doi.org/10.17487/RFC3964
Author(s)
Pekka Savola
Chirayu Patel
Latest version of IETF RFC 3964

Document Versions — IETF RFC 3964

  • ▶ IETF RFC 3964 (2004-12-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms for IPv6 Hosts and Routers", Work in Progress, September 2004. EXTERNAL
  • Bellovin, S., Leech, M. and T. Taylor, "ICMP Traceback Messages", Work in Progress, February 2003. EXTERNAL
  • Hagino, J., "Possible abuse against IPv6 transition technologies", Work in Progress, July 2000. EXTERNAL
  • Savola, P., "Security of IPv6 Routing Header and Home Address Options", Work in Progress, March 2002. EXTERNAL
  • Templin, F., Gleeson, T., Talwar, M. and D. Thaler, "Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)", Work in Progress, May 2004. EXTERNAL
  • Arkko, J., Kempf, J., Sommerfeld, B., Zill, B., and P. Nikander, "SEcure Neighbor Discovery (SEND)", Work in Progress, July 2004. EXTERNAL
  • IETF RFC 1771 [Superseded*]
  • IETF RFC 1812 [Active*]
  • IETF RFC 1853 [Active*]
  • IETF RFC 2827 [Active*]
  • IETF RFC 2893 [Superseded*]
  • IETF RFC 3330 [Superseded*]
  • IETF RFC 3484 [Superseded*]
  • IETF RFC 3756 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3964.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 3964, Security Considerations for 6to4. Available at https://doi.org/10.17487/RFC3964
Snippet:
IETF RFC 3964, Security Considerations for 6to4. Available at https://doi.org/10.17487/RFC3964

HTML (ISO 690 compliant)

Preview:
IETF RFC 3964, Security Considerations for 6to4. Available at https://doi.org/10.17487/RFC3964
Snippet:
<span class="citation"><cite>IETF RFC 3964</cite>, Security Considerations for 6to4. Available at <a href="https://doi.org/10.17487/RFC3964" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3964</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 3964, Security Considerations for 6to4
doi: 10.17487/RFC3964
url: https://doi.org/10.17487/RFC3964
Snippet:
<li>
<cite id="bib-rfc3964">IETF RFC 3964</cite>, Security Considerations for 6to4
<span class="doi">10.17487/RFC3964</span>
</li>

Referenced By