From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Fwd: ieee vs ietf stds for dscp mappings
Date: Tue, 17 Nov 2015 10:58:02 +0100 [thread overview]
Message-ID: <CAA93jw5NJ=sMW1f2e+4SstXE9J81c41_3UWJRn_+9vnEBJrs3g@mail.gmail.com> (raw)
In-Reply-To: <259F4BED-C6C3-421B-9B5B-116649DFD981@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
---------- Forwarded message ----------
From: Fred Baker (fred) <fred@cisco.com>
Date: Tue, Nov 17, 2015 at 8:57 AM
Subject: Fwd: [Cake] ieee vs ietf stds for dscp mappings
To: "Tim Szigeti (szigeti)" <szigeti@cisco.com>
Cc: Dave Taht <dave.taht@gmail.com>
I'm noting that there is no reference to RFC 4594/5127 in any of this
chart, or the RFCs it is based on.
> Begin forwarded message:
>
> From: Dave Taht <dave.taht@gmail.com>
> Subject: Fwd: [Cake] ieee vs ietf stds for dscp mappings
> Date: November 15, 2015 at 4:35:50 AM PST
> To: Fred Baker <fred@cisco.com>
>
> Yer killing me. I have no idea how to cope with this mess of diffserv
> values. See
> attached.
>
> arded message ----------
> From: Jonathan Morton <chromatix99@gmail.com>
> Date: Sat, Nov 14, 2015 at 2:55 PM
> Subject: Re: [Cake] ieee vs ietf stds for dscp mappings
> To: Dave Taht <dave.taht@gmail.com>
> Cc: cake@lists.bufferbloat.net
>
>
>
>> On 14 Nov, 2015, at 14:43, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> Just to keep confusing matters
>
> Yeah, Diffserv is a complete and utter mess, isn’t it?
>
>
>
> - Jonathan Morton
[-- Attachment #2: ATT00001.txt --]
[-- Type: text/plain, Size: 6 bytes --]
>
[-- Attachment #3: Untitled.pdf --]
[-- Type: application/pdf, Size: 39667 bytes --]
parent reply other threads:[~2015-11-17 9:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <259F4BED-C6C3-421B-9B5B-116649DFD981@cisco.com>]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5NJ=sMW1f2e+4SstXE9J81c41_3UWJRn_+9vnEBJrs3g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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