All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: TFRC Faster Restart implementation for Linux DCCP
Date: Mon, 16 Jul 2007 12:04:08 +0000	[thread overview]
Message-ID: <200707161304.09079@strip-the-willow> (raw)
In-Reply-To: <5640c7e00707152131k689ff53dn105ed1c0f3b90717@mail.gmail.com>

You didn't write whether you intend this as Linux mainline work.

I am not aware of anyone else working on this so far. However, it reopens a big can
of worms for the CCID3 code in the kernel: much in Faster Restart depends on the 
rfc3448bis changes to computing the sending rate and determining idle/application-limited
times. 
The algorithm keeps changing in each new revision of the rfc3448bis draft, which probably
means that when you've just finished your work, you can start from scratch again.

Thus my suggestion is - if you want to do this community-wise - to do this as part/sub-branch
of the testing tree. There is still a lot of space for further branches, and it is not clear
when all this will stabilise.

Thoughts?

Quoting Ian McDonald:
|  Folks,
|  
|  At the suggestion of my PhD supervisor, I am considering implementing
|  TFRC faster restart for the Linux version of DCCP.
|  
|  From my reading of the correspondence it would seem to me that the
|  testing was done in ns2 and not in the Linux kernel. If this is not
|  correct, or you know of any implementations, can you tell me so I
|  don't reinvent the wheel!
|  
|  Thanks,
|  
|  Ian

  parent reply	other threads:[~2007-07-16 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16  4:31 TFRC Faster Restart implementation for Linux DCCP Ian McDonald
2007-07-16  7:51 ` [dccp] " Arjuna Sathiaseelan
2007-07-16 12:04 ` Gerrit Renker [this message]
2007-07-17  4:25 ` Ian McDonald
2007-07-17 14:38 ` Gerrit Renker
2007-07-25  9:10 ` Ian McDonald
2007-07-26  8:32 ` Gerrit Renker
2007-07-26  9:42 ` Ian McDonald
2007-07-26 10:02 ` Gerrit Renker

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

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

  git send-email \
    --in-reply-to=200707161304.09079@strip-the-willow \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=dccp@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.