[77attendees] Bar BOF: Impact of NAT444 (etc) on content providers

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 17 March 2010 20:03 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: 77attendees@core3.amsl.com
Delivered-To: 77attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9FE328C0F1 for <77attendees@core3.amsl.com>; Wed, 17 Mar 2010 13:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.024
X-Spam-Level:
X-Spam-Status: No, score=-2.024 tagged_above=-999 required=5 tests=[AWL=-0.555, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 T2esjeeOM9ch for <77attendees@core3.amsl.com>; Wed, 17 Mar 2010 13:03:19 -0700 (PDT)
Received: from mail-px0-f183.google.com (mail-px0-f183.google.com [209.85.216.183]) by core3.amsl.com (Postfix) with ESMTP id 4B62128C0F8 for <77attendees@ietf.org>; Wed, 17 Mar 2010 13:03:19 -0700 (PDT)
Received: by pxi13 with SMTP id 13so1170023pxi.17 for <77attendees@ietf.org>; Wed, 17 Mar 2010 13:03:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=/Fuqp2qDH5dQIbNXU+XIdTx36Tb1BJiQXQJ/Wa2YGuQ=; b=Ac/7gHqHkE9AAb5km1cdzbQksF0gpWNOI1F/yA14lC6OMNdlJQV6JiYIySXiMdfP1z FM0yB9YGuaYXvPDyO5QbVYfbeOPaW1fIhxNQGBFCyW3nHAi9cqJfnpSdM1ZO0DpZBOEu I/g9zJzGbjdIm28x1rTojQWnIJlknMbRK8ykI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; b=oXZEN3/8BUbllFG5a5/BZns4nFMn0jwyLcP5my0lhnxTJrX9lL6IBVaamVK4EUb8WI zhcvsw3mJ5M4UIgB3IjbTnWpNc70wHvCr6/kLqLrFbm7l26PVND6Ko68Hy1MxB/dp7yF Skm6n0QKBhVsXUyQX/4S5DDC4lRPxoG/onsHg=
Received: by 10.114.186.36 with SMTP id j36mr435572waf.193.1268856207131; Wed, 17 Mar 2010 13:03:27 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 22sm2800054pzk.5.2010.03.17.13.03.25 (version=SSLv3 cipher=RC4-MD5); Wed, 17 Mar 2010 13:03:26 -0700 (PDT)
Message-ID: <4BA1358C.9060309@gmail.com>
Date: Thu, 18 Mar 2010 09:03:24 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 77attendees@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: [77attendees] Bar BOF: Impact of NAT444 (etc) on content providers
X-BeenThere: 77attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <77attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/77attendees>, <mailto:77attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/77attendees>
List-Post: <mailto:77attendees@ietf.org>
List-Help: <mailto:77attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/77attendees>, <mailto:77attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Mar 2010 20:03:20 -0000

Bar BOF: Impact of NAT444 (and IPv4 exhaustion in general) on content providers

Day:  Tuesday March 23
Time: 17:30
Room: Pacific B

Inspired by some remarks of Lorenzo Colitti (Google) at the recent
APRICOT/APNIC meeting in Kuala Lumpur, we plan to discuss the value
of a short draft aimed *specifically* at content providers, to describe
the impact on them and their customers if many of those customers are
trapped behind double IPv4 NAT (NAT444). Most likely, the scope
will include other IPv4 exhaustion effects on content providers too.

Clearly the issues are not news, but they tend to be described in complex
general drafts, or mixed in with proposed solutions or alternatives to double NAT.

Quoting Lorenzo: "...it would be
good to put together an IETF draft that very concisely lists the problems of
NAT444 from the content provider perspective. For example: worse geolocation
for targeted advertising and streaming content restrictions; higher latency;
IP blocking for abuse/spam causing collateral damage, etc."

(Also see http://www.isoc.org/educpillar/resources/docs/ipv6_200905.pdf)

The bar BOF agenda is to decide whether to proceed with such a draft and
if so, to identify the people who will write it and the target date.

Highly relevant existing documents include:

 draft-ford-shared-addressing-issues-02.txt
 draft-azinger-additional-private-ipv4-space-issues-03.txt

Drafts that touch on the topic in one way or another include:

 draft-nishitani-cgn-04.txt
 draft-shirasaki-nat444-01.txt
 draft-shirasaki-nat444-isp-shared-addr-03.txt
 draft-shirasaki-isp-shared-addr-04.txt
 draft-davies-reusable-ipv4-address-block-00.txt
 draft-boucadair-port-range-02.txt
 draft-ymbk-aplusp-05.txt
 draft-thaler-port-restricted-ip-issues-00.txt

Someone asked: "Other than reviewing the messages on this thread AND the list of
documents you posted earlier, is there any other recommended homework that I
should consider?"

Suggestions welcome, but that's all I've got.

     Brian Carpenter
     (whose only commitment is to make the bar BOF happen)