RFC 6139 on Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) Scenarios
rfc-editor@rfc-editor.org Mon, 28 February 2011 18:28 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 8F0B13A6C27 for <ietf-announce@core3.amsl.com>; Mon, 28 Feb 2011 10:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level:
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.137, 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 5xmEBzyobH1p for <ietf-announce@core3.amsl.com>; Mon, 28 Feb 2011 10:28:51 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 3E5B43A6C1D for <ietf-announce@ietf.org>; Mon, 28 Feb 2011 10:28:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 78777E0740; Mon, 28 Feb 2011 10:29:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6139 on Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) Scenarios
From: rfc-editor@rfc-editor.org
Message-Id: <20110228182951.78777E0740@rfc-editor.org>
Date: Mon, 28 Feb 2011 10:29:51 -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: Mon, 28 Feb 2011 18:28:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6139
Title: Routing and Addressing in Networks
with Global Enterprise Recursion (RANGER) Scenarios
Author: S. Russert, Ed.,
E. Fleischman, Ed.,
F. Templin, Ed.
Status: Informational
Stream: Independent
Date: February 2011
Mailbox: russerts@hotmail.com,
eric.fleischman@boeing.com,
fltemplin@acm.org
Pages: 39
Characters: 101101
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-russert-rangers-05.txt
URL: http://www.rfc-editor.org/rfc/rfc6139.txt
"Routing and Addressing in Networks with Global Enterprise Recursion
(RANGER)" (RFC 5720) provides an architectural framework for scalable
routing and addressing. It provides an incrementally deployable
approach for scalability, provider independence, mobility,
multihoming, traffic engineering, and security. This document
describes a series of use cases in order to showcase the
architectural capabilities. It further shows how the RANGER
architecture restores the network-within-network principles
originally intended for the sustained growth of the Internet.
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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