From: Vlad Yasevich <vyasevich@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: SCTP Quick failover status
Date: Tue, 22 Jul 2014 16:24:11 +0000 [thread overview]
Message-ID: <53CE902B.5030208@gmail.com> (raw)
On 07/22/2014 10:55 AM, Karen E. Egede Nielsen wrote:
> Hi Vlad,
>
> Would it possibly be feasible for you to provide feedback on as to
> whether:
>
> * Linux SCTP supports the most recent version of the SCTP PF draft,
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover/, ?
It appears that Linux partially supports the latest draft. Some of
the newer language in section 4.1 is not supported. The API doesn't
appear to be supported either.
We'll work on adding this functionality.
>
> * The Linux SCTP implementers group have any comments to the draft in
> question ?
>
I do not. I've cc'd the implementers mailing list to see if anyone else
has any comments.
Thanks
-vlad
> The draft is proposed for publication as Proposed Standard[*] by tsvwg.
> The check up towards potential comments from Linux SCTP
> was a request made by the chairs at the tsvwg at IETF90.
>
> Many thanks in advance !
>
> BR, Karen
>
> [* Even if present version says Experimental]
>
> PS. As you can see Michael kindly provided you as a good reference.. :-)
>
>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: 22. juli 2014 15:52
>> To: Karen E. Egede Nielsen
>> Cc: Vlad Yasevich
>> Subject: SCTP Quick failover status
>>
>> Hi Karen,
>>
>> Vlad, who is the Linux SCTP kernel maintainer, might be able to comment
> on
>> the status of the Linux implementation if quick failover and if there
> were any
>> comments related to the ID.
>>
>> Best regards
>> Michael
next reply other threads:[~2014-07-22 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 16:24 Vlad Yasevich [this message]
2014-07-23 11:19 ` SCTP Quick failover status Neil Horman
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=53CE902B.5030208@gmail.com \
--to=vyasevich@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.