[PATCH 0/5] CCID 4: initial implementation of CCID 4

[PATCH 0/5] CCID 4: initial implementation of CCID 4

[Tommi Saviranta]

Re-submitting, with hopefully proper tags etc.


After discussing the topic on IRC, we figured we need a place to have
the sources for CCID 4 available for everyone. This way we can finally
start cooperating on it.

I have created a few patches against dccp-exp. Even if they're not much,
or pretty, they may be something to start with.

The sources are based on ~a week old copy of CCID 3 from dccp-exp,
created with
	http://wnd.katei.fi/dccp/files/copy-ccid3-to-ccid4.sh


Patch #1: Adds DCCPC_CCID4 to include/linux/dccp.h, and initial entries
	about CCID 4 to net/dccp/ccids/{Kconfig,Makefile}.

Patch #2: Clones ~a week old implementation of CCID 3 into ccid4.[ch].

Patch #3: Implements TFRC-SP's 10 ms minimum sending rate (without
	possibility to decrese inter-packet interval below 10 ms, but
	still sending at most three packets every 30 ms).

Patch #4: Reduces allowed sending rate by a factor that accounts for
	packet header size.

Patch #5: Uses nominal segment size of 1460 bytes in TCP throughput
	equation.

Re: [PATCH 0/5] CCID 4: initial implementation of CCID 4

[Gerrit Renker]

|  Re-submitting, with hopefully proper tags etc.
|  
|  
|  After discussing the topic on IRC, we figured we need a place to have
|  the sources for CCID 4 available for everyone. This way we can finally
|  start cooperating on it.
|  
The patches applied fine, a new subtree `ccid4' has been created to host these.
The subtree can be checked out by

	1) create a subtree

		git-checkout -b ccid4 master

	2) pull the CCID4 subtree 

		pull  eden-feed:/usr/src/GIT/dccp_exp.git ccid4


This tree now sits on top of the test tree, i.e. inherits it. As said, I am ok
tracking changes required to ensure that patches remain applicable. 

What I can't do is to track updates to CCID3 into your code, since that would mean
altering your patches; so it is something you need to keep track of yourselves.

Gerrit

Re: [PATCH 0/5] CCID 4: initial implementation of CCID 4

[@ 2007-09-20 13:08 UTC (permalink / raw)]

2007/9/20, Gerrit Renker <gerrit@erg.abdn.ac.uk>:
> |  Re-submitting, with hopefully proper tags etc.
> |
> |
> |  After discussing the topic on IRC, we figured we need a place to have
> |  the sources for CCID 4 available for everyone. This way we can finally
> |  start cooperating on it.
> |
> The patches applied fine, a new subtree `ccid4' has been created to host these.
> The subtree can be checked out by
>
>         1) create a subtree
>
>                 git-checkout -b ccid4 master
>
>         2) pull the CCID4 subtree
>
>                 pull  eden-feed:/usr/src/GIT/dccp_exp.git ccid4
>
>
> This tree now sits on top of the test tree, i.e. inherits it. As said, I am ok
> tracking changes required to ensure that patches remain applicable.
>
> What I can't do is to track updates to CCID3 into your code, since that would mean
> altering your patches; so it is something you need to keep track of yourselves.
>
> Gerrit
> -
> To unsubscribe from this list: send the line "unsubscribe dccp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

I think that update ccid4 according to ccid-3 will not be a problem.

Leandro Melo de Sales.
Pervasive and Embedded Computing Laboratory
BRisa and E-Phone Projects Manager & Network Administrator
http://embedded.ufcg.edu.br/
+55 083 3310-1404 (extension 208)

"There are 10 types of people in this world: those who understand
binary, those who don't"