[ranger] Resend: RANGER BOF - call for participation

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 03 February 2009 18:37 UTC

Return-Path: <ranger-bounces@ietf.org>
X-Original-To: ranger-archive@ietf.org
Delivered-To: ietfarch-ranger-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CDDE3A67FD; Tue, 3 Feb 2009 10:37:54 -0800 (PST)
X-Original-To: ranger@core3.amsl.com
Delivered-To: ranger@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CEC13A69D2; Tue, 3 Feb 2009 10:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level:
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 24D+ycTyA4Dr; Tue, 3 Feb 2009 10:37:52 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id F2C603A6806; Tue, 3 Feb 2009 10:37:48 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n13IbETF027626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Feb 2009 10:37:24 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n13IbEhd022923; Tue, 3 Feb 2009 10:37:14 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n13Ib9OM022630; Tue, 3 Feb 2009 10:37:14 -0800 (PST)
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); Tue, 3 Feb 2009 10:37:13 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 3 Feb 2009 10:33:22 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10586649A@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Resend: RANGER BOF - call for participation
Thread-Index: AcmDBTLZUbaYGQdGQ1aj2tAZfubKMAAGdDEAAMKRmyA=
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "RRG" <rrg@irtf.org>, <int-area@ietf.org>, <routing-discussion@ietf.org>, <ranger@ietf.org>
X-OriginalArrivalTime: 03 Feb 2009 18:37:13.0113 (UTC) FILETIME=[6E225090:01C9862E]
Subject: [ranger] Resend: RANGER BOF - call for participation
X-BeenThere: ranger@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing and Addressing in Next-Generation EnteRprises <ranger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ranger>, <mailto:ranger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ranger>
List-Post: <mailto:ranger@ietf.org>
List-Help: <mailto:ranger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ranger>, <mailto:ranger-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ranger-bounces@ietf.org
Errors-To: ranger-bounces@ietf.org

Please see below for a resend of the IETF74 RANGER BOF
call for participation, including a link for subscribing
to the 'ranger@ietf.org' list which is now active. Please
post further discussion to 'ranger@ietf.org'org'.

Thanks - Fred
fred.l.templin@boeing.com

-----Original Message-----
From: Templin, Fred L 
Sent: Friday, January 30, 2009 1:21 PM
To: rrg@irtf.org; int-area@ietf.org
Subject: [Int-area] RANGER BOF - call for participation

A community of interest is being formed to gauge
whether there is sufficient interest to host a BOF
on "Routing and Addressing in Next-Generation
EnteRprises (RANGER)" at IETF74.

Please see below for proposed BOF agenda, and comment
on the RRG and int-area lists while we wait for the
ranger list to come up.

Fred Templin
fred.l.templin@boeing.com



Routing and Addressing in Next-Generation EnteRprises (RANGER) BOF
===================================================================

Chairs:  TBD

Reponsible AD:  TBD (INT Area; Routing Area)

Mailing List:  ranger at ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/ranger
Archive: http://www.ietf.org/mail-archive/web/ranger

Duration:  2 hours

Expected Attendance: 50

Conflicts: LISP BOF, NAT66 BOF, int-area open meeting,
           IRTF rrg meeting

Summary
=======

RANGER [1] is a scalable architecture for routing and
addressing in next-generation enterprise networks, where
an "enterprise" [2] can be as small as a SOHO network,
as dynamic as a Mobile Ad-hoc Network (MANET) [3] or as
large as the global Internet itself [4]. The architecture
is manifested through Virtual Enterprise Traversal (VET)
[5], in which IP-in-IP encapsulation provides a virtual
view of each enterprise as a Non-Broadcast, Multiple-
Access (NBMA) link.

RANGER is recursive, in that multiple enterprises can be
joined together in a nested "enterprise-within-enterprise"
fashion. In this way, the same RANGER principles that
apply in lower levels of recursion can extend upwards
to parent enterprises and ultimately to the core of the
global Internet itself. Furthermore, it is also worth
considering whether today's global Internet represents a
limiting condition for recursion, or if other Internets
could be manifested as "parallel universes" and joined
together at still higher levels of recursion.

The RANGER architecture is manifested through composite
technologies including Virtual Enterprise Traversal (VET),
the Subnetwork Encapsulation and Adaptation Layer (SEAL)
[6], the Intra-Site Automatic Tunnel Addressing Protocol
(ISATAP) [7], and many others. Noting that combinations
with other technologies are also possible, the issues
addressed either in full or in part by RANGER include:

- IPv6/IPv4 coexistence and transition
- scalable routing and addressing
- provider-independent addressing and its
  relation to provide-aggregated addressing
- site mobility and multi-homing
- ingress filtering for multi-homed sites
- address and prefix autoconfiguration
- border router discovery
- router-to-router tunneling
- neighbor discovery over tunnels
- MTU determination for tunnels.

As seen in the above list, the RANGER architecture
provides a framework for addressing a broad range of
problem areas that currently limit the functionality,
growth and maturation of today's Internet. Therefore,
it is the purpose of this BOF to discuss the formation
of an IETF WG to produce the following work items:

1) An Informational RFC describing the RANGER architecture.
   This document to provide a high-level overview of the
   RANGER enterprise-within-enterprise framework, its
   constituent technologies, and its domain of
   applicability.

2) An RFC specification of Virtual Enterprise Traversal
   (VET). This document to specify the inner workings of
   IP-in-IP encapsulation and its associated mechanisms
   within the RANGER context.

3) An RFC specification of the Subnetwork Encapsulation
   and Adaptation Layer (SEAL). This document to specify
   an encapsulation sublayer used to provide enhanced
   packet identification and tunnel MTU robustness.

4) Other work items within scope as determined, e.g.,
   by working group/BOF consensus, etc.

Agenda
======

- Administrivia (Chairs, 5 min)

- Purpose of BOF (Chairs, 10 min) [see above]

- Routing and Addressing in Next Generation EnteRprises
  (RANGER) (20 min)

- Virtual Enterprise Traversal (VET) (20 min)

- Subnetwork Encapsulation and Adaptation Layer (SEAL)
  (20 min)

- Proposed Charter (Chairs, 10 min)

- Questions/Next Steps (Chairs, 30 min)


Documents:
==========

[1] Templin, F., "Routing and Addressing in Next-Generation
    EnteRprises (RANGER), 'draft-templin-ranger',
    work-in-progress, January 2009.

[2] Bound, J., et. al., "IPv6 Enterprise Network Analysis -
    IP Layer 3 Focus", IETF RFC 4852, April 2007.

[3] Corson, S., et. al., "Mobile Ad hoc Networking (MANET):
    Routing Protocol Performance Issues and Evaluation
    Considerations", IETF RFC 2501, January 1999.

[4] IRTF Routing Research Group, http://www.irtf.org/rrg

[5] Templin, F., "Virtual Enterprise Traversal (VET)",
    'draft-templin-autoconf-dhcp', work-in-progress,
    January 2009.

[6] Templin, F., "Subnetwork Encapsulation and Adaptation
    Layer (SEAL)", 'draft-templin-seal', work-in-progress,
    December 2009.

[7] Templin, F., et. al., "Intra-Site Automatic Tunnel
    Addressing Protocol (ISATAP)", IETF RFC 5214, March 2008. 
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
ranger mailing list
ranger@ietf.org
https://www.ietf.org/mailman/listinfo/ranger