Indeed, RFC4960 has been already supported. I was misled. Another question: I am making a suite of SCTP testing tools. The paragraph 5.2.4.1 of RFC 4960 describes an example of an association restart. But I don't know how to trig or simulate a procedure of endpoints' restart. I find there are only functions to handle restart initiated by peer, but I've not found functions to initiate restart from local. Does lksctp lib have APIs or functions to initiate a restart? Or some of code fractions in kernel can do so? Handling restart initiated by peer: sctp_do_sm => sctp_sf_do_5_2_4_dupcook => sctp_sf_do_dupcook_a // Section 5.2.4, case 'A' Thanks && Best regards, Richard -----Original Message----- From: linux-sctp-owner@xxxxxxxxxxxxxxx [mailto:linux-sctp-owner@xxxxxxxxxxxxxxx] On Behalf Of Marcelo Ricardo Leitner Sent: 2015年11月6日 22:26 To: lemonskin Cc: linux-sctp@xxxxxxxxxxxxxxx Subject: Re: When will Linux implement SCTP protocol conforming to RFC4960? Hi, On Fri, Nov 06, 2015 at 08:51:20PM +0800, lemonskin wrote: > Dear experts, > > From comments of Linux source code v4.2.3, I find the SCTP code is > implemented still conforming to RFC2960. > Do we have any plan to implement the latest RFC4960 standard in Linux? > If so, when can we expect it to be done? What makes you think so? We do support RFC4960. It's even listed in http://lksctp.sourceforge.net/ that's the site for the userspace lib but it's minimal, 99% of the implementation is on kernel and should be compliant with RFC4960. Marcelo -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html ?韬{.n?????%??檩??w?{.n???{炳??Ф?塄}?财??j:+v?? ? ???2??璀??摺?囤??z夸z罐?+?????w棹f
