Specification of the Null Service Type
RFC 2997, “Specification of the Null Service Type”, is a Proposed Standard document published in November 2000 by Y. Bernet, A. Smith, B. Davie. The canonical text is published by the RFC Editor.
Abstract
The Null Service allows applications to identify themselves to network Quality of Service (QoS) policy agents, using RSVP signaling. However, it does not require them to specify resource requirements. QoS policy agents in the network respond by applying QoS policies appropriate for the application (as determined by the network administrator). This mode of RSVP usage is particularly applicable to networks that combine differentiated service (diffserv) QoS mechanisms with RSVP signaling. In this environment, QoS policy agents may direct the signaled application's traffic to a particular diffserv class of service. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 2997 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 2996 Format of the RSVP DCLASS Object
- RFC 2998 A Framework for Integrated Services Operation over Diffserv Networks
- RFC 2995 Pre-Spirits Implementations of PSTN-initiated Services
- RFC 2994 A Description of the MISTY1 Encryption Algorithm
- RFC 2993 Architectural Implications of NAT
- RFC 3001 A URN Namespace of Object Identifiers
- RFC 2992 Analysis of an Equal-Cost Multi-Path Algorithm
- RFC 3002 Overview of 2000 IAB Wireless Internetworking Workshop