Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
To: ecn-sane@lists.bufferbloat.net
Subject: [Ecn-sane] [tsvwg] Requesting TSVWG adoption of SCE draft-morton-tsvwg-sce (fwd)
Date: Sun, 17 Nov 2019 19:54:06 -0800 (PST)	[thread overview]
Message-ID: <201911180354.xAI3s6Ae064616@gndrsh.dnsmgr.net> (raw)

ecn-sane:

	I meant to send this out earlier, but overloooked it.  The SCE
developement team has announced that it intends to ask for adoption of
the signalling draft for SCE at the TSVWG meeting in Singapore this week,
those of you not on the tsvwg@ietf.org maillist list are encouraged to
catch up on the thread at
	https://mailarchive.ietf.org/arch/browse/tsvwg/?gbt=1&index=w7o1ei1YPsFwm4tWQnCyyV_X9N0

and join the mail list if you have an opinion to express.

We would also like your support during Thursdays tsvwg session
and if you can show up by remote attending that would be wonderful.

If you have time to read the draft:
https://datatracker.ietf.org/doc/draft-morton-tsvwg-sce/
and express your interest this too would be appreciated.

Regards,
Rod

----- Forwarded message from Rodney W. Grimes -----

Hello tsvwg list members,

It is our intent to ask for adoption by the TSVWG of draft-morton-tsvwg-sce (https://tools.ietf.org/html/draft-morton-tsvwg-sce-01) during the IETF/106 Singapore TSVWG session.

 
The TSVWG chairs have provided the following guidelines for this adoption request:
 
(1) The WG chairs want to see interest in SCE technology beyond the draft authors in order to adopt the SCE draft.   This will include surveying the room in Singapore (e.g., who has read this
 draft?).
 
(2) Coexistence of the L4S and SCE experiments is a concern that will need to be addressed by the WG if the SCE draft is adopted, and hence is in scope for discussion of this adoption request
..  In particular, absence of a coexistence plan (e.g., to deal with the different uses of the ECT(1) codepoint by L4S and SCE) is not an automatic barrier to WG adoption of the SCE draft.
 
(3) The TCPM WG chairs have indicated TCPM WG willingness to consider complementary TCP work needed to complete SCE functionality.  In particular, draft-grimes-tcpm-tcpsce is likely to be inc
luded in the TCPM Singapore agenda for Friday morning.
 
 
Regards,
-- 
Rod Grimes                                                 rgrimes@freebsd.org


----- End of forwarded message from Rodney W. Grimes -----

-- 
Rod Grimes                                                 rgrimes@freebsd.org

             reply	other threads:[~2019-11-18  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18  3:54 Rodney W. Grimes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-18  3:54 Rodney W. Grimes

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

  List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201911180354.xAI3s6Ae064616@gndrsh.dnsmgr.net \
    --to=freebsd@gndrsh.dnsmgr.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=rgrimes@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