Network Protocols: Handbook
Network Protocols: Handbook
Network
Protocols
Handbook
IP t y O
P /
AT M
L AN u r i I S
TC e c
T F
n et AN S I E
M
er W IP I B
th ay VO E E
E l IE o
Re / C7 s c
e S 7
AN Ci f t
m S o
Fr
a VL SI r o s
AN ic
L A N AN M
W S l
e l
AN N -T p l ve
M V P ITU A
p
N
o
Table of Contents
Protocols Guide••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11
TCP/IP Protocols••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••11
Application Layer Protocols••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••13
Routing Protocols••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••62
ICMP & ICMPv6: Internet Message Control Protocol and ICMP version 6••••••••••••••••••••••••••••••68
Multicasting Protocols••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••80
MPLS Protocols•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••92
Tunneling Protocols•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••107
H.225.0: Vall signalling protocols and media stream packetization for packet based multimedia
communication systems•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••125
H.235: Security and encryption for H-series (H.323 and other H.245-based) multimediateminals
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••127
Media/CODEC••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••142
Other Protocols•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••151
xDSL: Digital Subscriber Line Technologies (DSL, IDSL, ADSL, HDSL, SDSL,VDSL,G.Lite)•••185
PPP Protocols•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••186
BAP: PPP Bandwidth Allocation Protocol(BAP) and BACP: PPP Banwidth Allocation Control
Protocol (BACP)••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••187
Gigabit (1000 Mbps) Ethernet: IEEE 802.3z (1000Base-X) and 802.3ab (1000 Base-T)•••209
10 Gigabit Ethernet: The Ethernet Protocol IEEE 802.3ae for LAN, WAN and MAN•••••••••••211
IEEE 802.1X: EAP over LAN (EAPOL) for LAN/WLAN Authentication and Key Management•••224
Other Protocols•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••227
iSNS and iSNSP: Internet Storage Name Service and iSNS Protocol••••••••••••••••••••••••••••••••••••247
ISO-TP: OSI Transport Layer Protocols TP0, TP1, TP2, TP3, TP4••••••••••••••••••••••••••••••••••••271
Network Layer••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••273
Cisco Protocols•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••279
CDP: Cisco Discovery Protocol•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••280
ISL & DISL: Cisco Inter-Switch Link Protocol and Dynamic ISL Protocol••••••••••••••••••••••••••••286
MTP2 and MTP3: Message Transfer Part level 2 and level 3•••••••••••••••••••••••••••••••••••••••••323
Other Protocols••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••329
Microsoft CIFS: Common Internet File System•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••330
Appendix•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••336
Appendix A: TCP and UDP Port Numbers••••••••••••••••••••••••••••••••••••••••••••••••••••••336
Table of Figures
Figure 2-10: The relations between MGCP/NCS and other VOIP standards••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••131
Layer 1: Physical Layer Each layer may add a Header and a Trailer to its Data, which
consists of the upper layer’s Header, Trailer and Data as it
• Defines physical means of sending data over network proceeds through the layers. The Headers contain informa-
devices tion that specifically addresses layer-to-layer communication.
• Interfaces between network medium and devices Headers, trailers and data are relative concepts, depending
• Defines optical, electrical and mechanical characteris- on the layer that analyzes the information unit. For example,
tics the Transport Header (TH) contains information that only the
Transport layer sees. All other layers below the Transport
layer pass the Transport Header as part of their Data. At the
Information being transferred from a software application in
network layer, an information unit consists of a Layer 3 header
one computer to an application in another proceeds through
(NH) and data.
the OSI layers. For example, if a software application in com-
puter A has information to pass to a software application in At the data link layer, however, all the information passed
computer B, the application program in computer A need to down by the network layer (the Layer 3 header and the data)
pass the information to the application layer (Layer 7) of com- is treated as data. In other words, the data portion of an infor-
puter A, which then passes the information to the presenta- mation unit at a given OSI layer potentially can contain head-
tion layer (Layer 6), which relays the data to the session layer ers, trailers, and data from all the higher layers. This is known
(Layer 5), and so on all the way down to the physical layer as encapsulation.
(Layer 1). At the physical layer, the data is placed on the phys-
ical network medium and is sent across the medium to com- Application AH Data AT Application
puter B. The physical layer of computer B receives the data
Presentation Data Presentation
from the physical medium, and then its physical layer passes PH PT
the information up to the data link layer (Layer 2), which relays Session SH Data ST Session
it to the network layer (Layer 3), and so on, until it reaches Transport TH Data TT Transport
the application layer (Layer 7) of computer B. Finally, the ap-
Networt NH Data NT Networt
plication layer of computer B passes the information to the
Data Link Data Link
recipient application program to complete the communication DH Data DT
process. The following diagram illustrated this process. Physical Data Physical
Application Application
Presentation Presentation
Session Session
Transport Transport
Networt Networt
Physical Physical
TCP/IP architecture does not exactly follow the OSI model. Unfortunately, there is
no universal agreement regarding how to describe TCP/IP with a layered model.
It is generally agreed that TCP/IP has fewer levels (from three to five layers) than
the seven layers of the OSI model. We adopt a four layers model for the TCP/IP
architecture.
TCP/IP architecture omits some features found under the OSI model, combines
the features of some adjacent OSI layers and splits other layers apart. The 4-layer
structure of TCP/IP is built as information is passed down from applications to the
physical network layer. When data is sent, each layer treats all of the information it
receives from the upper layer as data, adds control information (header) to the front
of that data and then pass it to the lower layer. When data is received, the opposite
procedure takes place as each layer processes and removes its header before
passing the data to the upper layer.
The TCP/IP 4-layer model and the key functions of each layer is described below:
Application Layer
The Application Layer in TCP/IP groups the functions of OSI Application, Presenta-
tion Layer and Session Layer. Therefore any process above the transport layer is
called an Application in the TCP/IP architecture. In TCP/IP socket and port are used
to describe the path over which applications communicate. Most application level
protocols are associated with one or more port number.
Transport Layer
In TCP/IP architecture, there are two Transport Layer protocols. The Transmission
Control Protocol (TCP) guarantees information transmission. The User Datagram
Protocol (UDP) transports datagram swithout end-to-end reliability checking. Both
protocols are useful for different applications.
Network Layer
The Internet Protocol (IP) is the primary protocol in the TCP/IP Network Layer. All
upper and lower layer communications must travel through IP as they are passed
through the TCP/IP protocol stack. In addition, there are many supporting protocols
in the Network Layer, such as ICMP, to facilitate and manage the routing process.
In the TCP/IP architecture, the Data Link Layer and Physical Layer are normally
grouped together to become the Network Access layer. TCP/IP makes use of ex-
isting Data Link and Physical Layer standards rather than defining its own. Many
RFCs describe how IP utilizes and interfaces with the existing data link protocols
such as Ethernet, Token Ring, FDDI, HSSI, and ATM. The physical layer, which
defines the hardware communication properties, is not often directly interfaced with
the TCP/IP protocols in the network layer and above.
5 Network Communication Architecture and Protocols TCP/IP Four Layers Architecture Model
Data
Header Data
BOOTP uses two different well-known port numbers. UDP port Flags The flags.
number 67 is used for the server and UDP port number 68 is Ciaddr The client IP address.
used for the BOOTP client. The BOOTP client broadcasts a Yiaddr The “Your” (client) IP address.
single packet called a BOOTREQUEST packet that contains
Siaddr The IP address of the next server to use in boot-
the client’s physical network address and optionally, its IP ad-
strap.
dress if known. The client could send the broadcast using the
address 255.255.255.255, which is a special address called Giaddr The relay agent IP address used in booting via a re-
the limited broadcast address. The client waits for a response lay agent.
from the server. If a response is not received within a specified Chaddr The client hardware address.
time interval, the client retransmits the request. Sname Optional server host name, null terminated string
The server responds to the client’s request with a BOOTREPLY File Boot file name, null terminated string; generic name
packet. The request can (optionally) contain the ‘generic’ file- or null in DHCPDISCOVER, fully qualified directory-path name
name to be booted, for example, ‘unix’ or ‘ethertip’. When the in DHCPOFFER.
server sends the bootreply, it replaces this field with the fully Options Optional parameters field.
qualified path name of the appropriate boot file. In determining
this name, the server may consult its own database correlat- Related protocols
ing the client’s address and filename request, with a particular
IP, UDP, DHCP, RARP
boot file customized for that client. If the bootrequest filename
is a null string, then the server returns a filename field indicat-
Sponsor Source
ing the ‘default’ file to be loaded for that client.
BOOTP is defined by IETF (http://www.ietf.org) RFC951 and
In the case of clients which do not know their IP addresses, RFC 1542.
the server must also have a database relating hardware ad-
dress to IP address. This client IP address is then placed into Reference
a field in the bootreply. http://www.javvin.com/protocol/rfc951.pdf
BOOTSTRAP PROTOCOL (BOOTP)
BOOTP is an alternative to RARP, which operates at the Data
http://www.javvin.com/protocol/rfc1542.pdf
Link Layer for LAN only. BOOTP, a UDP/IP based configura-
Clarifications and Extensions for the Bootstrap Protocol
tion protocol, provides much more configuration information
http://www.javvin.com/protocol/rfc2132.pdf
and allows dynamic configuration for an entire IP network.
DHCP Options and BOOTP Vendor Extensions
BOOTP and its extensions became the basis for the Dynamic
http://www.javvin.com/protocol/rfc3396.pdf
Host Configuration Protocol (DHCP).
Encoding Long Options in the (DHCPv4)
Protocol Structure
8 16 24 32bit
Op Htype Hlen Hops
Xid
Secs Flags
Ciaddr
7 Protocols Guide TCP/IP - Network Layer Protocols
MPLS Protocals on the MPLS framework. Other protocols in the MPLS suite
Protocol Name and GMPLS will be discussed in separate documents.
Specifically, MPLS provide a rich set of traffic management Martini Frame Encapaulation
capabilities in the areas of traffic policing, congestion man-
agement, traffic shapping and priority queuing. MPLS Singnaling Protocols and Extensions
Related protocols
LDP, CR-LDP, RSVP-TE, IP, ATM, RSVP, OSPF, GMPLS
Sponsor Source
MPLS is defined by IETF (http://www.ietf.org) RFC3031 and
RFC 3032.
Reference
http://www.javvin.com/protocol/rfc3031.pdf
Multiprotocol Label Switching Architecture
http://www.javvin.com/protocol/rfc3032.pdf
MPLS Label Stack Encoding
http://www.javvin.com/protocol/rfc3443.pdf
Time To Live (TTL) Processing in Multi-Protocol Label Switch-
ing (MPLS) Networks
http://www.javvin.com/protocol/rfc3036.pdf
LDP Specification
http://www.javvin.com/protocol/rfc3209.pdf
RSVP-TE: Extensions to RSVP for LSP Tunnels
http://www.javvin.com/protocol/rfc3212.pdf
Constraint-Based LSP Setup using LDP
http://www.javvin.com/protocol/rfc3213.pdf
Applicability Statement for CR-LDP
http://www.faqs.org/ftp/pub/internet-drafts/draft-martini-
l2circuit-encap-mpls-08.txt
Encapsulation Methods for Transport of Layer 2 Frames Over
IP and MPLS Networks
9 Appendix TCP and UDP Port Numbers
Fully explains and illustrates all commonly used network communication protocols, including TCP/
IP, WAN, LAN technologies
Covers the latest and emerging technologies such as VOIP, SAN, MAN, VPN/Security,WLAN,
VLAN and more
Addresses vendor specific technologies: Cisco, IBM, Novell, Sun, HP, Microsoft, Apple,etc.
www.javvin.com