Dynamic TCP Connection Elapsing
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
electronics seminars
Active In SP
**

Posts: 694
Joined: Nov 2009
#1
20-12-2009, 11:45 AM


Abstract:
When designing systems for load-balancing, process migration, or fail-over, there is eventually the point where one would like to be able to "move" a socket from one machine to another one, without losing the connection on that socket, similar to file descriptor passing on a single host. Such a move operation usually involves at least three elements: 1. Moving any application space state related to the connection to the new owner. E.g. in the case of a Web server serving large static files, the application state could simply be the file name and the current position in the file Making sure that packets belonging to the connection are sent to the new owner of the socket. Normally this also means that the previous owner should no longer receive them.3. Last but not least, creating compatible network state in the kernel of the new connection such that it can resume the communication where the previous owner left off. We shall call the host from which ownership of the connection endpoint is taken the origin, the host to which it is transferred the destination, and the host on the other end of the connection (which does not change) the peer. Details of moving the application state are beyond the scope of this paper, and we will only sketch relatively simple examples. Similarly, we will mention a few ways for how the redirection in the network can be accomplished, but without going into too much detail. The complexity of the kernel state of a network connection, and the difficulty of moving this state from one host to another, varies greatly with the transport protocol being used. Among the two major transport protocols of the Internet, UDP [1] and TCP [2], the latter clearly presents more of a challenge in this regard. Nevertheless, some issues also apply to UDP. tcpcp (TCP Connection Passing) is a proof of concept implementation of a mechanism that allows applications to transport the kernel state of a TCP endpoint from one host to another, while the connection is established, and without requiring the peer to cooperate in any way. tcpcp is not a complete process migration or load-balancing solution, but rather a building block that can be integrated into such systems. tcpcp consists of a kernel patch (at the time of writing for version 2.6.4 of the Linux kernel) that implements the operations for dumping and restoring the TCP connection endpoint, a library with wrapper functions (see Section 3), and a few applications for debugging and demonstration. The remainder of this paper is organized as follows: this section continues with a description of the context in which connection passing exists. Section 2 explains the connection passing operation in detail. Section 3 introduces the APIs tcpcp provides. The information that defines a TCP connection and its state is described in Section 4. Sections 5 and 6 discuss congestion control and the limitations TCP imposes on check pointing. Security implications of the availability and use of tcpcp are examined in Section 7. We conclude with an outlook on future direction the work on tcpcp will take in Section 8, and the conclusions in Section 9. The excellent "TCP/IP Illustrated" is recommended for readers who wish to refresh their memory of TCP/IP concepts and terminology. The key feature of tcpcp is that the peer can be left completely unaware that the connection is passed from one host to another. In detail, this means: " The peer's networking stack can be used "as is," without modification and without requiring non-standard functionality
" The connection is not interrupted
" The peer does not have to stop sending
" No contradictory information is sent to the peer
" These properties apply to all protocol layers visible to the peer
Use Search at http://topicideas.net/search.php wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
Reply
seminar class
Active In SP
**

Posts: 5,361
Joined: Feb 2011
#2
16-03-2011, 09:53 AM


.doc   Dynamic TCP Connection Elapsing.doc (Size: 37 KB / Downloads: 55)
Dynamic TCP Connection Elapsing
When designing systems for process migration,load-balancing, or fail-over,
there comes point where one would like to move a socket from one
machine to another machine, without losing the connection on that socket,
similar to file descriptor passing on a single host.
Such a move operation usually involves three elements:
1)Making sure that packets belonging to the connection are sent to the
new owner of the socket.Automatically, this also means that the previous
owner should no longer receive the data packets.
2)Moving any application space state related to the connection to the
new owner.For example,taking the case of a Web server storing large
static files, the application state can be the file name and the
current position in the file.
3)The last and the important one: creating compatible network state
in the kernel of the new connection such that it can resume the
communication where the previous owner left off.
The origin server transfers the application state to the destination
server where the application state resides in the user space. Also
the kernel state is transferred from the origin server to the
destination server and the necessary packet routing being provided
by the peer(client).
Dynamic TCP Connection Elapsing
Abstract:

