CPSC 641 Project Brainstorming Carey Williamson Department of

CPSC 641: Project Brainstorming Carey Williamson Department of Computer Science University of Calgary Winter 2018

Course Project Overview § A “typical” course project might involve: —choosing a topic and perf eval methodology —designing/building appropriate testbed, environment, or platform for your project —extend/customize system as needed —obtain relevant data/measurements needed —design suitable experiment: clear goal, identify factors, levels, performance metrics —obtain and describe (new/interesting) results

Project Timeline § By Tuesday, February 27: — One-page project proposal (not marked) — Issues: uniqueness, relevance, fit, scale, data § By Monday, April 16: — Submit 12 -15 page research paper (hardcopy) — Worth 50% of your grade in CPSC 641 — Eval: problem statement, lit review, method, results, writing style, originality, difficulty, etc.

Examples of Past Projects § § § § § Benchmarking dynamic Web content generation Web browsing over wireless/mobile networks Traffic classification using machine learning Temporal locality in multimedia workloads WWW 2007 Web workload characterization Benchmarking modern Web browsers Probabilistic key distribution in WSNs Measurements and analysis of IP-TV Characterizing performance of multi-core Web servers Peer-assisted video streaming

Possible Project Ideas § § § Wavelet-based traffic modeling/forecasting DASH-based video streaming Multi-path TCP (MPTCP) performance Wavelength assignment in WDM optical networks Energy efficient routing in WSNs Office 365 email traffic characterization DNS-based attacks on U of C network HTTP/2. 0 deployment and performance D 2 L caching and/or content acceleration Design and performance of Netflix CDN Pyeong. Chang 2018 video streaming traffic Social network analysis and visualization

Experimental Equipment § § § § § Rack-mounted clients and servers Several routers and switches Wi. MAX modem Web proxy caching appliance Wireless laptops, PDAs, and APs Wireless network analyzers Gigabit Ethernet LAN analyzer Wireless video cameras Wireless sensor motes Access to SAVI national testbed for SDN

Some Available Simulators § § § § § ns-2 network simulator (TCP packet level) ns-3 network simulator OMNET++ simulator Web proxy caching simulator ATM-TN simulator (ATM cell-level) IP-TN simulator (U of C) IP-TNE network emulator (U of C) Mininet network emulator Speed scaling simulator

Some Useful Software Tools § § § § § Synthetic Web proxy workload generation Web client traffic model (mosaic, 1995) LRD traffic analysis (R/S, V-T, AC, etc) GUI for traffic modeling/analysis (syn. Traff) Wavelet-based traffic model (MWM) Synthetic MPEG video trace generation GISMO (Generator for Internet Streaming Media Objects) BRITE Internet Topology Emulator netalyzr tool for benchmarking network paths tcpanaly tool for TCP trace analysis

Public Traces and Data Sets § CRAWDAD: Community Resource for Archiving Wireless Data at Dartmouth (crawdad. cs. dartmouth. edu) § CAIDA: Cooperative Association for Internet Data Analysis (www. caida. org) § Internet Traffic Archive (ita. ee. lbl. gov) — Bellcore Ethernet LAN trace (1989) — LBL TCP/IP packet traces (1990) — Web server access logs (1996)

Local U of C Datasets § Connection-level summary logs for U of C inbound/outbound Internet traffic (hourly/daily/monthly for 10+ years) § Ucalgary. Blogs Web server access log § Carey’s email archives (3 years of data)

Dataset #1: UCalgary. Blogs Web Server § What: about 16 months of Web server access log data from UCalgary. Blogs Web server (1 GB. gz file) § Objective: characterization of Web site usage § Possible analyses: — Which of the hosted Web sites get the most activity? — Popularity analysis (URL based, Zipf-like distributions) — Traffic analysis (volume, time of day, day of week, sizes) — Longitudinal analysis (growth trends, seasonal effects) — Geographical analysis (IP geolocation of Web clients) — Security analysis (denial of service attacks) — D 2 L analysis (logout activity)

