I-D ACTION:draft-irtf-routing-reqs-09.txt

Internet-Drafts@ietf.org Mon, 07 January 2008 17:15 UTC

Return-path: <i-d-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBvZ5-0004Rd-Lh; Mon, 07 Jan 2008 12:15:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBvZ1-0004R3-6S for i-d-announce@ietf.org; Mon, 07 Jan 2008 12:15:03 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JBvZ0-0001yI-Ip for i-d-announce@ietf.org; Mon, 07 Jan 2008 12:15:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 6CC1426E80 for <i-d-announce@ietf.org>; Mon, 7 Jan 2008 17:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1JBvZ0-0000Op-9p for i-d-announce@ietf.org; Mon, 07 Jan 2008 12:15:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc:
From: Internet-Drafts@ietf.org
Message-Id: <E1JBvZ0-0000Op-9p@stiedprstage1.ietf.org>
Date: Mon, 07 Jan 2008 12:15:02 -0500
X-Spam-Score: -0.4 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Subject: I-D ACTION:draft-irtf-routing-reqs-09.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org

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


	Title		: Requirements for Inter-Domain Routing
	Author(s)	: A. Doria, et al.
	Filename	: draft-irtf-routing-reqs-09.txt
	Pages		: 72
	Date		: 2008-1-7
	
The requirements for routing architectures described in this document
   were produced by two sub-groups under the IRTF Routing Research Group
   in 2001, with some editorial updates up to 2006.  The two sub-groups
   worked independently, and the resulting requirements represent two
   separate views of the problem and of what is required to fix the
   problem.  This document may usefully serve as part of the recommended
   reading for anyone who works on routing architecture designs for the
   Internet in the future.

   The document is published with the support of the IRTF RRG as a
   record of the work completed at that time, but with the understanding
   that it does not necessarily represent either the latest technical
   understanding or the technical consensus of the research group at the
   date of publication.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-irtf-routing-reqs-09.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-irtf-routing-reqs-09.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-irtf-routing-reqs-09.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-irtf-routing-reqs-09.txt"><ftp://ftp.ietf.org/internet-drafts/draft-irtf-routing-reqs-09.txt>
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce