RE: RANGER

["Templin, Fred L" <Fred.L.Templin at boeing.com>]

Eric,

Interesting question, and I'm not entirely sure how to answer
it. But, if it helps, I was just in the process of adding the
following text to Section 3.1 when your message came in:

  "It is important to note that dual-stack systems such as 'V',
   'W' and 'Z' may be simple IPv6/IPv4 hosts, or they may be BRs
   that attach arbitrarily-complex IPv6-only edge networks. Such
   From ipv6-bounces at ietf.org  Fri Oct 17 15:09:30 2008
Return-Path: <ipv6-bounces at ietf.org>
X-Original-To: ipv6-archive at megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0CF2328C157;
	Fri, 17 Oct 2008 15:09:30 -0700 (PDT)
X-Original-To: ipv6 at core3.amsl.com
Delivered-To: ipv6 at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27C9228C0D6;
	Fri, 17 Oct 2008 15:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.21
X-Spam-Level: 
X-Spam-Status: No, score=-5.21 tagged_above=-999 required=5 tests=[AWL=-0.688, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077]
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 XVMKox0KUq01; Fri, 17 Oct 2008 15:09:26 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com
	[130.76.96.56])
	by core3.amsl.com (Postfix) with ESMTP id 1F83728C0E8;
	Fri, 17 Oct 2008 15:09:25 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m9HM9tOO014034
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 17 Oct 2008 17:10:00 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m9HM9sWP006695; Fri, 17 Oct 2008 15:09:54 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m9HM9s3L006686; Fri, 17 Oct 2008 15:09:54 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 17 Oct 2008 15:09:55 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: RANGER
Date: Fri, 17 Oct 2008 15:09:52 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1051B3DD9 at XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <courier.48F90B60.000004B7 at softhome.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RANGER
Thread-Index: AckwpAkPmJrFi1/8QVyudNl0+fdHGAAAHjGg
References: <39C363776A4E8C4A94691D2BD9D1C9A10517EDDF at XCH-NW-7V2.nw.nos.boeing.com>
	<courier.48F90B60.000004B7 at softhome.net>
From: "Templin, Fred L" <Fred.L.Templin at boeing.com>
To: <EricLKlein at softhome.net>
X-OriginalArrivalTime: 17 Oct 2008 22:09:55.0099 (UTC)
	FILETIME=[15D816B0:01C930A5]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-5.500.1027-16222.001
X-TM-AS-Result: No--17.174100-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: Internet Area <int-area at ietf.org>, manet <manet at ietf.org>,
	autoconf at ietf.org, rrg at irtf.org, DHC WG <dhcwg at ietf.org>,
	IPv6 Operations <v6ops at ops.ietf.org>, ipv6 at ietf.org
X-BeenThere: ipv6 at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipv6>
List-Post: <mailto:ipv6 at ietf.org>
List-Help: <mailto:ipv6-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces at ietf.org
Errors-To: ipv6-bounces at ietf.org

Eric,

Interesting question, and I'm not entirely sure how to answer
it. But, if it helps, I was just in the process of adding the
following text to Section 3.1 when your message came in:

  "It is important to note that dual-stack systems such as 'V',
   'W' and 'Z' may be simple IPv6/IPv4 hosts, or they may be BRs
   that attach arbitrarily-complex IPv6-only edge networks. Such
   IPv6-only edge networks could be as simple as a home network
   behind a residential gateway, or as complex as a major
   corporate/academic campus, a large service provider network,
   etc."

Comments are welcome,

Fred
fred.l.templin at boeing.com 

