Re: [p2pi] Fwd: For those who think "User Fairness/Cost Fairness" isunacceptable...

"Peterson, Jon" <jon.peterson@neustar.biz> Tue, 10 June 2008 01:22 UTC

Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2FB83A68C7; Mon, 9 Jun 2008 18:22:00 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7283F3A688D for <p2pi@core3.amsl.com>; Mon, 9 Jun 2008 18:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.28
X-Spam-Level:
X-Spam-Status: No, score=-2.28 tagged_above=-999 required=5 tests=[AWL=0.318, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 8uNYMd0soIpp for <p2pi@core3.amsl.com>; Mon, 9 Jun 2008 18:21:46 -0700 (PDT)
Received: from neustar.com (ns6.neustar.com [156.154.16.88]) by core3.amsl.com (Postfix) with ESMTP id 431033A67AD for <p2pi@ietf.org>; Mon, 9 Jun 2008 18:21:46 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; d=neustar.biz; s=neustarbiz; c=simple/simple; q=dns; t=1213060923; x=1213147323; h=From:Date:Subject:Message-ID:Content-class:Content-Type; b=VeAY34w6RbhJjHADkSdMU4N4qyWrKxkXtic9IgRo6ZcxKY2ip2YBtlclTgigzNZhceqlNwNkCtZn0R 2HvPZAoQ==
Received: from ([10.31.13.50]) by stihiron2.va.neustar.com with ESMTP id 5202732.8485957; Mon, 09 Jun 2008 21:21:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 09 Jun 2008 21:21:54 -0400
Message-ID: <C80ADC57CB3BB64B94A9954A816306C50C3268@STNTEXCH11.cis.neustar.com>
In-Reply-To: <484DCA46.7050405@bennett.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [p2pi] Fwd: For those who think "User Fairness/Cost Fairness" isunacceptable...
thread-index: AcjKkMPtFVBUKNXxTLCk7tMI6fl3+AABRehQ
References: <BBCA80CA-34E9-40B1-9B37-628F014F9108@ICSI.Berkeley.EDU> <3efc39a60806080822l575c83c1p2a370bbb20a41bd6@mail.gmail.com> <3efc39a60806080825yc1261ddmf2ce3da4b308a722@mail.gmail.com> <45AEC6EF95942140888406588E1A6602050F89D1@PACDCEXCMB04.cable.comcast.com> <3efc39a60806091639t3ff649a3i6421b1a334e458b7@mail.gmail.com><3efc39a60806091704t771b2e4ak8ef6c820abd15e80@mail.gmail.com> <484DCA46.7050405@bennett.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: Richard Bennett <richard@bennett.com>, Robb Topolski <robb@funchords.com>
Cc: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>, p2pi@ietf.org
Subject: Re: [p2pi] Fwd: For those who think "User Fairness/Cost Fairness" isunacceptable...
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0478096346=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

 

I'd like to second this.

 

We're certainly not here to pass judgment on Comcast or any other
network provider. What the IETF can do is engineer tools that may
improve the interaction between applications and the underlying network,
where previous assumptions about the relationship between those entities
have proven unreliable. The P2P case under examination here is such an
instance, and thus we have a few choices about what behaviors we might
tweak to alleviate the undesirable symptoms.

 

I'd like to keep the discussion here focused, to the degree that we can,
on what engineering deliverables we can identify and act upon. Is there
anything outside the proposed scope of TANA and ALTO that we've missed,
and that we should consider for IETF action? As a part of this ongoing
discussion, I personally find Comcast's updates on their planned trials
valuable, and I think the data that will result from those trials could
be very useful in refining the problem space as the IETF continues to
think through these problems. I would certainly be disappointed if our
prejudgment of those trials, or hostility to business models, ultimately
deprived us of that data.

 

The manner in which Comcast chooses to operate their network, and
collect revenues, is not something we can or should decide - nor should
this mailing list be a pillory where we revisit management practices
that no one here is going to advocate.

 

Jon Peterson

NeuStar, Inc.

 

________________________________

From: p2pi-bounces@ietf.org [mailto:p2pi-bounces@ietf.org] On Behalf Of
Richard Bennett
Sent: Monday, June 09, 2008 5:27 PM
To: Robb Topolski
Cc: p2pi@ietf.org; Livingood, Jason
Subject: Re: [p2pi] Fwd: For those who think "User Fairness/Cost
Fairness" isunacceptable...

 

This isn't a court of law, and it's not our mandate to determine who the
good guys (or good practices) are and who's being bad. It's certainly
not an established fact that an application-neutral per-user fairness
regime is "disruptive to the intended use of the Internet" or any such
thing; in fact, the evidence leads to quite a different conclusion.

Similarly, packet inspection (deep or shallow, if there is such a thing)
without retention for the purpose of prioritizing is quite a different
animal than packet inspection for the purpose of retaining personal
information  to be used for commercial or other purposes. 

Similarly, speculations about the viability of metered pricing are
probably not productive, given that it's already the norm on most
Internet access networks in the world. The Internet is, after all, a
global phenomenon and not simply a slice of American life.

I'd prefer to focus the energies of this group in a more productive
direction, namely to identify means of harmonizing the needs and
requirements of groups of users on shared network links, given that
"infinite bandwidth at no cost" is outside the solution space.

RB

Robb Topolski wrote: 

(Adding to my own message)

On Mon, Jun 9, 2008 at 4:39 PM, Robb Topolski <robb@funchords.com>
wrote:

 

On Mon, Jun 9, 2008 at 1:02 PM, Livingood, Jason
<Jason_Livingood@cable.comcast.com> wrote:

	 

	I was a bit thrown off by your RFC 1087 reference, "Ethics and
the Internet" from 1989.  Perhaps that RFC is somewhat geared towards a
non-commercial past, when as it says, the Internet is a "national
facility" used mostly by researchers. 

The reference is historical, relating to "Recent events involving the
hosts on the Internet and 

in similar network infrastructures underscore the need to reiterate the
professional responsibility every Internet user bears to colleagues ..."

 

		Can you advise your specific technical areas of concern,
as it relates to this RFC (see below)?


They are these acts, which Comcast's current RST method and proposed
"Protocol Agnostic" method violate.
 

      (b) disrupts the intended use of the Internet,

      (c) wastes resources (people, capacity, computer) through such
          actions,

      (d) destroys the integrity of computer-based information,

      (e) compromises the privacy of users.

 


All, please be clear that WRT to RFC 1087 I'm using it as an example and
expressing my criticisms at the methods being employed, not the persons
and companies themselves.  The effects of using Protocol discrimination
or Consumption discrimination are these four effects above.  

Comcast is here participating -- not here acting "unethically."
Unfortunately, the title of RFC 1087 is something like "Ethics and the
Internet."  Please do not interpret this fact as a criticism of Comcast
or its participation here.  Please do interpret my message as a
criticism of both the old and their new proposed method.

Thank you to the individual who sent me a corrective message in private.
It did look like a shot, and that wasn't what I was going for.


-- 
Robb Topolski (robb@funchords.com)
Hillsboro, Oregon USA
http://www.funchords.com/ 

 



________________________________



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





-- 
Richard Bennett
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi