Search RFCs

RFC Editor

File formats:

Status:

EXPERIMENTAL

Authors:

G. Ash, Ed.
D. McDysan

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6601

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6601

Abstract

This document presents a generic connection admission control (GCAC)reference model and algorithm for IP-/MPLS-based networks. Serviceprovider (SP) IP/MPLS networks need an MPLS GCAC mechanism, asone motivational example, to reject Voice over IP(VoIP) calls when additional calls would adversely affect callsalready in progress. Without MPLS GCAC, connections on congestedlinks will suffer degraded quality. The MPLS GCAC algorithm can beoptionally implemented in vendor equipment and deployed by serviceproviders. MPLS GCAC interoperates between vendor equipment andacross multiple service provider domains. The MPLS GCAC algorithmuses available standard mechanisms for MPLS-based networks, such asRSVP, Diffserv-aware MPLS Traffic Engineering (DS-TE), Path ComputationElement (PCE), Next Steps in Signaling (NSIS), Diffserv, and OSPF.The MPLS GCAC algorithm does not include aspects of CAC that might beconsidered vendor proprietary implementations, such as detailed path selectionmechanisms. MPLS GCAC functions are implemented in a distributedmanner to deliver the objective Quality of Service (QoS) for specifiedQoS constraints. The objective is that the source isable to compute a source route with high likelihood that via-elementsalong the selected path will in fact admit the request.In some cases (e.g., multiple Autonomous Systems (ASes)), this objectivecannot always be met, but this document summarizes methods that partially meetthis objective. MPLS GCAC is applicable to any service or flow that must meetan objective QoS (delay, jitter, packet loss rate) for a specified quantity oftraffic. This document defines an Experimental Protocol for the Internetcommunity.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.