Teredo Security Concerns
draft-ietf-v6ops-teredo-security-concerns-02
| Document | Type |
Replaced Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | James Hoagland , Suresh Krishnan | ||
| Last updated | 2008-07-15 (Latest revision 2008-02-25) | ||
| Replaced by | RFC 6169 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-tunnel-security-concerns | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 raise the awareness regarding the security issues in Teredo as deployed today.
Authors
James Hoagland
Suresh Krishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)