CoDel AQM discussions
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Tristan Seligmann <mithrandi@mithrandi.net>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
	bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Cerowrt-devel] [Bloat]  Latest codel, fq_codel, and pie sim study from cablelabs now available
Date: Tue, 11 Jun 2013 14:19:15 -0400	[thread overview]
Message-ID: <22354.1370974755@sandelman.ca> (raw)
In-Reply-To: <CAMcKhMSFu8WCnj9dQ7=mVTAKssde73NuxH2zOTwXO9+5RnP=Og@mail.gmail.com>


>>>>> "Tristan" == Tristan Seligmann <mithrandi@mithrandi.net> writes:
    >> It's pretty easy to configure the Transmission Bittorrent client to mark
    >> packets.
    >> 

    Tristan> Unfortunately this only helps with outgoing traffic. Marking on inbound
    Tristan> traffic is at the mercy of the torrent peer and your ISP (in my case, my
    Tristan> ISP seems to overwrite the TOS/DS field indiscriminately,
    Tristan> not that you

Ultimately, one wants PCP and/or RSVP and/or NSIS from the torrent
client to the local router, as the torrent client knows the 5-tuple of
the incoming packets.  Local router would in utopian world, in a diffedge
scenario be able to communicate that policy to ISP edge router, but at
least, the local router can police that flow.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	

  parent reply	other threads:[~2013-06-11 18:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 11:23 [Codel] " Dave Taht
2013-05-01 20:26 ` [Codel] [Bloat] " Simon Barber
2013-05-02  0:00   ` Jonathan Morton
2013-05-02  2:20     ` Simon Barber
2013-05-02  4:59       ` Andrew McGregor
2013-05-02 12:04       ` Jonathan Morton
2013-05-02 13:29         ` Simon Perreault
2013-05-14  2:26         ` Dan Siemon
2013-05-14  4:56           ` Tristan Seligmann
2013-05-14 10:24             ` Dave Taht
2013-05-14 13:02               ` Eric Dumazet
2013-06-11 18:19             ` Michael Richardson [this message]
2013-05-14 12:12           ` Jesper Dangaard Brouer
2013-05-06 17:54       ` Jesper Dangaard Brouer
2013-05-06 18:46         ` Jonathan Morton
2013-05-06 20:47           ` Jesper Dangaard Brouer
2013-05-07 16:22             ` Greg White
2013-05-07 13:31       ` [Codel] [Cerowrt-devel] " Michael Richardson
2013-05-07 16:30         ` [Codel] [Bloat] [Cerowrt-devel] " Greg White
2013-05-07 19:56           ` [Codel] [Bloat] " Wes Felter
2013-05-07 20:30             ` Eric Dumazet
2013-05-08 22:25               ` Dave Taht
2013-05-08 22:54                 ` Eric Dumazet
2013-05-09  1:45                   ` Andrew McGregor

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/codel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=22354.1370974755@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=mithrandi@mithrandi.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