All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH 0/6] sctp: implement IETF SCTP Stream Reconfiguration
Date: Tue, 10 Mar 2009 01:01:31 +0000	[thread overview]
Message-ID: <49B5BBEB.4030900@hp.com> (raw)
In-Reply-To: <49B48945.7060707@cn.fujitsu.com>

Wei Yongjun wrote:
> Hi All
> 
> The following series of 6 patches is the implementation of IETF STREAM-RESET
> draft (http://tools.ietf.org/html/draft-stewart-tsvwg-sctpstrrst-01).
> 
> With this series, we'll implement most of the draft's defines. We skip the
> "deferred reset processing" on receiver side procedures for the Outgoing SSN
> Reset Request Parameter. This may appear later as a patch.
> 
> I'd really appreciate people take a look and review this patches.
> 

Hi Wei

This is an interesting draft, and it's good to have an prototype implementation,
but I think there are some holes in the draft still.

I think the biggest hole is the API.  Since it's not documented at all, I would
be extremely hesitant of opening any of it.

I need to do a detailed review of this and I invite you to send any comments you
have to Randy and the rest of the authors.

I think that by missing the deferred reset processing, we are open to some interesting
problems.  The issue is that if the stream reset arrives prior to any pending TSNs, we
need to enter this deferred processing state.  This could be very easy to hit and it needs
to be done.  There are also some inconsistencies in the text for deferred processing.

This is really an RFC series, since I think the spec needs a lot of work before I can
take this for the main-line kernel.

-vlad


  reply	other threads:[~2009-03-10  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  3:13 [net-next-2.6 PATCH 0/6] sctp: implement IETF SCTP Stream Reconfiguration Wei Yongjun
2009-03-10  1:01 ` Vlad Yasevich [this message]
2009-03-10  1:33 ` Wei Yongjun

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=49B5BBEB.4030900@hp.com \
    --to=vladislav.yasevich@hp.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.