[144343] in North American Network Operators' Group
Re: Silently dropping QoS marked packets on the greater Internet
daemon@ATHENA.MIT.EDU (Mark Tinka)
Fri Sep 9 01:05:44 2011
From: Mark Tinka <mtinka@globaltransit.net>
To: nanog@nanog.org
Date: Fri, 9 Sep 2011 13:04:39 +0800
In-Reply-To: <4E60E717.5050406@gmail.com>
Reply-To: mtinka@globaltransit.net
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--nextPart1740171.oz5YZeAtpo
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Friday, September 02, 2011 10:24:23 PM Jesse McGraw=20
wrote:
> I've recently run into a hard-to-troubleshoot issue
> where, somewhere out in the greater Internet, someone
> was silently dropping packets from my company that
> happened to be marked with DSCP AF21. I'd fully expect
> others to either ignore these markings or zero them out
> but just silently dropping them seems unnecessary.
This is broken.
They likely aren't remarking their Internet traffic=20
appropriately to avoid having to schedule it internally, and=20
thus, perform some kind of action on it per their QoS=20
strategy.
You may consider remarking your traffic one egress to the=20
Internet to 0 (safe bet?), but this may be a platform-
specific capability, and can't tell you for sure it will=20
work; needless to say, you might not want to do this anyway=20
:-).
> So, how do you guys treat marked packets that come
> into/through your networks?
We generally remark all ingress IP Transit traffic to 0,=20
both for v4 and v6. This includes traffic from IP Transit=20
customers. In general terms, trying to provide QoS=20
scheduling services to Internet traffic is fairly=20
cumbersome.
There are special cases where Internet traffic could be=20
marked to a non-0 value, but these would be controlled=20
situations for interesting business opportunities.
Cheers,
Mark.
--nextPart1740171.oz5YZeAtpo
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQIcBAABAgAGBQJOaZ5qAAoJEGcZuYTeKm+G+S4P/jNon0f4Q/adLNSb75ZK2ep6
UT9E2bZBHBgqJM6zsfyRUuVxRdeauKwxkOJ0Sjv3Dnouz57IMTxUZSNw+QL75AOq
/NtjYFzDxgTHep8jyNIAaQ3RwfnCk/HJCd7vcthFhhof0ptEvOtFsbMYE7gXElYi
a94hC+kO1qyvnLFVdqsxrulbqji9SmCebByhMaLD6G9hkR/tK/bnAUkTMz0pQEUo
rZRqZNG1Jh5MPV25BCt0lbMGsarlKg+7MAxy92Ybe5lsTHE7XnzLmRCnM6E5vtBW
13g6ArnpxZnqHiXQ79lp7+MA80Ow1qg7nv7DzcATGXNKUb6ai3w9TQ8HaTezYAUn
sATZZIvciffruC3GkOQ0+zZKQH3sW66ZZpCMkNc3yTLtTtvtjTIYxdL8p7e7BpaZ
Bl4GA1rdpr7eMD57Dv7lGjX8S0sdQoxAxuM/gz8McTF/EFdWaI+bQEX6cgzbQW74
L1rj7jP2uXh0ZD6Cg23h/oWdrP48GsV6MRnjpy+BzL4StmeDREGYAI1xyJx69P6j
0JtzgVJYA9IsgCmJf9NeJN9zdm839fdGxegGjl3ESX9fiDQpFXCfMQa3qRgQushF
jm+OgXrRogkXEQohbSR1mY/2Nl5cdp08TIUi3s4mTjrpolXEw/BWyJ9AP3fLGmuA
FEEHukjc5nztUqRYTTGT
=LSab
-----END PGP SIGNATURE-----
--nextPart1740171.oz5YZeAtpo--
