From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: [PATCH 0/8]: Preparatory patches for feature negotiation
Date: Tue, 25 Sep 2007 14:23:50 +0000 [thread overview]
Message-ID: <200709251523.50165@strip-the-willow> (raw)
A small set of patches to prepare feature negotion, and one miscellaneous one.
I will start step by step, the patches will be put into the test tree after the
last batch has been set (although this time I made sure that patch sets also
compile separately).
Patch #1: Accounting, records an unused function.
Patch #2: Adds Data 1..3 fields to do more informative
processing of DCCP-Resets (RFC 4340, 5.6)
Patch #3: Removes duplicate code for generating Reset
from connected socket (now uses already prepared
route via dccp_transmit_skb).
Patch #4: Factors out common code for sending Resets from
control sockets. This includes processing the
Data 1..3 fields for Packet/Option/Mandatory Error.
Patch #5: Parsing options on request_socks, a prerequisite
for implementing feature-negotiation during
connection setup.
Patch #6: Integrates the code of Patch #5 with the processing
in dccp_check_req, so that options can be considered
by the server during the initial handshake (is a FIXME).
Patch #7: As the first option to be parseable on both request_socks
and connected socks, timestamp echo is made dynamic.
There are hooks/ideas there of turning this into a RFC1323-like
algorithm, which however requires some more work (to deal correctly
with delayed, lost, duplicate packets/timestamps).
Patch #8: Rounds off this request-sock patch set by adding support for
inserting options from request_socks as well (as opposed to sk's).
next reply other threads:[~2007-09-25 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 14:23 Gerrit Renker [this message]
2007-09-25 14:37 ` [PATCH 0/8]: Preparatory patches for feature negotiation Arnaldo Carvalho de Melo
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=200709251523.50165@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.