Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave@taht.net>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	 Cake List <cake@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-06 is in last call
Date: Thu, 22 Aug 2019 08:11:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1908220801280.21548@uplift.swm.pp.se> (raw)
In-Reply-To: <87pnkyea04.fsf@taht.net>

On Wed, 21 Aug 2019, Dave Taht wrote:

> Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
>
>> Maybe attached patch is more comprehensive?
>
> Yep! why was diffserv8 5 in the first place?

"diffserve8 is 5"? I don't understand. Do you mean 001000?

https://tools.ietf.org/html/rfc3662

3.2.  PHB configuration

    Either a Class Selector (CS) PHB [RFC2474], an Experimental/Local Use
    (EXP/LU) PHB [RFC2474], or an Assured Forwarding (AF) PHB [RFC2597]
    may be used as the PHB for the LE traffic aggregate.  This document
    does not specify the exact DSCP to use inside a domain, but instead
    specifies the necessary properties of the PHB selected by the DSCP.
    If a CS PHB is used, Class Selector 1 (DSCP=001000) is suggested.

So CS1 is the original PHB for LE. However, it has problems and was never 
really deployed and I was one who pushed for a specific codepoint within 
000xxx for LE, that might have a chance to be deployed internet-wide. 
000001 seems as good as any.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

      reply	other threads:[~2019-08-22  6:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 18:39 [Cerowrt-devel] " Dave Taht
2019-02-03 20:02 ` Jonathan Morton
2019-02-03 22:42 ` David P. Reed
2019-02-04  0:17   ` Dave Taht
2019-02-04  1:12   ` [Cerowrt-devel] [Cake] " Jonathan Morton
2019-02-04  6:02   ` [Cerowrt-devel] " Mikael Abrahamsson
2019-02-04  6:58     ` [Cerowrt-devel] [Cake] " Dave Taht
2019-02-04  7:11       ` Mikael Abrahamsson
2019-02-04 10:23         ` Dave Taht
2019-02-04 10:34           ` Mikael Abrahamsson
2019-02-04 10:40             ` Dave Taht
2019-08-21 15:07 ` [Cerowrt-devel] " Dave Taht
2019-08-21 16:38   ` [Cerowrt-devel] [Cake] " Kevin Darbyshire-Bryant
2019-08-21 16:52     ` Dave Taht
2019-08-22  6:11       ` Mikael Abrahamsson [this message]

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1908220801280.21548@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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