% % This file was created by the TYPO3 extension % bib % --- Timezone: CET % Creation date: 2024-03-29 % Creation time: 11-44-54 % --- Number of references % 62 % @Techreport { draft-irtf-coinrg-use-cases-02, title = {Use Cases for In-Network Computing}, year = {2022}, month = {3}, number = {draft-irtf-coinrg-use-cases-02}, note = {expires: 8 September 2022 (work in progress)}, url = {https://www.comsys.rwth-aachen.de/fileadmin/papers/2022/draft-irtf-coinrg-use-cases-02.pdf}, web_url = {https://datatracker.ietf.org/doc/draft-irtf-coinrg-use-cases/}, misc2 = {Online}, publisher = {IETF Trust}, series = {Internet Drafts}, organization = {Internet Engineering Task Force}, institution = {Internet Engineering Task Force}, author = {Kunze, Ike and Wehrle, Klaus and Trossen, Dirk and Montpetit, Marie-Jos{\'e} and de Foy, Xavier and Griffin, David and Rio, Miguel} } @Techreport { draft-kunze-coinrg-transport-issues-05, title = {Transport Protocol Issues of In-Network Computing Systems}, year = {2021}, month = {10}, number = {draft-kunze-coinrg-transport-issues-05}, note = {Expires: 28 April 2022 (work in progress)}, url = {https://www.comsys.rwth-aachen.de/fileadmin/papers/2022/draft-kunze-coinrg-transport-issues-05.pdf}, web_url = {https://datatracker.ietf.org/doc/draft-kunze-coinrg-transport-issues/}, publisher = {IETF Trust}, series = {Internet Drafts}, organization = {Internet Engineering Task Force}, institution = {Internet Engineering Task Force}, author = {Kunze, Ike and Wehrle, Klaus and Trossen, Dirk} } @Techreport { 2019-rueth-blitzstart, title = {Blitz-starting QUIC Connections}, year = {2019}, month = {5}, day = {8}, number2 = {arXiv:1905.03144 [cs.NI]}, pages = {1--8}, url = {https://www.comsys.rwth-aachen.de/fileadmin/papers/2019/2019-rueth-blitzstart.pdf}, web_url = {https://arxiv.org/abs/1905.03144}, misc2 = {Online}, publisher = {COMSYS, RWTH Aachen University}, address = {Ahornstr. 55, 52074 Aachen, Germany}, institution = {COMSYS, RWTH Aachen University}, type = {Technical Report}, language = {en}, author = {R{\"u}th, Jan and Wolsing, Konrad and Serror, Martin and Wehrle, Klaus and Hohlfeld, Oliver} } @Techreport { 2019-hohlfeld-santa-tr, title = {Application-Agnostic Offloading of Packet Processing}, year = {2019}, month = {4}, day = {1}, number2 = {arXiv:1904.00671 [cs.NI]}, pages = {1--14}, tags = {maki}, url = {https://www.comsys.rwth-aachen.de/fileadmin/papers/2019/2019-hohlfeld-santatr.pdf}, web_url = {https://arxiv.org/abs/1904.00671}, misc2 = {Online}, publisher = {COMSYS, RWTH Aachen University}, address = {Ahornstr. 55, 52074 Aachen, Germany}, institution = {COMSYS, RWTH Aachen University}, type = {Technical Report}, language = {en}, author = {Hohlfeld, Oliver and Reelfs, Helge and R{\"u}th, Jan and Schmidt, Florian and Zimmermann, Torsten and Hiller, Jens and Wehrle, Klaus} } @Techreport { 2016-henze-aib-sensorcloud, title = {The SensorCloud Protocol: Securely Outsourcing Sensor Data to the Cloud}, year = {2016}, month = {7}, day = {11}, number = {AIB-2016-06}, number2 = {arXiv:1607.03239 [cs.NI]}, pages = {1--24}, tags = {sensorcloud}, url = {fileadmin/papers/2016/2016-henze-aib-sensorcloud.pdf}, misc2 = {Online}, publisher = {Department of Computer Science, RWTH Aachen University}, address = {Ahornstr. 55, 52074 Aachen, Germany}, institution = {Department of Computer Science, RWTH Aachen University}, type = {Technical Report}, language = {en}, ISSN = {0935-3232}, author = {Henze, Martin and Hummen, Ren{\'e} and Matzutt, Roman and Wehrle, Klaus} } @Techreport { 2015-draft-moskowitz-hip-dex-04, title = {HIP Diet EXchange (DEX)}, year = {2015}, month = {7}, day = {20}, number = {draft-moskowitz-hip-dex-04}, abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIPv2. The HIP DEX protocol is primarily designed for computation or memory-constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-04}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Moskowitz, Robert and Hummen, Ren{\'e}} } @Techreport { 2015-draft-moskowitz-hip-dex-03, title = {HIP Diet EXchange (DEX)}, year = {2015}, month = {6}, day = {19}, number = {draft-moskowitz-hip-dex-03}, abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIPv2. The HIP DEX protocol is primarily designed for computation or memory-constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-03}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Moskowitz, Robert and Hummen, Ren{\'e}} } @Techreport { 2014-draft-moskowitz-hip-dex-02, title = {HIP Diet EXchange (DEX)}, year = {2014}, month = {12}, day = {19}, number = {draft-moskowitz-hip-dex-02}, abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIPv2. The HIP DEX protocol is primarily designed for computation or memory-constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-02}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Moskowitz, Robert and Hummen, Ren{\'e}} } @Techreport { 2015-aib-schmidt-hotbox, title = {HotBox: Testing Temperature Effects in Sensor Networks}, year = {2014}, month = {12}, day = {4}, number = {AIB-2014-14}, number2 = {arXiv:1412.2257 [cs.NI]}, pages = {1--17}, tags = {senserr}, url = {fileadmin/papers/2014/2014-schmidt-aib-hotbox.pdf}, misc2 = {Online}, publisher = {Department of Computer Science, RWTH Aachen}, address = {Ahornstr. 55, 52074 Aachen, Germany}, institution = {Department of Computer Science, RWTH Aachen}, type = {Technical Report}, language = {en}, ISSN = {0935-3232}, author = {Schmidt, Florian and Ceriotti, Matteo and Hauser, Niklas and Wehrle, Klaus} } @Techreport { 2014-draft-moskowitz-hip-dex-01, title = {HIP Diet EXchange (DEX)}, year = {2014}, month = {3}, day = {4}, number = {draft-moskowitz-hip-dex-01}, abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the HIP Base EXchange (HIP BEX) [rfc5201-bis]. The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIP BEX. The HIP DEX protocol is primarily targeted at computation or memory-constrained sensor devices. Like HIP BEX, it is expected to be used together with another suitable security protocol such as the Encapsulated Security Payload (ESP) [rfc5202-bis] for the protection of upper layer protocols. HIP DEX can also be used as a keying mechanism for a MAC layer security protocol as is supported by IEEE 802.15.4 [IEEE.802-15-4.2011].}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-01}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Moskowitz, Robert and Hummen, Ren{\'e}} } @Techreport { 2013-schmidt-rtp-extended, title = {Support for Error Tolerance in the Real-Time Transport Protocol}, year = {2013}, month = {12}, day = {20}, number = {AIB-2013-19}, number2 = {arXiv:1312.5892 [cs.NI]}, pages = {1--24}, tags = {refector}, url = {fileadmin/papers/2013/2013-schmidt-aib-rtp.pdf}, misc2 = {Online}, publisher = {Department of Computer Science, RWTH Aachen}, address = {Ahornstr. 55, 52074 Aachen, Germany}, institution = {Department of Computer Science, RWTH Aachen}, type = {Technical Report}, language = {en}, ISSN = {0935-3232}, author = {Schmidt, Florian and Orlea, David and Wehrle, Klaus} } @Techreport { 2013-draft-hummen-dtls-extended-session-resumption-01, title = {Extended DTLS Session Resumption for Constrained Network Environments}, year = {2013}, month = {10}, day = {18}, number = {draft-hummen-dtls-extended-session-resumption-01}, abstract = {This draft defines two extensions for the existing session resumption mechanisms of TLS that specifically apply to Datagram TLS (DTLS) in constrained network environments. Session resumption type negotiation enables the client and the server to explicitly agree on the session resumption mechanism for subsequent handshakes, thus avoiding unnecessary overheads occurring with the existing specifications. Session resumption without client-side state additionally enables a constrained DTLS client to resume a session without the need to maintain state while the session is inactive. The extensions defined in this draft update [RFC5077] and [RFC5246].}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-hummen-dtls-extended-session-resumption-01}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Hummen, Ren{\'e} and Gilger, Johannes and Shafagh, Hossein} } @Techreport { 2013-ceriotti-fgsn-appcentric, title = {Towards Application-Centric Deployment of Low-Power Wireless Networks}, year = {2013}, month = {9}, day = {13}, number = {SEEMOO-TR-2013-0}, number2 = {12. GI/ITG KuVS Fachgespr{\"a}ch ''Drahtlose Sensornetze''}, institution = {TU Cottbus}, type = {Technical Report}, author = {Ceriotti, Matteo and Krylovskiy, Alexandr and Wehrle, Klaus} } @Techreport { 2013-draft-garcia-core-security-06, title = {Security Considerations in the IP-based Internet of Things}, year = {2013}, month = {9}, day = {11}, number = {draft-garcia-core-security-06}, abstract = {A direct interpretation of the Internet of Things concept refers to the usage of standard Internet protocols to allow for human-to-thing or thing-to-thing communication. Although the security needs are well-recognized, it is still not fully clear how existing IP-based security protocols can be applied to this new setting. This Internet-Draft first provides an overview of security architecture, its deployment model and general security needs in the context of the lifecycle of a thing. Then, it presents challenges and requirements for the successful roll-out of new applications and usage of standard IP-based security protocols when applied to get a functional Internet of Things.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-garcia-core-security-06}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Garcia-Morchon, Oscar and Keoh, Sye Loong and Kumar, Sandeep S. and Hummen, Ren{\'e} and Struik, Ren{\'e}} } @Techreport { draft-hummen-dtls-extended-session-resumption-00, title = {Extended DTLS Session Resumption for Constrained Network Environments}, year = {2013}, month = {7}, day = {15}, number = {draft-hummen-dtls-extended-session-resumption-00}, abstract = {This draft defines two extensions for the existing session resumption mechanisms of TLS that specifically apply to Datagram TLS (DTLS) in constrained network environments. Session resumption type negotiation enables the client and the server to explicitly agree on the session resumption mechanism for subsequent handshakes, thus avoiding unnecessary overheads occurring with the existing specifications. Session resumption without client-side state additionally enables a constrained DTLS client to resume a session without the need to maintain state while the session is inactive. The extensions defined in this draft update [RFC5077] and [RFC5246].}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-hummen-dtls-extended-session-resumption-00}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Hummen, Ren{\'e} and Gilger, Johannes} } @Techreport { 2013-draft-garcia-core-security-05, title = {Security Considerations in the IP-based Internet of Things}, year = {2013}, month = {3}, day = {11}, number = {draft-garcia-core-security-05}, abstract = {A direct interpretation of the Internet of Things concept refers to the usage of standard Internet protocols to allow for human-to-thing or thing-to-thing communication. Although the security needs are well-recognized, it is still not fully clear how existing IP-based security protocols can be applied to this new setting. This Internet-Draft first provides an overview of security architecture, its deployment model and general security needs in the context of the lifecycle of a thing. Then, it presents challenges and requirements for the successful roll-out of new applications and usage of standard IP-based security protocols when applied to get a functional Internet of Things.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-garcia-core-security-05}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Garcia-Morchon, Oscar and Keoh, Sye Loong and Kumar, Sandeep S. and Hummen, Ren{\'e} and Struik, Ren{\'e}} } @Techreport { 2013-draft-hummen-hip-middle-puzzle-01, title = {HIP Middlebox Puzzle Offloading and End-host Notification}, year = {2013}, month = {1}, day = {9}, number = {draft-hummen-hip-middle-puzzle-01}, abstract = {The Host Identity Protocol [RFC5201] is a secure signaling protocol with a cryptographic namespace. It provides the communicating peers with a cryptographic puzzle mechanism to protect against Denial of Service (DoS) attacks exploiting the computation and memory overheads of the protocol exchange. This document specifies an extension of the protocol that enables an on-path network entity to assist in the choice of the puzzle difficulty in case of an attack. Furthermore, it defines a modification of the puzzle mechanism that enables a host to delegate puzzle solving to an on-path network entity.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-hummen-hip-middle-puzzle-01}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Hummen, Ren{\'e} and Henze, Martin and Hiller, Jens} } @Techreport { 2012-weingaertner-fgsn-sim-iot, title = {How to simulate the Internet of Things?}, year = {2012}, month = {9}, day = {26}, number = {SEEMOO-TR-2012-0}, booktitle = {11. GI/ITG KuVS Fachgespr{\"a}ch ''Drahtlose Sensornetze''}, institution = {TU Darmstadt}, type = {Sammelband der Beitr{\"a}ge zum 11. GI/ITG KuVS Fachgespr{\"a}ch ''Drahtlose Sensornetze'' (Technical Report)}, author = {Weingaertner, Elias and Ceriotti, Matteo and Wehrle, Klaus} } @Techreport { 2012-draft-hummen-hip-middle-puzzle, title = {HIP Middlebox Puzzle Offloading and End-host Notification}, year = {2012}, month = {7}, day = {9}, number = {draft-hummen-hip-middle-puzzle-00}, abstract = {The Host Identity Protocol [RFC5201] is a secure signaling protocol with a cryptographic namespace. It provides the communicating peers with a cryptographic puzzle mechanism to protect against Denial of Service (DoS) attacks targeting its computation and memory overhead. This document specifies an extension that enables middleboxes to assist in the choice of the puzzle difficulty as well as in solving the puzzle on behalf of the host.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-hummen-hip-middle-puzzle-00}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Hummen, Ren{\'e} and Henze, Martin} } @Techreport { 2012-draft-garcia-core-security, title = {Security Considerations in the IP-based Internet of Things}, year = {2012}, month = {3}, day = {26}, number = {draft-garcia-core-security-04}, abstract = {A direct interpretation of the Internet of Things concept refers to the usage of standard Internet protocols to allow for human-to-thing or thing-to-thing communication. Although the security needs are well-recognized, it is still not fully clear how existing IP-based security protocols can be applied to this new setting. This Internet-Draft first provides an overview of security architecture, its deployment model and general security needs in the context of the lifecycle of a thing. Then, it presents challenges and requirements for the successful roll-out of new applications and usage of standard IP-based security protocols when applied to get a functional Internet of Things.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-garcia-core-security-04}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Garcia-Morchon, Oscar and Keoh, Sye Loong and Kumar, Sandeep S. and Hummen, Ren{\'e} and Struik, Ren{\'e}} } @Techreport { 2011-draft-garcia-core-security-03, title = {Security Considerations in the IP-based Internet of Things}, year = {2011}, month = {10}, day = {31}, number = {draft-garcia-core-security-03}, abstract = {A direct interpretation of the Internet of Things concept refers to the usage of standard Internet protocols to allow for human-to-thing or thing-to-thing communication. Although the security needs are well-recognized, it is still not fully clear how existing IP-based security protocols can be applied to this new setting. This Internet-Draft first provides an overview of security architecture, its deployment model and general security needs in the context of the lifecycle of a thing. Then, it presents challenges and requirements for the successful roll-out of new applications and usage of standard IP-based security protocols when applied to get a functional Internet of Things.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-garcia-core-security-03}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Garcia-Morchon, Oscar and Keoh, Sye Loong and Kumar, Sandeep S. and Hummen, Ren{\'e} and Struik, Ren{\'e}} } @Techreport { 2011-draft-garcia-core-security-02, title = {Security Considerations in the IP-based Internet of Things}, year = {2011}, month = {7}, day = {11}, number = {draft-garcia-core-security-02}, abstract = {A direct interpretation of the Internet of Things concept refers to the usage of standard Internet protocols to allow for human-to-thing or thing-to-thing communication. Although the security needs are well-recognized, it is still not fully clear how existing IP-based security protocols can be applied to this new setting. This Internet-Draft first provides an overview of security architecture, its deployment model and general security needs in the context of the lifecycle of a thing. Then, it presents challenges and requirements for the successful roll-out of new applications and usage of standard IP-based security protocols when applied to get a functional Internet of Things.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-garcia-core-security-02}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Garcia-Morchon, Oscar and Keoh, Sye Loong and Kumar, Sandeep S. and Hummen, Ren{\'e} and Struik, Ren{\'e}} } @Techreport { rfc6253, title = {{Host Identity Protocol Certificates}}, year = {2011}, month = {5}, number = {rfc6253}, abstract = {The Certificate (CERT) parameter is a container for digital certificates. It is used for carrying these certificates in Host Identity Protocol (HIP) control packets. This document specifies the CERT parameter and the error signaling in case of a failed verification. Additionally, this document specifies the representations of Host Identity Tags in X.509 version 3 (v3) and Simple Public Key Infrastructure (SPKI) certificates. The concrete use of certificates, including how certificates are obtained, requested, and which actions are taken upon successful or failed verification, is specific to the scenario in which the certificates are used. Hence, the definition of these scenario- specific aspects is left to the documents that use the CERT parameter.}, tags = {mobile_access}, url = {http://www.ietf.org/rfc/rfc6253.txt}, publisher = {IETF}, howpublished = {RFC 6253 (Experimental)}, series = {Request for Comments}, organization = {Internet Engineering Task Force}, institution = {Internet Engineering Task Force}, type = {Request For Commments (Experimental Standard)}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { 2011-draft-garcia-core-security-01, title = {Security Considerations in the IP-based Internet of Things}, year = {2011}, month = {3}, day = {14}, number = {draft-garcia-core-security-01}, abstract = {A direct interpretation of the Internet of Things concept refers to the usage of standard Internet protocols to allow for human-to-thing or thing-to-thing communication. Although the security needs are well-recognized, it is still not fully clear how existing IP-based security protocols can be applied to this new setting. This Internet-Draft first provides an overview of security architecture, its deployment model and general security needs in the context of the lifecycle of a thing. Then, it presents challenges and requirements for the successful roll-out of new applications and usage of standard IP-based security protocols when applied to get a functional Internet of Things.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-garcia-core-security-01}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Garcia-Morchon, Oscar and Keoh, Sye Loong and Kumar, Sandeep S. and Hummen, Ren{\'e} and Struik, Ren{\'e}} } @Techreport { 2011-draft-garcia-core-security-00, title = {Security Considerations in the IP-based Internet of Things}, year = {2011}, month = {3}, day = {7}, number = {draft-garcia-core-security-00}, abstract = {A direct interpretation of the Internet of Things concept refers to the usage of standard Internet protocols to allow for human-to-thing or thing-to-thing communication. Although the security needs are well-recognized, it is still not fully clear how existing IP-based security protocols can be applied to this new setting. This Internet-Draft first provides an overview of security architecture, its deployment model and general security needs in the context of the lifecycle of a thing. Then, it presents challenges and requirements for the successful roll-out of new applications and usage of standard IP-based security protocols when applied to get a functional Internet of Things.}, note = {Work in progress}, tags = {iotsec; ietf}, url = {http://tools.ietf.org/html/draft-garcia-core-security-00}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Garcia-Morchon, Oscar and Keoh, Sye Loong and Kumar, Sandeep S. and Hummen, Ren{\'e} and Struik, Ren{\'e}} } @Techreport { rfc5201-bis-04, title = {{Host Identity Protocol Version 2}}, year = {2011}, month = {1}, volume = {1}, number = {draft-ietf-hip-rfc5201-bis-04.txt}, note = {{expires: July 24, 2011 (work in progress)}}, tags = {mobile_access}, url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-04}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-04}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Moskowitz, Robert and Jokela, Petri and Henderson, Thomas R. and Heer, Tobias} } @Techreport { draft-ietf-hip-cert-08, title = {{Host Identity Protocol Certificates}}, year = {2011}, month = {1}, volume = {1}, number = {draft-ietf-hip-cert-08.txt}, note = {{expires: July 22, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-08}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-08}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { draft-ietf-hip-cert-07, title = {{Host Identity Protocol Certificates}}, year = {2011}, month = {1}, volume = {1}, number = {draft-ietf-hip-cert-07.txt}, note = {{expires: July 16, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-07}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-07}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { draft-ietf-hip-cert-09, title = {{Host Identity Protocol Certificates}}, year = {2011}, month = {1}, volume = {1}, number = {draft-ietf-hip-cert-09.txt}, pages = {1}, note = {{expires: July 22, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-09}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-09}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { 2011-heer-draft-middle-auth, title = {End-Host Authentication for HIP Middleboxes (Version 4)}, year = {2011}, number = {draft-heer-hip-middle-auth-04}, abstract = {The Host Identity Protocol [RFC5201] is a signaling protocol for secure communication, mobility, and multihoming that introduces a cryptographic namespace. This document specifies an extension for HIP that enables middleboxes to unambiguously verify the identities of hosts that communicate across them. This extension allows middleboxes to verify the liveness and freshness of a HIP association and, thus, to secure access control in middleboxes.}, note = {Work in progress}, tags = {ietf, mobile_access}, url = {http://tools.ietf.org/html/draft-heer-hip-middle-auth-04}, misc2 = {Online}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, language = {en}, author = {Heer, Tobias and Komu, Miika and Hummen, Ren{\'e} and Wehrle, Klaus} } @Techreport { draft-ietf-hip-cert-06, title = {{Host Identity Protocol Certificates}}, year = {2010}, month = {11}, volume = {1}, number = {draft-ietf-hip-cert-06.txt}, note = {{expires: May 23, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-06}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-06}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { draft-ietf-hip-cert-05, title = {{Host Identity Protocol Certificates}}, year = {2010}, month = {11}, volume = {1}, number = {draft-ietf-hip-cert-05.txt}, note = {{expires: May 12, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-05}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-05}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { rfc5201-bis-03, title = {{Host Identity Protocol Version 2}}, year = {2010}, month = {10}, volume = {1}, number = {draft-ietf-hip-rfc5201-bis-03.txt}, note = {{expires: April 26, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-03}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-03}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias} } @Techreport { draft-ietf-hip-cert-04, title = {{Host Identity Protocol Certificates}}, year = {2010}, month = {9}, volume = {1}, number = {draft-ietf-hip-cert-04.txt}, note = {{expires: March 27, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-04}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-04}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { rfc5201-bis-01, title = {{Host Identity Protocol Version 2}}, year = {2010}, month = {9}, volume = {1}, number = {draft-ietf-hip-rfc5201-bis-01.txt}, note = {{expires: March 7, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-01}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-01}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias} } @Techreport { moskowitz-rfc5201-bis-02, title = {{Host Identity Protocol Version 2}}, year = {2010}, month = {7}, volume = {1}, number = {draft-moskowitz-hip-rfc5201-bis-02.txt}, note = {{expires: January 2, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-moskowitz-hip-rfc5201-bis-02}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-moskowitz-hip-rfc5201-bis-02}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias} } @Techreport { rfc5201-bis-02, title = {{Host Identity Protocol Version 2}}, year = {2010}, month = {7}, volume = {1}, number = {draft-ietf-hip-rfc5201-bis-02.txt}, note = {{expires: March 7, 2011 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-02}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-02}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias} } @Techreport { draft-ietf-hip-cert-03, title = {{Host Identity Protocol Certificates}}, year = {2010}, month = {4}, volume = {1}, number = {draft-ietf-hip-cert-03.txt}, note = {{expires: October 30, 2010 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-03}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-03}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { moskowitz-rfc5201-bis-01, title = {{Host Identity Protocol Version 2}}, year = {2010}, month = {3}, volume = {1}, number = {draft-moskowitz-hip-rfc5201-bis-01.txt}, note = {{expires: September 10, 2010 (work in progress)}}, url = {http://tools.ietf.org/html/draft-moskowitz-hip-rfc5201-bis-01}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-moskowitz-hip-rfc5201-bis-01}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Moskowitz Pekka Nikander, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias} } @Techreport { draft-ietf-hip-cert-02, title = {{Host Identity Protocol Certificates}}, year = {2009}, month = {10}, volume = {1}, number = {draft-ietf-hip-cert-02.txt}, note = {{expires: April 29, 2010 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-02}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-02}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { 200908munawarfgsndynamictinyos, title = {Remote Incremental Adaptation of Sensor Network Applications}, year = {2009}, month = {9}, pages = {9-12}, url = {fileadmin/papers/2009/2009-08-munawar-fgsn-dynamic-tinyos.pdf}, web_url = {http://doku.b.tu-harburg.de/volltexte/2009/581/pdf/proceedings.pdf}, misc2 = {Print}, publisher = {Technical University Hamburg}, address = {Technical University Hamburg}, booktitle = {Proceedings of the 8th GI/ITG KuVS Fachgespr{\"a}ch ''Wireless Sensor Networks'', Hamburg, Germany}, institution = {Technical University Hamburg}, language = {en}, author = {Munawar, Waqaas and Landsiedel, Olaf and Alizai, Muhammad Hamad and Wehrle, Klaus} } @Techreport { 200908alizaifgsnburstyrouting, title = {Routing Over Bursty Wireless Links}, year = {2009}, month = {9}, pages = {63-66}, abstract = {Accurate estimation of link quality is the key to enable efficient routing in wireless sensor networks. Current link estimators focus mainly on identifying long-term stable links for routing, leaving out a potentiality large set of intermediate links offering significant routing progress. Fine-grained analysis of link qualities reveals that such intermediate links are bursty, i.e., stable in the short term. In this paper, we use short-term estimation of wireless links to accurately identify short-term stable periods of transmission on bursty links. Our approach allows a routing protocol to forward packets over bursty links if they offer better routing progress than long-term stable links. We integrate a Short Term Link Estimator and its associated routing strategy with a standard routing protocol for sensor networks. Our evaluation reveals an average of 22\% reduction in the overall transmissions when routing over long-range bursty links. Our approach is not tied to any special routing protocol and integrates seamlessly with existing routing protocols and link estimators.}, tags = {wld}, url = {fileadmin/papers/2009/2009-08-alizai-fgsn-bursty-routing.pdf}, web_url = {doku.b.tu-harburg.de/volltexte/2009/581/pdf/proceedings.pdf}, misc2 = {Print}, publisher = {Technical University Hamburg}, address = {Technical University Hamburg}, booktitle = {Proceedings of the 8th GI/ITG KuVS Fachgespr{\"a}ch ''Wireless Sensor Networks'', Hamburg, Germany}, language = {en}, reviewed = {1}, author = {Alizai, Muhammad Hamad and Landsiedel, Olaf and Bitsch Link, J{\'o} Agila and G{\"o}tz, Stefan and Wehrle, Klaus} } @Techreport { draft-ietf-hip-cert-01, title = {{Host Identity Protocol Certificates}}, year = {2009}, month = {6}, volume = {1}, number = {draft-ietf-hip-cert-01.txt}, note = {{expires: January 2, 2010 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-01}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-01}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { 2009-heer-draft-midauth, title = {End-Host Authentication for HIP Middleboxes (Version 2)}, year = {2009}, number = {draft-heer-hip-midauth-02}, abstract = {The Host Identity Protocol is a signaling protocol for secure communication, mobility, and multihoming. It achieves these properties by introducing a new cryptographic namespace. This document specifies an extension for HIP that enables middleboxes to unambiguously verify the identities of hosts that communicate across them. This extension enables middleboxes to verify the liveness and freshness of a HIP association and, thus, enables reliable and secure access control in middleboxes.}, note = {Work in progress}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Heer, Tobias and Komu, Miika and Wehrle, Klaus} } @Techreport { 2009-heer-draft-service-id, title = {Service Identifiers for HIP}, year = {2009}, number = {draft-heer-hip-service-00}, abstract = {The Host Identity Protocol is a signaling protocol for secure communication, mobility, and multihoming that introduces a cryptographic namespace. This document specifies an extension for HIP that enables HIP end-hosts and HIP-aware middleboxes to announce services to HIP hosts during a HIP Base EXchange (BEX) or HIP update. Service providers are able to specify the type and requirements of a service; clients can then decide to agree on the terms of service. This allows the service provider to verify the accordance of the client with the service conditions while the client is able to verify the authenticity of the used service.}, note = {Work in progress}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Heer, Tobias and Varjonen, Samu and Wirtz, Hanno} } @Techreport { draft-ietf-hip-cert-00, title = {{Host Identity Protocol Certificates}}, year = {2008}, month = {10}, volume = {1}, number = {draft-ietf-hip-cert-00.txt}, note = {{expires: January 2, 2010 (work in progress)}}, url = {http://tools.ietf.org/html/draft-ietf-hip-cert-00}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-00}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { 2008-fgsn-sasnauskas-kleenet, title = {Bug Hunting in Sensor Network Applications}, year = {2008}, month = {9}, abstract = {Testing sensor network applications is an essential and a difficult task. Due to their distributed and faulty nature, severe resource constraints, unobservable interactions, and limited human interaction, sensor networks, make monitoring and debugging of applications strenuous and more challenging. In this paper we present KleeNet - a Klee based platform independent bug hunting tool for sensor network applications before deployment - which can automatically test applications for all possible inputs, and hence, ensures memory safety for TinyOS based applications. Upon finding a bug, KleeNet generates a concrete test case with real input values identifying a specific error path in a program. Additionally, we show that KleeNet integrates well into TinyOS application development life cycle with minimum manual effort, making it easy for developers to test their applications.}, tags = {kleenet}, url = {fileadmin/papers/2008/2008-09-Sasnauskas-FGSN08-BugHunting.pdf}, web_url = {ftp://ftp.inf.fu-berlin.de/pub/reports/tr-b-08-12.pdf}, misc2 = {Print}, publisher = {Freie Universit{\"a}t Berlin, Institute of Computer Science}, address = {Berlin, Germany}, booktitle = {Proceedings of the 7th GI/ITG Fachgespraech Wireless Sensor Networks, Berlin, Germany}, institution = {Chair of Communication and Distributed Systems (ComSys)}, language = {en}, reviewed = {1}, author = {Sasnauskas, Raimondas and Bitsch Link, J{\'o} Agila and Alizai, Muhammad Hamad and Wehrle, Klaus} } @Techreport { draft-varjonen-hip-cert-01, title = {{Host Identity Protocol Certificates}}, year = {2008}, month = {7}, volume = {1}, number = {draft-varjonen-hip-cert-01.txt}, note = {{expires: January 15, 2009 (work in progress)}}, url = {http://tools.ietf.org/html/draft-varjonen-hip-cert-01}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-varjonen-hip-cert-01}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, reviewed = {1}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { 2008-fgsn-alizai-stle, title = {Challenges in Short-term Wireless Link Quality Estimation}, year = {2008}, month = {7}, pages = {27-30}, tags = {wld}, url = {fileadmin/papers/2008/2008-08-alizai-fgsn-stle.pdf}, web_url = {ftp://ftp.inf.fu-berlin.de/pub/reports/tr-b-08-12.pdf}, misc2 = {Print}, publisher = {Fachbereich Mathematik und Informatik}, address = {Berlin, Germany}, booktitle = {Proceedings of the 7th GI/ITG Workshop on Wireless Sensor Networks}, event_name = {FGSN 08}, event_date = {September 2010}, language = {en}, reviewed = {1}, author = {Alizai, Muhammad Hamad and Landsiedel, Olaf and Wehrle, Klaus and Becher, Alexander} } @Techreport { draft-varjonen-hip-cert-00, title = {{Host Identity Protocol Certificates}}, year = {2008}, month = {2}, volume = {1}, number = {draft-varjonen-hip-cert-01.txt}, note = {{expires: August 21, 2008 (work in progress)}}, url = {http://tools.ietf.org/html/draft-varjonen-hip-cert-00}, misc2 = {Online}, publisher = {{IETF Trust}}, howpublished = {An online version is available at: http://tools.ietf.org/html/draft-varjonen-hip-cert-01}, series = {Internet Drafts}, organization = {{Internet Engineering Task Force}}, institution = {Internet Engineering Task Force}, language = {en}, author = {Heer, Tobias and Varjonen, Samu} } @Techreport { 200807VOMLEHNAIB200816NetworkSimulatorComparison, title = {Comparing recent network simulators: A performance evaluation study}, journal = {Aachener Informatik Berichte}, year = {2008}, volume = {2008-16}, number = {AIB 2008-16}, pages = {1-28}, abstract = {Ranging from the development of new protocols to validating analytical performance metrics, network simulation is the most prevalent methodology in the field of computer network research. While the well known ns-2 toolkit has established itself as the quasi standard for network simulation, the successors are on their way. In this paper, we first survey recent contributions in the field of network simulation tools as well as related aspects such as parallel network simulation. Moreover, we present preliminary results which compare the resource demands for ns-3, JiST, SimPy and OMNeT++ by implementing the identical simulation scenario in all these network simulation tools.}, url = {https://www.comsys.rwth-aachen.de/fileadmin/papers/2008/AIB-2008-16.pdf}, misc2 = {Online}, address = {Ahornstr. 55, Aachen, Germany}, institution = {RWTH Aachen University}, type = {Technical Report}, ISSN = {0935-3232}, author = {vom Lehn, Hendrik and Weingaertner, Elias and Wehrle, Klaus} } @Techreport { 2008-heer-draft-cert-2, title = {HIP Certificates (Version 0)}, year = {2008}, abstract = {This document specifies a certificate parameter called CERT for the Host Identity Protocol (HIP). The CERT parameter is a container for Simple Public Key Infrastructure (SPKI) and X.509 certificates. It is used for carrying these certificates in HIP control messages. Additionally, this document specifies the representations of Host Identity Tags in SPKI certificates.}, note = {Work in progress}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Varjonen, Samu and Heer, Tobias} } @Techreport { 2008-heer-draft-midauth, title = {End-Host Authentication for HIP Middleboxes (Version 1)}, year = {2008}, number = {draft-heer-hip-midauth-01}, abstract = {The Host Identity Protocol is a signaling protocol for secure communication, mobility, and multihoming. It achieves these properties by introducing a new cryptographic namespace. This document specifies an extension for HIP that enables middleboxes to unambiguously verify the identities of hosts that communicate across them. This extension enables middleboxes to verify the liveness and freshness of a HIP association and, thus, enables reliable and secure access control in middleboxes.}, note = {Work in progress}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Heer, Tobias and Komu, Miika and Wehrle, Klaus} } @Techreport { 2008-heer-draft-cert, title = {HIP Certificates (Version 1)}, year = {2008}, abstract = {This document specifies a certificate parameter called CERT for the Host Identity Protocol (HIP). The CERT parameter is a container for Simple Public Key Infrastructure (SPKI) and X.509 certificates. It is used for carrying these certificates in HIP control messages. Additionally, this document specifies the representations of Host Identity Tags in SPKI certificates.}, note = {draft-varjonen-hip-cert-01.txt. Work in progress.}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Varjonen, Samu and Heer, Tobias} } @Techreport { 2007-fgsn-alizai-timetossim, title = {Accurate Timing in Sensor Network Simulations}, year = {2007}, month = {7}, url = {fileadmin/papers/2008/2007-07-fgsn-alizai-accurate-timing.pdf}, web_url = {https://www.ds-group.info/events/fgsn07/fgsn07proc.pdf}, misc2 = {Print}, publisher = {RWTH Aachen}, address = {Aachen, Germany}, booktitle = {Proceedings of the 6th GI/ITG KuVS Workshop on Wireless Sensor Networks (FGSN 07)}, institution = {RWTH Aachen}, event_place = {Aachen, Germany}, event_name = {FGSN 07}, event_date = {July 2007}, language = {en}, author = {Alizai, Muhammad Hamad and Landsiedel, Olaf and Wehrle, Klaus} } @Techreport { 200706WeingaertnerFGSN07HSVNPrototype, title = {A prototype study on Hybrid Sensor-Vehicular Networks}, journal = {Proceedings of the 2007 GI Special Interest Meeting (''Fachgespraech'') on Wireless Sensor Networks}, year = {2007}, pages = {1-4}, note = {Proceedings published as technical report at RWTH Aachen.}, url = {https://www.comsys.rwth-aachen.de/fileadmin/papers/2007/2007-weingaertner-kargl-fgsn.pdf}, editor = {Klaus Wehrle}, publisher = {RWTH Aachen University}, address = {Bonn, Germany}, institution = {RWTH Aachen}, event_place = {Aachen, Germany}, event_name = {Fachgespraech Sensornetzwerke}, event_date = {16.7.2007 / 17.7.2007}, type = {A prototype study on Hybrid Sensor-Vehicular Networks}, ISSN = {0935-3232}, reviewed = {1}, author = {Weingaertner, Elias and Kargl, Frank} } @Techreport { 2007-heer-draft-lhip, title = {LHIP Lightweight Authentication Extension for HIP}, year = {2007}, abstract = {This document specifies the Lightweight authentication extension forthe Host Identifier Protocol (LHIP). The goal of LHIP is to reduce the computational requirements of the Host Identifier Protocol (HIP), thus, making its benefits, such as end-host mobility and multihoming, accessible to CPU-restricted devices. LHIP reduces the computational cost of establishing, updating, and closing a HIP association by providing an alternative way of signing and verifying HIP control packets which is based on computationally inexpensive hash function computations and hash chains. However, LHIP does not provide nor does it aim at providing the same level of security as HIP does. Especially, host authentication and payload encryption are not possible. The LHIP extensions in this draft specify also mechanisms for dynamic transitioning between lightweight and full HIP associations on the fly.}, note = {Work in progress}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Heer, Tobias} } @Techreport { 200707SNFGProceedings, title = {6. Fachgespr{\"a}ch Sensornetzwerke der GI/ITG Fachgruppe ''Kommunikation und Verteilte Systeme''}, year = {2007}, number = {AIB 2007-11}, address = {Aachen, Germany}, institution = {Distributed Systems Group, RWTH Aachen University}, type = {Proceedings of Workshop}, author = {Wehrle, Klaus} } @Techreport { 2007-heer-draft-midauth, title = {End-Host Authentication for HIP Middleboxes}, year = {2007}, number = {draft-heer-hip-midauth-00}, abstract = {The Host Identity Protocol is a signaling protocol for secure communication, mobility, and multihoming. It achieves these properties by introducing a new cryptographic namespace. This document specifies an extension for HIP that enables middleboxes to unambiguously verify the identities of hosts that communicate across them. This extension enables middleboxes to verify the liveness and freshness of a HIP association and, thus, enables reliable and secure access control in middleboxes.}, note = {Work in progress}, institution = {Internet Engineering Task Force}, type = {Internet-Draft}, author = {Heer, Tobias} } @Techreport { 200608riechetrmmog, title = {Peer-to-Peer-based Infrastructure Support for Massively Multiplayer Online Games}, year = {2006}, month = {8}, number = {WSI-2006-04}, abstract = {Online games are an interesting challenge and chance for the future development of the Peer-to-Peer paradigm. Massively multiplayer online games (MMOGs) are becoming increasingly popular today. However, even high-budget titles like World of Warcraft that have gone through extensive beta-testing suffer from downtimes because of hard- and software problems. Our approach is to use structured P2P technology for the server infrastructure of MMOGs to improve their reliability and scalability. Such P2P networks are also able to adapt to the current state of the game and handle uneven distributions of the players in the game world. Another feature of our approach is being able to add supplementary servers at runtime. Our system allows using off-the-shelf PCs as infrastructure peers for participation in different game worlds as needed. Due to the nature of the Economy of Scale the same number of hosts will provide a better service than dedicated servers for each game world.}, affiliation = {RWTH Aachen University - Distributed Systems Group}, url = {http://www.rieche.net/pdf/wsi-2006-04.pdf}, misc2 = {Online}, address = {T{\"u}bingen, Germany}, institution = {Wilhelm-Schickard-Institute for Computer Science, University of T{\"u}bingen}, type = {Technical Report}, language = {en}, author = {Rieche, Simon and Fouquet, Marc and Niedermayer, Heiko and Petrak, Leo and Wehrle, Klaus and Carle, Georg} } @Techreport { 200605OCALATechReportUCB, title = {OCALA: An Architecture for Supporting Legacy Applications over Overlays}, year = {2005}, number = {UCB/CSD-005/1397}, abstract = {The ever increasing demand of new applications coupled with the increasing rigidity of the Internet has led researchers to propose overlay networks as a means of introducing new functionality in the Internet. However, despite sustained efforts, few overlays are used widely. Providing support for legacy Internet applications to access such overlays would significantly expand the user base of the overlays, as the users can instantly benefit from the overlay functionality. We present the design and implementation of OCALA, an Overlay Convergence Architecture for Legacy Applications. Unlike previous efforts, OCALA allows users to access different overlays simultaneously, as well as hosts in different overlays to communicate with each other. In addition, OCALA reduces the implementation burden on the overlay developers, by factoring out the functions commonly required to support legacy applications, such as tapping legacy traffic, authentication and encryption. Our implementation of OCALA as a proxy requires no changes to the applications or operating systems. We currently support two overlays, i3 and RON, on Linux and Windows XP/2000 platforms. We (and a few other research groups and end-users) have used the proxy over a eleven-month period with many legacy applications ranging from web browsers to remote desktop applications.}, url = {http://ocala.cs.berkeley.edu}, address = {UCB, Berkeley, USA}, institution = {University of California at Berkeley}, author = {Joseph, Dilip and Kannan, Jayanthkumar and Kubota, Ayumu and Stoica, Ion and Wehrle, Klaus} } @Techreport { 200606i3proxytechreport, title = {Supporting Legacy Applications over i3}, year = {2004}, number = {UCB/CSD-04-1342}, abstract = {Providing support for legacy applications is a crucial component of many overlay networks, as it allows end-users to instantly benefit from the functionality introduced by these overlays. This paper presents the design and implementation of a proxy-based solution to support legacy applications in the context of the i3 overlay [24]. The proxy design relies on an address virtualization technique which allows the proxy to tunnel the legacy traffic over the overlay transparently. Our solution can preserve IP packet headers on an end-to-end basis, even when end-host IP addresses change, or when endhosts live in different address spaces (e.g., behind NATs). In addition, our solution allows the use of human-readable names to refer to hosts or services, and requires no changes to applications or operating systems. To illustrate how the proxy enables legacy applications to take advantage of the overlay (i.e., i3) functionality, we present four examples: enabling access to machines behind NAT boxes, secure Intranet access, routing legacy traffic through Bro, an intrusion detection system, and anonymous web download. We have implemented the proxy on Linux andWindows XP/2000 platforms, and used it over the i3 service on PlanetLab over a three month period with a variety of legacy applications ranging from web browsers to operating system-specific file sharing.}, url = {http://i3.cs.berkeley.edu}, address = {UCB, Berkeley, USA}, institution = {University of California at Berkeley}, type = {Technical Report}, author = {Kannan, Jayanthkumar and Kubota, Ayumu and Lakshminarayanan, Karthik and Stoica, Ion and Wehrle, Klaus} }