RFC 4016: Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security Requirements
In plain English — editorial summary, not part of the RFC
This document discusses the threats to protocols used to carry authentication for network access. The security requirements arising from these threats will be used as additional input to the Protocol for Carrying Authentication for Network Access (PANA) Working Group for designing the IP based network access authentication protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4016
- Published
- March 2005
- Authors
- M. Parthasarathy
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 3845DNS Security (DNSSEC) NextSECure (NSEC) RDATA FormatObsoleted
August 2004
- RFC 3833Threat Analysis of the Domain Name System (DNS)Current
August 2004
- RFC 3756IPv6 Neighbor Discovery (ND) Trust Models and ThreatsCurrent
May 2004
- RFC 3755Legacy Resolver Compatibility for Delegation Signer (DS)Obsoleted
May 2004
- RFC 3655Redefinition of DNS Authenticated Data (AD) bitObsoleted
November 2003
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?