From: Marcelo Ricardo Leitner Date: Mon, 19 Aug 2019 14:46:33 +0000 Subject: Re: [PATCH net-next 4/8] sctp: add SCTP_ASCONF_SUPPORTED sockopt Message-Id: <20190819144633.GD2870@localhost.localdomain> List-Id: References: <20190819143052.GC2870@localhost.localdomain> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Xin Long Cc: network dev , linux-sctp@vger.kernel.org, Neil Horman , davem On Mon, Aug 19, 2019 at 10:43:03PM +0800, Xin Long wrote: > On Mon, Aug 19, 2019 at 10:30 PM Marcelo Ricardo Leitner > wrote: > > > > On Mon, Aug 19, 2019 at 10:02:46PM +0800, Xin Long wrote: > > > SCTP_ASCONF_SUPPORTED sockopt is used to set enpoint's asconf > > > flag. With this feature, each endpoint will have its own flag > > > for its future asoc's asconf_capable, instead of netns asconf > > > flag. > > > > Is this backed by a RFC? If yes, it should be noted in the patch > > description. > > Quickly searching, I found only FreeBSD references. > RFC doesn't define this sockopt clearly, unlike prsctp and reconfig, > not sure why. > but BSD supports it, so does some userland SCTP. Ok. Thanks.