RFC 4126 on Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons

A new Request for Comments is now available in online RFC libraries.

        RFC 4126

        Title:      Max Allocation with Reservation Bandwidth
                    Constraints Model for Diffserv-aware MPLS Traffic
                    Engineering & Performance Comparisons
        Author(s):  J. Ash
        Status:     Experimental
        Date:       June 2005
        Mailbox:    gash@att.com
        Pages:      22
        Characters: 51232
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tewg-diff-te-mar-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4126.txt

This document complements the Diffserv-aware MPLS Traffic Engineering
(DS-TE) requirements document by giving a functional specification for
the Maximum Allocation with Reservation (MAR) Bandwidth Constraints
Model.  Assumptions, applicability, and examples of the operation of 
the MAR Bandwidth Constraints Model are presented.  MAR performance is
analyzed relative to the criteria for selecting a Bandwidth
Constraints Model, in order to provide guidance to user implementation
of the model in their networks.

This document is a product of the Internet Traffic Engineering Working
Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.