On 9/26/07, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote:
> [DCCP]: Factor out common code for generating Resets
>
> This factors code common to dccp_v{4,6}_ctl_send_reset into a separate function,
> and adds support for filling in the Data 1 ... Data 3 fields from RFC 4340, 5.6.
>
> It is useful to have this separate, since the following Reset codes will always
> be generated from the control socket rather than via dccp_send_reset:
> * Code 3, "No Connection", cf. 8.3.1;
> * Code 4, "Packet Error" (identification for Data 1 added);
> * Code 5, "Option Error" (identification for Data 1..3 added, will be used later);
> * Code 6, "Mandatory Error" (same as Option Error);
> * Code 7, "Connection Refused" (what on Earth is the difference to "No Connection"?);
> * Code 8, "Bad Service Code";
> * Code 9, "Too Busy";
> * Code 10, "Bad Init Cookie" (not used).
>
> Code 0 is not recommended by the RFC, the following codes would be used in
> dccp_send_reset() instead, since they all relate to an established DCCP connection:
> * Code 1, "Closed";
> * Code 2, "Aborted";
> * Code 11, "Aggression Penalty" (12.3).
>
> Signed-off-by: Gerrit Renker <gerrit@xxxxxxxxxxxxxx>
Acked-by: Ian McDonald <ian.mcdonald@xxxxxxxxxxx>
--
Web1: http://wand.net.nz/~iam4/
Web2: http://www.jandi.co.nz
Blog: http://iansblog.jandi.co.nz
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
