Teredo Security Concerns
draft-ietf-v6ops-teredo-security-concerns-02
| Document | Type | Replaced Internet-Draft (v6ops WG) | |
|---|---|---|---|
| Last updated | 2008-07-15 (latest revision 2008-02-25) | ||
| Replaced by | draft-ietf-v6ops-tunnel-security-concerns | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-tunnel-security-concerns | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-v6ops-teredo-security-concerns-02.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 raise the awareness regarding the security issues in Teredo as deployed today.
Authors
James Hoagland
(Jim_Hoagland@symantec.com)
Suresh Krishnan
(suresh.krishnan@ericsson.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)