RFC 4080: Next Steps in Signaling (NSIS): Framework
In plain English — editorial summary, not part of the RFC
The Next Steps in Signaling (NSIS) working group is considering protocols for signaling information about a data flow along its path in the network. The NSIS suite of protocols is envisioned to support various signaling applications that need to install and/or manipulate such state in the network. Based on existing work on signaling requirements, this document proposes an architectural framework for these signaling protocols. This document provides a model for the network entities that take part in such signaling, and for the relationship between signaling and the rest of network operation. We decompose the overall signaling protocol suite into a generic (lower) layer, with separate upper layers for each specific signaling application. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4080
- Published
- June 2005
- Authors
- R. Hancock; G. Karagiannis; J. Loughney; S. Van den Bosch
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 49
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4081Security Threats for Next Steps in Signaling (NSIS)Current
June 2005
- RFC 4077A Negative Acknowledgement Mechanism for Signaling CompressionCurrent
May 2005
- RFC 4067Context Transfer Protocol (CXTP)Current
July 2005
- RFC 4066Candidate Access Router Discovery (CARD)Current
July 2005
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 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?