[shara] Updated SHARA BOF description

marcelo bagnulo braun <marcelo@it.uc3m.es> Wed, 04 March 2009 18:42 UTC

Return-Path: <marcelo@it.uc3m.es>
X-Original-To: shara@core3.amsl.com
Delivered-To: shara@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19F5028C17A for <shara@core3.amsl.com>; Wed, 4 Mar 2009 10:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.279
X-Spam-Level:
X-Spam-Status: No, score=-6.279 tagged_above=-999 required=5 tests=[AWL=0.320, 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 s2yUfOZVE9VL for <shara@core3.amsl.com>; Wed, 4 Mar 2009 10:42:11 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id DA7C43A6CBB for <shara@ietf.org>; Wed, 4 Mar 2009 10:42:10 -0800 (PST)
Received: from marcelo-bagnulos-macbook-pro.local (70.pool85-53-139.dynamic.orange.es [85.53.139.70]) by smtp01.uc3m.es (Postfix) with ESMTP id 571A7B4D6EE for <shara@ietf.org>; Wed, 4 Mar 2009 19:42:37 +0100 (CET)
Message-ID: <49AECB9D.4000804@it.uc3m.es>
Date: Wed, 04 Mar 2009 19:42:37 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: shara@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16500.001
Subject: [shara] Updated SHARA BOF description
X-BeenThere: shara@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Sharing of an IPv4 Address discussion list <shara.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shara>
List-Post: <mailto:shara@ietf.org>
List-Help: <mailto:shara-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 18:42:12 -0000

Hi,

We have updated the SHARA bof description to adapt its scope to the 
non-wg forming bof that was accepted by the ADs.

Please find it below.

Comments are welcome

Regards, marcelo

(on behalf of Bernard, Magnus and myself)



Sharing IPv4 Addresses (SHARA) BOF

In the current Internet, it is fairly common for ISPs to provision
their subscribers with a single public IPv4 address and for those
subscribers to use NAT technology to allow multiple machines in
their networks to access the Internet. This setup essentially
requires one public IPv4 address per subscriber. As the IPv4 free
address pool becomes depleted, it seems likely that  ISPs will not
have enough public IPv4 addresses to assign one address per
subscriber. When that happens, multiple subscriber networks will
have to share a single public IPv4 address. Multiple approaches
have been proposed in order to implement the sharing of public
IPv4 addresses, as described in section 2.1 of
draft-arkko-townsley-coexistence-00.

The goal of this BOF is to discuss and gain understanding of a
particular family of solutions, the so called distributed-NAT
approaches described in section 2.1.2 of draft-arkko-townsley-
coexistence-00. This family of solutions, essentially assigns
a public IP address and a port range to each subscriber and
relies on some form of port range routing capability within
the ISP network. The result is that each subscriber still
obtains at least a part of a public IP address and retains
some of the capabilities of the current configuration.

During the BOF we intend to discuss the following items:
- Problem characterization: We need to understand what is
exactly the problem, what are the different scenarios that are
affected by the IPv4 address space depletion and what are the
possible approaches to address the problem. In addition, we
need to identify the different relevant aspects of the problem
and solution space that need to be taken into account during
the discussion of the solution space.
- Motivation for SHARA: Discuss the benefits and potential
issues with a distributed NAT approach.
- Distributed NAT approaches: Explore the solution space for
distributed NATs and the implications of the relevant aspects
previously identified.
- Interaction with other efforts. There are a significant
number of efforts in related areas, such as the work being
done in the BEHAVE WG and the SOFTWIRES WG. It is then relevant
to understand how the proposed mechanisms interact with these.
- Implication for the deployment of IPv6. Any mechanism that
aims to extend the lifetime of IPv4 can potentially delay IPv6
deployment. An analysis of the impact of the adoption of these
techniques is needed.


This is non-wg forming BOF and the goal is to provide input
material to the community in general and the IESG in particular
for them to scope out what gaps still need to be addressed in
chartered WG items in other WGs.