feat: add images for NAT traversal and STUN concepts, and update bibliography with new references

Biblio.bib

@@ -293,6 +293,14 @@
   note         = {[Accessed 18-03-2025]}
 }
 
+@misc{opentelemetryWhatOpenTelemetry,
+  author       = {},
+  title        = {{W}hat is {O}pen{T}elemetry? --- opentelemetry.io},
+  howpublished = {\url{https://opentelemetry.io/docs/what-is-opentelemetry/}},
+  year         = {},
+  note         = {[Accessed 25-03-2025]}
+}
+
 @article{Parameswaran2001,
   doi       = {10.1109/2.933501},
   url       = {https://doi.org/10.1109/2.933501},
@@ -341,6 +349,21 @@
   title  = {Research Based Data Rights Management Using Blockchain Over Ethereum Network}
 }
 
+@misc{rfc2663,
+  series       = {Request for Comments},
+  number       = 2663,
+  howpublished = {RFC 2663},
+  publisher    = {RFC Editor},
+  doi          = {10.17487/RFC2663},
+  url          = {https://www.rfc-editor.org/info/rfc2663},
+  author       = {Matt Holdrege and Pyda Srisuresh},
+  title        = {{IP Network Address Translator (NAT) Terminology and Considerations}},
+  pagetotal    = 30,
+  year         = 1999,
+  month        = aug,
+  abstract     = {This document attempts to describe the operation of NAT devices and the associated considerations in general, and to define the terminology used to identify various flavors of NAT. This memo provides information for the Internet community.}
+}
+
 @misc{rfc5128,
   series       = {Request for Comments},
   number       = 5128,
@@ -356,6 +379,21 @@
   abstract     = {This memo documents the various methods known to be in use by applications to establish direct communication in the presence of Network Address Translators (NATs) at the current time. Although this memo is intended to be mainly descriptive, the Security Considerations section makes some purely advisory recommendations about how to deal with security vulnerabilities the applications could inadvertently create when using the methods described. This memo covers NAT traversal approaches used by both TCP- and UDP-based applications. This memo is not an endorsement of the methods described, but merely an attempt to capture them in a document. This memo provides information for the Internet community.}
 }
 
+@misc{rfc5389,
+  series       = {Request for Comments},
+  number       = 5389,
+  howpublished = {RFC 5389},
+  publisher    = {RFC Editor},
+  doi          = {10.17487/RFC5389},
+  url          = {https://www.rfc-editor.org/info/rfc5389},
+  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{rfc8216,
   series       = {Request for Comments},
   number       = 8216,
@@ -495,7 +533,7 @@
   note         = {[Online; accessed 05-April-2023]}
 }
 
-@misc{wiki:PeerTube,
+ @misc{wiki:PeerTube,
   author       = {Wikipedia},
   title        = {{PeerTube} --- {W}ikipedia{,} The Free Encyclopedia},
   year         = {2025},
@@ -519,7 +557,7 @@
   note         = {[Accessed 08-Mar-2023]}
 }
 
- @misc{wikipediaTwitchservice,
+@misc{wikipediaTwitchservice,
   author       = {},
   title        = {{T}witch (service) - {W}ikipedia --- en.wikipedia.org},
   howpublished = {\url{https://en.wikipedia.org/wiki/Twitch_(service)}},