Re: [shara] Problem statement

<Gabor.Bajko@nokia.com> Wed, 28 January 2009 04:40 UTC

Return-Path: <shara-bounces@ietf.org>
X-Original-To: shara-archive@ietf.org
Delivered-To: ietfarch-shara-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6AD03A6BA5; Tue, 27 Jan 2009 20:40:51 -0800 (PST)
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 5BFA228C155 for <shara@core3.amsl.com>; Tue, 27 Jan 2009 20:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.079
X-Spam-Level:
X-Spam-Status: No, score=-6.079 tagged_above=-999 required=5 tests=[AWL=-0.720, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
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 Aad03BZWrXwG for <shara@core3.amsl.com>; Tue, 27 Jan 2009 20:40:49 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 908B73A6850 for <shara@ietf.org>; Tue, 27 Jan 2009 20:40:49 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n0S4d4CA021532 for <shara@ietf.org>; Tue, 27 Jan 2009 22:40:27 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Jan 2009 06:39:43 +0200
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Jan 2009 06:39:43 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Jan 2009 06:39:38 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Wed, 28 Jan 2009 05:39:37 +0100
From: <Gabor.Bajko@nokia.com>
To: <shara@ietf.org>
Date: Wed, 28 Jan 2009 05:39:32 +0100
Thread-Topic: [shara] Problem statement
Thread-Index: AcmA2lE3maEIELPaS0mG40N3HYpfHAAJ0kvQ
Message-ID: <A99B171D26E1564B92D36826128CD66127E33BC7F3@NOK-EUMSG-01.mgdnok.nokia.com>
References: <497F01B1.9030701@ericsson.com> <C5A4D260.1448C%omaennel@net.t-labs.tu-berlin.de> <A99B171D26E1564B92D36826128CD66127E33BC71F@NOK-EUMSG-01.mgdnok.nokia.com> <497F9E35.1080206@isoc.org>
In-Reply-To: <497F9E35.1080206@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Jan 2009 04:39:38.0032 (UTC) FILETIME=[6D4B0300:01C98102]
X-Nokia-AV: Clean
Subject: Re: [shara] Problem statement
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: shara-bounces@ietf.org
Errors-To: shara-bounces@ietf.org

  >-----Original Message-----
  >From: ext Matthew Ford [mailto:ford@isoc.org]
  >Sent: Tuesday, January 27, 2009 3:52 PM
  >To: Bajko Gabor (Nokia-CIC/MtView)
  >Cc: omaennel@net.t-labs.tu-berlin.de; magnus.westerlund@ericsson.com;
  >shara@ietf.org
  >Subject: Re: [shara] Problem statement
  >
  >Hi all,
  >
  >On 27/1/09 23:25, Gabor.Bajko@nokia.com wrote:
  >> Hi Olaf,
  >>
  >> I think what SHARA should be intended to is:
  >
  >> b) develop solutions for the problems a shared IPv4 address creates:
  >fragmentation, routing, tunneling, lack of port randomization, etc.
  >
  >If there were easy solutions for all the issues created by widespread
  >deployment of shared IPv4 addresses, we wouldn't need IPv6.
  >
  >I think an important work item to add to the charter is documentation of
  >as many of the issues that shared IPv4 addresses create that can be
  >identified by the community at the time. Shared addresses may (or may
  >not) be necessary but they should come with a health warning.

Good point to add. The intention is to emphasize that this solution is a temporary one to be used during the transition period, and not an alternative to IPv6 (not even on the short term).

  >I can offer cycles to work on this.

Thanks, your input is needed and appreciated.
- gabor

  >Mat
_______________________________________________
shara mailing list
shara@ietf.org
https://www.ietf.org/mailman/listinfo/shara