references.bib

   
    
@book{Sommerville2010,
author = {Sommerville, Ian},
title = {Software Engineering},
year = {2010},
isbn = {0137035152},
publisher = {Addison-Wesley Publishing Company},
address = {USA},
edition = {9th},
}


@inproceedings{Narayan2012,
author = {Ramasubbu, Narayan and Balan, Rajesh Krishna},
title = {Overcoming the Challenges in Cost Estimation for Distributed Software Projects},
year = {2012},
isbn = {9781467310673},
publisher = {IEEE Press},
booktitle = {Proceedings of the 34th International Conference on Software Engineering},
pages = {91–101},
numpages = {11},
location = {Zurich, Switzerland},
series = {ICSE '12}
}


@article{Robbes2015,
author = {Robbes, Romain Pierre Julien and Röthlisberger, D and Tanter, É},
issn = {1382-3256},
journal = {Empirical Software Engineering},
keywords = {Data extensions},
language = {eng},
number = {3},
volume = {20},
publisher = {Kluwer Academic Publishers},
title = {Object-oriented software extensions in practice},
year = {2015},
}

@misc{kinaSUR,
    author = {{Ministry for Primary Industries}},
    title = {{Kina sea urchin regions in NZ}},
    howpublished = {\url{http://fs.fish.govt.nz/Page.aspx?pk=7\&sc=SUR}},
    note = {Online; accessed 29 January 2014} 
}

@mastersthesis{mastersthesis1993,
  author       = {Peter Harwood}, 
  title        = {The title of the work},
  school       = {The school of the thesis},
  year         = 1993,
  address      = {The address of the publisher},
  month        = 7,
  note         = {An optional note}
}

@phdthesis{phdthesis1993,
  author       = {Peter Joslin}, 
  title        = {The title of the work},
  school       = {The school of the thesis},
  year         = 1993,
  address      = {The address of the publisher},
  month        = 7,
  note         = {An optional note}
}

% ------------------------------------------------------------------------------- 
% -------------------------- The articles I brought -------------------------- 

@misc{SDPWebRTC2013,
  title={{SDP for the WebRTC}},
  
 }
@misc{TeamsFlows2018,
  title= {{Microsoft Teams call flows}},
  publisher = {{Microsoft Corporation}},
  howpublished = {\url{https://docs.microsoft.com/en-us/microsoftteams/microsoft-teams-online-call-flows}},
  note = {Online; accessed 21 May 2021}
 }

@misc{WebMedia2014,
    title = {{Getting started with media devices}},
    publisher = {{Google Developers}},
    howpublished = {\url{https://webrtc.org/getting-started/media-devices}},
    note = {Online; accessed 13 April 2021}
 }

@misc{WebPeer2014,
    title = {{Getting started with peer connections}},
    publisher = {{Google Developers}},
    howpublished = {\url{https://webrtc.org/getting-started/peer-connections}},
    note = {Online; accessed 13 April 2021}
 }

@misc{WebStream2014,
    title = {{Getting started with remote streams}},
    publisher = {{Google Developers}},
    howpublished = {\url{https://webrtc.org/getting-started/remote-streams}},
    note = {Online; accessed 13 April 2021}
 }

@misc{TeamsReact2018,
  author       = {Mitra, Abhik},
  title        = {{Moving a huge AngularJS App to React, progressively at Microsoft Scale}},
  howpublished = {\url{https://hasgeek.com/jsfoo/2019-pune/sub/moving-a-huge-angularjs-app-to-react-progressively-X3igB6hPLDNnSfinWmpZER}},
  year         = {2018}
}

@misc{Telectroscope1877,
  author       = {{Lange, André}},
  title        = {{L'attribution imaginaire de l'invention du télectroscope  à Graham Bell par l'Abbé Moigno et Louis Figuier (1877-1878).}},
  year         = {2020},
  howpublished = {\url{https://www.histv.net/telectroscope1877}}
}

@misc{JitsiArchitecture,
  title        = {Architecture},
  journal      = {Jitsi Meet Handbook},
  howpublished = {\url{https://jitsi.github.io/handbook/docs/architecture}}
}

@misc{JitsiVideobridge,
  author       = {Grozev, Boris and Ivov, Emil},
  title        = {Jitsi Videobridge Performance Evaluation},
  howpublished = {\url{https://jitsi.org/jitsi-videobridge-performance-evaluation/}}
}

@misc{JitsiBridgeCascading,
  author       = {Ivov, Emil},
  title        = {{Jitsi Meet, now with geographical bridge cascading}},
  howpublished = {\url{https://jitsi.org/blog/jitsi-meet-now-with-geographical-bridge-cascading/}},
  year         = {2018}
}

@misc{Electroscope1878,
  author       = {{Lange, André}},
  title        = {{L'histoire de la télévision commence par un canular: l'électroscope de 1877}},
  year         = {2002},
  howpublished = {\url{https://www.histv.net/electroscope-1878}}
}

@article{Videophone1927,
  author          = {{Uenuma, Francine}},
  title           = {{Video Chat Is Helping Us Stay Connected in Lockdown. But the Tech Was Once a ‘Spectacular Flop’}},
  year            = {2020},
  date            = {2020-05-11},
  journal         = {{Time}},
  howpublished    = {\url{https://time.cvom/5834516/video-chat-zoom-history/}},
  urldate         = {2020-05-11},
}

@article{Borth98,
  author          = {Borth, David E.},
  title           = {{Videophone}},
  journal         = {Encyclopædia Britannica},
  url             = {https://www.britannica.com/technology/videophone},
  urldate         = {1998-07-20}
}

@article{Dorcey95,
  author          = {{Dorcey, Timothy}},
  title           = {{CU-SeeMe Desktop VideoConferencing Software}},
  journal         = {{Connexions}},
  volume          = {9},
  number          = {3},
  year            = {1995},
  howpublished    = {\url{https://ftp.icm.edu.pl/packages/cu-seeme/html/DorceyConnexions.html}}
}

@mastersthesis{Root2000,
  author  = {{Root, Timothy D.}},
  title   = {{Audio communications product strategy for the 21st century}},
  school  = {Massachusetts Institute of Technology},
  year    = {2000},
  doi     = {1721.1/88335}
}

@misc{Avoira2020,
  title = {{A History of Video Conferencing}},
  publisher = {Avoira},
  howpublished = {\url{https://www.videonations.co.uk/resources/blog/a-history-of-video-conferencing/}},
}

@misc{MicrosoftRTP,
  title        = {{RTP Packets}},
  publisher    = {{Microsoft Corporation}},
  howpublished = {\url{https://docs.microsoft.com/en-us/openspecs/office_protocols/ms-rtp/3b8dc3c6-34b8-4827-9b38-3b00154f471c}},
  year         = {2021}
}

@misc{Vidconf,
  title        = {{Distance Multimedia: 4 score \& more}},
  howpublished = {\url{https://vidconf.net/}}
}

@misc{ZoomWebRTC,
  author       = {Hancke, Philipp},
  title        = {{How Zoom’s web client avoids using WebRTC (DataChannel Update)}},
  journal      = {webrtcHacks}, 
  howpublished = {\url{https://webrtchacks.com/zoom-avoids-using-webrtc/}},
  year         = {2019}
}

@article{ZoomScalability,
  author       = {Sachdeva, Vikram},
  title        = {{Zoom — Video conf app at scale}},
  journal      = {Medium},
  url          = {https://medium.com/@vsachdeva/zoom-video-conf-tool-at-scale-e86289c290b8},
  year         = {2020}
}

@article{Nyman2013,
  author          = {Nyman, Robert},
  title           = {{Hello Chrome, it's Firefox calling!}},
  journal         = {Mozilla Hacks},
  year            = {2013},
  month           = {02},
  url             = {https://hacks.mozilla.org/2013/02/hello-chrome-its-firefox-calling/},
  urldate         = {2013-02-04}
}

@misc{rfc2543,
	series =	{Request for Comments},
	number =	2543,
	howpublished =	{RFC 2543},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC2543},
	url =		{https://rfc-editor.org/rfc/rfc2543.txt},
        author =	{Henning Schulzrinne and Eve Schooler and Jonathan Rosenberg and Mark J. Handley},
	title =		{{SIP: Session Initiation Protocol}},
	pagetotal =	151,
	year =		1999,
	month =		mar,
	abstract =	{The Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants. {[}STANDARDS-TRACK{]}},
}

@misc{rfc741,
	series =	{Request for Comments},
	number =	741,
	howpublished =	{RFC 741},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC0741},
	url = {https://rfc-editor.org/rfc/rfc741.txt},
        author =	{},
	title =		{{Specifications for the Network Voice Protocol (NVP)}},
	pagetotal =	34,
	year =		1977,
	month =		11,
	abstract =	{},
}

@misc{rfc3550,
	series =	{Request for Comments},
	number =	3550,
	howpublished =	{RFC 3550},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC3550},
	url =		{https://rfc-editor.org/rfc/rfc3550.txt},
        author =	{Henning Schulzrinne and Stephen L. Casner and Ron Frederick and Van Jacobson},
	title =		{{RTP: A Transport Protocol for Real-Time Applications}},
	pagetotal =	104,
	year =		2003,
	month =		jul,
	abstract =	{This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of- service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes. There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously. {[}STANDARDS-TRACK{]}},
}

@misc{rfc4566,
	series =	{Request for Comments},
	number =	4566,
	howpublished =	{RFC 4566},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC4566},
	url =		{https://rfc-editor.org/rfc/rfc4566.txt},
        author =	{Colin Perkins and Mark J. Handley and Van Jacobson},
	title =		{{SDP: Session Description Protocol}},
	pagetotal =	49,
	year =		2006,
	month =		jul,
	abstract =	{This memo defines the Session Description Protocol (SDP). SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. {[}STANDARDS-TRACK{]}},
}

@misc{rfc5245,
	series =	{Request for Comments},
	number =	5245,
	howpublished =	{RFC 5245},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC5245},
	url =		{https://rfc-editor.org/rfc/rfc5245.txt},
        author =	{Jonathan Rosenberg},
	title =		{{Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols}},
	pagetotal =	117,
	year =		2010,
	month =		apr,
	abstract =	{This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model. This protocol is called Interactive Connectivity Establishment (ICE). ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP). {[}STANDARDS-TRACK{]}},
}

@misc{rfc5389,
	series =	{Request for Comments},
	number =	5389,
	howpublished =	{RFC 5389},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC5389},
	url =		{https://rfc-editor.org/rfc/rfc5389.txt},
        author =	{Philip Matthews and Jonathan Rosenberg and Dan Wing and Rohan Mahy},
	title =		{{Session Traversal Utilities for NAT (STUN)}},
	pagetotal =	51,
	year =		2008,
	month =		oct,
	abstract =	{Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with Network Address Translator (NAT) traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints, and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs, and does not require any special behavior from them. STUN is not a NAT traversal solution by itself. Rather, it is a tool to be used in the context of a NAT traversal solution. This is an important change from the previous version of this specification (RFC 3489), which presented STUN as a complete solution. This document obsoletes RFC 3489. {[}STANDARDS-TRACK{]}},
}

@misc{rfc8445,
	series =	{Request for Comments},
	number =	8445,
	howpublished =	{RFC 8445},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC8445},
	url =		{https://rfc-editor.org/rfc/rfc8445.txt},
        author =	{Ari Keränen and Christer Holmberg and Jonathan Rosenberg},
	title =		{{Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal}},
	pagetotal =	100,
	year =		2018,
	month =		jul,
	abstract =	{This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based communication. This protocol is called Interactive Connectivity Establishment (ICE). ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). This document obsoletes RFC 5245.},
}

@misc{SFU2020,
  title        = {{An Introduction to Selective Forwarding Units}},
  journal      = {Voximplant},
  howpublished = {\url{https://voximplant.com/blog/an-introduction-to-selective-forwarding-units}},
  year         = {2020}
}

@misc{QuickCam94,
  title = {{Connectix QuickCam}},
  howpublished = {\url{http://people.vcu.edu/~aplinas/opticnerve/quickcam.html}}
}

@misc{SSE97,
  title        = {{What is SSE and AVX?}},
  publisher    = {CodinGame},
  howpublished = {\url{https://www.codingame.com/playgrounds/283/sse-avx-vectorization/what-is-sse-and-avx}}
}

@misc{Videocomm2020,
  publisher       = {Avoira},
  title           = {{A History of Video Conferencing}},
  howpublished    = {\url{https://www.videonations.co.uk/resources/blog/a-history-of-video-conferencing/}},
  year            = {2020}
}

@article{Perey2000,
  author          = {Perey, Christine},
  title           = {{Microsoft expands platform for voice and video on the LAN}},
  url             = {https://www.computerworld.com/article/2783021/microsoft-expands-platform-for-voice-and-video-on-the-lan.html},
  journal         = {Computer World},
  year            = {2000}
}

@article{Wolfe2019,
  author          = {Wolfe, Erinn},
  title           = {{The History of Video Conferencing from 1870 to Today}},
  journal         = {Lifesize},
  howpublished    = {\url{https://www.lifesize.com/en/blog/history-of-video-conferencing/}},
  year            = {2019}
}

@article{Royal2007,
  author       = {Royal, Greg},
  title        = {{Apple iChat Next Wave of VoIP}},
  journal      = {Network World},
  howpublished = {\url{https://www.networkworld.com/article/2347535/apple-ichat-next-wave-of-voip.html}},
  year         = {2007},
  month        = {06},
}

@article{Whittaker2013,
  author       = {Whittaker, Zack},
  title        = {{Skype ditched peer-to-peer supernodes for scalability, not surveillance}},
  journal      = {ZDNet},
  howpublished = {\url{https://www.zdnet.com/article/skype-ditched-peer-to-peer-supernodes-for-scalability-not-surveillance/}},
  year         = {2013}
}

@article{Baset2004,
  author    = {Baset, Salman A. Schulzrinne, Henning},
  title     = {{An Analysis of the Skype Peer-to-Peer Internet Telephony Protocol}},
  journal   = {CoRR},
  volume    = {abs/cs/0412017},
  year      = {2004},
  url       = {http://arxiv.org/abs/cs/0412017},
  archivePrefix = {arXiv},
  eprint    = {cs/0412017},
  timestamp = {Mon, 13 Aug 2018 16:47:34 +0200},
  biburl    = {https://dblp.org/rec/journals/corr/abs-cs-0412017.bib},
  bibsource = {dblp computer science bibliography, https://dblp.org}
}

@article{ACMRTC,
  author          = {Blum, Niklas and Lachapelle, Serge and Alvestrand, Harald},
  title           = {{WebRTC - Realtime Communication for the Open Web Platform}},
  journal         = {{ACM Queue}},
  volume          = {19},
  issue           = {1},
  year            = {2021}
}

@article{MacMillan2021,
  author    = {MacMillan, Kyle and
               Mangla, Tarun and
               Saxon, James and
               Feamster, Nick},
  title     = {{Measuring the Performance and Network Utilization of Popular Video
               Conferencing Applications}},
  journal   = {CoRR},
  volume    = {abs/2105.13478},
  year      = {2021},
  url       = {https://arxiv.org/abs/2105.13478},
  archivePrefix = {arXiv},
  eprint    = {2105.13478},
  timestamp = {Tue, 01 Jun 2021 18:07:59 +0200},
  biburl    = {https://dblp.org/rec/journals/corr/abs-2105-13478.bib},
  bibsource = {dblp computer science bibliography, https://dblp.org}
}

@techreport{H.264,
  title       = {{ITU-T Recommendation H.264: Advanced video coding for generic audiovisual services}},
  institution = {},
  year        = {2003},
  month       = {05},
}

@article{DBLP:journals/corr/abs-2105-07558,
  author    = {Halder, Debajyoti and
               Kumar, Prashant and
               Bhushan, Saksham and
               Baswade, Anand M.},
  title     = {{fybrrStream: A WebRTC based Efficient and Scalable P2P Live Streaming
               Platform}},
  journal   = {CoRR},
  volume    = {abs/2105.07558},
  year      = {2021},
  url       = {https://arxiv.org/abs/2105.07558},
  archivePrefix = {arXiv},
  eprint    = {2105.07558},
  timestamp = {Tue, 18 May 2021 18:46:40 +0200},
  biburl    = {https://dblp.org/rec/journals/corr/abs-2105-07558.bib},
  bibsource = {dblp computer science bibliography, https://dblp.org}
}


@article{WebNSM2017,
author = {Edan, Naktal and Al-Sherbaz, Ali and Turner, Scott},
year = {2018},
month = {02},
pages = {390-399},
title = {{Design and Implement a Hybrid WebRTC Signalling Mechanism for Unidirectional \& Bi-directional Video Conferencing}},
volume = {8},
journal = {International Journal of Electrical and Computer Engineering},
doi = {10.11591/ijece.v8i1.pp390-399}
}

% ------------------------------------------------------------------------------- 
% -------------------------------------------------------------------------------