I-D ACTION:draft-ietf-tsvwg-mlpp-that-works-01.txt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.

	Title		: Implementing MLPP for Voice and Video in the Internet Protocol Suite
	Author(s)	: F. Baker, J. Polk
	Filename	: draft-ietf-tsvwg-mlpp-that-works-01.txt
	Pages		: 44
	Date		: 2005-7-19
	
The Defense Information Systems Agency of the United States
   Department of Defense, with its contractors, has proposed a service
   architecture for military (NATO and related agencies) telephone
   systems.  This is called the Assured Service, and is defined in two
   documents: "Architecture for Assured Service Capabilities in Voice
   over IP" and "Requirements for Assured Service Capabilities in Voice
   over IP".  Responding to these are two documents: "Extending the
   Session Initiation Protocol Reason Header to account for Preemption
   Events", "Communications Resource Priority for the Session Initiation
   Protocol".

   What remains to this specification is to provide a Call Admission
   Control procedure and a Per Hop Behavior for the data which meet the
   needs of this architecture.  Such a CAC procedure and PHB is
   appropriate to any service that might use H.323 or SIP to set up real
   time sessions.  These obviously include but are not limited to Voice
   and Video applications, although at this writing the community is
   mostly thinking about Voice on IP and many of the examples in the
   document are taken from that environment.

   In a network where a call that is permitted initially and is not
   denied or rejected at a later time, call and capacity admission
   procedures performed only at the time of call setup may be
   sufficient.  However in a network where sessions' status can be
   reviewed by the network and preempted or denied due to changes in
   routing (when the new routes lack capacity to carry calls switched to
   them) or changes in offered load (where higher precedence calls
   supercede existing calls), maintaining a continuing model of the
   status of the various calls is required.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-mlpp-that-works-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also 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-ietf-tsvwg-mlpp-that-works-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tsvwg-mlpp-that-works-01.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-ietf-tsvwg-mlpp-that-works-01.txt>
_______________________________________________

I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux