Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-zero-checksum-01.txt

[Michael Tuexen <[e-mail]>]

> On 14. Jul 2023, at 07:37, Claudio Porfiri <claudio.porfiri=[e-mail]> wrote:
> 
> Hi Michael,
> I am fine with the adoption, I only have a comment on the procedural part that may be ambiguous so that I'd wish to suggest clarification.
> In section 3 it's specified that the Zero Checksum parameter may appear in INIT and INIT ACK so I assume that it can also be the Server side asking the Client for Zero Checksum by including the parameter in INIT ACK. Is this case the Client cannot confirm that it has accepted Zero checksum.
> It should be stated that it's always the Client asking for Zero Checksum and the Server MUST answer in INIT ACK.
Hi Claudio,

the intention is they each side declares whether it is willing to accept packets
with incorrect zero checksums. It is not a negotiation.
See for example the test case
https://github.com/sctplab/zero-checksum/blob/main/zero-checksum-tests/sctp-zero-checksum-07.pkt
where the client does not announce that it is willing to accept packets with zero
checksums, but the server does.
Please note that I have not updated the code to revision 01, but that is not relevant
for the point we are discussing.

Best regards
Michael
> 
> Best regards,
> Claudio.
> 
> -----Original Message-----
> From: tsvwg <[e-mail]> On Behalf Of [e-mail]
> Sent: Tuesday, 11 July 2023 01:25
> To: [e-mail]
> Cc: [e-mail]
> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-zero-checksum-01.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the Transport Area Working
> Group (TSVWG) WG of the IETF.
> 
>   Title           : Zero Checksum for the Stream Control Transmission Protocol
>   Authors         : Michael Tüxen
>                     Victor Boivie
>                     Florent Castelli
>                     Randell Jesup
>   Filename        : draft-ietf-tsvwg-sctp-zero-checksum-01.txt
>   Pages           : 10
>   Date            : 2023-07-10
> 
> Abstract:
>   The Stream Control Transmission Protocol (SCTP) uses a 32-bit
>   checksum in the common header of each packet to provide some level of
>   data integrity.  When an alternate method used by SCTP provides
>   already the same or a higher level of data integrity, computing this
>   checksum does not provide any additional protection, but does require
>   computing resources.  This document provides a simple extension to
>   SCTP allowing to save these computing resources by using the constant
>   0 as a checksum in a backwards compatible way.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-zero-checksum/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-tsvwg-sctp-zero-checksum-01.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-sctp-zero-checksum-01
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>