[175954] in North American Network Operators' Group
FW: M-Lab-Related PCAPs
daemon@ATHENA.MIT.EDU (Livingood, Jason)
Sun Nov 9 00:46:33 2014
X-Original-To: nanog@nanog.org
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: NANOG list <nanog@nanog.org>, "srknth.s@gmail.com" <srknth.s@gmail.com>
Date: Sun, 9 Nov 2014 05:46:35 +0000
Errors-To: nanog-bounces@nanog.org
FYI to this list since I suspect few of you are on the M-Lab Discuss list.
Srikanth from ICSI has kindly taken on consolidating some PCAPs. If anyone =
wishes to send any to him, he is at srknth.s@gmail.com<mailto:srknth.s@gmai=
l.com>.
JL
On 11/6/14, 7:24 PM, "Srikanth S" <srknth.s@gmail.com<mailto:srknth.s@gmail=
.com>> wrote:
So it looks as though marking is not done for all MLab traffic. Also, some =
web traffic (to CNN) is marked at a lower priority than streaming (Netflix)=
, which is strange as web traffic is likely more sensitive to degradation t=
han streaming (?).
Here are the traces:
http://www1.icsi.berkeley.edu/~srikanth/pcaps/google.pcap
http://www1.icsi.berkeley.edu/~srikanth/pcaps/youtube-image.pcap
http://www1.icsi.berkeley.edu/~srikanth/pcaps/cnn.pcap
http://www1.icsi.berkeley.edu/~srikanth/pcaps/netflix-streaming.pcap
On Tuesday, November 4, 2014 1:29:16 PM UTC-8, Jason Livingood wrote:
Another follow-up. Someone emailed me a PCAP off-list from an enterprise ty=
pe of customer. Their PCAP was somewhat incomplete (so I still need more) b=
ut they noticed that some traffic at the next priority down from 0x48 at 0x=
28 (priority). And some other traffic was marked with the next priority dow=
n again at 0x00 (routine).
So it appears there are three DSCP / ToS markings in use rather than just t=
wo (0x00, 0x28, 0x48).
So safe to say more research is needed here =96 anyone collecting PCAPs sho=
uld IMHO continue. :-)
Jason
