RFC 5981: Authorization for NSIS Signaling Layer Protocols
In plain English — editorial summary, not part of the RFC
Signaling layer protocols specified within the Next Steps in Signaling (NSIS) framework may rely on the General Internet Signaling Transport (GIST) protocol to handle authorization. Still, the signaling layer protocol above GIST itself may require separate authorization to be performed when a node receives a request for a certain kind of service or resources. This document presents a generic model and object formats for session authorization within the NSIS signaling layer protocols. The goal of session authorization is to allow the exchange of information between network elements in order to authorize the use of resources for a service and to coordinate actions between the signaling and transport planes. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5981
- Published
- February 2011
- Authors
- J. Manner; M. Stiemerling; H. Tschofenig; R. Bless
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5979NSIS Operation over IP TunnelsCurrent
March 2011
- RFC 5978Using and Extending the NSIS Protocol FamilyCurrent
October 2010
- RFC 5977RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in DiffservCurrent
October 2010
- RFC 5973NAT/Firewall NSIS Signaling Layer Protocol (NSLP)Current
October 2010
- RFC 5971GIST: General Internet Signalling TransportCurrent
October 2010
- RFC 5980NSIS Protocol Operation in Mobile EnvironmentsCurrent
March 2011
- RFC 5976Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service ClassesCurrent
October 2010
- RFC 5975QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)Current
October 2010
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?