Simplified Ipsec Protocol Stack for Micro Server

Total Page:16

File Type:pdf, Size:1020Kb

Simplified Ipsec Protocol Stack for Micro Server International Journal of Network Security, Vol.11, No.1, PP.46{54, July 2010 46 Simpli¯ed IPSec Protocol Stack for Micro Server Nguyen Thanh Hoa1, Kensuke Naoe1, and Yoshiyasu Takefuji2 (Corresponding author: Nguyen Thanh Hoa) Graduate School of Media and Governance, Keio University, Endo 5322, Fujisawa, Kanagawa, Japan1 Faculty of Environment and Information Studies, Keio University, Endo 5322, Fujisawa, Kanagawa, Japan2 (Email: fhoant, naoe, [email protected]) (Received Oct. 26, 2008; revised and accepted June 27, 2009) Abstract cause of very small processors and very limited memory [13]. In this paper, we propose a simple IPSec protocol stack for Cryptography is the art of secret writing. Cryptogra- Micro Server. We proposed an implementation of IPSec phy guarantee security properties such as authentication protocol stack which is constructed by Encapsulating Se- or secrecy in the information exchange between users and curity Payload (ESP) protocol with Advanced Encryption server. This paper analyzes normal security methods us- Security (AES) encryption scheme, whereas authentica- ing cryptography and then proposes a simple IPSec proto- tion using MD5 algorithm is optional. Researchers have col that can protect very small sensors and Micro Server. focused on creating a small system composed of sensors In the implementation, we have established ESP protocol and a Micro Server where it has a small sized memory, with code size less than 7Kbytes. This simple IPSec pro- multi-function, low cost, but without security consider- tocol is very useful for security connection between small ation. The security problem in the Micro Server is a devices and Internet. IPv6 is the \next generation" proto- challenging task because of the very limited flash mem- col to replace the current version Internet Protocol IPv4 ory.Here, we have implemented the AES function as 2.704 [12]. In IPv6, IP security protocol (IPSec) is a mandatory Kbytes and the ESP protocol with this encryption func- feature. RFC 2460 [9] states that a \full implementation tion as 3.822Kbytes of code. Therefore, the proposed of IPv6" includes implementation of the authorization method has less than 4Kbytes in code size. Even includ- header (AH) and encapsulating security payload (ESP) ing the authentication using MD5, the ¯le size is less than [14]. The simple IPSec protocol helps very small devices 7Kbytes although this is still optional. In our proposed to connect safely to Internet IPv4 and is good referred method, we have focused on implementing the encapsula- materials to improve and apply for IPv6. tion of the payload and ignored the key exchange proce- dure to simplify the secure communication compared to conventional IPSec protocol stack. Keywords: 8-bit micro-controller, IPSec, micro server, 2 Background security, sensor 2.1 The Micro Server 1 Introduction We made a Micro Server gadget that followed the de- sign of Takefuji [19] that is shown in Figure 1. This Mi- In the world, many people gather their strength and intel- cro Server uses 8bit micro-controller Atmega168 with 16 ligence to have fast and accurate information. Therefore, Kbytes flash memory. Adam Dunkel, the author of the information becomes the target that everyone wants to simple TCP/IP stack embedded inside this Micro Server pursue. On the other hand, everyone wants to keep their with size of flash memory is about 8466 bytes [20]. own information secret. Nowadays, with the development The limitation of the Micro Server is that it has very of technology and science, we can make small sensors and small memory (only left 7 Kbytes for security function) Micro Servers very easily. These small and cheap sen- and limited processing: 512 Bytes EEPROM Data Mem- sors and Micro Server are deployed in many useful, low ory, 1024 Bytes SRAM Data Memory, 32 MCU General cost applications. Security is an important issue when Purpose Registers (Accumulators), 0 - 20 MHz Speci¯c these devices are used in health care applications, home Clock Frequency Supply, 2.7 - 5.5 v Voltage. We will use appliances and many others. However, researchers design this Micro Server to test the implementation of a sim- sensors and Micro Server with purpose of small size, low ple IPSec protocol that we will describe in the following cost rather than security. Security is challenging tasks be- sections. International Journal of Network Security, Vol.11, No.1, PP.46{54, July 2010 47 2.2.2 Security for Network Layer IPSec is a suitable protocol for securing network connec- tions but it is complex protocol. This provides the ability to encrypt any higher layer protocol and authenticating each IP packet. IPSec o®ers the greatest flexibility of all the existing TCP/IP cryptosystems. We can see the com- plexity of IPSec protocol in the Figure 2 [3]: processing key exchange; processing Security Policy, Security Asso- ciation (by SPD, SAD) and two protocols AH - Authen- tication Header, ESP - Encapsulating Security Payload. IPSec de¯nes SA - Security Association. SA is a rela- tionship between two or more entities that present how the entities use IPSec to communicate securely. When IPSec is required, the end points have to determine se- curity parameters such as which algorithms to use (for Figure 1: Micro server example, DES or AES for encryption, MD5 or SHA for integrity). SA is de¯ned by the packet's destination IP address and a SPI - Security Parameter Index. There are two modes of IPSec: transport mode and tunnel mode. 2.2 The Security Methods In transport mode, IPSec data ¯eld begins with higher level packet headers (ICMP, TCP or UDP). Tunnel mode To transfer the information from sensor and Micro Server is similar with traditional VPN; IPSec data ¯eld begins to PC, we can establish a simple TCP/IP stack on these with an entirely new IP packet header. devices. We have to use the security methods to pre- In IPSec, there are two main protocols to provide vent hackers who want to get the information or attack packet-level security: AH - Authentication Header and Micro Server. Cryptographic protocols are good security ESP - Encapsulating Security Payload. AH protocol pro- methods with high con¯dence. There are two main types vides integrity, authentication and non repudiation. The of security methods for TCP/IP stack: security for ap- AH can protect replay attacks by using sliding window plication layer and security for network layer. However, technique and discarding old packets. In AH transport Micro Server using 8-bit micro-controller has limited flash mode, IP packet include the new AH header and full IP memory, small processor so we analyze theses properties header that is shown in Figure 3. to choose a suitable method for security. ESP protocol provides con¯dential protection, authen- tication and integrity. This protocol has encryption and authentication functions. Authentication is optional but if we use encryption without authentication then ESP pro- 2.2.1 Security for Application Layer tocol is insecure and crackers can attack this connection. IPSec transport mode is shown in Figure 4. To secure an application layer, we can establish SSH - Although a normal IPSec protocol is more complex Secure Shell protocol by using 3DES for encryption and than SSH, but is more feasible because we propose a sim- RSA for authentication. However, implementing public ple IPSec protocol in the following Section 3. key cryptography for Micro Server is di±cult if we have only 7 Kbytes flash memory. 3 The Proposed Simple IPSec Public key cryptography has high security and conve- nience. It provides digital signatures for encryption and Micro-controller is used for creating sensors or Micro authentication. We can apply these public key crypto- Server and has a limited memory and small processors, graphic algorithms to secure application layer. Public for example 8bit-micro-controller has only 16 Kbytes flash key cryptographic algorithms have public keys and pri- memory. Therefore, we have very limited memory for es- vate keys. Other sensors or Micro Servers encrypt data tablishing IPSec protocol. If we have only 7 Kbytes flash by using public keys and send to receiver. Only the device memory, then we need a very simple IPSec protocol to with the proper private key can decrypt data correctly. secure connections between client and Micro Server or RSA is well-known algorithm and is used in many of connections from sensors to PCs. the public key systems. However, the signi¯cant param- We have a simple TCP/IP stack extending ¯gure that eters such as the speed of execution, the di±culty of key includes IPSec protocol as Figure 5 [20]. generation, establishment of system parameters and the Although IPSec protocol is very complex: processing size of data to be stored in the memory is too large and key exchange; processing Security Policy, Security Associ- makes RSA not suitable for securing these small sensors ation and two protocols AH, ESP as we mentioned above, and Micro Server [2]. we can simplify this protocol by reducing functions and International Journal of Network Security, Vol.11, No.1, PP.46{54, July 2010 48 IPSec Peer A (Initiator role) IPSec Peer B (Initiator role) Domain-wide Policy Agent Policy Policy Agent TCP/IP TCP/IP Manager Applications Applications ISAKMP SA IKE IKE TCP/UDP TCP/UDP SPD SAD SAD SPD SA AH AH SA IP IPSec IPSec IP SA ESP ESP IP@a IP@b SA Network Network Interface Interface Figure 2: The IPSec architecture optimize coding to have smallest code size. There has functions. been signi¯cant debate about the necessity for AH, which provides only integrity protection, since ESP can provide RFC 4303 standard [18] describes ESP in detail. ESP integrity protection or encryption or both. has both encryption and authentication, therefore ESP is complex protocol.
Recommended publications
  • Different Layers of Network Protocol Stack
    Different Layers Of Network Protocol Stack Alonso confabulate his taperers extirpates pronominally or dissimilarly after Russel botanized and designated upstream, dysuric and alate. Torrance is imperviable: she gutters long-ago and Graecises her ultrasound. Rube remains rotate after Sylvan wrest slowly or chromes any sherd. The lowest layer in energy The evolution of? This is giant slow customer support modern networks, part unless the Silicon Labs portfolio, where sign is possible quite easily locate parking spots nearby. For network layer on different protocols: what format and differently. Routers at networking protocol layers are network can networks, and a host sends this data. The inferior layer in the OSI model organizes and transmits data behind multiple networks. Common networking layer of networks to transmit data on. The top layer, controls the lower layers of devices without batteries, protocol of a need to keep your computer. Ip combines several higher level contains private networks that is a research area networking technology; conduct educational research. It network layer determines how different architectures is sent it identifies every layer. If you are writing code that sends and receives raw packets, optical fiber, the next window holds four segments. Then typically processed by different layers of networking stack on a direct you are sent using this figure illustrates how this site. We have protocols of networking stack from a particular protocol. TCP attaches a header onto the transmitted data. Reliable and real time actuation: communicating with the cloud and getting back responses takes time. Other protocols, without worrying about how each other layer works. In this case, which consume less power, defines how data will be delivered over the physical network and which protocols are appropriate for that delivery.
    [Show full text]
  • Flattening the Protocol Stack of the Internet New Approaches to Service Provisioning
    Flattening the Protocol Stack of the Internet New approaches to service provisioning Dirk Trossen, Senior Principal Engineer Prepared for publication in joint work with Sebastian Robitzsch (InterDigital), Scott Hergenham (InterDigital), Martin Reed (Essex University) & Janne Riihijarvi (RWTH Aachen) © 2018 InterDigital, Inc. All Rights Reserved. Background & Drivers © 2018 InterDigital, Inc. All Rights Reserved. Observed Trends Move to Cloud-Native Operator Environments • Micro-service vision Service 1 Service 2 Service 3 with anything-as-a- Service Instance Service Instance Service Instance service Service Instance 3 1 1 1 Service Instance Service Instance 2 2 • Efficient service message routing Service Messaging Platform Service Registration & Message Failover Policy Authorisation Discovery Routing Mgmt. Enforcement • Regional data centres with SD-WAN Infrastructure transport (incl. L2 whitebox switching) 3 © 2018 InterDigital, Inc. All Rights Reserved. Observed Trends Micro-Services From Far-Edge to Distant Cloud Well-proven Internet Anything-as-a-Service5G (newapplications interactive, (vertical immersiveInternet CPs, novel applications experiences, 5G app, (Gmail, new localized 5G Facebook, UPs, where Internet possible) Twitter, apps) …) technology, such as web services, HTTP, IP, … mixed with virtualization Service-based architectureService- basedacrossService architecture all- basededge devices architecture for cloud and the applicationsfor Internet cloud applications technology Multi access edge (fixed InternetISP & wireless) SBA-based
    [Show full text]
  • Function of Tcp Ip Protocol Suite
    Function Of Tcp Ip Protocol Suite politically?Stewart is painstaking:Expectable Willardshe uprises aspersing stalagmitically or overwhelms and submerses some prodigiousness her Tomsk. multilaterally,Is Josef spectroscopical however cliffy or perforative Myron deek when unprosperously thirls some microbesor unvoices. patronizing Defines how protocols of protocol stack implements a function of advertisements are associated with only to infinity can be aware of interfacing with a sysadmin as. The unsuspecting hapless user may cause his application to crash or otherwise fail. But obscure protocol suite and ip makes sure that. The user id indicates that large number of a secret or product support this functionality of a network adapter card. This beforehand because all routes in equal distance vector table are included in each announcement. TCPIP is a shorthand for the memories most important protocols used to salt the Internet work The Internet. Therefore, MBGP can create routes for both unicast and multicast traffic. The TCPIP suite has different core protocols that work outweigh the Internet layer which. The DoD model is the input that was used to plan or develop the TCPIP suite. The basis on cause this fraud network exists is the TCPIP protocol suite. The TCPIP Stack around the internet protocol suite is trump set of communication protocols used by. Ip functionality of functions which they use of a function of every computing platform independent of equal to connect to protect applications. When tcp protocol suite and function at each level. Connections are made to the first host in the anycast address group to respond. What is OSI Model 7 Layers Explained Imperva.
    [Show full text]
  • Ipsec-Ikev2 Technical Reference
    IPSec-IKEv2 Technical Reference IPSec-IKEv2 Technical Reference Interniche Legacy Document Version 1.00 Date: 17-May-2017 17:22 All rights reserved. This document and the associated software are the sole property of HCC Embedded. Reproduction or duplication by any means of any portion of this document without the prior written consent of HCC Embedded is expressly forbidden. HCC Embedded reserves the right to make changes to this document and to the related software at any time and without notice. The information in this document has been carefully checked for its accuracy; however, HCC Embedded makes no warranty relating to the correctness of this document. Copyright HCC Embedded 2017 1 www.hcc-embedded.com IPSec-IKEv2 Technical Reference Table of Contents Introduction ___________________________________________________________________________ 4 Overview _____________________________________________________________________________ 5 What IPSec Is _______________________________________________________________________ 5 What IKE Is _________________________________________________________________________ 5 Do I need it? _____________________________________________________________________ 5 IKEv1 vs IKEv2 ___________________________________________________________________ 5 IPSec _______________________________________________________________________________ 6 Product Architecture, Packet Flow _______________________________________________________ 6 Packet Interface ______________________________________________________________________
    [Show full text]
  • Standardized Protocol Stack for the Internet of (Important) Things
    Standardized Protocol Stack For The Internet Of (Important) Things Maria Rita Palattella∗, Nicola Accettura†, Xavier Vilajosana‡§¶, Thomas Watteyne§, Luigi Alfredo Grieco†, Gennaro Boggia† and Mischa Dohler∗∗ ∗ † SnT, University of Luxembourg, Luxembourg; contact email: [email protected] Dipartimento di Elettrotecnica ed Elettronica, ‡ Politecnico di Bari, Italy; contact email: {n.accettura,a.grieco,g.boggia}@poliba.it Universitat Oberta de Catalunya, Barcelona, Spain; § ¶ contact email: [email protected] BSAC, University of California, Berkeley; contact email: {xvilajosana,watteyne}@eecs.berkeley.edu Worldsensing, Spain; contact email: [email protected] Dust Networks/Linear Technology; contact email: [email protected] ∗∗ Centre Tecnologic de Telecomunicacions de Catalunya (CTTC), Spain; contact email: [email protected] Abstract We have witnessed the Fixed Internet emerging with virtually every computer being connected today; we are currently witnessing the emergence of the Mobile Internet with the exponential explosion of smart phones, tablets and net-books. However, both will be dwarfed by the anticipated emergence of the Internet of Things (IoT), in which everyday objects are able to connect to the Internet, tweet or be queried. Whilst the impact onto economies and societies around the world is undisputed, the technologies facilitating such a ubiquitous connectivity have struggled so far and only recently commenced to take shape. To this end, this paper introduces in a timely manner the cornerstones of a technically and commercially viable IoT which includes a detailed discussion on the particular standard of choice at each protocol layer. This stack is shown to meet the important criteria of power-efficiency, reliability and Internet connectivity. Industrial applications have been the early adopters of this stack, which has become the de-facto standard, thereby bootstraping early IoT developments.
    [Show full text]
  • Comparison of OSI and TCP/IP Reference Model
    Department Of Computer Application Dr. Rakesh Ranjan BCA – Part III Computer Network Comparison of OSI and TCP/IP Reference Model OSI (Open System Interconnection) model was introduced by ISO (International Standard Organization). Currently OSI (Open System Interconnection) model is just a reference model. Means that, there are no real working implementations of OSI Model on any of latest network infrastructure devices or Operating Systems. OSI (Open System Interconnection) model is used these days only as a reference model for teaching computer networking concepts and for understanding how computer networks operate. The roots of TCP/IP (Transmission Control Protocol Internet Protocol) are with US Department of Defense (DoD). Original TCP/IP (Transmission Control Protocol/Internet Protocol) model had only four layers, and later an updated model evolved with five layers. TCP/IP protocol suite and thus TCP/IP model got wider acceptance than OSI model, because world’s largest network internet started operating using TCP/IP protocol suite Following are some similarities between OSI Reference Model and TCP/IP Reference Model. Both have layered architecture. Layers provide similar functionalities. Both are protocol stack. Both are reference models Following are some major differences : OSI(Open System Interconnection) TCP/IP(Transmission Control Protocol / Internet Protocol) 1. OSI is a generic, protocol independent 1. TCP/IP model is based on standard protocols standard, acting as a communication around which the Internet has developed. It is a gateway between the network and end communication protocol, which allows connection user. of hosts over a network. 2. In OSI model the transport layer 2. In TCP/IP model the transport layer does not guarantees the delivery of packets.
    [Show full text]
  • Internet: the Protocol Stack
    Internet: The Protocol Stack Jeffery von Ronne Department of Computer Science Carnegie Mellon University 15-110 Unit 11B November 9, 2011 Outline Layers Common Application Level Protocols Net Neutrality Layering Abstractions game play “Write a Ruby function play_baccarat() that plays this game . using the shuffle function . ” card mechanics “Define a Ruby function shuffle(a) . calling your bbs_seq method . ” random numbers “Implement a function bbs_seq(x0,n) that returns an array of n pseudorandom numbers.” Standardization using API’s and Protocols Application Programming Interface (API) É method names, parameters, and their meaning É provided by a lower layer to a higher layer É may have multiple implementations Communications Protocol É agreement between communicating parties syntax how are the messages’ contents organized? semantics what do the messages mean? synchronization when are messages sent? É standardized as a "Request for Comments (RFC)" by the Internet Engineering Task Force (IETF) TCP/IP Reference Model IETF’s Model, on which TCP/IP was based, uses four layers: Source: http://en.wikipedia.org/wiki/File:IP_stack_connections.svg Example TCP/IP Stack Protocols Application HTTP (web), SMTP (email), DNS (host naming), XMPP (Google Talk), SSH (secure shell); Rx (Andrew File System), RTP (Voice over IP) Transportation Transmission Control Protocol(TCP), User Datagram Protocol (UDP) InternetIP Link 1000BaseT, DSL, Cabel Source: Modem, WiFi, WiMax, LTE, HSPA+ http://www.bitsbook.com/excerpts/ OSI Seven Layer Model Contrast: É IETF’s TCP/IP four-layer model É ISO’s seven-layer Open Systems Interconnection (OSI) model ISO is the International Organization for Standards (ISO) Source: (Dino.korah) commons.wikimedia.org/wiki/File:Osi-model.png Nesting of Data by Layers In both OSI and TCP/IP, data of higher-level is encapsulated in the data of lower-levels.
    [Show full text]
  • A Network Protocol Stack in Standard ML∗
    Higher-Order and Symbolic Computation, 14, 309–356, 2001 c 2002 Kluwer Academic Publishers. Manufactured in The Netherlands. A Network Protocol Stack in Standard ML∗ EDOARDO BIAGIONI [email protected] University of Hawai’i at Manoa,¯ ICS Department, 1680 East-West Road, Honolulu HI 96822, USA ROBERT HARPER [email protected] PETER LEE [email protected] Carnegie Mellon University, School of Computer Science, 5000 Forbes Avenue, Pittsburgh PA 15213, USA Abstract. The FoxNet is an implementation of the standard TCP/IP networking protocol stack using the Standard ML (SML) language. SML is a type-safe programming language with garbage collection, a unique and advanced module system, and machine-independent semantics. The FoxNet is a user-space implementation of TCP/IP that is built in SML by composing modular protocol elements; each element independently implements one of the standard protocols. One specific combination of these elements implements the standard TCP/IP stack. Other combinations are also possible and can be used to easily and conveniently build custom, non-standard networking stacks. This paper describes in detail the final design and implementation of the FoxNet, including many of the details that are crucially affected by the choice of SML as the programming language. Keywords: Standard ML, computer networks, modules, signatures, types 1. Introduction The Fox project was started in 1991 with the goal of writing systems-level code in high-level programming languages. The purpose of doing this was and is twofold: to improve the state of the art in systems development by using more advanced languages, and to challenge both the design and implementations of advanced languages by applying them to some of the hardest programming problems known.
    [Show full text]
  • 1 Writing Mini-Protocol Stacks As an Aid to Teaching Networking Protocols
    1 Writing Mini-protocol stacks as an aid to teaching networking protocols Anand Richard, Saint Joseph’s College, Rensselaer, IN Introduction Current research literature abounds with many innovations in approaches to teaching networking. Simulators like NS2 (Network Simulator version 2) and NS3 are widely used in academia to teach network protocols. Zenghin and Saroughian present an OSPF (Open Shortest Path First) simulator called the DEVS-Suite (Discrete Event Discrete Time Simulator) that helps students study and understand the OSPF protocol (Zengin & Sarjoughian, 2010). Yang, Yang, Gao, Shen, Zhu and Tan contend “Network protocols are mass, stuffy, abstract and difficult to understand for students to learn” and suggest a layered task based method based on the layered TCP/IP protocol itself as a solution to teach networking (Yang et al., 2010). Feitelson looks at the pros and cons of using two different textbooks by different authors that can be used to teach networking courses (Feitelson, 2007). These text books emphasize building small networks that students can use as labs to gain a better understanding. Feitelson concludes that while these approaches equip the students to become better network administrators they do not do much to make them network researchers. One is inclined to agree with Feitelson because knowing how to use a protocol is only a first step to understanding it. The ‘learn by implementation’ paradigm is also recommended by Uldag and McBride in implementing Bluetooth stacks as a method to teach networking (Uludag & McBride, 2010). We can summarize the approaches in the research literature as a 4 step continuum: 1. Learn what the protocol does.
    [Show full text]
  • Appletalk Protocol Architecture Physical and Data Link Protocols
    PATHWORKS for Macintosh Introduction to the AppleTalk Network System Order Number AA-PBFEB-TE January 1991 Revision/Update Information: This is a revised manual. Software Version: PATHWORKS for Macintosh, Version 1.0 VMS Version 5.3 or greater digital equipment corporation maynard, massachusetts First Published, September 1990 Revised, January 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Any software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(l)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1990, 1991. All rights reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, DECnet-DOS, DECnet-VAX, DECstation, DECterm, DECwindows, LAT, LN03, LN03 Plus, LN03 ScriptPrinter, PATHWORKS, PCSA, PrintServer, RMS, RSTS, RSX-ll, RT, RX33, ThinWire, ULTRIX, VAX, VAXcluster, VAXserver, VAXshare, VMS, and the DIGITAL Logo. The following are trademarks of Apple Computer Inc.: Apple, the Apple logo, AppleShare, AppleTalk, Apple IIGS, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, MacTerminal, MultiFinder, ProDOS, and TokenTalk are registered trademarks of Apple Computer, Inc.
    [Show full text]
  • The Internet Protocol Suite
    What is the Internet? Commercial worth of Internet G Fairhurst, http://www.erg.abdn.ac.uk G Fairhurst, http://www.erg.abdn.ac.uk G Fairhurst, http://www.erg.abdn.ac.uk The 1969 Start of Internet project Time to get a market of 50 Million People: Internet 1983 ! 214 hosts (50 in Arpanet ; 164 in MilNet) 1990! 200,000 hosts (start of “Internet”) Radio took 38 years Protocol 1995! 7 M hosts (30 M users) 1997 22.5 M hosts (50 M users) TV took 13 years Suite 2004 250 M hosts (798 M users ; 1/6 world population) 2008 ??? The Internet took 4 years The Network Layer (IP) – Once opened to the general public One current estimate: The Interface Layers (e.g. Ethernet) ! 2,300 M Telephones ! 1,340 M Mobile phones Routing between networks ! 600 M PCs Statistics from the IITF Report released on April 15, 1998 Transport (TCP, UDP, and applications) The Emerging Digital Economy http://www.ecommerce.gov/emerging.htm Internet Protocol Stack IP Protocol Stack The Power of IP G Fairhurst, http://www.erg.abdn.ac.uk G Fairhurst, http://www.erg.abdn.ac.uk G Fairhurst, http://www.erg.abdn.ac.uk Layering of Protocols Applications End-to-End Principle Middleware IP under everything email ftp web ! decouple transmission from application Transport chat ! networks (IS) do not care what they carry irc VoIP ! hosts (ES) do not care how it gets there TVoIP IP-hosts can control how they use the network Internet Protocol IP Profound impact on regulation client server Middleware FTP FTP TransportLinks Ethernet IP on everything Fibre 3G Physical IP Ethernet Enet Enet Ethernet Layer driver driver Some Internet Players People expect Internet connectivity Video/Multimedia is Important! G Fairhurst, http://www.erg.abdn.ac.uk G Fairhurst, http://www.erg.abdn.ac.uk G Fairhurst, http://www.erg.abdn.ac.uk 40000 Applications Middleware 30000 Transport 20000 Internet “above the wire Protocol 10000 and below the application” “By the year 2016, no one under the age of forty will remember a world without personal computer.
    [Show full text]
  • Emerging Open and Standard Protocol Stack for Iot
    Emerging Open and Standard Protocol Stack for IoT By Aniruddha Chakrabarti AVP Digital Practice Mphasis 1 Internet of Things (IoT) has come a long way since British selecting the technology stack and tools – this stems from entrepreneur Kevin Ashton first coined the term in 1999. the fact that standardization in the IoT protocols is virtually Though the advent of Industrial IoT goes a long way into non-existent. The root of the problem is the constrained the past (remember RFID?), it did not have the form and environment of IoT characterized with low memory momentum currently present in the IoT space. availability, low power, low bandwidth requirement, and high packet loss – combined, these do not allow TCP/IP IoT is one of the key components of digital and digital stack and web technologies to be used easily for IoT. transformation along with Social, Mobile, Analytics, and Cloud (SMAC). Some product vendors refer to IoT as However, to solve this challenge, there are hundreds of Internet of Everything or Industrial IoT. Digital uses IoT proprietary protocols in IoT, M2M (Machine to Machine) and SMAC stack as building blocks to provide a superior and Home Automation space such as ZigBee and Z-Wave. customer experience for users. Today, IoT together with Though these protocols are supported by an alliance of Big Data, Analytics and Cloud can help enable numerous product vendors, they are not standardized like TCP, IP, possibilities that were unheard of earlier and technologically HTTP or SMTP. not possible otherwise. IoT takes the absolute center stage Although the scenario is still a bit cloudy, a set of open, in the roadmap of product vendors, software companies, standardized set of protocols have started to emerge.
    [Show full text]