I-D ACTION:draft-vaananen-mpls-tm-framework-00.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-vaananen-mpls-tm-framework-00.txt



A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Framework for Traffic Management in MPLS Networks
	Author(s)	: P. Vaananen, R. Ravikanth
	Filename	: draft-vaananen-mpls-tm-framework-00.txt
	Pages		: 55
	Date		: 19-Mar-98
	
It has been recognised that the success of the MPLS depends on the
ability to better support the multiservice traffic integration with
some levels of service guarantees, which are not feasible to implement
with the current destination prefix only based packet forwarding
paradigms.
 
The efficient support for these services throughout the network is
expected to be possible using label based forwarding paradigm in the
network.
 
However, the service categories and the enabling mechanisms to support
those service categories are not well addressed in the current
proposals for the MPLS working group; the effort has mostly
concentrated on the handling of the best effort traffic and associated
scalability and routing related issues.
 
The goal of this document is to define a framework for traffic
management in MPLS networks. We discuss the set of mechanisms that have
been proposed for enabling the implementation of the more advanced
services than pure best-effort packet forwarding, and the impact of
those mechanisms with respect to MPLS network environments and MPLS
protocol implementation.

The document describes the mechanisms and their application with the
intent to approach the level of the traffic management capabilities
that are currently available in hybrid router/ATM or frame relay
networks using the MPLS. The approach taken is that no modifications
are required in the end station protocol or application software in the
first phase of deployment, while this might be allowed later, if deemed
necessary.
 
This document concentrates on the issues from the public network
operators point of view, although most of the discussion applies as
well in the local network environments.
 
Concepts and mechanisms described in this document are based on the
previous work done in the subject on various working groups of IETF and
other standardisation bodies. It has been attempted to use applicable
concepts and terminology from previous work as

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-vaananen-mpls-tm-framework-00.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-vaananen-mpls-tm-framework-00.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	
	Europe: ftp.nordu.net
		ftp.nis.garr.it
			
	Pacific Rim: munnari.oz.au
	
	US East Coast: ftp.ietf.org
	
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv at ietf.org.  In the body type:
	"FILE /internet-drafts/draft-vaananen-mpls-tm-framework-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
<ftp://ftp.ietf.org/internet-drafts/draft-vaananen-mpls-tm-framework-00.txt>

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.