[NSIS] I-D ACTION:draft-ietf-nsis-req-08.txt

Internet-Drafts@ietf.org Thu, 19 June 2003 12:24 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12394 for <nsis-archive@odin.ietf.org>; Thu, 19 Jun 2003 08:24:52 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5JCONf17341 for nsis-archive@odin.ietf.org; Thu, 19 Jun 2003 08:24:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19SxyP-0002sa-Db; Thu, 19 Jun 2003 07:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19SxdS-0001jM-6S for nsis@optimus.ietf.org; Thu, 19 Jun 2003 07:31:22 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09336; Thu, 19 Jun 2003 07:31:20 -0400 (EDT)
Message-Id: <200306191131.HAA09336@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: nsis@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 19 Jun 2003 07:31:20 -0400
Subject: [NSIS] I-D ACTION:draft-ietf-nsis-req-08.txt
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Steps in Signaling Working Group of the IETF.

	Title		: Requirements for Signaling Protocols
	Author(s)	: M. Brunner
	Filename	: draft-ietf-nsis-req-08.txt
	Pages		: 36
	Date		: 2003-6-18
	
This document defines requirements for signaling across different 
network environments, such as across administrative and/or 
technology domains. Signaling is mainly considered for Quality of 
Service such as The Resource Reservation Protocol, however in recent 
years several other applications of signaling have been defined such 
as signaling for label distribution in Multiprotocol Label Switching 
or signaling to middleboxes. To achieve wide applicability of the 
requirements, the starting point is a diverse set of scenarios/use 
cases concerning various types of networks and application 
interactions. This document presents the assumptions before listing 
the requirements.  The requirements are grouped according to areas 
such as architecture and design goals, signaling flows, layering, 
performance, flexibility, security, and mobility.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-req-08.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-nsis-req-08.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-nsis-req-08.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-nsis-req-08.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-nsis-req-08.txt>