The Experts below are selected from a list of 32130 Experts worldwide ranked by ideXlab platform

Ivan Bogomilov - One of the best experts on this subject based on the ideXlab platform.

  • ipv6 based building automation solution integration into an ipv4 Network service provider infrastructure case study
    Computer Systems and Technologies, 2012
    Co-Authors: Nikolay Milovanov, Ivan Bogomilov
    Abstract:

    The paper describes an Internet Protocol (IP) version 6 (v6) introduction to an IP version 4 (v4) Internet Service Provider (ISP) Network infrastructure. The case study driver is an ISP willing to introduce a new "killer" service related to Internet of Things (IoT) style building automation. The ISP and cooperation of third party companies specialized in building automation will provide the service. The ISP has to deliver the Network Access Layer and to accommodate the building automation solution traffic throughout its Network infrastructure. The third party companies are system integrators and building automation solution vendors. IPv6 is suitable for such solutions due to the following reasons. The operator can't accommodate large number of IPv4 embedded devices in its current Network due to the lack of address space and the fact that many of those will need clear 2-way IP communication channel. The Authors propose a strategy for IPv6 introduction into operator infrastructure based on the current Network architecture, present service portfolio and several transition mechanisms. The strategy has been tested in laboratory with setup close or identical to the current operator's Network. The criteria for a successful experiment is full two-way IPv6 application Layer connectivity between the IPv6 server and the IPv6 Internet of Things (IoT) cloud.

  • case study ipv6 based building automation solution integration into an ipv4 Network service provider infrastructure
    2012
    Co-Authors: Nikolay Milovanov, Ivan Bogomilov
    Abstract:

    The article presents a case study describing an Internet Protocol (IP) version 6 (v6) introduction to an IPv4 Internet Service Provider (ISP) Network infrastructure. The case study driver is an ISP willing to introduce a new "killer" service related to Internet of Things (IoT) style building automation. The service will be sold and provided by the provider and cooperation of third party companies specialized in building automation. The ISP has to deliver the Network Access Layer and to accommodate the building automation solution traffic throughout its Network infrastructure. The third party companies are system integrators and building automation solution vendors. The solution has to be IPv6 based because of the following facts. The operator's current Network can't accommodate large number of IPv4 embedded devices due to the lack of address space. The manufacturing costs for an embedded device with a dual IP stack are higher then the same one for a device with a single stack. The Authors propose a strategy for IPv6 introduction into operator infrastructure based on the current Network architecture present service portfolio and several transition mechanisms. The strategy has been applied in laboratory with setup close enough to the current operator's Network. The criterion for a successful experiment is full two-way IPv6 application Layer connectivity between the IPv6 server and the IPv6 Internet of Things (IoT) cloud.

Nikolay Milovanov - One of the best experts on this subject based on the ideXlab platform.

  • ipv6 based building automation solution integration into an ipv4 Network service provider infrastructure case study
    Computer Systems and Technologies, 2012
    Co-Authors: Nikolay Milovanov, Ivan Bogomilov
    Abstract:

    The paper describes an Internet Protocol (IP) version 6 (v6) introduction to an IP version 4 (v4) Internet Service Provider (ISP) Network infrastructure. The case study driver is an ISP willing to introduce a new "killer" service related to Internet of Things (IoT) style building automation. The ISP and cooperation of third party companies specialized in building automation will provide the service. The ISP has to deliver the Network Access Layer and to accommodate the building automation solution traffic throughout its Network infrastructure. The third party companies are system integrators and building automation solution vendors. IPv6 is suitable for such solutions due to the following reasons. The operator can't accommodate large number of IPv4 embedded devices in its current Network due to the lack of address space and the fact that many of those will need clear 2-way IP communication channel. The Authors propose a strategy for IPv6 introduction into operator infrastructure based on the current Network architecture, present service portfolio and several transition mechanisms. The strategy has been tested in laboratory with setup close or identical to the current operator's Network. The criteria for a successful experiment is full two-way IPv6 application Layer connectivity between the IPv6 server and the IPv6 Internet of Things (IoT) cloud.

  • case study ipv6 based building automation solution integration into an ipv4 Network service provider infrastructure
    2012
    Co-Authors: Nikolay Milovanov, Ivan Bogomilov
    Abstract:

    The article presents a case study describing an Internet Protocol (IP) version 6 (v6) introduction to an IPv4 Internet Service Provider (ISP) Network infrastructure. The case study driver is an ISP willing to introduce a new "killer" service related to Internet of Things (IoT) style building automation. The service will be sold and provided by the provider and cooperation of third party companies specialized in building automation. The ISP has to deliver the Network Access Layer and to accommodate the building automation solution traffic throughout its Network infrastructure. The third party companies are system integrators and building automation solution vendors. The solution has to be IPv6 based because of the following facts. The operator's current Network can't accommodate large number of IPv4 embedded devices due to the lack of address space. The manufacturing costs for an embedded device with a dual IP stack are higher then the same one for a device with a single stack. The Authors propose a strategy for IPv6 introduction into operator infrastructure based on the current Network architecture present service portfolio and several transition mechanisms. The strategy has been applied in laboratory with setup close enough to the current operator's Network. The criterion for a successful experiment is full two-way IPv6 application Layer connectivity between the IPv6 server and the IPv6 Internet of Things (IoT) cloud.

