RFC 6115 on Recommendation for a Routing Architecture

rfc-editor@rfc-editor.org Tue, 22 February 2011 18:57 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 1C61B3A6781 for <ietf-announce@core3.amsl.com>; Tue, 22 Feb 2011 10:57:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.414
X-Spam-Level:
X-Spam-Status: No, score=-102.414 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 zj+9a7GZbBZk for <ietf-announce@core3.amsl.com>; Tue, 22 Feb 2011 10:57:47 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 043FF3A68EA for <ietf-announce@ietf.org>; Tue, 22 Feb 2011 10:57:47 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3E785E0706; Tue, 22 Feb 2011 10:58:32 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6115 on Recommendation for a Routing Architecture
From: rfc-editor@rfc-editor.org
Message-Id: <20110222185832.3E785E0706@rfc-editor.org>
Date: Tue, 22 Feb 2011 10:58:32 -0800 (PST)
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: Tue, 22 Feb 2011 18:57:48 -0000

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