General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: bloat <bloat@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd:  [Internet Policy] Back to the root justification...
Date: Sat, 07 Jun 2014 10:48:32 -0400	[thread overview]
Message-ID: <53932640.7010504@rogers.com> (raw)
In-Reply-To: <1402138375-ace6f65271058161063ac1bd71e214a9@hill-a.ch>

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

For people interested, there is a discussion of the roots of the
"network neutrality" concept at internetpolicy@elists.isoc.org

Some of it seems, to my eyes, to be uninformed by the community that
works in the AQM space, so I see perfectly serious quotes like
>
>     Longer packets might be dropped in favor of shorter ones. Packets
>     in a
>     burst might be dropped in favor of ones that are spaced out.
>
>     This gets back to the point of neutrality - which describes some
>     level
>     of "equivalence", but there's never just one version of
>     equivalence that
>     everyone will accept.
>
>     If you want to preserve the Internet architecture, you need to
>     make sure
>     that:
>
>     Packets shall not be discriminated except on their inherent
>     properties (size, time of arrival) or explicit user-inserted
>     label (e.g., a QoS tag).
>
>     If you want to make sure that packets are "fairly dropped",
>     there's no
>     single such thing; one link might be bandwidth limited (so drop
>     proportional to length is fair), and the next might be header
>     processing
>     limited (so per-packet drop is fair); for a given path, there's no
>     single mechanism that satisfies the variety of fairnesses that
>     could be
>     required. 
>
If anyone's also interested in Network Neutrality and its roots, please
feel free to hop over and contribute some informed opinions (;-))

--dave





-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


[-- Attachment #2: Type: text/html, Size: 2573 bytes --]

           reply	other threads:[~2014-06-07 14:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1402138375-ace6f65271058161063ac1bd71e214a9@hill-a.ch>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53932640.7010504@rogers.com \
    --to=davec-b@rogers.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox