Re: Informational RFC to be: <draft-irtf-rrg-recommendation-15.txt>
The IESG <iesg-secretary@ietf.org> Mon, 22 November 2010 21:56 UTC
Return-Path: <iesg-secretary@ietf.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 1F5E628C167; Mon, 22 Nov 2010 13:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.842
X-Spam-Level:
X-Spam-Status: No, score=-101.842 tagged_above=-999 required=5 tests=[AWL=-0.642, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 KBLD2Vl-cd8k; Mon, 22 Nov 2010 13:56:52 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF73128C16D; Mon, 22 Nov 2010 13:56:51 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: irsg@isi.edu, jmh@joelhalpern.com
Subject: Re: Informational RFC to be: <draft-irtf-rrg-recommendation-15.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101122215651.25348.76173.idtracker@localhost>
Date: Mon, 22 Nov 2010 13:56:51 -0800
Cc: iana@iana.org, The IESG <iesg@ietf.org>, ietf-announce@ietf.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: Mon, 22 Nov 2010 21:56:53 -0000
The IESG has no problem with the publication of 'Recommendation for a Routing Architecture' <draft-irtf-rrg-recommendation-15.txt> as an Informational RFC. The IESG would also like the IRSG to review the comments in the datatracker (http://datatracker.ietf.org/doc/draft-irtf-rrg-recommendation/) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-irtf-rrg-recommendation/ The process for such documents is described at http://www.rfc-editor.org/indsubs.html Thank you, The IESG Secretary Technical Summary It is commonly recognized that the Internet routing and addressing architecture is facing challenges in scalability, multihoming, and inter-domain traffic engineering. This document presents, as a recommendation of future directions for the IETF, solutions which will aid the future scalability of the Internet. To this end, this document surveys many of the proposals that were brought forward for discussion in this activity, as well as some of the subsequent analysis and the architectural recommendation of the chairs. This document is a product of the Routing Research Group. Working Group Summary This is a product of the IRTF routing research group (RRG). The document is the chair's view of the results of the group. Document Quality The document and specific technical point have been discussed at length in the routing research group of the IRTF. Personnel The document shepherd is Joel Halpern, and the responsible AD is Jari Arkko. IESG Note Our conclusion is this: 2. The IESG has concluded that this work is related to IETF work done in WGs V6OPS and LISP, but this relationship does not prevent publishing.