Skip to main content
The impending exhaustion of internet protocol (IP) version four (IPv4) addresses necessitates a transition to the more expansive IP version six (IPv6) protocol. However, this shift faces challenges due to the widespread legacy of IPv4... more
The impending exhaustion of internet protocol (IP) version four (IPv4) addresses necessitates a transition to the more expansive IP version six (IPv6) protocol. However, this shift faces challenges due to the widespread legacy of IPv4 infrastructure and resistance among organizations to overhaul networks. Host-based translators offer a critical bridging solution by enabling IPv6-only devices to communicate with IPv4-only devices through software-level protocol translation. This paper comprehensively evaluates four pivotal host-based translator mechanisms—bump-in-the-stack (BIS), bump-in-the-application programming interface (API) (BIA), BIA version 2 (BIAv2), and bump-in-the-host (BIH). Using simulated networks with diverse configurations of IPv4/IPv6 applications, hosts, and routing protocols, the authors assessed performance through metrics including packet loss, convergence time, traffic throughput, and overhead. The results reveal variability in effectiveness across both transla...
The Web of Things (WoT) is a concept that aims to create a network of intelligent devices capable of remote monitoring, service provisioning, and control. Virtual and Physical Internet of Things (IoT) gateways facilitate communication,... more
The Web of Things (WoT) is a concept that aims to create a network of intelligent devices capable of remote monitoring, service provisioning, and control. Virtual and Physical Internet of Things (IoT) gateways facilitate communication, processing, and storage among social nodes that form the social Web of Things (SWoT). Peripheral IoT services commonly use device data. However, due to the limited bandwidth and processing power of edge devices in the IoT, they must dynamically alter the quality of service provided to their connected clients to meet each user's needs while also meeting the service quality requirements of other devices that may access the same data. Consequently, deciding which transactions get access to which Internet of Things data is a scheduling problem. Edge-cloud computing requires transaction management because several Internet of Things transactions may access shared data simultaneously. However, cloud transaction management methods cannot be employed in ed...
One area of anatomy, which is a true passage of secrecy, is the anatomy of the potential anatomical spaces. The study of the fascial layers of the head and neck and the potential spaces they make-up is both fascinating and confusing. Much... more
One area of anatomy, which is a true passage of secrecy, is the anatomy of the potential anatomical spaces. The study of the fascial layers of the head and neck and the potential spaces they make-up is both fascinating and confusing. Much of the confusion is a function of the multiple synonymous terms and classifications that various authors use, and not the basic anatomical description. Their anatomy and communications, to the base of skull and downward to diaphragm, acts like a route through which infection from mouth and throat can reach the superior mediastinum. Understanding the anatomy of the parapharyngeal space is important in making a correct diagnosis and surgical plan for removing tumors in this region.
This paper evaluates and compares the performance of some selected network-based translators (e.g. SIIT, AIN-SLT and AIN-PT). The rationale behind this paper is to investigate the performance of heterogeneous networks (i.e. IPv4/IPv6... more
This paper evaluates and compares the performance of some selected network-based translators (e.g. SIIT, AIN-SLT and AIN-PT). The rationale behind this paper is to investigate the performance of heterogeneous networks (i.e. IPv4/IPv6 networks) when different types of network-based translators are used. The SIIT protocol translates full IP packet headers when connections are initiated from IPv4-only networks to IPv6-only networks and vice-versa. Whereas, the AIN-PT protocol uses tunneling approach to achieve the interoperability between IPv4-only/IPv6-only networks without translating full IP packet headers. Similarly, the AIN-SLT protocol uses the IPv6/IPv4 socket Application Programming Interface (API) translation technique instead of translating the packet headers between two heterogeneous networks. This could be achieved by ending IPv6/IPv4 connection points at the application layer. The experimental results show that the performance analysis of AIN-PT protocol is much better than that of SIIT and AIN-SLT protocols.
Abstract This paper introduces a new mechanism called AIN-PT, which stands for Assuring Interoperability between heterogeneous (IPv4/IPv6) Networks without ("minus") using Protocol Translation. The mechanism intends to make... more
Abstract This paper introduces a new mechanism called AIN-PT, which stands for Assuring Interoperability between heterogeneous (IPv4/IPv6) Networks without ("minus") using Protocol Translation. The mechanism intends to make communication between two heterogeneous networks (operating on two different IP protocols) possible by tunneling IPv4 packets in IPv6 packets, instead of translating complete headers between IPv4 and IPv6. With the AIN-PT mechanism, the translation is limited to mapping addresses between IPv4 and IPv6. This mechanism can be deployed by Internet Service Providers (ISPs) or any other service providers in different stages of the transition to IPv6. The performance of AIN-PT was measured on different interoperation network scenarios, and the overall performance analysis showed that AIN-PT has better performance, in comparison with current protocol translation-based techniques.
ABSTRACT In this paper we introduce a mechanism for hosts to use applications of any IP version capability (IPv4-only, IPv6 only, or dual IPv4/IPv6) regardless of the IP version of their network communication (IPv4 or IPv6), without any... more
ABSTRACT In this paper we introduce a mechanism for hosts to use applications of any IP version capability (IPv4-only, IPv6 only, or dual IPv4/IPv6) regardless of the IP version of their network communication (IPv4 or IPv6), without any modification to those programs. DAC effectively shields the application layer IPv4/IPv6 operation from the underlying IPv4/IPv6 communication between the hosts. The authors consider the provision of this kind of functionality an essential condition for the changeover towards IPv6 to succeed. The proposed mechanism is a generalisation of an experimental protocol called “Bump-in-the-API (BIA)”
This document describes a bi-directional IPv6/IPv4 Socket Layer Translator (SLT) for border gateway routers. The new technique is called AIN-SLT which stands for Assuring Interconnection between Heterogeneous (IPv4/IPv6) Networks Using... more
This document describes a bi-directional IPv6/IPv4 Socket Layer Translator (SLT) for border gateway routers. The new technique is called AIN-SLT which stands for Assuring Interconnection between Heterogeneous (IPv4/IPv6) Networks Using SLT. This mechanism assures a smooth heterogeneous communication between IPv6 and IPv4 nodes without using protocol translation. It applies IPv6/IPv4 socket Application Programming Interface (API) translation methodology between two heterogeneous networks by terminating IPv6/IPv4 connection points at the application layer. The AIN-SLT mechanism has many advantages over current translation/tunneling approaches, and so it does not require any configuration at end-users’ hosts, it has the ability to translate non-NAT friendly traffic (i.e. FTP and SIP traffic), and it achieves a reliable communication by not breaking end-to-end protocol characteristics and security at physical layer (i.e. IPsec).
draft-hamarsheh-behave-biav2-01 This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual... more
draft-hamarsheh-behave-biav2-01 This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification to those applications. It is a generalisation of a previous experimental protocol called "Bump-in-the-API" (BIA) [RFC3338]. New mechanism of BIA allows a changeover between the application layer and the IP communication layers from IPv4 to IPv6 and vice versa or IPv6 to IPv4 and vice versa, without requiring those applications to be converted in addressing capabilities, effectively shielding the application layer from IPv4 or IPv6 connectivity. This is considered by the authors to be one of the essential conditions for the transition to IPv6 in the Internet to be successful.
Cloud computing is an emerging and innovative technology that has taken the business information systems to wider extent with the fast sharing of vast web resources over the internet. It considers as an extension to distributed and... more
Cloud computing is an emerging and innovative technology that has taken the business information systems to wider extent with the fast sharing of vast web resources over the internet. It considers as an extension to distributed and parallel computing. Additionally, it enables sharing, organizing and aggregation of computational machines to satisfy the user demands. Utilizing the resources efficiently is the main challenge of cloud service provider. Task scheduling in cloud computing plays the main role in decreasing the execution time and cost and hence, increasing the profit. This paper addresses the problem independent tasks scheduling over different virtual machines in computational cloud environment. It introduces two batch mode heuristics algorithms for scheduling independent task: high mean absolute deviation first heuristic and QoS Guided Sufferage-HMADF heuristic. Besides, the paper presented other existing batch mode heuristics such as, Min-Min, Max-Min and Sufferage. The f...
This paper analyzes the technical and nontechnical impediments for a smooth and successful transition from IPv4 protocol to IPv6 protocol in the Internet. It tries to illustrate and defines most obstacles that hold the widespread... more
This paper analyzes the technical and nontechnical impediments for a smooth and successful transition from IPv4 protocol to IPv6 protocol in the Internet. It tries to illustrate and defines most obstacles that hold the widespread deployment of IPv6 at both sides: end-users and Internet Service Providers (ISPs). The paper also suggests transparent, auto-configured, and cost effective solutions for both end-users and ISPs parties to allow a smooth and successful widespread deployment of IPv6.
Cloud computing is an emerging and innovative technology that is used for solving large-scale complex problems. It considers as an extension to distributed and parallel computing. Additionally, it enables sharing, organizing and... more
Cloud computing is an emerging and innovative technology that is used for solving large-scale complex problems. It considers as an extension to distributed and parallel computing. Additionally, it enables sharing, organizing and aggregation of computational machines to satisfy the user demands. One of the main goals of the task scheduling is to minimize the makespan (i.e. the overall processing time) and maximize the machine utilization. This paper addresses the problem of how to schedule many independent tasks when using different machines. It introduces two batch mode heuristics algorithms for scheduling independent task in the computational cloud environment, high mean absolute deviation first heuristic and QoS Guided Sufferage-HMADF heuristic. Besides, the paper presented other existing batch mode heuristics such as, Min-Min, Max-Min and Sufferage. The four heuristic modes are simulated and the experimental results are discussed using two performance measures, makespan and machi...
This paper addresses a new optimisticbased concurrency control protocol, called OCC-Mix. The proposed protocol could be used to reduce the scars wasting and expensive resources of mobile environment. This can be achieved by avoiding the... more
This paper addresses a new optimisticbased concurrency control protocol, called OCC-Mix. The proposed protocol could be used to reduce the scars wasting and expensive resources of mobile environment. This can be achieved by avoiding the unnecessary mobile transaction restarts. Consequently, a dynamic adjustment of serialization order in the conflicting transactions with respect to the validating transaction will be used. As a result, much resources of mobile environment are saved and a many fixed host transactions finished their execution without being affected by other mobile transactions. The performance of the proposed protocol was measured along with other related CC protocols; the simulation results show that the performance of these protocols is consistently much better than the traditional 2PL and OCC protocols in mixed transaction environments. Subject Categories and Descriptors C.2.1 [Network Architecture and Design]; Wireless communication: H.2.4 [Systems]; Concurrency: C....
This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification to... more
This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification to those applications. It is a generalisation of a previous experimental protocol called "Bump-in- the-API" (BIA) [RFC3338]. New mechanism of BIA allows a changeover between the application layer and the IP communication layers from IPv4 to IPv6 and vice versa or IPv6 to IPv4 and vice versa, without requiring those applications to be converted in addressing capabilities, effectively shielding the application layer from IPv4 or IPv6 connectivity. This is considered by the authors to be one of the essential conditions for the transition to IPv6 in the Internet to be successful.
This paper introduces a new protocol called D6across4, which stands for Deploying IPv6 Service across local IPv4 access networks. The protocol aims to encourage Internet Service Providers (ISPs) to start deploying IPv6 service to their... more
This paper introduces a new protocol called D6across4, which stands for Deploying IPv6 Service across local IPv4 access networks. The protocol aims to encourage Internet Service Providers (ISPs) to start deploying IPv6 service to their customers (end-users). It utilizes the automatic IPv6-in-IPv4 tunnels to transport IPv6 traffic (data and control information) over local IPv4 access networks. The key aspects of this protocol include: providing IPv6 service to end-users equivalent to native one, stateful operation, and requiring simple configurations on both end-user's host and ISP sides at the time of setup. D6across4 connected hosts can communicate with other IPv6 hosts outside their local IPv4 access network. The simulation results showed that D6across4 performance parameters (e.g. latency and throughput) are acceptable in comparison to both IPv4 and IPv6 performance parameters.
This paper presents a new SRNC relocation approach based on BOFC functions. The new approach handles all possible combinations of the user equipment movements, particularly, when it moves across overlapped regions with different GGSN... more
This paper presents a new SRNC relocation approach based on BOFC functions. The new approach handles all possible combinations of the user equipment movements, particularly, when it moves across overlapped regions with different GGSN branches. Additionally, it integrates both RNC and BS levels in order to reduce the number of packets loss during the hard handover process. The experimental results showed that the new approach reduces the packet-loss ratio in comparison to both SRNC and BOFC approaches. Besides, the experimental results showed that the average execution time of the handover procedure in each network component is closed to the average execution time of the BOFC approach.
This paper explores the main impediments that negatively affect deploying IPv6 in the Internet. Additionally, it presents the latest mechanisms and protocols that allow a smooth transition to IPv6. This could be achieved by merging the... more
This paper explores the main impediments that negatively affect deploying IPv6 in the Internet. Additionally, it presents the latest mechanisms and protocols that allow a smooth transition to IPv6. This could be achieved by merging the IPv6 protocol along-side with the IPv4 protocol until the IPv6 is fully deployed. The paper also presents cost-effective protocols that might lead to improve the transition process and encourage the ISPs and the end users to start using the IPv6 protocol.
ABSTRACT This document specifies a new mechanism called D4across6, which stands for Deploying IPv4-only Connectivity across Local IPv6-only Access Networks. This protocol could be used to ease the process of transition to IPv6 protocol,... more
ABSTRACT This document specifies a new mechanism called D4across6, which stands for Deploying IPv4-only Connectivity across Local IPv6-only Access Networks. This protocol could be used to ease the process of transition to IPv6 protocol, particularly in the ISPs’ access networks. This protocol allows legacy IPv4-only devices to communicate with IPv4-only content providers over an IPv6-only infrastructure. The main part is an application level tunnelling protocol that allows IPv6-only ISPs to provide IPv4 connectivity in addition to IPv6 connectivity across IPv6-only access networks. It carries IPv4 packets and routing information of the IPv4 protocol over an IPv6-only network infrastructure. The features of the proposed protocol are: offers IPv4 connectivity across IPv6-only access networks, stateless operation, cost-effective solution, and requires simple and automatic configuration at customers’ hosts. D4across6 requires installing an application and a pseudo network driver at the IPv4-only hosts in order to allow them to communicate with IPv4-only content providers. The configured IPv4-only hosts will be able to auto-detect the ISP available connectivity in the following precedence: native IPv6, IPv4-in-IPv6, or no IPv4 connectivity. The protocol does not require replacing or upgrading customer edges. Thus, a minimal cost is expected in providing IPv4-only connectivity after successfully deploying of IPv6 service to subscribers. The simulation analysis showed that the performance metrics of D4across6 is pretty near to those of native IPv6 and IPv4 protocols. Additionally, the performance of D4across6 is better than that of all (A+P), DS-Lite and 4rd protocols.
This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification to... more
This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification to those applications. It is a generalisation of a previous experimental protocol called "Bump-in-the-API" (BIA) [RFC3338]. New mechanism of BIA allows a changeover between the application layer and the IP communication layers from IPv4 to IPv6 and vice versa or IPv6 to IPv4 and vice versa, without requiring those applications to be converted in addressing capabilities, effectively shielding the application layer from IPv4 or IPv6 connectivity. This is considered by the authors to be one of the essential conditions for the transition to IPv6 in the Internet to be successful.
This paper proposes a new steganography mechanism which can be used to hide text-in-text messages using the Omega Network (Multistage Network). Unlike other steganography methods that are introduced to hide secret messages (i.e.... more
This paper proposes a new steganography mechanism which can be used to hide text-in-text messages using the Omega Network (Multistage Network). Unlike other steganography methods that are introduced to hide secret messages (i.e. Text-in-image, image-in-image, text-in-audio, etc.), this mechanism does not require to seek for a suitable cover message in order to hide the secret messages. Alternatively, the mechanism must be supported with any preferred dictionary which will be used in creating cover messages.
Research Interests:
This paper is to examine the IPv6 in Palestine and to examine where are Palestinian companies in the deployment process. Also, to examine if the infrastructure can withstand the transition to IPv6 or not. This study used quantitative... more
This paper is to examine the IPv6 in Palestine and to examine where are Palestinian companies in the deployment process. Also, to examine if the infrastructure can withstand the transition to IPv6 or not. This study used quantitative research methods and collect the data through a survey from the Internet companies in Palestine as reported anonymously. Due to the lack of research related to the internet in Palestine, we saw that it is necessary to discover the internet companies and how much they achieved of the deployment process. The collected data have been analyzed and described using SPSS. The data analysis showed that one internet company representing 11% of the companies in Palestine did apply the transition process to IPv6, and the percentages have set a positive indicator for the transition process. It turns out that the other companies on their way to start deploying the IPv6.
This document specifies a new IPv6 deployment protocol called CHANC, which stands for Configuring Hosts to Auto-detect (IPv6, IPv6-in-IPv4, or IPv4) Network Connectivity. The main part is an application level tunneling protocol that... more
This document specifies a new IPv6 deployment protocol called CHANC, which stands for Configuring Hosts to Auto-detect (IPv6, IPv6-in-IPv4, or IPv4) Network Connectivity. The main part is an application level tunneling protocol that allows Internet Service Providers (ISPs) to rapidly start deploying IPv6 service to their subscribers whom connected to the Internet via IPv4-only access networks. It carries IPv6 packets over HTTP protocol to be transmitted across IPv4-only network infrastructure. The key aspects of this protocol are: offers IPv6 connectivity via IPv4-only access networks, stateless operation, economical solution, assures most firewall traversal, and requires simple installation and automatic configuration at customers‟ hosts. All data packets and routing information of the IPv6 protocol will be carried over the IPv4 network infrastructure. A simple application and a pseudo network driver must be installed at the end-user‟s hosts to make them able to work with this prot...
ABSTRACT This paper analyses the technical and non-technical obstacles that block the widespread deployment of IPv6 on the Internet (at both sides: end-users and Internet Service Providers (ISPs)). It reviews the current basic and... more
ABSTRACT This paper analyses the technical and non-technical obstacles that block the widespread deployment of IPv6 on the Internet (at both sides: end-users and Internet Service Providers (ISPs)). It reviews the current basic and standard IPv6 transition mechanisms that have been proposed by the Internet Engineering Task Force (IETF). The paper also suggests transparent, auto-configured, and cost-effective solutions for both end-users and ISPs parties, and compares them with the current techniques to allow a smooth and successful widespread deployment of IPv6.
Mobile computing environment is subject to the constraints of bounded network bandwidth, frequently encountered disconnections, insufficient battery power, and system asymmetry. To meet these constraints and to gain high scalability, data... more
Mobile computing environment is subject to the constraints of bounded network bandwidth, frequently encountered disconnections, insufficient battery power, and system asymmetry. To meet these constraints and to gain high scalability, data broadcasting has been proposed on data transmission techniques. However, updates made to the database in any broadcast cycle are deferred to the next cycle in order to appear to mobile clients with lower data currency. The main goal of this paper is to enhance the transaction performance processing and database currency. The main approach involves decomposing the main broadcast cycle into a number of sub-cycles, where data items are broadcasted as they were originally sequenced in the main cycle while appearing in the most current versions. A concurrency control method AOCCRBSC is proposed to cope well with the cycle decomposition. The proposed method exploits predeclaration and adapts the AOCCRB method by customizing prefetching, back-off, and partial backward and forward validation techniques. As a result, more than one of the conflicting transactions is allowed to commit at the server in the same broadcast cycle which empowers the processing of both update and read-only transactions and improves data currency.
This article introduces a new technique to hide text-in-text messages. The proposed mechanism uses the structure of omega network to hide and extract secret messages. The generation of secret message is made as follows, take every letter... more
This article introduces a new technique to hide text-in-text messages. The proposed mechanism uses the structure of omega network to hide and extract secret messages. The generation of secret message is made as follows, take every letter from the original message, use the omega network to generate two related letters from the selected letter, and finally search the dictionary for a suitable English cover word to hide the generated two letters. In order to increase the chance of find a suitable words, the generated two letters need not to be adjacent in the cover word. As a result, the white-space steganography is used in order to hide the position of the two letters in the selected cover word. The experiments show that the proposed mechanism gives a better execution time and better cover words than the current similar mechanisms especially when we are trying to hide long text messages.
This paper addresses a new optimistic-based concurrency control protocol, called OCC-Mix. The proposed protocol could be used to reduce the scars wasting and expensive resources of mobile environment. This can be achieved by avoiding the... more
This paper addresses a new optimistic-based concurrency control protocol, called OCC-Mix. The proposed protocol could be used to reduce the scars wasting and expensive resources of mobile environment. This can be achieved by avoiding the unnecessary mobile transaction restarts. Consequently, a dynamic adjustment of serialization order in the conflicting transactions with respect to the validating transaction will be used. As a result, much resources of mobile environment are saved and a many fixed host transactions finished their execution without being affected by other mobile transactions. The performance of the proposed protocol was measured along with other related CC protocols; the simulation results show that the performance of these protocols is consistently much better than the traditional 2PL and OCC protocols in mixed transaction environments.
This paper evaluates and compares the performance of some selected network-based translators (e.g. SIIT, AIN-SLT and AIN-PT). The rationale behind this paper is to investigate the performance of heterogeneous networks (i.e. IPv4/IPv6... more
This paper evaluates and compares the performance of some selected network-based translators (e.g. SIIT, AIN-SLT and AIN-PT). The rationale behind this paper is to investigate the performance of heterogeneous networks (i.e. IPv4/IPv6 networks) when different types of network-based translators are used. The SIIT protocol translates full IP packet headers when connections are initiated from IPv4-only networks to IPv6-only networks and vice-versa. Whereas, the AIN-PT protocol uses tunneling approach to achieve the interoper‐ ability between IPv4-only/IPv6-only networks without translating full IP packet headers. Similarly, the AIN-SLT protocol uses the IPv6/IPv4 socket Application Programming Interface (API) translation technique instead of translating the packet headers between two heterogeneous networks. This could be achieved by ending IPv6/IPv4 connection points at the application layer. The experimental results show that the performance analysis of AIN-PT protocol is much better than that of SIIT and AIN-SLT protocols.
This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification to... more
This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification to those applications. It is a generalisation of a previous experimental protocol called "Bump-in-the-API" (BIA) [RFC3338]. New mechanism of BIA allows a changeover between the application layer and the IP communication layers from IPv4 to IPv6 and vice versa or IPv6 to IPv4 and vice versa, without requiring those applications to be converted in addressing capabilities, effectively shielding the application layer from IPv4 or IPv6 connectivity. This is considered by the authors to be one of the essential conditions for the transition to IPv6 in the Internet to be successful.
This paper proposes a new steganography mechanism which can be used to hide text-in-text messages using the Omega Network (Multistage Network). Unlike other steganography methods that are introduced to hide secret messages (i.e.... more
This paper proposes a new steganography mechanism which can
be used to hide text-in-text messages using the Omega Network
(Multistage Network). Unlike other steganography methods that
are introduced to hide secret messages (i.e. Text-in-image,
image-in-image, text-in-audio, etc.), this mechanism does not
require to seek for a suitable cover message in order to hide the
secret messages. Alternatively, the mechanism must be supported
with any preferred dictionary which will be used in creating
cover messages.
Research Interests:
This paper analyses the technical and non-technical obstacles that block the widespread deployment of IPv6 on the Internet (at both sides: end-users and Internet Service Providers (ISPs)). It reviews the current basic and standard IPv6... more
This paper analyses the technical and non-technical obstacles that block the widespread deployment of IPv6 on the Internet (at both sides: end-users and Internet Service Providers (ISPs)). It reviews the current basic and standard IPv6 transition mechanisms that have been proposed by the Internet Engineering Task Force (IETF). The paper also suggests transparent, auto-configured, and cost-effective solutions for both end-users and ISPs parties, and compares them with the current techniques to allow a smooth and successful widespread deployment of IPv6.
Research Interests:
영어 초록 In traditional unstructured P2P file sharing network, each peer establishes connections with a certain number of randomly chosen other peers. This would lead to redundant traffic and P2P network partition in mobile ad hoc network... more
영어 초록 In traditional unstructured P2P file sharing network, each peer establishes connections with a certain number of randomly chosen other peers. This would lead to redundant traffic and P2P network partition in mobile ad hoc network (MANET). We ...
In this paper we introduce a mechanism for hosts to use applications of any IP version capability (IPv4-only, IPv6 only, or dual IPv4/IPv6) regardless of the IP version of their network communication (IPv4 or IPv6), without any... more
In this paper we introduce a mechanism for hosts to use applications of any IP
version capability (IPv4-only, IPv6 only, or dual IPv4/IPv6) regardless of the IP version of
their network communication (IPv4 or IPv6), without any modification to those programs.
DAC effectively shields the application layer IPv4/IPv6 operation from the underlying
IPv4/IPv6 communication between the hosts. The authors consider the provision of this
kind of functionality an essential condition for the changeover towards IPv6 to succeed.
The proposed mechanism is a generalisation  of an experimental protocol called
“Bump-in-the-API (BIA)”
This document specifies a new IPv6 deployment protocol called CHANC, which stands for Configuring Hosts to Auto-detect (IPv6, IPv6-in-IPv4, or IPv4) Network Connectivity. The main part is an application level tunneling protocol that... more
This document specifies a new IPv6 deployment protocol called CHANC, which stands for Configuring Hosts to Auto-detect (IPv6, IPv6-in-IPv4, or IPv4) Network Connectivity. The main part is an application level tunneling protocol that allows Internet Service Providers (ISPs) to rapidly start deploying IPv6 service to their subscribers whom connected to the Internet via IPv4-only access networks. It carries IPv6 packets over HTTP protocol to be transmitted across IPv4-only network infrastructure. The key aspects of this protocol are: offers IPv6 connectivity via IPv4-only access networks, stateless operation, economical solution, assures most firewall traversal, and requires simple installation and automatic configuration at customers‟ hosts. All data packets and routing information of the IPv6 protocol will be carried over the IPv4 network infrastructure. A simple application and a pseudo network driver must be installed at the end-user‟s hosts to make them able to work with this protocol. Such hosts will be able to auto-detect the ISP available connectivity in the following precedence: native IPv6, IPv6-in-IPv4, or no IPv6 connectivity. Because the protocol does not require changing or upgrading customer edges, a minimal cost in the deployment to IPv6 service should be expected. The simulation analysis showed that the performance of CHANC is pretty near to those of native IPv6, 6rd, and IPv4 protocols. Also, the performance of CHANC is much better than that of D6across4 protocol.
This paper introduces a new IPv6 deployment protocol called E4Deliver6, which stands for Exploiting Local IPv4- only Access Networks to Deliver IPv6 Service to End-users. The protocol intends to help the Internet Service Providers... more
This paper introduces a new IPv6 deployment
protocol called E4Deliver6, which stands for Exploiting Local IPv4-
only Access Networks to Deliver IPv6 Service to End-users. The
protocol intends to help the Internet Service Providers (ISPs) to
rapidly start providing IPv6 service to the end-users. E4Deliver6
tunnels the IPv6 traffic into IPv4 traffic to transit the IPv4-only
access network infrastructure. The new protocol offers IPv6 service
alongside IPv4 service to the end-users, economical solution, and
requires simple and automatic configurations at both end-users’ hosts
and ISP sides at the time of setup. E4Deliver6 connected hosts will
be able to communicate with other IPv6-only servers outside their
local IPv4-only access network. The performance analysis of
E4Deliver6 showed that the performance parameters (e.g. Latency
and Throughput) are acceptable in comparison to other stateless
protocols (e.g. 6rd) and it is much better than other stateful protocols
(e.g. BDMS) performance parameters.
This paper introduces a new protocol called D6across4, which stands for Deploying IPv6 Service across local IPv4 access networks. The protocol aims to encourage Internet Service Providers (ISPs) to start deploying IPv6 service to their... more
This paper introduces a new protocol called D6across4, which stands for Deploying IPv6 Service across
local IPv4 access networks. The protocol aims to encourage Internet Service Providers (ISPs) to start deploying IPv6
service to their customers (end-users). It utilizes the automatic IPv6-in-IPv4 tunnels to transport IPv6 traffic (data and
control information) over local IPv4 access networks. The key aspects of this protocol include: providing IPv6 service
to end-users equivalent to native one, stateful operation, and requiring simple configurations on both end-user’s host
and ISP sides at the time of setup. D6across4 connected hosts can communicate with other IPv6 hosts outside their
local IPv4 access network. The simulation results showed that D6across4 performance parameters (e.g. latency and
throughput) are acceptable in comparison to both IPv4 and IPv6 performance parameters.
This document describes a bi-directional IPv6/IPv4 Socket Layer Translator (SLT) for border gateway routers. The new technique is called AIN-SLT which stands for Assuring Interconnection between Heterogeneous (IPv4/IPv6) Networks Using... more
This document describes a bi-directional IPv6/IPv4 Socket Layer Translator (SLT)
for border gateway routers. The new technique is called AIN-SLT which stands for
Assuring Interconnection between Heterogeneous (IPv4/IPv6) Networks Using SLT. This
mechanism assures a smooth heterogeneous communication between IPv6 and IPv4 nodes
without using protocol translation. It applies IPv6/IPv4 socket Application Programming
Interface (API) translation methodology between two heterogeneous networks by
terminating IPv6/IPv4 connection points at the application layer. The AIN-SLT mechanism
has many advantages over current translation/tunneling approaches, and so it does not
require any configuration at end-users’ hosts, it has the ability to translate non-NAT
friendly traffic (i.e. FTP and SIP traffic), and it achieves a reliable communication by not
breaking end-to-end protocol characteristics and security at physical layer (i.e. IPsec).
This document specifies a mechanism for hosts with any network connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6 connectivity) to run applications of any capability (IPv4 only, IPv6 only, or dual IPv4/IPv6) without any modification... more
This document specifies a mechanism for hosts with any network
connectivity (IPv4 only, IPv6 only, or dual IPv4/IPv6
connectivity) to run applications of any capability
(IPv4 only, IPv6 only, or dual IPv4/IPv6) without any
modification to those applications. It is a generalisation
of a previous experimental protocol called "Bump-in-the-API"
(BIA) [RFC3338]. New mechanism of BIA allows a changeover between
the application layer and the IP communication layers from IPv4
to IPv6 and vice versa or IPv6 to IPv4 and vice versa, without
requiring those applications to be converted in addressing
capabilities, effectively shielding the application layer from
IPv4 or IPv6 connectivity. This is considered by the authors to
be one of the essential conditions for the transition to IPv6
in the Internet to be successful.