Teredo Security Concerns Beyond What Is In RFC 4380
draft-hoagland-v6ops-teredosecconcerns-01

Document Type Expired Internet-Draft (individual)
Last updated 2007-07-12
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-hoagland-v6ops-teredosecconcerns-01.txt

Abstract

Additional security concerns with Teredo are documented, beyond what is in RFC 4380. This is based on an independent analysis of Teredo's security implications. The primary intent of this document is to provide information and recommendations to the IETF that can be used in any updated Teredo specification. The second intended audience is anyone that can help improve security in Teredo as deployed, so they will be aware of these concerns.

Authors

Suresh Krishnan (suresh.krishnan@ericsson.com)
James Hoagland (Jim_Hoagland@symantec.com)

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