Re: [v4v6interim] Can we squeeze a tiny topic in the agenda?

Mark Townsley <townsley@cisco.com> Mon, 29 September 2008 12:09 UTC

Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B4DD3A6881; Mon, 29 Sep 2008 05:09:25 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95BE23A6881 for <v4v6interim@core3.amsl.com>; Mon, 29 Sep 2008 05:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level:
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 cTJB1A+avmH1 for <v4v6interim@core3.amsl.com>; Mon, 29 Sep 2008 05:09:23 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 3C10A3A67E6 for <v4v6interim@ietf.org>; Mon, 29 Sep 2008 05:09:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,331,1220227200"; d="scan'208";a="21106505"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 29 Sep 2008 12:09:38 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m8TC9cKf007629; Mon, 29 Sep 2008 14:09:38 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8TC9cSI022067; Mon, 29 Sep 2008 12:09:38 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Sep 2008 14:09:38 +0200
Received: from Townsley-MacBook.local ([10.61.83.194]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Sep 2008 14:09:37 +0200
Message-ID: <48E0C53B.6040409@cisco.com>
Date: Mon, 29 Sep 2008 14:08:27 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Andrei Robachevsky <andrei@ripe.net>
References: <48E086C5.7040004@ripe.net>
In-Reply-To: <48E086C5.7040004@ripe.net>
X-OriginalArrivalTime: 29 Sep 2008 12:09:38.0066 (UTC) FILETIME=[3E957F20:01C9222C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2112; t=1222690178; x=1223554178; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=townsley@cisco.com; z=From:=20Mark=20Townsley=20<townsley@cisco.com> |Subject:=20Re=3A=20[v4v6interim]=20Can=20we=20squeeze=20a= 20tiny=20topic=20in=20the=20agenda? |Sender:=20; bh=gukbDlWxvfNJqbjSG2pkVyUzesL9LDE7jxYO1fqN1IM=; b=PKbTv0dydY/fdEt1Hf2ZvAHjI8tRT7nRItypi9TrcK36BZNtTYTvBQgs3s xQ1MjdH5kDmYVBU07U2P+JOdsJXQMrKCUZQCM1YCFCXiyIm3zu3t9oeBSdhy /XmszXSJvc;
Authentication-Results: ams-dkim-2; header.From=townsley@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Can we squeeze a tiny topic in the agenda?
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


Coming from RIPE, I'd like to know if you have seen this draft, and what 
you think of the idea.

http://www.ietf.org/internet-drafts/draft-shirasaki-isp-shared-addr-00.txt

This draft plainly argues against using 240/4 (on the basis that it is 
already too "polluted" in IP stacks today), and instead asks IANA to set 
aside some new space for SPs to "share" within NAT zones or walled gardens.

But aside of whether 240/4 is used or not, I'd like to know if the 
community believes we need to define some IPv4 "SP Private" space 
(presumably to sit between two NATs, or to communicate to devices within 
an SP walled-garden). If we as a community decide that this kind of SP 
space is needed, we are effectively defining a new scope that is 
different from RFC1918 scope and global scope. As such, our evaluation 
criteria for how 240/4 could be used changes by default - as we have a 
new type of scope to consider.

I don't think this is a tiny topic, but it is one that could become an 
elephant in the room if we don't put it on the table and discuss it a 
bit. I think it at least falls under the "SP's running out of RFC1918 
space" problem space scenario, and how to deploy NAT444 CGNs in the 
solution space.

Thanks,

- Mark

Andrei Robachevsky wrote:
> Colleagues,
>
> I know the agenda is already very full, but I wonder if we could squeeze
> a small topic.
>
> Coming from the RIR side I'd like to bring up an issue of usability of
> the former class E space (240/4). I know many are sceptical about this,
> but I am not aware of any more or less comprehensive usability tests.
> I'd like to discuss the feasibility of such experiment.
>
> I think this is relevant to this meeting, because if usable this space
> could be a very good candidate for some of the translation proposals
> being discussed here.
>
> It's only a few slides.
>
> Thanks,
>
> Andrei Robachevsky
> RIPE NCC
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>
>   

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