linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: Michael Tuexen <tuexen@freebsd.org>,
	"linux-sctp @ vger . kernel . org" <linux-sctp@vger.kernel.org>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Subject: add SPP_PLPMTUD_ENABLE/DISABLE flag for spp_flags
Date: Tue, 18 May 2021 12:43:45 -0400	[thread overview]
Message-ID: <CADvbK_dqs84c7Yr_eUuENe9Y9HQXwG3AXh-0EcKFD3mjPwfpQQ@mail.gmail.com> (raw)

Hi, Michael,

We're implementing RFC8899 (PLPMTUD) on Linux SCTP recently,
and to make this be controlled by setsockopt with
SCTP_PEER_ADDR_PARAMS, as in

  https://datatracker.ietf.org/doc/html/rfc6458#section-8.1.12:

we need another two flags to add for spp_flags:

  SPP_PLPMTUD_ENABLE
  SPP_PLPMTUD_DISABLE

Do you think it makes sense? if yes, does the RFC6458 need to update?
if not, do you have a better suggestion for it?

Thanks.

             reply	other threads:[~2021-05-18 16:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 16:43 Xin Long [this message]
2021-05-18 17:38 ` add SPP_PLPMTUD_ENABLE/DISABLE flag for spp_flags Michael Tuexen
2021-05-18 18:33   ` Xin Long
2021-05-18 19:19     ` Michael Tuexen
2021-05-19 22:24       ` mleitner
2021-05-20  2:05         ` Xin Long
2021-05-20  7:06           ` tuexen
2021-05-20 15:13             ` Xin Long
2021-05-19 16:18     ` Xin Long
2021-05-19 18:15       ` Michael Tuexen
2021-05-19 18:44         ` Xin Long
2021-05-19 22:44           ` mleitner
2021-05-19 23:16             ` Michael Tuexen
2021-05-20  0:45               ` Marcelo Ricardo Leitner
2021-05-20  6:59                 ` tuexen
2021-05-20 19:27                   ` Marcelo Ricardo Leitner
2021-05-19 23:10           ` Michael Tuexen

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=CADvbK_dqs84c7Yr_eUuENe9Y9HQXwG3AXh-0EcKFD3mjPwfpQQ@mail.gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=linux-sctp@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=tuexen@freebsd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).