datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Security Considerations for 6to4
draft-ietf-v6ops-6to4-security-04

RFC
Document Stream: IETF
Last updated: 2004-07-20
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 3964
Responsible AD: David Kessens
Send notices to: pekkas@netcore.fi, jonne.Soininen@nokia.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-v6ops-6to4-security.

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.

Authors:
Chirayu Patel <chirayu@chirayu.org>
Pekka Savola <psavola@funet.fi>

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