Example: Data Format 188. 143. 232. 27 - - [24/Jan/2016: 03: 15: 26 -0700] "GET /2013/03/04/krazy-kats-remarkably-changing-dynamics/ HTTP/1. 1" 200 8054 "-" "Mozilla/5. 0 (Windows NT 6. 1; WOW 64) Apple. Web. Kit/537. 36 (KHTML, like Gecko) Chrome/40. 0. 2214. 111 Safari/537. 36" 188. 143. 234. 155 - - [24/Jan/2016: 03: 15: 26 -0700] "GET /2013/04/24/manga-vs-comics-another-perspective/ HTTP/1. 1" 200 11835 "-" "Mozilla/5. 0 (Windows NT 6. 1; WOW 64) Apple. Web. Kit/537. 36 (KHTML, like Gecko) Chrome/40. 0. 2214. 111 Safari/537. 36" 195. 154. 199. 128 - - [24/Jan/2016: 03: 15: 26 -0700] "POST /wp-login. php HTTP/1. 1" 200 4216 "http: //richardzach. org/wp-login. php" "Mozilla/4. 0 (compatible; MSIE 9. 0; Windows NT 6. 1; 125 LA; . NET CLR 2. 0. 50727; . NET CLR 3. 0. 04506. 648; . NET CLR 3. 5. 21022)" 70. 180. 122. 48 - - [24/Jan/2016: 03: 15: 26 -0700] "POST /wp-signup. php HTTP/1. 0" 200 31441 "http: //ucalgaryblogs. ca/wp-signu p. php? action=register" "Opera/9. 80 (Windows NT 6. 2; Win 64; x 64) Presto/2. 12. 388 Version/12. 17" 195. 154. 199. 128 - - [24/Jan/2016: 03: 15: 28 -0700] "POST /wp-login. php HTTP/1. 1" 200 4216 "http: //richardzach. org/wp-login. php" "Mozilla/4. 0 (compatible; MSIE 9. 0; Windows NT 6. 1; 125 LA; . NET CLR 2. 0. 50727; . NET CLR 3. 0. 04506. 648; . NET CLR 3. 5. 21022)" 188. 143. 232. 32 - - [24/Jan/2016: 03: 15: 30 -0700] "GET /2013/02/27/why-the-web-slinger/ HTTP/1. 1" 200 11605 "-" "Mozilla/5. 0 (Windows NT 6. 1; WOW 64) Apple. Web. Kit/537. 36 (KHTML, like Gecko) Chrome/40. 0. 2214. 111 Safari/537. 36" 195. 154. 199. 128 - - [24/Jan/2016: 03: 15: 29 -0700] "POST /wp-login. php HTTP/1. 1" 200 4216 "http: //richardzach. org/wp-login. php" "Mozilla/4. 0 (compatible; MSIE 9. 0; Windows NT 6. 1; 125 LA; . NET CLR 2. 0. 50727; . NET CLR 3. 0. 04506. 648; . NET CLR 3. 5. 21022)"

Dataset #2: Email Archive § What: about 3 years of “sent-mail” archive (1 GB) recorded by the pine mail reading client on Linux § Objective: characterization of email usage § Possible analyses: — “The Email Chronicles: A Year in the Life of a CPSC Head” — Workload characterization (volume, size, attachments) — Temporal analysis of email usage (date timestamps) — Topical analysis (subject header for theme river analysis) — Social network analysis (CPSC, Fo. S, Uof. C, research, etc) — Seasonal analysis (spiral model a la Charles Perrin) Note: Confidentiality agreement would be required before working with this data

Example: Metadata Date: Thu, 1 Jan 2015 11: 50: 14 -0700 (MST) From: Carey Williamson <carey@cpsc. ucalgary. ca> To: Ken Barker <kbarker@ucalgary. ca> Subject: Re: What to include in the Executive Summary? Date: Thu, 1 Jan 2015 12: 54: 55 -0700 (MST) From: Carey Williamson <carey@cpsc. ucalgary. ca> To: Ken Barker <kbarker@ucalgary. ca> Subject: Re: Unit Reviewers Date: Fri, 2 Jan 2015 08: 57: 13 -0700 (MST) From: Carey Williamson <carey@cpsc. ucalgary. ca> To: Niklas Carlsson <nikca@ida. liu. se> Subject: Re: Happy New Year 2015 Date: Fri, 2 Jan 2015 10: 28: 12 -0700 (MST) From: Carey Williamson <carey@cpsc. ucalgary. ca> To: Carey Williamson <carey@ucalgary. ca> Subject: [Hiring-cpsc-l] CRC Advertisements for Revision (fwd) Date: Tue, 1 Oct 2013 09: 50: 05 From: Erin Moloney <moloney@ucalgary. ca> To: "hiring@cpsc. ucalgary. ca" <hiring@cpsc. ucalgary. ca> Subject: [Hiring-cpsc-l] CRC Advertisements for Revision