Issll Workgroup RFCs

Browse Issll Workgroup RFCs by Number

RFC2379 - RSVP over ATM Implementation Guidelines: This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2380 - RSVP over ATM Implementation Requirements: This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. [STANDARDS-TRACK]
RFC2381 - Interoperation of Controlled-Load Service and Guaranteed Service with ATM: This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. [STANDARDS-TRACK]
RFC2382 - A Framework for Integrated Services and RSVP over ATM: This document outlines the issues and framework related to providing IP Integrated Services with RSVP over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2686 - The Multi-Class Extension to Multi-Link PPP: This document proposes the fragment-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK]
RFC2687 - PPP in a Real-time Oriented HDLC-like Framing: This document proposes the suspend/resume-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK]
RFC2688 - Integrated Services Mappings for Low Speed Networks: This document defines the service mappings of the IETF Integrated Services for low-bitrate links, specifically the controlled load and guaranteed services. [STANDARDS-TRACK]
RFC2689 - Providing Integrated Services over Low-bitrate Links: This document describes an architecture for providing integrated services over low-bitrate links, such as modem lines, ISDN B-channels, and sub-T1 links. This memo provides information for the Internet community.
RFC2814 - SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networks: This document describes a signaling method and protocol for RSVP-based admission control over IEEE 802-style LANs. [STANDARDS-TRACK]
RFC2815 - Integrated Service Mappings on IEEE 802 Networks: This document describes mappings of IETF Integrated Services over LANs built from IEEE 802 network segments which may be interconnected by IEEE 802.1D MAC Bridges (switches). [STANDARDS-TRACK]
RFC2816 - A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies: This memo describes a framework for supporting IETF Integrated Services on shared and switched LAN infrastructure. This memo provides information for the Internet community.
RFC2996 - Format of the RSVP DCLASS Object: This document specifies the format of the DCLASS object and briefly discusses its use. [STANDARDS-TRACK]
RFC2997 - Specification of the Null Service Type: 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]
RFC2998 - A Framework for Integrated Services Operation over Diffserv Networks: This document describes a framework by which Integrated Services may be supported over Diffserv networks. This memo provides information for the Internet community.
RFC3175 - Aggregation of RSVP for IPv4 and IPv6 Reservations: This document describes the use of a single RSVP (Resource ReSerVation Protocol) reservation to aggregate other RSVP reservations across a transit routing region, in a manner conceptually similar to the use of Virtual Paths in an ATM (Asynchronous Transfer Mode) network. It proposes a way to dynamically create the aggregate reservation, classify the traffic for which the aggregate reservation applies, determine how much bandwidth is needed to achieve the requirement, and recover the bandwidth when the sub-reservations are no longer required. It also contains recommendations concerning algorithms and policies for predictive reservations. [STANDARDS-TRACK]