DOCSLIB.ORG

Deliverable D3.2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Deliverable D3.2 Ref. Ares(2016)3479770 - 15/07/2016 Converged Heterogeneous Advanced 5G Cloud-RAN Architecture for Intelligent and Secure Media Access Project no. 671704 Research and Innovation Action Co-funded by the Horizon 2020 Framework Programme of the European Union Call identifier: H2020-ICT-2014-1 Topic: ICT-14-2014 - Advanced 5G Network Infrastructure for the Future Internet Start date of project: July 1st, 2015 Deliverable D3.2 Initial 5G multi-provider v-security realization: Orchestration and Management Due date: 30/06/2016 Submission date: 15/07/2016 Deliverable leader: I2CAT Editor: Shuaib Siddiqui (i2CAT) Reviewers: Konstantinos Filis (COSMOTE), Oriol Riba (APFUT), and Michael Parker (UESSEX) Dissemination Level PU: Public PP: Restricted to other programme participants (including the Commission Services) RE: Restricted to a group specified by the consortium (including the Commission Services) CO: Confidential, only for members of the consortium (including the Commission Services) CHARISMA – D3.2 – v1.0 Page 1 of 145 List of Contributors Participant Short Name Contributor Fundació i2CAT I2CAT Shuaib Siddiqui, Amaia Legarrea, Eduard Escalona Demokritos NCSRD NCSRD Eleni Trouva, Yanos Angelopoulos APFutura APFUT Oriol Riba Innoroute INNO Andreas Foglar, Marian Ulbricht JCP-Connect JCP-C Yaning Liu University of Essex UESSEX Mike Parker, Geza Koczian, Stuart Walker Intracom ICOM Spiros Spirou, Konstantinos Katsaros, Konstantinos Chartsias, Dimitrios Kritharidis Ethernity ETH Eugene Zetserov Ericsson Ericsson Carolina Canales Altice Labs Altice Victor Marques Fraunhofer HHI HHI Kai Habel CHARISMA – D3.2 – v1.0 Page 2 of 145 Table of Contents List of Contributors ................................................................................................................ 2 1. Introduction ...................................................................................................................... 7 1.1. 5G network challenges: Security and Multi-tenancy ......................................................................... 7 1.2. SDN/NFV paradigms in the 5G network ............................................................................................ 9 2. CHARISMA Security and Multi-tenancy Scope ...................................................................10 2.1. CHARISMA Security: threats and risks analysis ...............................................................................10 2.1.1. CHARISMA Use Case Security Analysis ....................................................................................11 2.1.2. Security Requirements Summary ............................................................................................14 2.2. CHARISMA Multi-tenancy considerations ........................................................................................15 3. CHARISMA Control, Management and Orchestration (CMO) Overview ..............................17 3.1. CHARISMA Aggregation Levels Requirements .................................................................................17 3.2. CHARISMA CMO ...............................................................................................................................19 3.2.1. Overview ..................................................................................................................................19 3.2.2. CMO Workflows and Procedures .............................................................................................20 3.2.3. Service Orchestration ...............................................................................................................23 3.2.4. Virtual Infrastructure Manager (VIM) ......................................................................................27 4. CHARISMA Security and Multi-tenancy CMO Extensions....................................................42 4.1. Service Policy Manager ....................................................................................................................42 4.1.1. Security Policy Manager ...........................................................................................................42 4.2. Service Monitoring and Analytics ....................................................................................................47 4.2.1. Security Monitoring and Analytics ...........................................................................................47 4.3. Virtual Infrastructure Manager (VIM) .............................................................................................51 4.3.1. Open Access Manager..............................................................................................................51 4.3.2. VI Security ................................................................................................................................55 4.3.3. VI Monitoring ...........................................................................................................................57 4.4. VNF/VSF ...........................................................................................................................................58 4.4.1. vIDS ..........................................................................................................................................58 4.4.2. vFW ..........................................................................................................................................63 5. Conclusions ......................................................................................................................69 References ............................................................................................................................70 Appendix I: Orchestrator Comparisons ..................................................................................73 Appendix II: v-IDS Implementation ........................................................................................98 Appendix III: v-Firewall Implementation .............................................................................. 114 Appendix IV: Smart NIC card CLI example ............................................................................ 120 Appendix V: NETCONF ......................................................................................................... 125 Appendix VI: Basics of OpenFlow protocol .......................................................................... 126 Appendix VII: EPC & eNB Configuration files ....................................................................... 130 Appendix VIII: Integration of Wireless Backhaul in the CHARISMA CMO Plane .................... 140 CHARISMA – D3.2 – v1.0 Page 3 of 145 Appendix IX: IEEE 802.1ad Q-in-Q Primer ............................................................................ 143 Acronyms ............................................................................................................................ 144 CHARISMA – D3.2 – v1.0 Page 4 of 145 List of Figures Figure 1 Security Overview in SDN/NFV Environment .......................................................................................8 Figure 2 Architectural Schematic of CHARISMA Converged Aggregation Levels (CALs) ................................. 17 Figure 3 Scalability of CHARISMA CALs from x=0 to x=5 ................................................................................. 18 Figure 4 CHARISMA's CMO Architecture ......................................................................................................... 19 Figure 5 VNO registration at CHARISMA Operator ......................................................................................... 21 Figure 6 Slice & Service Provisioning by a VNO ............................................................................................... 22 Figure 7: TeNOR high-level architecture ......................................................................................................... 27 Figure 8 Managing OLT locally ......................................................................................................................... 33 Figure 9: Managing OLT by the Management Network ................................................................................. 34 Figure 10 Ethernity NIC APIs: Server view ....................................................................................................... 37 Figure 11 Management interface for Cache Node in CHARISMA ................................................................... 38 Figure 12 Management interface of OFDM-PON using current hardware ..................................................... 39 Figure 13 Planned management interface of OFDM-PON for new hardware ................................................ 39 Figure 14 Adaptation on Physical Switches ..................................................................................................... 40 Figure 15 NFVO Zoomed In: Service Policy Manager ...................................................................................... 42 Figure 16 Security Policy Manager Architecture ............................................................................................. 43 Figure 17 Security Policy Information Model .................................................................................................. 44 Figure 18 Automated security management via CHARISMA Security Policy Manager ................................... 47 Figure 19: Monitoring and Analytics architecture ..........................................................................................
Load more

Recommended publications
  • IP Addressing: DNS Configuration Guide, Cisco IOS Release 12.4
    IP Addressing: DNS Configuration Guide, Cisco IOS Release 12.4 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Physical Or Virtual Firewall for Perimeter Protection in Cloud Computer Infrastructure
    16th INTERNATIONAL CONFERENCE ON INFORMATION SYSTEMS & TECHNOLOGY MANAGEMENT - CONTECSI - 2019 DOI: 10.5748/16CONTECSI/ITM-6115 PHYSICAL OR VIRTUAL FIREWALL FOR PERIMETER PROTECTION IN CLOUD COMPUTER INFRASTRUCTURE Thiago Mello Valcesia - IPT - Instituto de Pesquisas Tecnológicas - [email protected] Antonio Luiz Rigo - IPT - Instituto de Pesquisas Tecnológicas - [email protected] SUMMARY This article presents an examination of the different types of firewalls geared toward protecting Datacenters. The idea is to perform a survey of the different ways of installation, the safety perceived by customers, the positive and negative points of each model and the market trends for perimeter protection. In addition, it is intended to categorize rules, protection filters, application inspection criteria and services offered by firewalls, by analyzing the various protection schemes available in firewalls, regardless of the structure as a service in Cloud adopted. Keywords: Physical firewall, Virtual firewall, Cloud firewall, Security, Cloud Computing. INTRODUCTION The term Digital Security is increasingly present in our daily lives. The need to protect computers or prevent corporate networks from receiving unnecessary traffic, improper access, and unknown packets, coupled with the concern of professional information security staff about content accessed by Internet users, make data control a vital task. Firewall is much more than a "fire wall" isolating the company network from the external world represented by the Internet. The Firewall function is therefore essential to raise the level of security of the internal environment, protecting it from external attacks, increasing security and reducing the vulnerability of the local network. There are currently three Firewall alternatives to install on enterprise networks that aggregate cloud network segments: 1.
    [Show full text]
  • La Sécurité Informatique Edition Livres Pour Tous (
    La sécurité informatique Edition Livres pour tous (www.livrespourtous.com) PDF générés en utilisant l’atelier en source ouvert « mwlib ». Voir http://code.pediapress.com/ pour plus d’informations. PDF generated at: Sat, 13 Jul 2013 18:26:11 UTC Contenus Articles 1-Principes généraux 1 Sécurité de l'information 1 Sécurité des systèmes d'information 2 Insécurité du système d'information 12 Politique de sécurité du système d'information 17 Vulnérabilité (informatique) 21 Identité numérique (Internet) 24 2-Attaque, fraude, analyse et cryptanalyse 31 2.1-Application 32 Exploit (informatique) 32 Dépassement de tampon 34 Rétroingénierie 40 Shellcode 44 2.2-Réseau 47 Attaque de l'homme du milieu 47 Attaque de Mitnick 50 Attaque par rebond 54 Balayage de port 55 Attaque par déni de service 57 Empoisonnement du cache DNS 66 Pharming 69 Prise d'empreinte de la pile TCP/IP 70 Usurpation d'adresse IP 71 Wardriving 73 2.3-Système 74 Écran bleu de la mort 74 Fork bomb 82 2.4-Mot de passe 85 Attaque par dictionnaire 85 Attaque par force brute 87 2.5-Site web 90 Cross-site scripting 90 Défacement 93 2.6-Spam/Fishing 95 Bombardement Google 95 Fraude 4-1-9 99 Hameçonnage 102 2.7-Cloud Computing 106 Sécurité du cloud 106 3-Logiciel malveillant 114 Logiciel malveillant 114 Virus informatique 120 Ver informatique 125 Cheval de Troie (informatique) 129 Hacktool 131 Logiciel espion 132 Rootkit 134 Porte dérobée 145 Composeur (logiciel) 149 Charge utile 150 Fichier de test Eicar 151 Virus de boot 152 4-Concepts et mécanismes de sécurité 153 Authentification forte
    [Show full text]
  • Microsoft DNS
    1 a. Domain Name Service (DNS) encompassing Microsoft DNS From Wikipedia, the free encyclopedia Jump to: navigation, search Microsoft DNS is the name given to the implementation of domain name system services provided in Microsoft Windows operating systems. Contents [hide] 1 Overview 2 DNS lookup client o 2.1 The effects of running the DNS Client service o 2.2 Differences from other systems 3 Dynamic DNS Update client 4 DNS server o 4.1 Common issues 5 See also 6 References 7 External links [edit] Overview The Domain Name System support in Microsoft Windows NT, and thus its derivatives Windows 2000, Windows XP, and Windows Server 2003, comprises two clients and a server. Every Microsoft Windows machine has a DNS lookup client, to perform ordinary DNS lookups. Some machines have a Dynamic DNS client, to perform Dynamic DNS Update transactions, registering the machines' names and IP addresses. Some machines run a DNS server, to publish DNS data, to service DNS lookup requests from DNS lookup clients, and to service DNS update requests from DNS update clients. The server software is only supplied with the server versions of Windows. [edit] DNS lookup client Applications perform DNS lookups with the aid of a DLL. They call library functions in the DLL, which in turn handle all communications with DNS servers (over UDP or TCP) and return the final results of the lookup back to the applications. 2 Microsoft's DNS client also has optional support for local caching, in the form of a DNS Client service (also known as DNSCACHE). Before they attempt to directly communicate with DNS servers, the library routines first attempt to make a local IPC connection to the DNS Client service on the machine.
    [Show full text]
  • Test-Beds and Guidelines for Securing Iot Products and for Secure Set-Up Production Environments
    IoT4CPS – Trustworthy IoT for CPS FFG - ICT of the Future Project No. 863129 Deliverable D7.4 Test-beds and guidelines for securing IoT products and for secure set-up production environments The IoT4CPS Consortium: AIT – Austrian Institute of Technology GmbH AVL – AVL List GmbH DUK – Donau-Universit t Krems I!AT – In"neon Technologies Austria AG #KU – JK Universit t Lin$ / Institute for &ervasive 'om(uting #) – Joanneum )esearch !orschungsgesellschaft mbH *+KIA – No,ia -olutions an. Net/or,s 0sterreich GmbH *1& – *1& -emicon.uctors Austria GmbH -2A – -2A )esearch GmbH -)!G – -al$burg )esearch !orschungsgesellschaft -''H – -oft/are 'om(etence 'enter Hagenberg GmbH -AG0 – -iemens AG 0sterreich TTTech – TTTech 'om(utertechni, AG IAIK – TU Gra$ / Institute for A((lie. Information &rocessing an. 'ommunications ITI – TU Gra$ / Institute for Technical Informatics TU3 – TU 3ien / Institute of 'om(uter 4ngineering 1*4T – 1-Net -ervices GmbH © Copyright 2020, the Members of the IoT4CPS Consortium !or more information on this .ocument or the IoT5'&- (ro6ect, (lease contact8 9ario Drobics7 AIT Austrian Institute of Technology7 mario:.robics@ait:ac:at IoT4C&- – <=>?@A Test-be.s an. guidelines for securing IoT (ro.ucts an. for secure set-up (ro.uction environments Dissemination level8 &U2LI' Document Control Title8 Test-be.s an. gui.elines for securing IoT (ro.ucts an. for secure set-u( (ro.uction environments Ty(e8 &ublic 4.itorBsC8 Katharina Kloiber 4-mail8 ,,;D-net:at AuthorBsC8 Katharina Kloiber, Ni,olaus DEr,, -ilvio -tern )evie/erBsC8 -te(hanie von )E.en, Violeta Dam6anovic, Leo Ha((-2otler Doc ID8 DF:5 Amendment History Version Date Author Description/Comments VG:? ?>:G?:@G@G -ilvio -tern Technology Analysis VG:@ ?G:G>:@G@G -ilvio -tern &ossible )esearch !iel.s for the -2I--ystem VG:> >?:G<:@G@G Katharina Kloiber Initial version (re(are.
    [Show full text]
  • NFV Decouples the Network Functions Such As NAT, Firewall, DPI, IPS/IDS, WAAS, SBC, RR Etc
    Virtualizing Enterprise Network Functions • BRKCRS-3447 Matt Falkner, Distinguished Engineer, Technical Marketing Agenda BRKCRS-3447 • Introduction & Motivation • Deployment Models and Characteristics • The Building Blocks of Virtualization (today) • Virtualization Trade-offs and Research Topics • Conclusion Abstract Network Function Virtualization (NfV) is gaining increasing traction in the industry based on the promise of reducing both CAPEX and OPEX using COTS hardware. This session introduces the use-cases for virtualizing Enterprise network architectures, such as virtualizing branch routers, LISP nodes, IWAN deployments, or enabling enterprise hybrid cloud deployments. The sessions also discusses the technology of Virtualization from both a system architecture as well as a network architecture perspective. Particular focus is given on understanding the impact of running routing functions on top of hypervisors, as well as the placement and chaining of network functions. Performance of virtualized functions is also discussed. BRKCRS-3447 © 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 4 Introduction and Motivation Network Functions Virtualization (NFV) Announced at SDN World Congress, Oct 2012 • AT&T • BT • CenturyLink • China Mobile • Colt • Deutsche Telekom • KDDI • NTT • Orange • Telecom Italia • Telstra • Verizon • Others TBA… BRKCRS-3447 © 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 10 What is NfV? A Definition … NFV decouples the network functions such as NAT, Firewall, DPI, IPS/IDS,
    [Show full text]
  • Exploiting Cloud Management Services As an Information Leakage Channel
    I Heard It through the Firewall: Exploiting Cloud Management Services as an Information Leakage Channel Hyunwook Baek∗ Eric Eide [email protected] [email protected] University of Utah University of Utah Salt Lake City, UT, USA Salt Lake City, UT, USA Robert Ricci Jacobus Van der Merwe [email protected] [email protected] University of Utah University of Utah Salt Lake City, UT, USA Salt Lake City, UT, USA ABSTRACT Though there has been much study of information leakage chan- nels exploiting shared hardware resources (memory, cache, and disk) in cloud environments, there has been less study of the ex- ploitability of shared software resources. In this paper, we analyze the exploitability of cloud networking services (which are shared among cloud tenants) and introduce a practical method for build- ing information leakage channels by monitoring workloads on the cloud networking services through the virtual firewall. We also demonstrate the practicality of this attack by implementing two different covert channels in OpenStack as well as a new classof side channels that can eavesdrop on infrastructure-level events. By utilizing a Long Short-Term Memory (LSTM) neural network model, our side channel attack could detect infrastructure level VM creation/termination events with 93.3% accuracy. CCS CONCEPTS • Security and privacy → Distributed systems security; Fire- walls; • Computer systems organization → Cloud computing; • Networks → Cloud computing; Figure 1: Resource sharing of two requests KEYWORDS cloud management, cloud security, side channel, OpenStack 1 INTRODUCTION However, shared resources also cause interference among cloud tenants and can even be exploited as information leakage channels Resource sharing is a fundamental part of cloud computing.
    [Show full text]
  • Who Is Ivan Pepelnjak (@Ioshints)
    Virtual Firewalls Ivan Pepelnjak ([email protected]) NIL Data Communications Who is Ivan Pepelnjak (@ioshints) • Networking engineer since 1985 • Focus: real-life deployment of advanced technologies • Chief Technology Advisor @ NIL Data Communications • Consultant, blogger (blog.ioshints.info), book and webinar author • Teaching “Scalable Web Application Design” at University of Ljubljana Current interests: • Large-scale data centers and network virtualization • Networking solutions for cloud computing • Scalable application design • Core IP routing/MPLS, IPv6, VPN 2 © ipSpace.net / NIL Data Communications 2013 Virtual Firewalls Virtualization Webinars on ipSpace.net Coming in 2013 Coming in 2013 vSphere 5 Update Overlay Virtual Networking Coming in 2013 Virtual Firewalls OpenFlow and SDN Use Cases VXLAN Deep Dive OpenFlow VMware Networking Cloud Computing Networking Introduction to Virtualized Networking Availability Other options • Live sessions • Customized webinars • Recordings of individual webinars • ExpertExpress • Yearly subscription • On-site workshops 3 InterMore© ipSpace.net- DCinformation /FCoE NIL Data Communications has @ very2013 http://www.ipSpace.net/Webinars limitedVirtual use Firewalls and requires no bridging Firewalls Used To Be Easy Packet filters Application-level firewalls (WAF) Firewalls Stateful Load firewalls balancers? 4 © ipSpace.net / NIL Data Communications 2013 Virtual Firewalls Routed or Bridged? Routed (inter-subnet) Transparent (bridged) • Packet filtering and IP routing • Packet filtering and bridging
    [Show full text]
  • The Virtual Firewall
    The Virtual Firewall Vassilis Prevelakis Computer Science Department Drexel University 1. Introduction The trend towards portable computing means that the traditional security perimeter architecture (where a firewall protects computers in the LAN by controlling access to the outside world) is rapidly becoming obsolete. This has resulted in a number of products described as “personal firewalls” that control that computer’s access to the network and hence can protect it in the same way as a traditional firewall. Existing systems such as Windows and most Unix and Unix-like systems already provide security features that can be used to implement firewall functionality on every machine. However, the difficulty of securing general purpose operating systems has im- peded the widespread use of this approach. Moreover, it is difficult to ensure that a secured sys- tem remains secure after the user has had the opportunity to install software and perform recon- figurations and upgrades. Recognizing the futility of attempting to secure the user machines themselves, in [Prev03, Denk99] the authors proposed the use of a portable “shrink-wrapped” firewall. This was a sepa- rate machine running an embedded system that included firewall capabilities and was intended to be placed between the general purpose computer and the network. The problem of securing the firewall became much simpler as it utilized a special-purpose firewall platform with a highly controlled architecture. Sadly, the proposal saw limited adoption because carrying around yet another device is expensive and inconvenient. To make matters worse, if the external device is lost or damaged the user will be presented with a dilemma: remain disconnected from the net- work until the firewall box is replaced, or accept the risk and connect the laptop directly to the unprotected network.
    [Show full text]
  • WP-MIRROR 0.7.4 Reference Manual
    WP-MIRROR 0.7.4 Reference Manual Dr. Kent L. Miller November 22, 2014 DRAFT 1 DRAFT 2 To Tylery DRAFT i WP-MIRROR 0.7.4 Reference Manual Legal Notices Copyright (C) 2012–2014 Dr. Kent L. Miller. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. THIS PUBLICATION AND THE INFORMATION HEREIN ARE FURNISHED AS IS, ARE FURNISHED FOR INFORMATIONAL USE ONLY, ARE SUBJECT TO CHANGE WITH- OUT NOTICE, AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY THE AU- THOR. THE AUTHOR ASSUMES NO RESPONSIBILITY OR LIABILITY FOR ANY ER- RORS OR INACCURACIES THAT MAY APPEAR IN THE INFORMATIONAL CONTENT CONTAINED IN THIS MANUAL, MAKES NO WARRANTY OF ANY KIND (EXPRESS, IMPLIED, OR STATUTORY) WITH RESPECT TO THIS PUBLICATION,AND EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES OF MERCHANTABILITY, FITNESS FOR PAR- TICULAR PURPOSES, AND NONINFRINGEMENT OF THIRD-PARTY RIGHTS. The WP-MIRROR logotype (see margin) was released by the author into the public domain on 2014-Apr-10. See https://www.mediawiki.org/wiki/File:Wp-mirror.png. This logotype fea- tures a sunflower that is derived from 119px-Mediawiki logo sunflower Tournesol 5x rev2.png, which is also in the public domain. See https://en.wikipedia.org/wiki/File:Mediawiki_logo_sunflower_Tournesol_5x.png.
    [Show full text]
  • Stateless DNS
    Technical Report KN{2014{DiSy{004 Distributed System Laboratory Stateless DNS Daniel Kaiser, Matthias Fratz, Marcel Waldvogel, Valentin Dietrich, Holger Strittmatter Distributed Systems Laboratory Department of Computer and Information Science University of Konstanz { Germany Konstanzer Online-Publikations-System (KOPS) URL: http://nbn-resolving.de/urn:nbn:de:bsz:352-0-267760 Abstract. Several network applications, like service discovery, file dis- covery in P2P networks, distributed hash tables, and distributed caches, use or would benefit from distributed key value stores. The Domain Name System (DNS) is a key value store which has a huge infrastructure and is accessible from almost everywhere. Nevertheless storing information in this database makes it necessary to be authoritative for a domain or to be \registered" with a domain, e.g. via DynDNS, to be allowed to store and update resource records using nsupdate . Applications like the ones listed above would greatly benefit from a configurationless approach, giving users a much more convenient experience. In this report we describe a technique we call Stateless DNS, which allows to store data in the cache of the local DNS server. It works without any infrastructure updates; it just needs our very simple, configurationless echo DNS server that can parse special queries containing information desired to be stored, process this information, and generate DNS answers in a way that the DNS cache that was asked the special query will store the desired information. Because all this happens in the authority zone of our echo DNS server, we do not cause cache poisoning. Our tests show that Stateless DNS works with a huge number of public DNS servers.
    [Show full text]
  • GW1000 User Manual
    GW1000 User Manual Issue: 1.7 Date: 09 September 2016 Table of Contents _______________________________________________________________________________________________________ 1 Introduction ................................................................................................. 8 1.1 Document scope ....................................................................................... 8 1.2 Using this documentation ........................................................................... 8 2 GW1000 Series hardware ........................................................................... 11 2.1 Hardware model varients ......................................................................... 11 2.2 GW1000 Series hardware features ............................................................ 12 2.3 GSM technology ...................................................................................... 12 2.4 WiFi technology ...................................................................................... 12 2.5 Power supply .......................................................................................... 13 2.6 GW1000 Series router dimensions............................................................. 13 2.7 GW1000M Series router dimensions .......................................................... 13 2.8 Compliance ............................................................................................ 13 2.9 Operating temperature range ................................................................... 14 2.10
    [Show full text]