Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: "Holland\, Jake" <jholland@akamai.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>,
	"Cake List" <cake@lists.bufferbloat.net>,
	"codel\@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
	"ecn-sane\@lists.bufferbloat.net"
	<ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Bloat] The "Some Congestion Experienced" ECN codepoint - a new internet draft -
Date: Sun, 10 Mar 2019 23:23:04 -0400	[thread overview]
Message-ID: <2252.1552274584@localhost> (raw)
In-Reply-To: <550C0248-1704-49DA-ABDC-49A91E0AC6F3@akamai.com>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]


Holland, Jake <jholland@akamai.com> wrote:
    > 1.
    > "Some" in "Some Congestion Experienced" is maybe misleading, and
    > arguably has the same meaning as "Congestion Experienced".

    > I was thinking maybe "Pre-Congestion Experienced" or "Queue
    > Utilization Observed", or if you want to preserve "SCE" and the

I'll combine them:
     "Some Congestion Observed"

(I image a packet rubber-necking to observe some collision on the exressway)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2019-03-11  3:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 18:04 [Ecn-sane] " Dave Taht
2019-03-10 18:53 ` [Ecn-sane] [Cake] " Sebastian Moeller
2019-03-10 19:08 ` [Ecn-sane] [Bloat] " Holland, Jake
2019-03-10 19:30   ` Jonathan Morton
     [not found]     ` <alpine.DEB.2.20.1903110800310.3161@uplift.swm.pp.se>
2019-03-11  7:35       ` Richard Scheffenegger
2019-03-11  7:54         ` Sebastian Moeller
2019-03-11  8:59         ` Jonathan Morton
2019-03-11  9:07           ` Mikael Abrahamsson
2019-03-11  9:10             ` Jonathan Morton
2019-03-11  9:47               ` Mikael Abrahamsson
2019-03-11 10:11                 ` [Ecn-sane] [Codel] " Dave Taht
     [not found]                   ` <00133e20-6639-c6db-a06c-57856bf78167@bobbriscoe.net>
2019-03-11 16:34                     ` [Ecn-sane] [Bloat] [Codel] " Dave Taht
2019-03-11 16:14                 ` [Ecn-sane] [Bloat] " Holland, Jake
2019-03-11 15:29             ` Holland, Jake
2019-03-11 16:13               ` Jonathan Morton
2019-03-11  7:43       ` [Ecn-sane] [Cake] " Sebastian Moeller
2019-03-13  4:39         ` David Lang
2019-03-10 21:11   ` [Ecn-sane] " Dave Taht
2019-03-10 21:28     ` Dave Taht
2019-03-10 21:49       ` Dave Taht
2019-03-10 22:37         ` Toke Høiland-Jørgensen
2019-03-11  3:23   ` Michael Richardson [this message]
2019-03-11  3:26     ` Dave Taht

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=2252.1552274584@localhost \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=jholland@akamai.com \
    /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