Requirements for Signaling Protocols
RFC 3726, “Requirements for Signaling Protocols”, is an Informational document published in April 2004 by M. Brunner. The canonical text is published by the RFC Editor.
Abstract
This document defines requirements for signaling across different network environments, such as across administrative and/or technology domains. Signaling is mainly considered for Quality of Service (Qos) such as the Resource Reservation Protocol (RSVP). However, in recent years, several other applications of signaling have been defined. For example, signaling for label distribution in Multiprotocol Label Switching (MPLS) or signaling to middleboxes. To achieve wide applicability of the requirements, the starting point is a diverse set of scenarios/use cases concerning various types of networks and application interactions. This document presents the assumptions before listing the requirements. The requirements are grouped according to areas such as architecture and design goals, signaling flows, layering, performance, flexibility, security, and mobility. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3726 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3725 Best Current Practices for Third Party Call Control in the Session Initiation Protocol
- RFC 3727 ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules
- RFC 3724 The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture
- RFC 3728 Definitions of Managed Objects for Very High Speed Digital Subscriber Lines
- RFC 3723 Securing Block Storage Protocols over IP
- RFC 3729 Application Performance Measurement MIB
- RFC 3722 String Profile for Internet Small Computer Systems Interface Names
- RFC 3730 Extensible Provisioning Protocol