CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 18:33:34 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=FUwdNcEwDP9WByEDZ3y9baTznIDNzhgfhqwtiM0Vdj4-1760121214-1.0.1.1-YdHQ29P2MjbULZWb6pDHFrlkRmve5TGYD6xE_Fsiu4a_dzxrUfC1QMk2BXmbSPfrQZkSNC58h5cXS3slLALKcWe2yuGMRQ7YlC..R5e3vNo; path=/; expires=Fri, 10-Oct-25 19:03:34 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c834f188b7343c-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5991 » RFC Editor
Search RFCs
RFC 5991
Teredo Security Updates, September 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 4380
- Authors:
- D. Thaler
S. Krishnan
J. Hoagland - Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5991
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5991
Abstract
The Teredo protocol defines a set of flags that are embedded in every Teredo IPv6 address. This document specifies a set of security updates that modify the use of this flags field, but are backward compatible. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us