From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: [PATCH 0/10]: Support for passive close
Date: Thu, 12 Jul 2007 14:20:48 +0000 [thread overview]
Message-ID: <200707121520.48349@strip-the-willow> (raw)
I am sending the last two batches in my current patch set; both
are concerned with ensuring correct behaviour on closing a DCCP
connection. This requires the use of intermediate states, details
are described on
http://www.erg.abdn.ac.uk/users/gerrit/dccp/notes/closing_states/
Patch #1: Separates the list of DCCP protocol states into connection-oriented generic
states and DCCP-specific states.
Patch #2: Makes PARTOPEN autonomous (addressing a FIXME in the list of states).
Patch #3: Introduces the two dedicated intermediate/auxiliary states
PASSIVE_1 and PASSIVE_2, which are the basis of the entire patch set (cf. url).
Patch #4: Implements the basic state transitions featuring PASSIVE_1/2.
Patch #5: DCCP does not support half-close (RFC 4340), thus this patch performs SHUT_WR in
addition to SHUT_RD (as done previously).
Patch #6: Is analogous to patch #5: since DCCP does not support half-close, the state
DCCPF_CLOSING is removed in the opening statement of dccp_sendmsg().
Patch #7: Shifts the retransmit timer for active-close into output.c and uses the RFC 4340
fallback RTT value to set the timeout.
Patch #8: Realises the maximum-RTO backoff from the DCCP specification.
Patch #9: Implements support for Server holding TIMEWAIT state as per RFC 4340, 8.3.
Patch #10: Collapses 4 repeated statements of the same kind into one.
I will send the other part, which concerns aborting a connection, tomorrow.
next reply other threads:[~2007-07-12 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 14:20 Gerrit Renker [this message]
2007-07-17 4:16 ` [PATCH 0/10]: Support for passive close Ian McDonald
2007-07-17 15:43 ` Gerrit Renker
2007-09-06 4:02 ` Ian McDonald
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=200707121520.48349@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.