All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Heiss <kheiss@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: HB.Max.Burst
Date: Thu, 20 Mar 2014 13:31:53 +0000	[thread overview]
Message-ID: <CAGugRbWm5=S_6Sf2YQ1=0=AYx40yBTt8+cYcL_3UcDpd8O1rNg@mail.gmail.com> (raw)

I have a question about the HB.Max.Burst parameter for the LKSCTP
stack.  I notice that there is no explicit parameter for this value
and the alternative from RFC 5062 (only one HB per RTT) does not
appear to be implemented either (see excerpt below).  The only
limiting factor appears to be max.burst.  Am I missing something
obvious or should there be some other form of limiting heartbeats to
mitigate some of the issues outlined in RFC 5062?

6.3.  Mitigation Option

   To limit the effectiveness of this attack, the new parameter
   HB.Max.Burst was introduced in [RFC4960] and an endpoint should:

   1) not allow very large cookie lifetimes, even if they are requested.

   2) not use larger HB.Max.Burst parameter values than recommended.
      Note that an endpoint may decide to send only one Heartbeat per
      RTT instead of the maximum (i.e., HB.Max.Burst).  An endpoint that
      chooses this approach will however slow down detection of
      endpoints camping on valid addresses.

   3) not use large HEARTBEATs for path confirmation.


Karl

             reply	other threads:[~2014-03-20 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 13:31 Karl Heiss [this message]
2014-03-20 14:54 ` HB.Max.Burst Karl Heiss
2014-03-20 19:55 ` HB.Max.Burst Vlad Yasevich
2014-03-21 12:11 ` HB.Max.Burst Karl Heiss
2014-03-21 13:52 ` HB.Max.Burst Vlad Yasevich

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='CAGugRbWm5=S_6Sf2YQ1=0=AYx40yBTt8+cYcL_3UcDpd8O1rNg@mail.gmail.com' \
    --to=kheiss@gmail.com \
    --cc=linux-sctp@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.