Re: [77attendees] Bar BOF: Impact of NAT444 on content providers

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 16 March 2010 22:13 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 6005A3A6829 for <77attendees@core3.amsl.com>; Tue, 16 Mar 2010 15:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level:
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599]
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 qUT1DfZnWjCV for <77attendees@core3.amsl.com>; Tue, 16 Mar 2010 15:13:34 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 86D8A3A6782 for <77attendees@ietf.org>; Tue, 16 Mar 2010 15:13:34 -0700 (PDT)
Received: by pwj6 with SMTP id 6so380070pwj.31 for <77attendees@ietf.org>; Tue, 16 Mar 2010 15:13:41 -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:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+RtsqtEXQQcL4snzlWPju1n5LphVXDm46uZu20yOdS0=; b=ZSoLUybUdmqfQ1mJdj4KClUHpJE8xY7ODaMVtulREB3LkNCwIx9jnRfHlCnvtaIJeY VWFQLKDipBBalzbmNsOy1IfHV57M0Cjyp1qWyzy/XB5NTRXl//vBYffXLE3OsvMFacgA +cPkQWKbDqSsB34BTtiMaa5++NzBy6XQxN8hs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=tjn4+X5evCmA3qmmcjyGlHRHK3vV72pgHhxstgSHP3RwpzHtlbJBKal/QTrHatLFac aiB/aSn+Uk9hQqezU1dcP/Ti/d/3Lwc0/fBtY2bZgY7ZSkaa2smsIA2b9dfNhJs5ZOAS g03H9W1TEDG62RiR22OvNypDkkAOCR2ZEezmg=
Received: by 10.115.84.40 with SMTP id m40mr26366wal.124.1268777617123; Tue, 16 Mar 2010 15:13:37 -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 20sm7405718pzk.7.2010.03.16.15.13.35 (version=SSLv3 cipher=RC4-MD5); Tue, 16 Mar 2010 15:13:36 -0700 (PDT)
Message-ID: <4BA0028A.9060506@gmail.com>
Date: Wed, 17 Mar 2010 11:13:30 +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: Matthew Ford <ford@isoc.org>
References: <4B9D70B7.2050001@gmail.com> <04c301cac48b$383e84c0$c4f0200a@cisco.com> <4B9F4E39.4000508@isoc.org>
In-Reply-To: <4B9F4E39.4000508@isoc.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: 77attendees@ietf.org
Subject: Re: [77attendees] Bar BOF: Impact of NAT444 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: Tue, 16 Mar 2010 22:13:35 -0000

On 2010-03-16 22:24, Matthew Ford wrote:
> On 15/03/2010 23:02, Dan Wing wrote:
>> A different layout of draft-ford-shared-addressing-issues might
>> go a long way towards addressing the desire for a citable
>> document on the negative affect of IPv4 address sharing to a
>> content provider.  Failing that, perhaps a separate draft; however
>> it seems difficult to describe any of these as solely or even
>> primarily impacting the content provider -- it is the collateral
>> damage caused by the negative reputation of the IPv4 identifier
>> that is the foundation of much of the woe (for the penalty boxes).
> 
> The latest rev of draft-ford-shared-addressing-issues includes an
> initial, basic assessment of whether issues identified pertain to either
> the party implementing the shared addressing solution, or to third
> parties, or both. That analysis could certainly be improved.
> 
> At present I plan to briefly present the updates to the draft in the
> intarea meeting in Anaheim, and to ask for interest in adoption as a WG
> work item. If there's energy and interest in working on improving the
> structure and content of this draft, that'd be a good place to bring it.

Sure. But what we are talking about in the bar BOF is a *specific* focus
on the issues (and surprises) affecting content providers. I am quite
sure that your draft will be a major reference for any resulting
document.

   Brian