IETF Logo Mail Archive

Re: [shara] Problem statement

Matthew Ford <ford@isoc.org> Tue, 27 January 2009 23:52 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 8A9C63A69EF; Tue, 27 Jan 2009 15:52:44 -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 4BACE3A69EF for <shara@core3.amsl.com>; Tue, 27 Jan 2009 15:52:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level:
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 9vJ6yl3haL7X for <shara@core3.amsl.com>; Tue, 27 Jan 2009 15:52:42 -0800 (PST)
Received: from smtp225.iad.emailsrvr.com (smtp225.iad.emailsrvr.com [207.97.245.225]) by core3.amsl.com (Postfix) with ESMTP id 88FFB3A67EF for <shara@ietf.org>; Tue, 27 Jan 2009 15:52:42 -0800 (PST)
Received: from relay12.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay12.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id BCB4020D98E; Tue, 27 Jan 2009 18:52:23 -0500 (EST)
Received: by relay12.relay.iad.mlsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id CF71D20D913; Tue, 27 Jan 2009 18:52:22 -0500 (EST)
Message-ID: <497F9E35.1080206@isoc.org>
Date: Tue, 27 Jan 2009 23:52:21 +0000
From: Matthew Ford <ford@isoc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1
MIME-Version: 1.0
To: Gabor.Bajko@nokia.com
References: <497F01B1.9030701@ericsson.com> <C5A4D260.1448C%omaennel@net.t-labs.tu-berlin.de> <A99B171D26E1564B92D36826128CD66127E33BC71F@NOK-EUMSG-01.mgdnok.nokia.com>
In-Reply-To: <A99B171D26E1564B92D36826128CD66127E33BC71F@NOK-EUMSG-01.mgdnok.nokia.com>
Cc: shara@ietf.org
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: shara-bounces@ietf.org
Errors-To: shara-bounces@ietf.org

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.

I can offer cycles to work on this.

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

v2.8.7 | Report a Bug | By Email