Scott Shenker - One of the best experts on this subject based on the ideXlab platform.

  • Extending Networking into the Virtualization Layer.
    8th ACM Workshop on Hot Topics inNetworks, 2009
    Co-Authors: Ben Pfaff, Keith Amidon, Justin Pettit, Teemu Koponen, Martin Casado, Scott Shenker
    Abstract:

    The move to virtualization has created a new Network Access Layer residing on hosts that connects the various VMs. Virtualized deployment environments impose re- quirements on Networking for which traditional models are not well suited. They also provide advantages to the Networking Layer (such as software flexibility and well- defined end host events) that are not present in physical Networks. To date, this new virtualization Network Layer has been largely built around standard Ethernet switching, but this technology neither satisfies these new requirements nor leverages the available advantages. We present Open vSwitch, a Network switch specifically built for virtual environments. Open vSwitch differs from traditional approaches in that it exports an external interface for fine-grained control of configuration state and forwarding behavior. We describe how Open vSwitch can be used to tackle problems such as isolation in joint-tenant environments, mobility across subnets, and distributing configuration and visibility across hosts.

Ben Pfaff - One of the best experts on this subject based on the ideXlab platform.

  • Extending Networking into the Virtualization Layer.
    8th ACM Workshop on Hot Topics inNetworks, 2009
    Co-Authors: Ben Pfaff, Keith Amidon, Justin Pettit, Teemu Koponen, Martin Casado, Scott Shenker
    Abstract:

    The move to virtualization has created a new Network Access Layer residing on hosts that connects the various VMs. Virtualized deployment environments impose re- quirements on Networking for which traditional models are not well suited. They also provide advantages to the Networking Layer (such as software flexibility and well- defined end host events) that are not present in physical Networks. To date, this new virtualization Network Layer has been largely built around standard Ethernet switching, but this technology neither satisfies these new requirements nor leverages the available advantages. We present Open vSwitch, a Network switch specifically built for virtual environments. Open vSwitch differs from traditional approaches in that it exports an external interface for fine-grained control of configuration state and forwarding behavior. We describe how Open vSwitch can be used to tackle problems such as isolation in joint-tenant environments, mobility across subnets, and distributing configuration and visibility across hosts.

Keith Amidon - One of the best experts on this subject based on the ideXlab platform.

  • Extending Networking into the Virtualization Layer.
    8th ACM Workshop on Hot Topics inNetworks, 2009
    Co-Authors: Ben Pfaff, Keith Amidon, Justin Pettit, Teemu Koponen, Martin Casado, Scott Shenker
    Abstract:

    The move to virtualization has created a new Network Access Layer residing on hosts that connects the various VMs. Virtualized deployment environments impose re- quirements on Networking for which traditional models are not well suited. They also provide advantages to the Networking Layer (such as software flexibility and well- defined end host events) that are not present in physical Networks. To date, this new virtualization Network Layer has been largely built around standard Ethernet switching, but this technology neither satisfies these new requirements nor leverages the available advantages. We present Open vSwitch, a Network switch specifically built for virtual environments. Open vSwitch differs from traditional approaches in that it exports an external interface for fine-grained control of configuration state and forwarding behavior. We describe how Open vSwitch can be used to tackle problems such as isolation in joint-tenant environments, mobility across subnets, and distributing configuration and visibility across hosts.