[AAA-DOCTORS] FW: Evaluation: draft-irtf-routing-reqs-10.txt to Historic
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 05 February 2009 10:41 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB2B13A6C82; Thu, 5 Feb 2009 02:41:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[AWL=-0.424, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, SARE_SUB_RAND_LETTRS4=0.799]
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 1tpJKiHbvvsd; Thu, 5 Feb 2009 02:41:07 -0800 (PST)
Received: from co300216-co-outbound.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id DE6E63A6C80; Thu, 5 Feb 2009 02:41:06 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,384,1231131600"; d="scan'208";a="160405342"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 05 Feb 2009 05:40:47 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Feb 2009 05:40:46 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 05 Feb 2009 11:40:43 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401394EF1@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Evaluation: draft-irtf-routing-reqs-10.txt to Historic
thread-index: AcmG9ibwZWgYhjvPQc2jIrK9Vch8gAAiAF1Q
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: aaa-doctors@ietf.org, ops-dir@ietf.org
Subject: [AAA-DOCTORS] FW: Evaluation: draft-irtf-routing-reqs-10.txt to Historic
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2009 10:41:08 -0000
A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-irtf-routing-reqs-10.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary Technical Summary 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. Working Group Summary This is an IRTF output, and is being considered by the IESG only to consider whether there is any overlap or conflict with IETF work. Document Quality This is an informational document which is not subject to implementation. It has been carefully reviewed in the IRTF. Personnel Ross Callon has agreed to shepherd this through IESG review. RFC Editor Note This work does not conflict with IETF work, and we recommend that the RFC editor publish this document. Right after the first paragraph of section 3.1 (which starts: "It is generally accepted..."), please add the following note: Reviewer's Note: Even in 2001, there was a wide difference of opinion across the community regarding the shortcomings of interdomain routing. In the years between writing and publication, further analysis, changes in operational practice, alterations to the demands made on inter-domain routing, modifications made to BGP and a recognition of the difficulty of finding a replacement may have altered the views of some members of the community. IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section)
- [AAA-DOCTORS] FW: Evaluation: draft-irtf-routing-… Romascanu, Dan (Dan)