references-biblatex.bib

@techreport{BoschCAN,
  type = {Specification},
  title = {CAN Specification 2.0},
  key = {CAN Specification 2.0},
  month = {sep},
  year = {1991},
  address = {Stuttgart, DE},
  institution = {Robert Bosch GmbH}
}

@techreport{BoschCANFD,
  type = {Specification},
  title = {CAN with Flexible Data-Rate},
  key = {CAN with Flexible Data-Rate Version 1.0},
  month = {apr},
  year = {2011},
  address = {Gerlingen, DE},
  institution = {Robert Bosch GmbH}
}

@techreport{ISO11898,
type = {Standard},
key = {ISO 11898-1:2003(E)},
month = {dec},
year = {2003},
title = {{Road vehicles — Controller area network. Part 1: Data link layer and physical signalling}},
volume = {2003},
address = {Geneva, CH},
institution = {International Organization for Standardization}
}


@techreport{ISO15765,
type = {Standard},
key = {ISO 15765-2:2016(E)},
month = {dec},
year = {2016},
title = {{Road vehicles — Diagnostic communication over Controller Area Network (DoCAN). Part 2: Transport protocol and network layer services.}},
volume = {2016},
address = {Geneva, CH},
institution = {International Organization for Standardization}
}

@techreport{TiCANPhy,
type = {Application Report},
key = {SLLA270},
month = {jan},
year = {2008},
title = {Controller Area Network Physical Layer Requirements},
institution = {Texas Instruments}
}

@misc{rfc8200,
	series =	{Request for Comments},
	number =	8200,
	howpublished =	{RFC 8200},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC8200},
	url =		{https://rfc-editor.org/rfc/rfc8200.txt},
	author =	{Dr. Steve E. Deering and Bob Hinden},
	title =		{{Internet Protocol, Version 6 (IPv6) Specification}},
	pagetotal =	42,
	year =		2017,
	month =		jul,
	abstract =	{This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.},
}

@misc{rfc2460,
	series =	{Request for Comments},
	number =	2460,
	howpublished =	{RFC 2460},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC2460},
	url =		{https://rfc-editor.org/rfc/rfc2460.txt},
	author =	{Bob Hinden and Dr. Steve E. Deering},
	title =		{{Internet Protocol, Version 6 (IPv6) Specification}},
	pagetotal =	39,
	year =		1998,
	month =		dec,
	abstract =	{This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. {[}STANDARDS-TRACK{]}},
}

@misc{rfc1122,
	series =	{Request for Comments},
	number =	1122,
	howpublished =	{RFC 1122},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC1122},
	url =		{https://rfc-editor.org/rfc/rfc1122.txt},
	author =	{Robert T. Braden},
	title =		{{Requirements for Internet Hosts - Communication Layers}},
	pagetotal =	116,
	year =		1989,
	month =		oct,
	abstract =	{This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. {[}STANDARDS-TRACK{]}},
}

@misc{rfc791,
	series =	{Request for Comments},
	number =	791,
	howpublished =	{RFC 791},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC0791},
	url =		{https://rfc-editor.org/rfc/rfc791.txt},
	author =	{},
	title =		{{Internet Protocol}},
	pagetotal =	51,
	year =		1981,
	month =		sep,
	abstract =	{},
}

@misc{rfc4861,
	series =	{Request for Comments},
	number =	4861,
	howpublished =	{RFC 4861},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC4861},
	url =		{https://rfc-editor.org/rfc/rfc4861.txt},
	author =	{William A. Simpson and Dr. Thomas Narten and Erik Nordmark and Hesham Soliman},
	title =		{{Neighbor Discovery for IP version 6 (IPv6)}},
	pagetotal =	97,
	year =		2007,
	month =		sep,
	abstract =	{This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. {[}STANDARDS-TRACK{]}},
}

@misc{rfc6282,
	series =	{Request for Comments},
	number =	6282,
	howpublished =	{RFC 6282},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC6282},
	url =		{https://rfc-editor.org/rfc/rfc6282.txt},
	author =	{Pascal Thubert and Jonathan Hui},
	title =		{{Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks}},
	pagetotal =	24,
	year =		2011,
	month =		sep,
	abstract =	{This document updates RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks". This document specifies an IPv6 header compression format for IPv6 packet delivery in Low Power Wireless Personal Area Networks (6LoWPANs). The compression format relies on shared context to allow compression of arbitrary prefixes. How the information is maintained in that shared context is out of scope. This document specifies compression of multicast addresses and a framework for compressing next headers. UDP header compression is specified within this framework. {[}STANDARDS-TRACK{]}},
}

@misc{rfc4944,
	series =	{Request for Comments},
	number =	4944,
	howpublished =	{RFC 4944},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC4944},
	url =		{https://rfc-editor.org/rfc/rfc4944.txt},
        author =	{Gabriel Montenegro and Jonathan Hui and David Culler and Nandakishore Kushalnagar},
	title =		{{Transmission of IPv6 Packets over IEEE 802.15.4 Networks}},
	pagetotal =	30,
	year =		2007,
	month =		sep,
	abstract =	{This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes. {[}STANDARDS-TRACK{]}},
}

@misc{rfc2474,
	series =	{Request for Comments},
	number =	2474,
	howpublished =	{RFC 2474},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC2474},
	url =		{https://rfc-editor.org/rfc/rfc2474.txt},
	author =	{Fred Baker and David L. Black and Kathleen Nichols and Steven L. Blake},
	title =		{{Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers}},
	pagetotal =	20,
	year =		1998,
	month =		dec,
	abstract =	{This document defines the IP header field, called the DS (for differentiated services) field. {[}STANDARDS-TRACK{]}},
}

@misc{rfc3168,
	series =	{Request for Comments},
	number =	3168,
	howpublished =	{RFC 3168},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC3168},
	url =		{https://rfc-editor.org/rfc/rfc3168.txt},
	author =	{Sally Floyd and Dr. K. K. Ramakrishnan and David L. Black},
	title =		{{The Addition of Explicit Congestion Notification (ECN) to IP}},
	pagetotal =	63,
	year =		2001,
	month =		sep,
	abstract =	{This memo specifies the incorporation of ECN (Explicit Congestion Notification) to TCP and IP, including ECN's use of two bits in the IP header. {[}STANDARDS-TRACK{]}},
}

@misc{rfc4443,
	series =	{Request for Comments},
	number =	4443,
	howpublished =	{RFC 4443},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC4443},
	url =		{https://rfc-editor.org/rfc/rfc4443.txt},
	author =	{Mukesh Gupta and Alex Conta},
	title =		{{Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification}},
	pagetotal =	24,
	year =		2006,
	month =		mar,
	abstract =	{This document describes the format of a set of control messages used in ICMPv6 (Internet Control Message Protocol). ICMPv6 is the Internet Control Message Protocol for Internet Protocol version 6 (IPv6). {[}STANDARDS-TRACK{]}},
}

@misc{rfc5952,
	series =	{Request for Comments},
	number =	5952,
	howpublished =	{RFC 5952},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC5952},
	url =		{https://rfc-editor.org/rfc/rfc5952.txt},
	author =	{Seiichi Kawamura and Masanobu Kawashima},
	title =		{{A Recommendation for IPv6 Address Text Representation}},
	pagetotal =	14,
	year =		2010,
	month =		aug,
}

@misc{rfc4291,
	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 =	{Robert M. Hinden and Stephen E. Deering},
	title =		{{IP Version 6 Addressing Architecture}},
	pagetotal =	22,
	year =		2006,
	month =		feb,
}

@misc{rfc4862,
	series =	{Request for Comments},
	number =	4862,
	howpublished =	{RFC 4862},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC4862},
	url =		{https://rfc-editor.org/rfc/rfc4862.txt},
	author =	{Susan Thomson and Thomas Narten and Tatuya Jinmei},
	title =		{{ IPv6 Stateless Address Autoconfiguration}},
	pagetotal =	27,
	year =		2007,
	month =		sep,
}

@techreport{wachter-6lo-can-00,
	number =	{draft-wachter-6lo-can-00},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-wachter-6lo-can-00},
        author =	{Alexander Wachter},
	title =		{{IPv6 over Controller Area Network}},
	pagetotal =	17,
	year =		2019,
	month =		oct,
	day =		17,
	abstract =	{Controller Area Network (CAN) is a fieldbus initially designed for automotive applications. It is a multi-master bus with 11-bit or 29-bit frame identifiers. The CAN standard (ISO 11898 series) defines the physical and data-link layer. This document describes how to transfer IPv6 packets over CAN using ISO-TP, a dedicated addressing scheme, and IP header compression (IPHC).},
}


@ARTICLE{posix,
	author={IEEE and the Open Group},
	journal={IEEE Std 1003.1-2017 (Revision of IEEE Std 1003.1-2008)},
	title={IEEE Standard for Information Technology--Portable Operating System Interface (POSIX(R)) Base Specifications, Issue 7},
	year={2018},
	volume={},
	number={},
	pages={1-3951},
	keywords={IEEE Standards;Operating systems;Access control;Information technology;Utility programs;Synchronization;Batch production systems;Application programming interfaces;application program interface (API);argument;asynchronous;basic regular expression (BRE);batch job;batch system;built-in utility;byte;child;command language interpreter;CPU;extended regular expression (ERE);FIFO;file access control mechanism;IEEE 1003.1(TM);input/output (I/O);job control;network;parent;portable operating system interface (POSIX(R));shell;stream;string;synchronous;system;thread;X/Open System Interface (XSI)},
	doi={10.1109/IEEESTD.2018.8277153},
	ISSN={null},
	month={Jan},
	url=https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_socket.h.html
}

@misc{rfc8446,
	series =	{Request for Comments},
	number =	8446,
	howpublished =	{RFC 8446},
	publisher =	{RFC Editor},
	doi =		{10.17487/RFC8446},
	url =		{https://rfc-editor.org/rfc/rfc8446.txt},
        author =	{Eric Rescorla},
	title =		{{The Transport Layer Security (TLS) Protocol Version 1.3}},
	pagetotal =	160,
	year =		2018,
	month =		aug,
	abstract =	{This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.},
}

@INPROCEEDINGS{6296937,
	author={M. {Jung} and C. {Reinisch} and W. {Kastner}},
	booktitle={2012 Sixth International Conference on Innovative Mobile and Internet Services in Ubiquitous Computing},
	title={Integrating Building Automation Systems and IPv6 in the Internet of Things},
	year={2012},
	volume={},
	number={},
	pages={683-688},
	keywords={actuators;building management systems;home automation;Internet;IP networks;sensors;ubiquitous computing;virtual reality;building automation systems;IPv6;Internet of Things;physical objects;virtual representation;IoT;supply chains;ubiquitous computing;pervasive computing;smart building operation;sustainable building operation;BA;sensors;actuators;control devices;layered system architecture;field tier nonIP communication;twisted pair;power line;radio frequency technologies;automation tier;management tier;IPv4;de-facto standard;address space;selfconfiguration;service quality mechanisms;integration scenarios;BACnet;Buildings;Automation;IP networks;Internet;Protocols;Logic gates;Servers;Internet of Things;IPv6;Building Automation},
	doi={10.1109/IMIS.2012.134},
	ISSN={null},
	month={July},
}

@Misc{sparkplug,
  OPTkey = 	 {},
  author = 	 {Eclipse Foundation},
  title = 	 {Eclipse Sparkplug Working Group},
  howpublished = {https://sparkplug.eclipse.org/},
  month = 	 feb,
  year = 	 2020,
  OPTnote = 	 {},
  OPTannote = 	 {}
}

@Misc{canopen,
  OPTkey = 	 {},
  author = 	 {CAN in Automation},
  title = 	 {CANopen – The standardized embedded network},
  howpublished = {https://www.can-cia.org/canopen/},
  month = 	 feb,
  year = 	 2020,
  OPTnote = 	 {},
  OPTannote = 	 {}
}

@Misc{connhome,
  OPTkey = 	 {},
  author = 	 {Zigbee Alliance},
  title = 	 {Project Connected Home over IP},
  howpublished = {https://www.connectedhomeip.com/},
  month = 	 feb,
  year = 	 2020,
  OPTnote = 	 {},
  OPTannote = 	 {}
}