DCCP protocol discussions
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: [PATCH 0/5][BUG-fix]: Sync-Flood Fixes
Date: Wed, 20 Jun 2007 09:55:17 +0000	[thread overview]
Message-ID: <200706201055.17078@strip-the-willow> (raw)

Arnaldo asked me to send these, they have been made independent of the patches in the 
test tree (but will be made available for review).

Patch #1: Cosmetics, but required by other patches - shortens many occurrences of
          very long variable names.

Patch #2: Reset/Sync-Flood Bug fix. 
          The bug has been known for a long while (I recently found an email from Ian
          who mentioned it as early as December), a previous discussion with Eddie helped
          to track down where the bug originates. Patch has detailed description of how
          bug is triggered, and fixes the described symptom.

Patch #3: Renames parameter for clarity (was confusing).

Patch #4: Rate-Limit DCCP Syncs. This is recommended in RFC 4340 and from own experience
          I found that rate-limiting alone can terminate oscillating Sync message exchanges,
          i.e. it increases resilience against malfunction and attacks.
 
Patch #5: Second bug - in REQUEST state, a Reset is sent in response to Sync, not SyncAck.

                 reply	other threads:[~2007-06-20  9:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200706201055.17078@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox