@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{ASIPM,
        series =	{Request for Comments},
        number =	2365,
        howpublished =	{RFC 2365},
        publisher =	{RFC Editor},
        doi =		{10.17487/RFC2365},
        url =		{https://rfc-editor.org/rfc/rfc2365.txt},
        author =	{David Meyer},
        title =		{{Administratively Scoped IP Multicast}},
        pagetotal =	8,
        year =		1998,
        month =		jul,
        abstract =	{This document defines the "administratively scoped IPv4 multicast space" to be the range 239.0.0.0 to 239.255.255.255. In addition, it describes a simple set of semantics for the implementation of Administratively Scoped IP Multicast. Finally, it provides a mapping between the IPv6 multicast address classes {[}RFC1884{]} and IPv4 multicast address classes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.},
}


@misc{UnicastPrefixMcast,
        series =	{Request for Comments},
        number =	3306,
        howpublished =	{RFC 3306},
        publisher =	{RFC Editor},
        doi =		{10.17487/RFC3306},
        url =		{https://rfc-editor.org/rfc/rfc3306.txt},
        author =	{Brian Haberman and Brian Haberman and Dave Thaler},
        title =		{{Unicast-Prefix-based IPv6 Multicast Addresses}},
        pagetotal =	7,
        year =		2002,
        month =		sep,
        abstract =	{This specification defines an extension to the multicast addressing architecture of the IP Version 6 protocol. The extension presented in this document allows for unicast-prefix-based allocation of multicast addresses. By delegating multicast addresses at the same time as unicast prefixes, network operators will be able to identify their multicast addresses without needing to run an inter-domain allocation 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{EmbeddedRP,
        series =	{Request for Comments},
        number =	3956,
        howpublished =	{RFC 3956},
        publisher =	{RFC Editor},
        doi =		{10.17487/RFC3956},
        url =		{https://rfc-editor.org/rfc/rfc3956.txt},
        author =	{Brian Haberman and Pekka Savola},
        title =		{{Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address}},
        pagetotal =	18,
        year =		2004,
        month =		nov,
        abstract =	{This memo defines an address allocation policy in which the address of the Rendezvous Point (RP) is encoded in an IPv6 multicast group address. For Protocol Independent Multicast - Sparse Mode (PIM-SM), this can be seen as a specification of a group-to-RP mapping mechanism. This allows an easy deployment of scalable inter-domain multicast and simplifies the intra-domain multicast configuration as well. This memo updates the addressing format presented in RFC 3306. {[}STANDARDS-TRACK{]}},
}


@misc{uuid,
        series =	{Request for Comments},
        number =	4122,
        howpublished =	{RFC 4122},
        publisher =	{RFC Editor},
        doi =		{10.17487/RFC4122},
        url =		{https://rfc-editor.org/rfc/rfc4122.txt},
        author =	{Paul J. Leach and Rich Salz and Michael H. Mealling},
        title =		{{A Universally Unique IDentifier (UUID) URN Namespace}},
        pagetotal =	32,
        year =		2005,
        month =		jul,
        abstract =	{This specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation\textbackslash{}'s (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms. This specification is derived from the DCE specification with the kind permission of the OSF (now known as The Open Group). Information from earlier versions of the DCE specification have been incorporated into this document. {[}STANDARDS-TRACK{]}},
}


@misc{IPv6Addr,
        series =	{Request for Comments},
        number =	4291,
        howpublished =	{RFC 4291},
        publisher =	{RFC Editor},
        doi =		{10.17487/RFC4291},
        url =		{https://rfc-editor.org/rfc/rfc4291.txt},
        author =	{Dr. Steve E. Deering and Bob Hinden},
        title =		{{IP Version 6 Addressing Architecture}},
        pagetotal =	25,
        year =		2006,
        month =		feb,
        abstract =	{This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". {[}STANDARDS-TRACK{]}},
}


@misc{IPv6McastScope,
        series =	{Request for Comments},
        number =	7346,
        howpublished =	{RFC 7346},
        publisher =	{RFC Editor},
        doi =		{10.17487/RFC7346},
        url =		{https://rfc-editor.org/rfc/rfc7346.txt},
        author =	{Ralph Droms},
        title =		{{IPv6 Multicast Address Scopes}},
        pagetotal =	6,
        year =		2014,
        month =		aug,
        abstract =	{This document updates the definitions of IPv6 multicast scopes and therefore updates RFCs 4007 and 4291.},
}