>-----Original Message-----
>From: EricLKlein at softhome.net [mailto:EricLKlein at softhome.net] 
>Sent: Friday, October 17, 2008 3:02 PM
>To: Templin, Fred L
>Cc: Internet Area; rrg at irtf.org; IPv6 Operations; 
>autoconf at ietf.org; manet; ipv6 at ietf.org; DHC WG
>Subject: Re: RANGER
>
>Hi Fred, 
>
>How do you see RANGER fitting into the requirements for 
>carriers to supply 
>IP support (v4/v6) to mobile devices? Especially requirements that are 
>similar to the enterprise ones that you describe? 
>
>Eric 
>
>Templin, Fred L writes: 
>
>> This message is to introduce a new Internet-Draft titled: 
>> 
>>   "Routing and Addressing in Next-Generation EnteRprises (RANGER)" 
>> 
>> RANGER is an architectural framework that uses well known
>> (and in some cases widely-deployed) functional elements.
>> RANGER is not a technical specification in itself, however
>> it provides applicability analysis for the combination of
>> existing and emerging technical specifications. In particular,
>> it outlines an "enterprise-within-enterprise" framework that
>> addresses issues such as routing scaling, IPv6/IPv4 coexistence,
>> link MTU diversity, mobile ad-hoc networking, autoconfiguration,
>> etc. 
>> 
>> The RANGER enterprise network model supports cooperative
>> operations between diverse organizations that may have
>> competing interests. The model can therefore be applied
>> to the global Internet itself. 
>> 
>> In order to reduce fragmentation, please post any follow-up
>> comments or questions to the int-area and rrg lists only. 
>> 
>> Fred Templin
>> fred.l.templin at boeing.com     
>> 
>> -----Original Message-----
>> From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org] 
>> Sent: Tuesday, October 14, 2008 11:45 AM
>> To: i-d-announce at ietf.org
>> Subject: I-D Action:draft-templin-ranger-00.txt  
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. 
>> 
>> 	Title           : Routing and Addressing in Next-Generation
>> EnteRprises (RANGER)
>> 	Author(s)       : F. Templin
>> 	Filename        : draft-templin-ranger-00.txt
>> 	Pages           : 17
>> 	Date            : 2008-10-14 
>> 
>> Enterprise networks will require support for both Internet protocol
>> versions (IPv4 and IPv6) for an indeterminant period; perhaps even
>> indefinitely.  This is particularly true for existing enterprise
>> networks that must introduce IPv6 without disruption of IPv4
>> services, but the same principles apply also to clean-slate
>> deployments in new enterprises.  Next-generation enterprises
>> therefore require an architected solution for coordination of their
>> internal routing and addressing plans for both IPv6 and IPv4.  The
>> RANGER architecture addresses these requirements. 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-templin-ranger-00.txt 
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/ 
>> 
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft. 
>> 
> 
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


IPv6-only edge networks could be as simple as a home network
   behind a residential gateway, or as complex as a major
   corporate/academic campus, a large service provider network,
   etc."

Comments are welcome,

Fred
fred.l.templin at boeing.com 

>-----Original Message-----
>From: EricLKlein at softhome.net [mailto:EricLKlein at softhome.net] 
>Sent: Friday, October 17, 2008 3:02 PM
>To: Templin, Fred L
>Cc: Internet Area; rrg at irtf.org; IPv6 Operations; 
>autoconf at ietf.org; manet; ipv6 at ietf.org; DHC WG
>Subject: Re: RANGER
>
>Hi Fred, 
>
>How do you see RANGER fitting into the requirements for 
>carriers to supply 
>IP support (v4/v6) to mobile devices? Especially requirements that are 
>similar to the enterprise ones that you describe? 
>
>Eric 
>
>Templin, Fred L writes: 
>
>> This message is to introduce a new Internet-Draft titled: 
>> 
>>   "Routing and Addressing in Next-Generation EnteRprises (RANGER)" 
>> 
>> RANGER is an architectural framework that uses well known
>> (and in some cases widely-deployed) functional elements.
>> RANGER is not a technical specification in itself, however
>> it provides applicability analysis for the combination of
>> existing and emerging technical specifications. In particular,
>> it outlines an "enterprise-within-enterprise" framework that
>> addresses issues such as routing scaling, IPv6/IPv4 coexistence,
>> link MTU diversity, mobile ad-hoc networking, autoconfiguration,
>> etc. 
>> 
>> The RANGER enterprise network model supports cooperative
>> operations between diverse organizations that may have
>> competing interests. The model can therefore be applied
>> to the global Internet itself. 
>> 
>> In order to reduce fragmentation, please post any follow-up
>> comments or questions to the int-area and rrg lists only. 
>> 
>> Fred Templin
>> fred.l.templin at boeing.com     
>> 
>> -----Original Message-----
>> From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org] 
>> Sent: Tuesday, October 14, 2008 11:45 AM
>> To: i-d-announce at ietf.org
>> Subject: I-D Action:draft-templin-ranger-00.txt  
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. 
>> 
>> 	Title           : Routing and Addressing in Next-Generation
>> EnteRprises (RANGER)
>> 	Author(s)       : F. Templin
>> 	Filename        : draft-templin-ranger-00.txt
>> 	Pages           : 17
>> 	Date            : 2008-10-14 
>> 
>> Enterprise networks will require support for both Internet protocol
>> versions (IPv4 and IPv6) for an indeterminant period; perhaps even
>> indefinitely.  This is particularly true for existing enterprise
>> networks that must introduce IPv6 without disruption of IPv4
>> services, but the same principles apply also to clean-slate
>> deployments in new enterprises.  Next-generation enterprises
>> therefore require an architected solution for coordination of their
>> internal routing and addressing plans for both IPv6 and IPv4.  The
>> RANGER architecture addresses these requirements. 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-templin-ranger-00.txt 
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/ 
>> 
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft. 
>> 
> 
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------