LISTSERV mailing list manager LISTSERV 16.5

Help for P2P Archives


P2P Archives

P2P Archives


P2P@LISTSERV.UTK.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

P2P Home

P2P Home

P2P  March 2001

P2P March 2001

Subject:

Re: How much bandwidth is reasonable?

From:

Joe St Sauver <[log in to unmask]>

Reply-To:

Peer-to-Peer <[log in to unmask]>

Date:

Wed, 21 Mar 2001 16:43:44 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (138 lines)

>Date: Wed, 21 Mar 2001 14:49:13 -0500
>From: Jerry Sobieski <[log in to unmask]>
>Subject: Re: [P2P] How much bandwidth is reasonable?
>To: [log in to unmask]

Hi Jerry,

>I agree whole heartedly with the sentiment.  In fact, we had a rather spirited
>conversation at the Internet2 meeting over this topic.  And fundamentally it
>came down to the cost of provisioning the the campus connection(s) to the "rest"
>of the Internet.

Yep, commodity Internet connectivity is key (and has been basically ignored).

Envision Chris Rock (the great comedian, who does that deadpan delivery of
bites from the reality sandwich of life):

   "If you're going to go fast to Internet2, you're going to have to
    go fast EVERYWHERE. You CAN'T just go fast to Internet2."

Tried to make this point at the Minnesota Joint Techs (see:
http://www.ncne.nlanr.net/news/workshop/2000/000515/Talks/sauver-jt05152000/ ).

Tried to make this point at the UCSD Meeting on Campus Focused Networks
(see: http://darkwing.uoregon.edu/~joe/how-to-go-fast.ppt ).

Tried to make this point during discussions of a possible role for the
proposed I2 Scavenger Service (see, for example:
http://archives.internet2.edu/guest/archives/i2ss-dt/log0102/msg00003.html ).

Tried to make this point during the peer to peer discussion at the recent
members meeting in DC (you can see my brief summary at:
http://darkwing.uoregon.edu/~joe/peer2peeronepager.pdf )

and so on, and so on, ad infinitum. I'm a broken record, what can I say. :-)

Because users do NOT know when they are using I2 or some other sort of
connectivity, you can't just provision a big pipe to I2, and a small or
medium sized pipe to the commodity Internet and expect it to work.

And why can't university's deploy large (OC3 class) commodity transit pipes?
Because they're expensive... So if buying commodity transit won't scale,
what will? Settlement free exchange-point based peering solutions.
Unless you're fortunate enough to be able to buy give-it-away-priced
commodity connectivity from one of the Cogent Communications or Yipes
of the world, Universities really need to be moving toward a settlement
free peering-based solutions... and many of them are.

The question then really becomes, "Is this anything that Internet2 can
help facilitate for the rest of 'em, assuming it wanted to do so?" and
clearly the answer is yes...

>So, in order to solve this problem, we need to recognize that Internet access is
>not free.

And yet, of course, Internet access has many characteristics that make people
behave as if it is costless.

Users get no report telling them how much they've used (unlike filling up
the gas tank, where the pump tells you how much you're using, as you
pump the gas).

Charges (if any) aren't usage sensitive -- this isn't like having dim sum
or sushi at places where you pay per plate, and you better stop when the
plates start piling up high. The current Internet model is more like Bob's
"Eat All You Want" Smorgasbord.

For many sites (and particularly for Internet2 connectivity),
overprovisioning means that usage has no direct incremental cost until
capacity reaches a step boundary (OC3 to OC12, say).

etc., etc., etc.

And who can blame users? Users think of network access the same way they
think of the campus library. They don't get charged to check out a book or
look at a journal, right? Of course, there are still costs associated with
offering campus a library (or network connectivity), those charges just
aren't usage sensitive (with rare exceptions).

>And as long as campuses provide free access, they are in fact
>subsidizing this sort of activity.  Maybe that is a good thing, or at least is
>consistent with the philosophical search for knowledge we espouse.

My experience has been that most campuses do NOT provide free access, they
just don't employ usage sensitive pricing. For example, students pay
educational technology fees, departments may pay per-port installation fees,
etc. We just don't have per-port (or per-IP or per-MAC address) usage
monitoring and usage-senstive charge back.

>What would happen when the Web100 project gets really moving and starts
>automatically tuning TCP stacks for high speed links?  UltraFTP...even
>legitimate users will be able to oversubscribe the link:-)

Conventionally deployed systems can do it today, using uncopywritten content,
and using already-well-known protocols (such as regular FTP). Web100's key
contribution will be in facilitating near-100Mbps *single* flows. If you
assume multiple flows, you can already get there today. :-)

>I agree with Rene.  We really need to put at least part of our efforts to
>exploring ways to make bandwidth a non-issue.

Commodity internet settlement-free peering based solutions could do that for
you....

If you aren't building out a local exchange point (or peering at an
established exchange point), you're headed down the wrong road. And of
course, the only way major carriers will be willing to peer with you is
if you either individually have "a lot" of traffic for them, or if you
collectively are part of some aggregate that has "a lot" of traffic for
them. So anytime people choke back the traffic they're seeing their users
produce, they are (perversely) reducing their attractiveness as a
potential peering partner, not increasing it.

>Perhaps, such [illegitimate] over use of best effort networks will push campuses
>to explore and more agressively deploy advanced technologies to manage these
>resources such as usage based charging, QoS/CoS, line rate policy routing, etc.

I'm QoS skeptical. Edge policing issues, billing issues, and a host of
other practical problems makes deploying premium service awfully hard,
particularly on the commodity internet. And, of course, QoS/Cos can't
manufacture additional bandwidth; etc.

If the goal is to offer less-than-best effort services, there are
issues there, too, I think (largely associated with incenting people
to use that less-than-best effort service; see the discussion at:
http://archives.internet2.edu/guest/archives/i2ss-dt/log0102/msg00019.html)

I'm also of the belief that billing is a huge pain with only marginal
returns for most users (that's why we don't track and charge back water
usage at most campuses);

The only thing that does scale is to deploy settlement-free peering based
commodity connectivity.

Regards,

Joe

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
May 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
September 2018
August 2018
June 2018
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
July 2015
June 2015
April 2015
March 2015
February 2015
January 2015
September 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
January 2013
December 2012
November 2012
September 2012
August 2012
June 2012
May 2012
March 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
April 2009
January 2009
July 2008
October 2007
July 2007
June 2007
May 2007
February 2007
October 2006
July 2006
June 2006
March 2006
January 2006
September 2005
June 2005
April 2005
March 2005
February 2005
November 2004
October 2004
September 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000

ATOM RSS1 RSS2



LISTSERV.UTK.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager