TCP/IP

Transmission Control Protocol / Internet Protocol Based on Notes by D. Hollinger

Netprog 2002 TCP/IP

Topics

IPv6 TCP Java TCP Programming

Netprog 2002 TCP/IP

IPv6 availability

Generally available with (new) versions

of most operating systems.

An option with Windows 2000/NT Most routers can support IPV6 Supported in J2SDK/JRE 1.4
Netprog 2002 TCP/IP

BSD, Linux 2.2 Solaris 8

IPv6 Design Issues

Overcome IPv4 scaling problem Flexible transition mechanism. New routing capabilities. Quality of service. Security. Ability to add features in the future.
Netprog 2002 TCP/IP

lack of address space.

IPv6 Headers

Simpler header - faster processing by

routers.

Support for multiple headers

Netprog 2002 TCP/IP

No optional fields - fixed size (40 bytes) No fragmentation fields. No checksum more flexible than simple protocol field.

4 for IPv4

IPv4 Header
1 byte VERS 1 byte 1 byte 1 byte HL Service Fragment Length Datagram ID FLAG Fragment Offset TTL Protocol Header Checksum Source Address Destination Address Options (if any) Data

Netprog 2002 TCP/IP

6 for IPv6

IPv6 Header
1 byte 1 byte 1 byte Flow Label Next Header 1 byte Hop Limit

VERS PRIO Payload Length

Source Address (128 bits - 16 bytes)

Dest. Address (128 bits - 16 bytes)

Netprog 2002 TCP/IP

IPv6 Header Fields

VERS: 6 (IP version number) Priority: will be used in congestion control Flow Label: experimental - sender can label a

sequence of packets as being in the same flow. Payload Length: number of bytes in everything following the 40 byte header (up to 64Kb), or 0 for a Jumbogram (up to 4Gb).
Netprog 2002 TCP/IP

IPv6 Header Fields

Next Header is similar to the IPv4

protocol field - indicates what type of header follows the IPv6 header.

Hop Limit is similar to the IPv4 TTL field

Netprog 2002 TCP/IP

(but now it really means hops, not time).

Extension Headers

Routing Header - source routing Fragmentation Header - supports

fragmentation of IPv6 datagrams. Authentication Header Encapsulating Security Payload Header

Netprog 2002 TCP/IP

IPv6 Addresses

128 bits - written as eight 16-bit hex

numbers.
5f1b:df00:ce3e:e200:0020:0800:2078:e3e3

High order bits determine the type of

address.
Netprog 2002 TCP/IP

IPv6 Aggregate Global Unicast Address

3 13 32 NLA ID 16 SLA ID 64 Interface ID 010 TLA ID

TLA: top-level aggregation (provider) NLA: next-level (subscriber) SLA: site-level (subnet) Interface ID is (typically) based on hardware MAC address Netprog 2002 TCP/IP

IPv4-Mapped IPv6 Address

addresses allow a host that IPv4-MappedIPv4 and IPv6 to communicate support both with a host that supports only IPv4.

IPv6 address TheIPv4 address. is based completely on the

Netprog 2002 TCP/IP

IPv4-Mapped IPv6 Address

80 bits of 0s followed by 16 bits of ones,

followed by a 32 bit IPv4 Address:
0000 . . . 0000 80 bits FFFF 16 bits IPv4 Address 32 bits

Netprog 2002 TCP/IP

Works with DNS

An IPv6 application asks DNS for the

address of a host, but the host only has an IPv4 address. DNS creates the IPv4-Mapped IPv6 address automatically. Kernel understands this is a special address and really uses IPv4 communication.
Netprog 2002 TCP/IP

IPv4-Compatible IPv6 Address

An IPv4 compatible address allows a

host supporting IPv6 to talk IPv6 even if the local router(s) dont talk IPv6. IPv4 compatible addresses tell endpoint software to create a tunnel by encapsulating the IPv6 packet in an IPv4 packet.
Netprog 2002 TCP/IP

IPv4-Compatible IPv6 Address

80 bits of 0s followed by 16 bits of 0s, followed by a 32 bit IPv4 Address:
0000 . . . 0000 80 bits 0000 16 bits IPv4 Address 32 bits

Netprog 2002 TCP/IP

Tunneling (done automatically by kernel when IPv4-Compatible IPv6 addresses used) IPv6 Host
IPv4 Routers IPv4 Datagram IPv6 Datagram

IPv6 Host

Netprog 2002 TCP/IP

IPv6 in Java 1.4

Inet6Address class
:: corresponds to 0.0.0.0 (unspecified) in IPv4 ::1 corresponds to 127.0.0.1 (loopback) in IPv4 ::ffff:w.x.y.z IPv4-mapped address ::w.x.y.z to tunnel IPv6 packets over IPv4 routing

For details, see:

http://java.sun.com/j2se/1.4/docs/guide/net/ipv6_guide/

Netprog 2002 TCP/IP

TCP Transmission Control Protocol

TCP is an alternative transport layer

protocol over IP. TCP provides: Connection-oriented Reliable Full-duplex Byte-Stream

Netprog 2002 TCP/IP

Connection-Oriented

Connection oriented means that

a virtual connection is established before any user data is transferred. If the connection cannot be established - the user program is notified. If the connection is ever interrupted - the user program(s) is notified.
Netprog 2002 TCP/IP

Reliable

Reliable means that every

transmission of data is acknowledged by the receiver. If the sender does not receive acknowledgement within a specified amount of time, the sender retransmits the data.
Netprog 2002 TCP/IP

Byte Stream

Stream means that the

connection is treated as a stream of bytes.

The user application does not

Netprog 2002 TCP/IP

need to package data in individual datagrams (as with UDP).

Buffering

TCP is responsible for buffering data

and determining when it is time to send a datagram.

It is possible for an application to tell

Netprog 2002 TCP/IP

TCP to send the data it has buffered without waiting for a buffer to fill up.

Full Duplex

TCP provides transfer in both directions.

the application program these appear To 2 unrelated data streams, although as TCP can piggyback control and data communication by providing control information (such as an ACK) along with user data.
Netprog 2002 TCP/IP

TCP Ports

Interprocess communication via

TCP is achieved with the use of ports (just like UDP).

UDP ports have no relation to TCP

ports (different name spaces).
Netprog 2002 TCP/IP

TCP Segments

The chunk of data that TCP asks IP

to deliver is called a TCP segment.

Each segment contains:

data bytes

data bytes from the byte stream control information that identifies the
Netprog 2002 TCP/IP

TCP Segment Format

1 byte 1 byte 1 byte 1 byte Source Port Destination Port Sequence Number Acknowledgment Number offset Reser. Control Window Checksum Urgent Pointer Options (if any) Data
Netprog 2002 TCP/IP

TCP Lingo

When a client requests a connection it

sends a SYN segment (a special TCP segment) to the server port. SYN stands for synchronize. The SYN message includes the clients ISN. ISN is Initial Sequence Number.

Netprog 2002 TCP/IP

More...

Every TCP segment includes a

Sequence Number that refers to the first byte of data included in the segment. Every TCP segment includes an Acknowledgement Number that indicates the byte number of the next data that is expected to be received.

All bytes up through this number have

already been received.
Netprog 2002 TCP/IP

And more...

There are a bunch of control flags:

URG: urgent data included. ACK: this segment is (among other things)
an acknowledgement. RST: error connection must be reset. SYN: synchronize Sequence Numbers (setup) FIN: polite connection termination.
Netprog 2002 TCP/IP

And more...

MSS: Maximum segment size (A TCP

option) Window: Every ACK includes a Window field that tells the sender how many bytes it can send before the receiver will have to toss it away (due to fixed buffer size).

Netprog 2002 TCP/IP

TCP Connection Creation

Programming details later - for now we are

concerned with the actual communication. A server accepts a connection.

A client requests a connection.

Must know where the server is!
Netprog 2002 TCP/IP

Must be looking for new connections!

Client Starts

A client starts by sending a SYN

segment with the following information:

Clients ISN (generated pseudo-randomly) Maximum Receive Window for client. Optionally (but usually) MSS (largest
datagram accepted). No payload! (Only TCP headers)

Netprog 2002 TCP/IP

Server Response

When a waiting server sees a new

connection request, the server sends back a SYN segment with:

Servers ISN (generated pseudo-randomly) Request Number is Client ISN+1 Maximum Receive Window for server. Optionally (but usually) MSS No payload! (Only TCP headers)
Netprog 2002 TCP/IP

Finally

When the Servers SYN is received, the

client sends back an ACK with:
ISN+1

Acknowledgment Number is Servers

Netprog 2002 TCP/IP

Client
SYN SYN ISN=X ISN=X 1

Server

2 SYN SYN ISN=Y ACK=X+1 ISN=Y ACK=X+1

ACK=Y+1 3 ACK=Y+1

Netprog 2002 TCP/IP

TCP 3-way handshake

1

Client: I want to talk, and Im starting with byte number X. Server: OK, Im here and Ill talk. My first byte will be called number Y, and I know your first byte will be number X+1. Client: Got it - you start at byte number Y+1. Bill: Monica, Im afraid Ill syn and byte your ack Netprog 2002 TCP/IP

3 ?

Why 3-Way?

Why is the third message necessary? HINTS:

TCP is a reliable service. IP delivers each TCP segment. IP is not reliable.
Netprog 2002 TCP/IP

TCP Data and ACK

Once the connection is established,

data can be sent. Each data segment includes a sequence number identifying the first byte in the segment. Each segment (data or empty) includes a request number indicating what data has been received.
Netprog 2002 TCP/IP

Buffering

Keep in mind that TCP is part of the

Operating System. The O.S. takes care of all these details asynchronously. The TCP layer doesnt know when the application will ask for any received data. TCP buffers incoming data so its ready when we ask for it.
Netprog 2002 TCP/IP

TCP Buffers

Both the client and server allocate

The TCP layer does this.

buffers to hold incoming and outgoing data

Both the client and server announce

Netprog 2002 TCP/IP

with every ACK how much buffer space remains (the Window field in a TCP segment).

Send Buffers

The application gives the TCP layer

some data to send. The data is put in a send buffer, where it stays until the data is ACKd. The TCP layer wont accept data from the application unless (or until) there is buffer space.
Netprog 2002 TCP/IP

ACKs

A receiver doesnt have to ACK every

segment (it can ACK many segments with a single ACK segment). Each ACK can also contain outgoing data (piggybacking). If a sender doesnt get an ACK after some time limit, it resends the data.
Netprog 2002 TCP/IP

TCP Segment Order

Most TCP implementations will accept

out-of-order segments (if there is room in the buffer). Once the missing segments arrive, a single ACK can be sent for the whole thing. Remember: IP delivers TCP segments, and IP is not reliable - IP datagrams can be lost or arrive out of order.
Netprog 2002 TCP/IP

Termination

The TCP layer can send a RST

segment that terminates a connection if something is wrong. Usually the application tells TCP to terminate the connection politely with a FIN segment.

Netprog 2002 TCP/IP

FIN

Either end of the connection can initiate

termination. A FIN is sent, which means the application is done sending data. The FIN is ACKd. The other end must now send a FIN. That FIN must be ACKd.
Netprog 2002 TCP/IP

App1
FIN FIN SN=X SN=X ACK=X+1 ACK=X+1 1

App2

...
FIN FIN SN=Y SN=Y 3 ACK=Y+1 4 ACK=Y+1
Netprog 2002 TCP/IP

TCP Termination
1 2

App1: I have no more data for you. App2: OK, I understand you are done sending. dramatic pause App2: OK - Now Im also done sending data. App1: Roger, Over and Out, Goodbye, Hastalavista Baby, Adios, Its been real ... camera fades to black ...
Netprog 2002 TCP/IP

3 4

TCP TIME_WAIT

Once a TCP connection has been terminated

(the last ACK sent) there is some unfinished business:

What if the ACK is lost? The last FIN will be resent

and it must be ACKd. What if there are lost or duplicated segments that finally reach the destination after a long delay?

TCP hangs out for a while to handle these

situations.
Netprog 2002 TCP/IP

TCP Sockets Programming

Creating a passive mode (server)

socket. Establishing an application-level connection. Sending/receiving data. Terminating a connection.

Netprog 2002 TCP/IP

Establishing a passive mode TCP socket

Passive mode:

Address already determined. Tell the kernel to accept incoming connection requests directed at the socket address.
3-way handshake

Tell the kernel to queue incoming connections for us.

Netprog 2002 TCP/IP

Accepting an incoming connection.

Once we start listening on a socket, the

O.S. will queue incoming connections

Handles the 3-way handshake Queues up multiple connections.

When our application is ready to handle a

new connection, we need to ask the O.S. for the next connection.
Netprog 2002 TCP/IP

Terminating a TCP connection

Either end of the connection can call

the close() system call. If the other end has closed the connection, and there is no buffered data, reading from a TCP socket returns 0 to indicate EOF.

Netprog 2002 TCP/IP

Client Code

TCP clients can connect to a server,

which:

takes care of establishing an endpoint

address for the client socket.

dont need to call bind first, the O.S. will take

care of assigning the local endpoint address (TCP port number, IP address).

Attempts to establish a connection to the

specified server.

3-way handshake
Netprog 2002 TCP/IP

Reading from a TCP socket

By default read() will block until data is

available. Reading from a TCP socket may return less than max bytes (whatever is available). You must be prepared to read data 1 byte at a time!

Netprog 2002 TCP/IP

Writing to a TCP socket

write might not be able to write all bytes

(on a nonblocking socket).

Netprog 2002 TCP/IP

Metaphor for Good Relationships

Copyright Dr. Lauras Network Programming Corp.

d() To succeed in relationships: bin you need to establish your own identity. accept() you need to be open & accepting.

you need to establish contacts. connect() you need to take things as they come, not you need to handle problems as they arise. rs
check for erro
Netprog 2002 TCP/IP

as you expect them. read might return 1 byte

Java Sockets Programming

The package java.net provides support

for sockets programming Typically you import everything defined in this package with:

import java.net.*;
Netprog 2002 TCP/IP

Classes
InetAddress Socket ServerSocket DatagramSocket DatagramPacket

UDP UDP

Netprog 2002 TCP/IP

Socket class

Corresponds to active TCP sockets only!

client sockets socket returned by accept();

Passive sockets are supported by a

different class: ServerSocket
Netprog 2002 TCP/IP

Socket Constructors

Constructor creates a TCP connection

to a named TCP server.

There are a number of constructors:

Socket(InetAddress server, int port); Socket(InetAddress server, int port, InetAddress local, int localport); Socket(String hostname, int port);
Netprog 2002 TCP/IP

Socket Methods
void close(); InetAddress getInetAddress(); getpeername InetAddress getLocalAddress(); getsockname InputStream getInputStream(); OutputStream getOutputStream();

Lots more (setting/gettting socket options,

partial close, etc.)
Netprog 2002 TCP/IP

Socket I/O

Socket I/O is based on the Java I/O

support (in the package java.io).

InputStream and OutputStream are

abstract classes

common operations defined for all kinds of

InputStreams, OutputStreams
Netprog 2002 TCP/IP

ServerSocket Class (TCP Passive Socket)

Constructors:

ServerSocket(int port); ServerSocket(int port, int backlog); ServerSocket(int port, int backlog, InetAddress bindAddr);
Netprog 2002 TCP/IP

ServerSocket Methods
Socket accept(); void close(); InetAddress getInetAddress(); int getLocalPort();
throw IOException, SecurityException
Netprog 2002 TCP/IP

Sample Echo Server

TCPEchoServer.java, EchoClient.java, GenericClient.java Simple TCP Echo server. Based on code from: TCP/IP Sockets in Java, Java Online Tutorial
Netprog 2002 TCP/IP