RFC 6169: Security Concerns with IP Tunneling
In plain English — editorial summary, not part of the RFC
A number of security concerns with IP tunnels are documented in this memo. The intended audience of this document includes network administrators and future protocol developers. The primary intent of this document is to raise the awareness level regarding the security issues with IP tunnels as deployed and propose strategies for the mitigation of those issues. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6169
- Published
- April 2011
- Authors
- S. Krishnan; D. Thaler; J. Hoagland
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 6177IPv6 Address Assignment to End SitesCurrent
March 2011
- RFC 6183IP Flow Information Export (IPFIX) Mediation: FrameworkCurrent
April 2011
- RFC 6192Protecting the Router Control PlaneCurrent
March 2011
- RFC 6198Requirements for the Graceful Shutdown of BGP SessionsCurrent
April 2011
- RFC 6201Device Reset CharacterizationCurrent
March 2011
- RFC 6204Basic Requirements for IPv6 Customer Edge RoutersObsoleted
April 2011
- RFC 6110Mapping YANG to Document Schema Definition Languages and Validating NETCONF ContentUpdated
February 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?