Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Kurt Wagner <kwagner@cosy.sbg.ac.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Is this a mistake (AF level)?????
Date: Wed, 09 May 2001 15:47:36 +0000	[thread overview]
Message-ID: <marc-lartc-98942308530265@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98938247512870@msgid-missing>

Hello Juergen,

> I saw the draft-almesberger-wajhak-diffserv-linux-00.txt file.
> But in this file say that AF21 is 0x18

and two paragraphs before that they state that AF21 is 0x12 - so maybe its
a typing error. Or the AF-DSCP values were not defined clearly at that
time - both, rfc2597 and the draft were written in june99. Or its pure
stubbornness - imagine Werner realy _wanted_ his AF22 to be 0x1a. The
values in rfc2597 are RECOMMENDED values after all. ;)

> If the rfc2597 is right(list below)
>   The RECOMMENDED values of the AF codepoints are as follows: AF11 = '
>    001010', AF12 = '001100', AF13 = '001110', AF21 = '010010', AF22 = '
>    010100', AF23 = '010110', AF31 = '011010', AF32 = '011100', AF33 = '
>    011110', AF41 = '100010', AF42 = '100100', and AF43 = '100110'.
>
> AF21 and AF22 is 010010 and 010100
> 010010 = 0x12
> 010100 = 0x14
> is that right??????

Yes.

> Why many papers and documents arent' use this table?????

Stubbornness, ignorance, inertia, eccentricsm, typos... hmm, probably
mostly ignorance - that's my guess.


Kurt




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

      reply	other threads:[~2001-05-09 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09  4:25 [LARTC] Is this a mistake (AF level)????? Juergen
2001-05-09 15:47 ` Kurt Wagner [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

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

  git send-email \
    --in-reply-to=marc-lartc-98942308530265@msgid-missing \
    --to=kwagner@cosy.sbg.ac.at \
    --cc=lartc@vger.kernel.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