[rrg] Fwd: RFC 6115 on Recommendation for a Routing Architecture

Tony Li <tony.li@tony.li> Tue, 01 March 2011 08:27 UTC

Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DE5B3A6A43 for <rrg@core3.amsl.com>; Tue, 1 Mar 2011 00:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 5yDt3o2kydCl for <rrg@core3.amsl.com>; Tue, 1 Mar 2011 00:27:58 -0800 (PST)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 2BFF73A69C2 for <rrg@irtf.org>; Tue, 1 Mar 2011 00:27:57 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta07.westchester.pa.mail.comcast.net with comcast id DkUp1g0011c6gX857kV19E; Tue, 01 Mar 2011 08:29:01 +0000
Received: from sjc-vpn5-168.cisco.com ([128.107.239.233]) by omta23.westchester.pa.mail.comcast.net with comcast id DkUp1g00C52qHCY3jkUsbW; Tue, 01 Mar 2011 08:28:57 +0000
From: Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Tue, 01 Mar 2011 00:28:48 -0800
References: <20110222185832.3E785E0706@rfc-editor.org>
To: rrg@irtf.org
Message-Id: <5E59E392-3D31-4EE1-AE59-E7F221B83391@tony.li>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [rrg] Fwd: RFC 6115 on Recommendation for a Routing Architecture
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 08:27:59 -0000

In case folks missed this...

One down.  ;-)

Tony


Begin forwarded message:

> From: rfc-editor@rfc-editor.org
> Date: February 22, 2011 10:58:32 AM PST
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: rfc-editor@rfc-editor.org
> Subject: RFC 6115 on Recommendation for a Routing Architecture
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 6115
> 
>        Title:      Recommendation for a Routing Architecture 
>        Author:     T. Li, Ed.
>        Status:     Informational
>        Stream:     IRTF
>        Date:       February 2011
>        Mailbox:    tony.li@tony.li
>        Pages:      73
>        Characters: 178526
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-irtf-rrg-recommendation-16.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc6115.txt
> 
> 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 that
> could 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.  This document 
> is not an Internet Standards Track specification; it is
> published for informational purposes.
> 
> This document is a product of the IRTF.
> 
> 
> INFORMATIONAL: This memo provides information 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
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce