Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering
draft-malis-diff-te-serviceclass-04
The information below is for an old version of the document that is already published as an RFC.
| Document | Type | RFC Internet-Draft (sub) | |
|---|---|---|---|
| Authors | Tony Hsiao , Andrew G. Malis | ||
| Last updated | 2015-10-14 (Latest revision 2002-09-30) | ||
| Stream | Legacy stream | ||
| Formats | plain text htmlized pdfized bibtex | ||
| Stream | Legacy state | (None) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | RFC 3496 (Informational) | |
| Telechat date | (None) | ||
| Responsible AD | Scott O. Bradner | ||
| Send notices to | (None) |
draft-malis-diff-te-serviceclass-04
A new Request for Comments is now available in online RFC libraries.
RFC 3496
Title: Protocol Extension for Support of Asynchronous
Transfer Mode (ATM) Service Class-aware
Multiprotocol Label Switching (MPLS)
Traffic Engineering
Author(s): A. G. Malis, T. Hsiao
Status: Informational
Date: March 2003
Mailbox: Andy.Malis@vivacenetworks.com,
Tony.Hsiao@VivaceNetworks.com
Pages: 6
Characters: 11431
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-malis-diff-te-serviceclass-04.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3496.txt
This document specifies a Resource ReSerVation Protocol-Traffic
Engineering (RSVP-TE) signaling extension for support of Asynchronous
Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching
(MPLS) Traffic Engineering.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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.echo
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.