| > DCCP mandates a `minimum implementation' = CCID2
| > ==> CCID2 mandates Ack Vectors
| > ==> Ack Vectors are not optional but mandatory
|
| Its useful for debugging, reducing the complexity by disabling this feature.
|
| It is possible to build a kernel without CCID2, and thu
On 7/27/07, Gerrit Renker <[EMAIL PROTECTED]> wrote:
> Quoting Ian McDonald:
> | > [DCCP]: Always support Ack Vectors
> | >
> | > This removes CONFIG_IP_DCCP_ACKVEC for reasons of inter-operability.
> | >
> | > In RFC 4340 requires CCID2 as a kind of default (section 10):
> | > "A DCCP implem
Quoting Ian McDonald:
| > [DCCP]: Always support Ack Vectors
| >
| > This removes CONFIG_IP_DCCP_ACKVEC for reasons of inter-operability.
| >
| > In RFC 4340 requires CCID2 as a kind of default (section 10):
| > "A DCCP implementation intended for general use, such as an implementation
| >
On 7/27/07, Gerrit Renker <[EMAIL PROTECTED]> wrote:
> [DCCP]: Always support Ack Vectors
>
> This removes CONFIG_IP_DCCP_ACKVEC for reasons of inter-operability.
>
> In RFC 4340 requires CCID2 as a kind of default (section 10):
> "A DCCP implementation intended for general use, such as an impleme
[DCCP]: Always support Ack Vectors
This removes CONFIG_IP_DCCP_ACKVEC for reasons of inter-operability.
In RFC 4340 requires CCID2 as a kind of default (section 10):
"A DCCP implementation intended for general use, such as an implementation
in a general-purpose operating system kernel, SHOULD
5 matches
Mail list logo
