The Experts below are selected from a list of 168 Experts worldwide ranked by ideXlab platform
Kyoungsoo Park - One of the best experts on this subject based on the ideXlab platform.
-
a case for a stateful middlebox Networking Stack
ACM Special Interest Group on Data Communication, 2015Co-Authors: Muhammad Jamshed, Donghwi Kim, Younggyoun Moon, Dongsu Han, Kyoungsoo ParkAbstract:Statful middleboxes such as intrustion detection systems, application-layer firewalls, and protocol analyzers are increasingly popular as they perform critical operations in modern networks. Such middleboxes typically operate by maintaining flow states of live TCP connections that pass through a network. Despite its growing demand, developing a stateful middlebox remains a challenging task. The root of complexity stems from a lack of common programming abstraction for middleboxes that clearly separates flow management from custom middlebox logic. As a result, middlebox developers often resort to writing a complex flow management module from scratch, which results in tens of thousands of code lines that are hardly portable [4, 2]. This is in stark contrast to developing Networking applications for end nodes, which significantly benefits from a nice network abstraction layer such as Berkeley socket API. The lack of a reusable Networking Stack for middleboxes makes the code highly dependent on a custom packet library, which greatly reduces readability, modularity, and extensibility. In this work, we formulate a general-purpose flow management Stack that serves the basic requirements of monitoring middlebox applications. The flow management Stack should satisfy three requirements. First, it should abstract TCP state management such that the developers can focus on the custom middlebox processing instead of dealing with low level detail. Clear separation of flow management and a custom middlebox logic is the key to high code readability and modularity. Second, it should be flexible enough to express any packet or flow-level event that triggers a special middlebox operation. An event can be as simple as TCP state change or packet retransmission. Or one should be able to extend a basic event by evaluating an arbitrary function (e.g., retransmitted packet whose content is different from the original packet). A flexible event-based system enables a developer to write a middlebox application as a set of logical middlebox events and their event handlers. Third, the flow management Stack should allow efficient resource management. Depending on the needs of a middlebox, a developer might want to avoid the flow reassembly on the server side while she actively monitors the flow content from the client side. Or one should be able to deallocate all resources for a flow even if the flow has not terminated yet.
-
SIGCOMM - A Case for a Stateful Middlebox Networking Stack
Proceedings of the 2015 ACM Conference on Special Interest Group on Data Communication - SIGCOMM '15, 2015Co-Authors: Muhammad Jamshed, Donghwi Kim, Younggyoun Moon, Dongsu Han, Kyoungsoo ParkAbstract:Statful middleboxes such as intrustion detection systems, application-layer firewalls, and protocol analyzers are increasingly popular as they perform critical operations in modern networks. Such middleboxes typically operate by maintaining flow states of live TCP connections that pass through a network. Despite its growing demand, developing a stateful middlebox remains a challenging task. The root of complexity stems from a lack of common programming abstraction for middleboxes that clearly separates flow management from custom middlebox logic. As a result, middlebox developers often resort to writing a complex flow management module from scratch, which results in tens of thousands of code lines that are hardly portable [4, 2]. This is in stark contrast to developing Networking applications for end nodes, which significantly benefits from a nice network abstraction layer such as Berkeley socket API. The lack of a reusable Networking Stack for middleboxes makes the code highly dependent on a custom packet library, which greatly reduces readability, modularity, and extensibility. In this work, we formulate a general-purpose flow management Stack that serves the basic requirements of monitoring middlebox applications. The flow management Stack should satisfy three requirements. First, it should abstract TCP state management such that the developers can focus on the custom middlebox processing instead of dealing with low level detail. Clear separation of flow management and a custom middlebox logic is the key to high code readability and modularity. Second, it should be flexible enough to express any packet or flow-level event that triggers a special middlebox operation. An event can be as simple as TCP state change or packet retransmission. Or one should be able to extend a basic event by evaluating an arbitrary function (e.g., retransmitted packet whose content is different from the original packet). A flexible event-based system enables a developer to write a middlebox application as a set of logical middlebox events and their event handlers. Third, the flow management Stack should allow efficient resource management. Depending on the needs of a middlebox, a developer might want to avoid the flow reassembly on the server side while she actively monitors the flow content from the client side. Or one should be able to deallocate all resources for a flow even if the flow has not terminated yet.
Jinyeop Chang - One of the best experts on this subject based on the ideXlab platform.
-
hons hybrid open Networking Stack for diverse wireless sensor networks
International Conference on Embedded Networked Sensor Systems, 2009Co-Authors: Jeonghoon Kang, Sukun Kim, Taejoon Choi, Pilman Jeong, Jinyeop ChangAbstract:HONS (Hybrid Open Networking Stack) is a system which can service diverse types of sensor nodes as a single network. By defining open packet format of IEEE 802.15.4 standard, it can form low-power multi-hop network of diverse sensors. HONS system is composed of routers and wireless sensor nodes. Routers are motes with wired power and form the basic backbone of the multi-hop network. Wireless sensor nodes are motes powered by battery, and operate in a lower-power mode, and are attached to the multi-hop network formed by routers.
-
SenSys - HONS (hybrid open Networking Stack) for diverse wireless sensor networks
Proceedings of the 7th ACM Conference on Embedded Networked Sensor Systems - SenSys '09, 2009Co-Authors: Jeonghoon Kang, Sukun Kim, Taejoon Choi, Pilman Jeong, Jinyeop ChangAbstract:HONS (Hybrid Open Networking Stack) is a system which can service diverse types of sensor nodes as a single network. By defining open packet format of IEEE 802.15.4 standard, it can form low-power multi-hop network of diverse sensors. HONS system is composed of routers and wireless sensor nodes. Routers are motes with wired power and form the basic backbone of the multi-hop network. Wireless sensor nodes are motes powered by battery, and operate in a lower-power mode, and are attached to the multi-hop network formed by routers.
Muhammad Jamshed - One of the best experts on this subject based on the ideXlab platform.
-
a case for a stateful middlebox Networking Stack
ACM Special Interest Group on Data Communication, 2015Co-Authors: Muhammad Jamshed, Donghwi Kim, Younggyoun Moon, Dongsu Han, Kyoungsoo ParkAbstract:Statful middleboxes such as intrustion detection systems, application-layer firewalls, and protocol analyzers are increasingly popular as they perform critical operations in modern networks. Such middleboxes typically operate by maintaining flow states of live TCP connections that pass through a network. Despite its growing demand, developing a stateful middlebox remains a challenging task. The root of complexity stems from a lack of common programming abstraction for middleboxes that clearly separates flow management from custom middlebox logic. As a result, middlebox developers often resort to writing a complex flow management module from scratch, which results in tens of thousands of code lines that are hardly portable [4, 2]. This is in stark contrast to developing Networking applications for end nodes, which significantly benefits from a nice network abstraction layer such as Berkeley socket API. The lack of a reusable Networking Stack for middleboxes makes the code highly dependent on a custom packet library, which greatly reduces readability, modularity, and extensibility. In this work, we formulate a general-purpose flow management Stack that serves the basic requirements of monitoring middlebox applications. The flow management Stack should satisfy three requirements. First, it should abstract TCP state management such that the developers can focus on the custom middlebox processing instead of dealing with low level detail. Clear separation of flow management and a custom middlebox logic is the key to high code readability and modularity. Second, it should be flexible enough to express any packet or flow-level event that triggers a special middlebox operation. An event can be as simple as TCP state change or packet retransmission. Or one should be able to extend a basic event by evaluating an arbitrary function (e.g., retransmitted packet whose content is different from the original packet). A flexible event-based system enables a developer to write a middlebox application as a set of logical middlebox events and their event handlers. Third, the flow management Stack should allow efficient resource management. Depending on the needs of a middlebox, a developer might want to avoid the flow reassembly on the server side while she actively monitors the flow content from the client side. Or one should be able to deallocate all resources for a flow even if the flow has not terminated yet.
-
SIGCOMM - A Case for a Stateful Middlebox Networking Stack
Proceedings of the 2015 ACM Conference on Special Interest Group on Data Communication - SIGCOMM '15, 2015Co-Authors: Muhammad Jamshed, Donghwi Kim, Younggyoun Moon, Dongsu Han, Kyoungsoo ParkAbstract:Statful middleboxes such as intrustion detection systems, application-layer firewalls, and protocol analyzers are increasingly popular as they perform critical operations in modern networks. Such middleboxes typically operate by maintaining flow states of live TCP connections that pass through a network. Despite its growing demand, developing a stateful middlebox remains a challenging task. The root of complexity stems from a lack of common programming abstraction for middleboxes that clearly separates flow management from custom middlebox logic. As a result, middlebox developers often resort to writing a complex flow management module from scratch, which results in tens of thousands of code lines that are hardly portable [4, 2]. This is in stark contrast to developing Networking applications for end nodes, which significantly benefits from a nice network abstraction layer such as Berkeley socket API. The lack of a reusable Networking Stack for middleboxes makes the code highly dependent on a custom packet library, which greatly reduces readability, modularity, and extensibility. In this work, we formulate a general-purpose flow management Stack that serves the basic requirements of monitoring middlebox applications. The flow management Stack should satisfy three requirements. First, it should abstract TCP state management such that the developers can focus on the custom middlebox processing instead of dealing with low level detail. Clear separation of flow management and a custom middlebox logic is the key to high code readability and modularity. Second, it should be flexible enough to express any packet or flow-level event that triggers a special middlebox operation. An event can be as simple as TCP state change or packet retransmission. Or one should be able to extend a basic event by evaluating an arbitrary function (e.g., retransmitted packet whose content is different from the original packet). A flexible event-based system enables a developer to write a middlebox application as a set of logical middlebox events and their event handlers. Third, the flow management Stack should allow efficient resource management. Depending on the needs of a middlebox, a developer might want to avoid the flow reassembly on the server side while she actively monitors the flow content from the client side. Or one should be able to deallocate all resources for a flow even if the flow has not terminated yet.
Eric Fleury - One of the best experts on this subject based on the ideXlab platform.
-
Neighbor discovery analysis in wireless sensor networks
2006Co-Authors: Elyes Ben Hamida, Guillaume Chelius, Eric FleuryAbstract:In wireless sensor networks, hello protocols for neighbor discovery are a basic service offered by the Networking Stack. However, their study usually rely on rather simplistic models. In this paper we study the impact of radio interferences on neighbor discovery and we introduce an analytical model to estimate the average number of neighbors that a node may expect to discover in his neighborhood.
-
Revisiting neighbor discovery with interferences consideration
2006Co-Authors: Elyes Ben Hamida, Guillaume Chelius, Eric FleuryAbstract:In wireless multi-hop networks, hello protocols for neighbor discovery are a basic service offered by the Networking Stack. However, their study usually rely on rather simplistic models which do not take into account problems resulting from low level layers, such as the physical layer. One of the peculiarities of radio communications is the presence of interferences which decrease the capacity of the medium.In this paper, we consider a random hello protocol inspired by aloha and we study the impact of the interferences on the neighbor discovery process. As expected, we prove that, in average and in the presence of interferences, a node discovers only a subset of its neighbors. We propose then an analytical model to compute the average number of nodes that a given node may expect to discover in its neighborhood.Finally, we present a hello protocol with sleep periods. We show how to optimize this protocol using our hybrid model. A real scenario stemming from the CAPNET project is then analyzed and studied.
Dongsu Han - One of the best experts on this subject based on the ideXlab platform.
-
a case for a stateful middlebox Networking Stack
ACM Special Interest Group on Data Communication, 2015Co-Authors: Muhammad Jamshed, Donghwi Kim, Younggyoun Moon, Dongsu Han, Kyoungsoo ParkAbstract:Statful middleboxes such as intrustion detection systems, application-layer firewalls, and protocol analyzers are increasingly popular as they perform critical operations in modern networks. Such middleboxes typically operate by maintaining flow states of live TCP connections that pass through a network. Despite its growing demand, developing a stateful middlebox remains a challenging task. The root of complexity stems from a lack of common programming abstraction for middleboxes that clearly separates flow management from custom middlebox logic. As a result, middlebox developers often resort to writing a complex flow management module from scratch, which results in tens of thousands of code lines that are hardly portable [4, 2]. This is in stark contrast to developing Networking applications for end nodes, which significantly benefits from a nice network abstraction layer such as Berkeley socket API. The lack of a reusable Networking Stack for middleboxes makes the code highly dependent on a custom packet library, which greatly reduces readability, modularity, and extensibility. In this work, we formulate a general-purpose flow management Stack that serves the basic requirements of monitoring middlebox applications. The flow management Stack should satisfy three requirements. First, it should abstract TCP state management such that the developers can focus on the custom middlebox processing instead of dealing with low level detail. Clear separation of flow management and a custom middlebox logic is the key to high code readability and modularity. Second, it should be flexible enough to express any packet or flow-level event that triggers a special middlebox operation. An event can be as simple as TCP state change or packet retransmission. Or one should be able to extend a basic event by evaluating an arbitrary function (e.g., retransmitted packet whose content is different from the original packet). A flexible event-based system enables a developer to write a middlebox application as a set of logical middlebox events and their event handlers. Third, the flow management Stack should allow efficient resource management. Depending on the needs of a middlebox, a developer might want to avoid the flow reassembly on the server side while she actively monitors the flow content from the client side. Or one should be able to deallocate all resources for a flow even if the flow has not terminated yet.
-
SIGCOMM - A Case for a Stateful Middlebox Networking Stack
Proceedings of the 2015 ACM Conference on Special Interest Group on Data Communication - SIGCOMM '15, 2015Co-Authors: Muhammad Jamshed, Donghwi Kim, Younggyoun Moon, Dongsu Han, Kyoungsoo ParkAbstract:Statful middleboxes such as intrustion detection systems, application-layer firewalls, and protocol analyzers are increasingly popular as they perform critical operations in modern networks. Such middleboxes typically operate by maintaining flow states of live TCP connections that pass through a network. Despite its growing demand, developing a stateful middlebox remains a challenging task. The root of complexity stems from a lack of common programming abstraction for middleboxes that clearly separates flow management from custom middlebox logic. As a result, middlebox developers often resort to writing a complex flow management module from scratch, which results in tens of thousands of code lines that are hardly portable [4, 2]. This is in stark contrast to developing Networking applications for end nodes, which significantly benefits from a nice network abstraction layer such as Berkeley socket API. The lack of a reusable Networking Stack for middleboxes makes the code highly dependent on a custom packet library, which greatly reduces readability, modularity, and extensibility. In this work, we formulate a general-purpose flow management Stack that serves the basic requirements of monitoring middlebox applications. The flow management Stack should satisfy three requirements. First, it should abstract TCP state management such that the developers can focus on the custom middlebox processing instead of dealing with low level detail. Clear separation of flow management and a custom middlebox logic is the key to high code readability and modularity. Second, it should be flexible enough to express any packet or flow-level event that triggers a special middlebox operation. An event can be as simple as TCP state change or packet retransmission. Or one should be able to extend a basic event by evaluating an arbitrary function (e.g., retransmitted packet whose content is different from the original packet). A flexible event-based system enables a developer to write a middlebox application as a set of logical middlebox events and their event handlers. Third, the flow management Stack should allow efficient resource management. Depending on the needs of a middlebox, a developer might want to avoid the flow reassembly on the server side while she actively monitors the flow content from the client side. Or one should be able to deallocate all resources for a flow even if the flow has not terminated yet.