RFC 4081: Security Threats for Next Steps in Signaling (NSIS)
In plain English — editorial summary, not part of the RFC
This threats document provides a detailed analysis of the security threats relevant to the Next Steps in Signaling (NSIS) protocol suite. It calls attention to, and helps with the understanding of, various security considerations in the NSIS Requirements, Framework, and Protocol proposals. This document does not describe vulnerabilities of specific parts of the NSIS protocol suite. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4081
- Published
- June 2005
- Authors
- H. Tschofenig; D. Kroeselberg
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 28
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4080Next Steps in Signaling (NSIS): FrameworkCurrent
June 2005
- RFC 4077A Negative Acknowledgement Mechanism for Signaling CompressionCurrent
May 2005
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 4067Context Transfer Protocol (CXTP)Current
July 2005
- RFC 4066Candidate Access Router Discovery (CARD)Current
July 2005
- RFC 4065Instructions for Seamoby and Experimental Mobility Protocol IANA AllocationsCurrent
July 2005
- RFC 4097Middlebox Communications (MIDCOM) Protocol EvaluationUpdated
June 2005
- RFC 4044Fibre Channel Management MIBCurrent
May 2005
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?