RFC 5772 on A Set of Possible Requirements for a Future Routing Architecture
rfc-editor@rfc-editor.org Thu, 18 February 2010 18:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 904D128C30E for <ietf-announce@core3.amsl.com>; Thu, 18 Feb 2010 10:21:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level:
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9bAnRgWOkufS for <ietf-announce@core3.amsl.com>; Thu, 18 Feb 2010 10:21:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 9298C28C1D2 for <ietf-announce@ietf.org>; Thu, 18 Feb 2010 10:21:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4B749130013; Thu, 18 Feb 2010 10:23:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5772 on A Set of Possible Requirements for a Future Routing Architecture
From: rfc-editor@rfc-editor.org
Message-Id: <20100218182305.4B749130013@rfc-editor.org>
Date: Thu, 18 Feb 2010 10:23:05 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2010 18:21:22 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5772 Title: A Set of Possible Requirements for a Future Routing Architecture Author: A. Doria, E. Davies, F. Kastenholz Status: Historic Date: February 2010 Mailbox: avri@ltu.se, elwynd@dial.pipex.com, frank@bbn.com Pages: 68 Characters: 158456 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-routing-reqs-11.txt URL: http://www.rfc-editor.org/rfc/rfc5772.txt The requirements for routing architectures described in this document were produced by two sub-groups under the IRTF Routing Research Group (RRG) 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. This document defines a Historic Document for the Internet community. This document is a product of the IRTF. HISTORIC: This memo defines a Historic Document 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC