[27682] in North American Network Operators' Group
RE: Napster and others...
daemon@ATHENA.MIT.EDU (Christian Kuhtz)
Tue Mar 7 14:33:43 2000
From: "Christian Kuhtz" <ck@arch.bellsouth.net>
To: "Michael Ridley" <michael@napster.com>, <smd@clock.org>
Cc: <nanog@merit.edu>
Date: Tue, 7 Mar 2000 14:31:03 -0500
Message-ID: <NDBBIHGIMLHECOLBHAACKEDFCEAA.ck@arch.bellsouth.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20000307100306.A1835@napster.com>
Errors-To: owner-nanog-outgoing@merit.edu
> I believe there was some discussion about doing that, actually, although
> I don't know where it went (as I just do system admin stuff, not development
> stuff). I'll have to inquire as I haven't heard anything about it recently.
> Of course, the real impact would be pretty limited since I don't know that
> most peoples' routers really look to that header for QoS. Nevertheless...
Err, excuse me.. if a service provider reclassifies the traffic inside their
cloud and rewrite the IP ToS precedence, your wonderful marking gets messed up.
It is highly unlikely that the original ToS of each packet will be restored once
it leaves the provider's cloud... keep it TCP, keep it predictable and you got
a KISS pattern to match.
Cheers,
Chris
--
Christian Kuhtz, Sr. Network Architect Architecture, BellSouth.net
<ck@arch.bellsouth.net> -wk, <ck@gnu.org> -hm Atlanta, GA
"Speaking for myself only."