When designing systems for load-balancing, process migration, or fail-over, there is eventually the point where one would like to be able to "move" a socket from one machine to another one, without losing the connection on that socket, similar to file descriptor passing on a single host. Such a move operation usually involves at least three elements: 1. Moving any application space state related to the connection to the new owner. E.g. in the case of a Web server serving large static files, the application state could simply be the file name and the current position in the file Making sure that packets belonging to the connection are sent to the new owner of the socket. Normally this also means that the previous owner should no longer receive them.3. Last but not least, creating compatible network state in the kernel of the new connection such that it can resume the communication where the previous owner left off. We shall call the host from which ownership of the connection endpoint is taken the origin, the host to which it is transferred the destination, and the host on the other end of the connection (which does not change) the peer. Details of moving the application state are beyond the scope of this paper, and we will only sketch relatively simple examples. Similarly, we will mention a few ways for how the redirection in the network can be accomplished, but without going into too much detail. The complexity of the kernel state of a network connection, and the difficulty of moving this state from one host to another, varies greatly with the transport protocol being used. Among the two major transport protocols of the Internet, UDP [1] and TCP [2], the latter clearly presents more of a challenge in this regard. Nevertheless, some issues also apply to UDP. tcpcp (TCP Connection Passing) is a proof of concept implementation of a mechanism that allows applications to transport the kernel state of a TCP endpoint from one host to another, while the connection is established, and without requiring the peer to cooperate in any way. tcpcp is not a complete process migration or load-balancing solution, but rather a building block that can be integrated into such systems. tcpcp consists of a kernel patch (at the time of writing for version 2.6.4 of the Linux kernel) that implements the operations for dumping and restoring the TCP connection endpoint, a library with wrapper functions (see Section 3), and a few applications for debugging and demonstration. The remainder of this paper is organized as follows: this section continues with a description of the context in which connection passing exists. Section 2 explains the connection passing operation in detail. Section 3 introduces the APIs tcpcp provides. The information that defines a TCP connection and its state is described in Section 4. Sections 5 and 6 discuss congestion control and the limitations TCP imposes on check pointing. Security implications of the availability and use of tcpcp are examined in Section 7. We conclude with an outlook on future direction the work on tcpcp will take in Section 8, and the conclusions in Section 9. The excellent "TCP/IP Illustrated" is recommended for readers who wish to refresh their memory of TCP/IP concepts and terminology. The key feature of tcpcp is that the peer can be left completely unaware that the connection is passed from one host to another. In detail, this means: " The peer's networking stack can be used "as is," without modification and without requiring non-standard functionality
" The connection is not interrupted
Dynamic TCP Connection Elapsing
• All
• networks
By MalaChandrasekaran ~ Posted Sun, 19/12/2010 - 14:23
INTRODUCTION
When designing systems for load-balancing, process migration, or fail-over, there is eventually the point where o
ne would like to be able to "move" a socket from one machine to another one, without losing the connection on that socket, similar to file descriptor passing on a single host. Such a move operation usually involves at least three elements:
1. Moving any application space state related to the connection to the new owner. E.g. in the case of a Web server serving large static files, the application state could simply be the file name and the current position in the file.
2. Making sure that packets belonging to the connection are sent to the new owner of the socket. Normally this also means that the previous owner should no longer receive them.
3. Last but not least, creating compatible network state in the kernel of the new connection such that it can resume the communication where the previous owner left off.
We shall call the host from which ownership of the connection endpoint is taken the origin, the host to which it is transferred the destination, and the host on the other end of the connection (which does not change) the peer. Details of moving the application state are beyond the scope of this paper, and we will only sketch relatively simple examples. Similarly, we will mention a few ways for how the redirection in the network can be accomplished, but without going into too much detail. The complexity of the kernel state of a network connection, and the difficulty of moving this state from one host to another, varies greatly with the transport protocol being used.
Among the two major transport protocols of the Internet, UDP [1] and TCP [2], the latter clearly presents more of a challenge in this regard. Nevertheless, some issues also apply to UDP. tcpcp (TCP Connection Passing) is a proof of concept implementation of a mechanism that allows applications to transport the kernel state of a TCP endpoint from one host to another, while the connection is established, and without requiring the peer to cooperate in any way. tcpcp is not a complete process migration or load-balancing solution, but rather a building block that can be integrated into such systems. tcpcp consists of a kernel patch (at the time of writing for version 2.6.4 of the Linux kernel) that implements the operations for dumping and restoring the TCP connection endpoint, a library with wrapper functions (see Section 3), and a few applications for debugging and demonstration.
The remainder of this paper is organized as follows: this section continues with a description of the context in which connection passing exists. Section 2 explains the connection passing operation in detail. Section 3 introduces the APIs tcpcp provides. The information that defines a TCP connection and its state is described in Section 4. Sections 5 and 6 discuss congestion control and the limitations TCP imposes on check pointing. Security implications of the availability and use of tcpcp are examined in Section 7. We conclude with an outlook on future direction the work on tcpcp will take in Section 8, and the conclusions in Section 9. The excellent "TCP/IP Illustrated" [3] is recommended for readers who wish to refresh their memory of TCP/IP concepts and terminology.
The key feature of tcpcp is that the peer can be left completely unaware that the connection is passed from one host to another. In detail, this means:
" The peer's networking stack can be used "as is," without modification and without requiring non-standard functionality
" The connection is not interrupted
" The peer does not have to stop sending
" No contradictory information is sent to the peer
" These properties apply to all protocol layers visible to the peer
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Message
Type your reply to this message here.


Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  Towards Reliable Data Delivery for Highly Dynamic Mobile Ad Hoc Networks seminar ideas 11 3,925 02-04-2014, 12:50 PM
Last Post: Guest
  Protocols and the TCP/IP Suite PPT seminar projects maker 0 369 28-09-2013, 02:42 PM
Last Post: seminar projects maker
  AN INTRODUCTION TO TCP/IP REPORT seminar projects maker 0 437 26-09-2013, 04:31 PM
Last Post: seminar projects maker
  TCP/IP PROTOCOLS seminar projects maker 0 470 25-09-2013, 04:26 PM
Last Post: seminar projects maker
  Report on Exploiting Dynamic Resource Allocation for Efficient Parallel Data study tips 0 368 21-08-2013, 04:36 PM
Last Post: study tips
  Protocols and the TCP/IP Protocol Suite PPT study tips 0 341 03-08-2013, 03:17 PM
Last Post: study tips
  Dynamic synchronous Transfer Mode (DTM) ppt study tips 1 2,149 05-07-2013, 02:44 PM
Last Post: study tips
  Report on Dynamic network load balancing study tips 0 302 05-07-2013, 12:23 PM
Last Post: study tips
  Efficient Key Agreement for Large and Dynamic Multicast Groups pdf study tips 0 708 20-06-2013, 12:21 PM
Last Post: study tips
  Dynamic partial reconfiguration in FPGAs pdf study tips 0 283 19-06-2013, 12:41 PM
Last Post: study tips