more bibs

ESTA.bib

@@ -66,6 +66,17 @@
 }
 
 
+@manual{epi19,
+ key       = "ACN-xEPI-19",
+ title     = "ANSI E1.17-2015 (R2020), Architecture for Control Networks -
+              EPI 19. ACN Discovery on IP Networks",
+ organization = ESTA.org,
+ year      =  2020,
+ address   = "New York City",
+ note      = "TSP Document CP/2013-1018r4"
+}
+
+
 @manual{epi33,
  key       = "ACN-xEPI-33",
  title     = "ANSI E1.30-11 – 2019,

IETF.bib

@@ -1,4 +1,35 @@
-@misc{rfc4122,
+@misc{udp,
+        series =	{Request for Comments},
+        number =	768,
+        howpublished =	{RFC 768},
+        publisher =	{RFC Editor},
+        doi =		{10.17487/RFC0768},
+        url =		{https://rfc-editor.org/rfc/rfc768.txt},
+        author =	{J. Postel},
+        title =		{{User Datagram Protocol}},
+        pagetotal =	3,
+        year =		1980,
+        month =		aug,
+        abstract =	{This User Datagram  Protocol  (UDP)  is  defined  to  make  available  a datagram   mode  of  packet-switched   computer   communication  in  the environment  of  an  interconnected  set  of  computer  networks.   This protocol  assumes  that the Internet  Protocol  (IP) is used as the underlying protocol.},
+}
+
+@misc{utf8,
+        series =	{Request for Comments},
+        number =	3629,
+        howpublished =	{RFC 3629},
+        publisher =	{RFC Editor},
+        doi =		{10.17487/RFC3629},
+        url =		{https://rfc-editor.org/rfc/rfc3629.txt},
+        author =	{François Yergeau},
+        title =		{{UTF-8, a transformation format of ISO 10646}},
+        pagetotal =	14,
+        year =		2003,
+        month =		nov,
+        abstract =	{ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.},
+}
+
+
+@misc{uuid,
         series =	{Request for Comments},
         number =	4122,
         howpublished =	{RFC 4122},