Panko Bdnt7e ch02

Network Standards
Chapter 2
Updated January 2009
Raymond Panko’s
Business Data Networks and Telecommunications, 7th edition
May only be used by adopters of the book
© 2009 Pearson Education, Inc. Publishing as Prentice Hall

2-1: Network Standards
• Network Standards
– Network standards govern the exchange of messages
between hardware or software processes on different host
computers, including message order, semantics, syntax,
reliability, and connection orientation
– Also known as protocols
– Computers are not intelligent, so standards must be very rigid
Message
2-2
2-2
1.
Message Standards
(Protocols)
Message syntax
Message semantics
Message order

2-1: Network Standards
• Network Standards Govern

– Message Syntax (organization)
• Like human grammar, but more rigid
• Header, data field, and trailer (Figure 2-2)
– Message order
• Turn taking, order of messages in a complex transaction, who
must initiate communication, etc.
– Message semantics (meaning)
• HTTP request message: “Please give me this file”
• HTTP response message: Here is the file. (Or, I could not
comply for the following reason)
2-4
2-2: General Message Organization
• General Message Syntax (Organization)

– General Message Organization (Figure 2-4)
– Primary parts of messages
• Data Field (content to be delivered)
• Header (everything before the data field)
• Trailer (everything after the data field)
– The header and trailer act like a delivery envelope for
the data field
Trailer Data Field Header

2-5
• General Message Syntax (Organization)

– Header and trailer are further divided into fields
Trailer Data Field Header
Other
Header Destination
Message with
Field Address
all three parts
Field is
Used by Switches and Routers
Like the Address on an Envelope
2-6
Data Field Header
Message without a trailer Other Destination

Header Address
Field Field
2-7
Header
Other Destination
Message with Header Address
only a header Field Field
e.g.
TCP supervisory messages are pure headers
(there is no data field content to deliver)
2-8
2.
Reliability
Error Detection and Correction

2-3: Reliable Transmission Control
Protocol (TCP) Session 2
• The Transmission Control Protocol (TCP) is an

important standard in Internet transmission
• TCP
– Receiver acknowledges each correctly-received
TCP message (called a TCP segment)
– If an acknowledgments is not received by the

sender, the sender retransmits the TCP segment
– This gives reliability: error detection AND error
correction
2-10
2-3: Reliable TCP Session 1
Client PC Webserver
TCP Process TCP Process
4. Data = HTTP Request
Carry 5. ACK (4)

HTTP
Req &
6. Data = HTTP Response
Resp
(4)
7. ACK (6) TCP Segment (Message) 4
Carries an HTTP Request
Request-Response
Cycle for Data Transfer Segment 5 Acknowledges It
There Is No Need to Resend
2-11
2-3: Reliable TCP Session
3
Client PC Webserver
8. Data = HTTP Request (Error)
Carry No receipt, so
HTTP so no ACK
Req &
8. Data = Retransmits HTTP Request because
Resp
No ACK was received
(4)
9. ACK (8)
Error Handling
2-12
Unreliable Protocols
• HTTP is an unreliable protocol

– If an HTTP message is lost, there is no retransmission
• Some protocols detect errors, dropping incorrect

messages
– There is no retransmission, so these protocols are
unreliable
– There must be both error detection and error correction
for a protocol to be reliable
Message
2-13
3.
Connection-Oriented and
Connectionless Protocols

2-4: Connection-Oriented and Connectionless
Protocols
Client PC
In TCP Webserver
Connection-Opening Messages
Messages During the Connection

Time
Connection-Closing Messages
Connection-oriented protocols have formal openings

and closings, like human telephone calls
2-15
2-4: Connection-Oriented and Connectionless
Protocols 4
Connection-Oriented Protocol Connectionless Protocol
A B A B
Open Connection Message
(No Sequence Number)
Message with Sequence Number A1
Connectionless protocols, like
HTTP simply send messages
Message with Sequence Number B1 without prior connection
openings and without
subsequent connection closings
Message with Sequence Number A2
Connection-oriented protocols
give each message a
unique sequence number
Close Connection
2-16
2-5: Advantages and Disadvantages of
Connection-Oriented Protocols
• Advantages
– Connection-oriented protocols give each message a sequence number
• Thanks to sequence numbers, the parties can tell when a message is
lost (There will be a gap in the sequence numbers)
• Error messages, such as ACKs, can refer to specific messages
according to the sequence numbers of these messages
– Long messages can be fragmented into many smaller messages that can
fit inside of packets
• The fragments will be given sequence numbers so that they can be
assembled at the other end
• Fragmentation followed by reassembly is an important concept in
networking
2-17
2-5: Advantages and Disadvantages of Connection-
Oriented Protocols
• Disadvantages
– Connection-oriented protocols place a heavy load on networks and on
computers connected to the Internet
• For example, we will see in Chapter 8 that it takes about 7 messages to
open and close a connection
• This is high overhead if only one or two content messages will be sent
during a connection.
– Connections-oriented protocols require more processing time on each host
• Error detection and correction take up many processing cycles for each
message
2-18
4.
The Hybrid TCP/IP-OSI
Standards Architecture

Standards Architecture
• A Standards Architecture Is a Broad Plan for Creating

Standards
– Break the problem into smaller pieces for ease of
development
– Develop standards for the individual pieces
• Assign individual standards to specialists in each area
– The dominant architecture today is the hybrid TCP/IP-OSI
standards architecture shown in the next slide
2-20
Figure 2-8: Hybrid TCP/IP-OSI Architecture
General Purpose Layer Specific Layer

(Core Layer) Purpose
Application-application Application (5) Application-application
communication interworking
Transmission of a Transport (4) Host-host
packet across an communication
internet
Internet (3) Packet delivery across
an internet
Transmission of a frame Data Link (2) Frame delivery across
across a single network a network
(switched or wireless
LAN or WAN) Physical (1) Device-device
connection
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2-21

2-7: Physical and Data Link Layer Standards in a
Switched or Wireless Network
1
A data link is a frame’s path though a single

switched or wireless network: A-R1 (host-router)
A physical link is a connection between two devices:

A-X1 (host-switch), X1-X2 (switch-switch), X2-R1 (switch-router)
2-22
2-8: Internet and Data Link Layers in a Routed Network
1
A data link is a
frame’s path through
a single switched
network. There are
individual switched
or wireless networks
in the figure, so
there are three data
links
A route is a
packet’s path all
the way through
the internet. There
always is a single
route because
there is only one
packet 2-23
2-8: Internet and Data Link Layers in a Routed
Network 3
A simplified view
Host
A Data Link A-R1
R1
Network X
3 Data Links: One per Network Network Y
1 Route through the internet Data
Link
Network Z Route A-B R1-R2
R2
Host
B Data Link R3-B
2-24
Network
In Network X:
Two destination addresses:
Frame X Packet: Host B (destination host)
Packet Frame: Router R1
Data Link
Switch
A-R1
Host A
Switch Server
Station
Switch
X1
Mobile Client
Station Switch Route
X2 Router R1
A-B
Network X
2-25
Network
To
Network X
Route
A-B Router R1
In Network Y: Frame Y
Two destination Data Link
R1-R2 Packet
addresses:
Packet: Host B
(destination host)
Frame: Router R2
To Router R2 Network Y
Network Z
2-26
Network
Frame Z
Packet
Data Link
R2-B
Host Switch
Z1 Router R2
B
Switch
Z2
Mobile Client Switch

Stations X2 Router
In Network Z:
Network Z Two destination addresses:
Packet: Host B (destination host) 2-27
© 2009 Pearson Education,
Frame:Inc. Publishing
Host B as Prentice Hall
Figure 2-10: Internet and Data Link Layers
in an Internet
• Internet and Transport Layers

– An internet is a group of switched or wireless
networks connected by routers so that any
application on any host on any network can
communicate with any application on any other host
on any other network
– Internet and transport layer standards govern

communication across an internet composed of two
or more switched or wireless networks
2-28
2-9: Internet and Transport Layers Standards
1
The transport layer adds functionality for the two hosts
to talk with each other to fix errors and do other things
The internet layer carries packets on the route

between the two hosts, across a series of routers.
There will be many hops across pairs of routers, so
internet layer protocols are kept very simple to reduce cost 2-29
2-9: Internet and Transport Layers Standards
1
The transport layer adds functionality for the two hosts
to talk with each other to fix errors and do other things
Transport Layer
End-to-End (Host-to-Host)
TCP is reliable and connection-oriented
UDP is unreliable and connectionless
Internet Layer
Hop-by-Hop (Router to Router)
IP is connectionless and unreliable
The internet layer carries packets on the route

between the two hosts, across a series of routers.
There will be many hops across pairs of routers, so
internet layer protocols are kept very simple to reduce cost 2-30
2-10: Application Layer Standards
• Application Layer Standards

– Govern how two applications work with each other, even
if they are from different vendors
• There are many application layer standards
because there are many applications
– World Wide Web (HTTP)
– E-Mail (SMTP, POP, etc.)
– FTP (FTP)
– Database (ODBC)
– Etc.
– There are more application layer standards than any other type of
standards
2-31
Standards Layers: Recap
Be able to repeat
• Application (5)
this in your sleep!
• Transport (4)
• Internet (3)
• Data Link (2)
• Physical (1)
2-32
5.
Syntax Examples:
Ethernet and IP

Syntax
• How Messages are Organized

– Usually organized as a succession of parts called fields
– Fields are a few or many bits long
Field Field Field Field Field Field

1 2 3 4 5 6
2-34
Octets
• Field length may be measured in bits

• Field length also may be measured in octets
• An octet is a group of eight bits
• In computer science, an octet is called a byte
Octet = 8 Bits
10010111
2-35
Figure 2-11: Ethernet Frame
This is an Ethernet
Start Preamble (7 octets) Frame
Start of Frame Delimiter (1 octet)
The address fields
Destination MAC Address (48 bits) give the Ethernet
addresses of
Source MAC Address (48 bits)
the source and
Length (2 octets) destination
hosts
LLC Subheader (7 octets)
Data
Field Packet (usually IP Packet) (variable) Each address is
48-bits long
PAD (variable)
Ethernet addresses
End Frame Check Sequence (4 octets) are called MAC
addresses
2-36
Start Preamble (7 octets)

Start of Frame Delimiter (1 octet)
Destination MAC Address (48 bits)
Source MAC Address (48 bits)
Length (2 octets)
LLC Subheader (7 octets) The Ethernet frame
Data
Field Packet (usually IP Packet) (variable) usually contains an
IP address in its
data field
PAD (variable)
End Frame Check Sequence (4 octets)
2-37
The sender computes
a value and puts it in
Start Preamble (7 octets)
the Frame Check
Start of Frame Delimiter (1 octet) Sequence Field
Destination MAC Address (48 bits)
The sender does the
Source MAC Address (48 bits) same calculation. If
its value matches the
Length (2 octets) transmitted value, the
frame is OK
LLC Subheader (7 octets)
Data
Field Packet (usually IP Packet) (variable) If the value is different,
an error has occurred.
PAD (variable) The receiver drops the
frame.
End Frame Check Sequence (4 octets)
Ethernet is not reliable
Ethernet Frame Layout

Ethernet frame
• Preamble
Trailer consisting of the bit sequence
“0101010101...” serving the bit synchronization of
the receiver.
• SFD (Start Frame Delimiter)
Start character consisting of the bit pattern
“10101011” showing the recipient that the actual
information will follow now.
• DA (Destination Address)
Evaluated by the recipient‘s address filter; only data
frames destined for this recipient will be passed on
to the communication software.
• SA (Source Address)
Sender‘s address
• LEN (Length)
Indicates the length of the subsequent data field in
Bytes according to IEEE 802.3.

Ethernet frame
• Data and Pad
The data field may contain 46 to 1500 user data
bytes. Are there less than 46 bytes the Ethernet
controller independently adds padding bytes, until the
total amount (data + pad) is 46. The data field can be
used at will, it only has to contain complete bytes.
• FCS (Frame Check Sequence)
A check character. It is obtained by taking the rest of
the division operation from the formula representing
the wide-spread cyclic- redundancy-check procedure.
This formula is applied to the bit sequence including
the address field through to the padding field. In case
of en error the whole frame is ignored, i.e. not passed
on to the application program.

2-12: Internet Protocol (IP) Packet
Bit 0 Bit 31
Version Header Diff-Serv Total Length
Number Length (8 bits) (16 bits)
(4 bits) (4 bits)
Identification (16 bits) Flags Fragment Offset (13

The IP packet is a long (3 bits) bits)
string of bits
Time to Live (8 Protocol (8 bits) Header Checksum (16 bits)
bits)
It is drawn 32 bits on a line
Source IP Address (32 bits)
Destination IP Address (32 bits)
The first line is bits 0
through 31 Options (if any) Padding
(to 32-bit
(binary counting starts at
boundary)
zero)
The next line is bits 32

through 63 Data Field (dozens, hundreds, or thousands of bits)
Often contains a TCP segment
2-42
Bit 0 Bit 31
The receiver uses the header (4 bits) (4 bits)
checksum field to check for Identification (16 bits) Flags Fragment Offset (13
errors (3 bits) bits)
Time to Live (8 Protocol (8 bits) Header Checksum (16 bits)
If an error is found, the bits)
receiver Source IP Address (32 bits)
discards the packet Destination IP Address (32 bits)
Options (if any) Padding
(to 32-bit
As in Ethernet, there is no boundary)
retransmission, so IP is not
reliable
Data Field (dozens, hundreds, or thousands of bits)
2-43
Bit 0 Bit 31
(4 bits) (4 bits)
The source and destination
IP addresses are each 32 bits long (3 bits) bits)
Time to Live (8 bits) Protocol (8 bits) Header Checksum (16 bits)
(to 32-bit boundary)

2-44
Bit 0 Bit 31
(4 bits) (4 bits)

(3 bits) bits)
Time to Live (8 bits) Protocol (8 bits) Header Checksum (16 bits)
The data field usually contains a
TCP segment or UDP datagram
(to 32-bit boundary)

2-45
6.
Reliability Options at the
Transport Layer
TCP versus UDP

2-13: Why Not Make All Layers Reliable?
• Reliability Is Expensive
– When errors are rare (in hops between routers and switches),
the cost is not justified
– Switches and routers would be much more expensive if they
did hop-by-hop error correction
– There are many switch and router hops, so doing error
correction between hops would be very expensive
– Error correction at the transport layer corrects errors made at
lower layers, making correction at lower layer unnecessary as
well as expensive
2-47
2-13: Why Not Make All Layers Reliable?
2
• Why Does Doing Error Correction at the
Transport Layer Make Sense?
• First,
– There are only two transport processes: one on the
source host, one on the destination host
– So error correction has to be done only once, keeping
cost low
• Second,
– The transport process is just below the application layer
– So doing error correction at the transport layer frees the
application layer from doing error correction
2-48
2-14: TCP and UDP at the Transport Layer
• Not all applications need reliability

– Voice over IP cannot wait for lost or damaged packets
to be retransmitted
– Network management protocols need to place as low
a burden on the network as possible
– Both types of applications use the simpler User
Datagram Protocol (UDP) instead of TCP
2-49
2-14: TCP and UDP at the Transport Layer
Comparison TCP UDP
Layer Transport* Transport*

Connection-orientation? Connection- Connectionless
oriented
Reliable? Reliable Unreliable
Burden on the two hosts High Low
Traffic burden on the network High Low
*Note: TCP and UDP are the only transport-layer protocols
2-50
7.
Vertical
Communication
Between Layer
Processes on the
Same Host

2-15: Layered Communication on the Source Host
Each layer requires

a process (hardware)
or software) on the host
In this section, we will

see how these layer
processes work together
on the source and
destination hosts,
beginning
with the source host
2-52
2
The process begins when a browser creates an
HTTP request message
Application HTTP
Process Message
Passes Message
New
Down to Transport Process
Not in the Book
Transport HTTP HTTP HTTP

Process Message Message Message
Fragment 1 Fragment 2 Fragment 3
If the application message is long,

the transport process will first fragment it
into fragments small enough to fit into single packets 2-53
2
Transport HTTP TCP

Process Message Hdr
For TCP,
The transport process
encapsulate each HTTP message
In the data field of
a TCP message (TCP segment)
by adding a TCP header
2-54
2-15: Layered Communication on the
Source Host
• When a layer process (N) creates a

message, it passes it down to the next-
lower-layer process (N-1) immediately
• The receiving process (N-1) will
encapsulate the Layer N message, that is,
place it in the data field of its own (N-1)
message

1
The transport process then passes the

message down to the internet layer process
Transport HTTP TCP

Process Message Hdr
Internet HTTP TCP IP

Process Message Hdr Hdr
The internet layer process encapsulates

The TCP segment in the data field of an IP Packet
2-56
1
Internet HTTP TCP IP

Process Message Hdr Hdr
Data Link Eth HTTP TCP IP Eth

Process Trlr Message Hdr Hdr Hdr
Encapsulation of IP Packet
in Data Field of Ethernet Frame
2-57
1
Data Link Eth HTTP TCP IP Eth

Process Trlr Message Hdr Hdr Hdr
The data link process passes the frame down to the physical layer
Physical
Process
Physical Layer converts the bits of the frame into signals.

There are no messages at the physical layer, so
there is no encapsulation at the physical layer
2-58
Recap
2-59
4
The following is the final frame for
an HTTP message on an Ethernet LAN
Eth HTTP TCP IP Eth

Trlr Message Hdr Hdr Hdr
L2 L5 L4 L3 L2
Notice the Pattern: From Right to Left: L2, L3, L4, L5, maybe L2
Start with the highest-layer message (in this case, 5)
Add headers for each lower layer (L4, L3, and L2, in this case)
Don’t forget the possible trailing L2 trailer
2-60
2-16: Decapsulation on the Destination Host
2-61
2-17: Layered End-to-End Communication
Encapsulation and decapsulation also occurs

on each switch and router along the way
In switches, the highest layer is the data link layer,

so switches are called Layer 2 devices
On routers, the highest layer is the internet layer,

So routers are called Layer 3 devices
2-62
Figure 2-18: Layered Message Exchange Initiated at
the Internet Layer
The application layer

process does not always
initiate communication
In ICMP, the internet layer

initiates the communication
and so is the highest layer
2-63
2-19: Combining Horizontal and Vertical
Communication
Horizontal communication using protocols lets processes

talk to their peers on other hosts, switches, or routers
Vertical communication links processes on the same device
Horizontal and vertical communication

work together to provide message delivery
2-64
8.
OSI, TCP/IP, and Other
Standards Architectures

2-20: The Hybrid TCP/IP-OSI Architecture
Broad Purpose TCP/IP OSI Hybrid TCP/IP-OSI

Applications Application Application (Layer 7) Application (Layer 5)
Presentation (Layer 6)
Session (Layer 5)
Internetworking Transport Transport (Layer 4) TCP/IP Transport
Layer (Layer 4)
Internet Network (Layer 3) TCP/IP Internet
Layer (Layer 3)
Communication Use OSI Data Link (Layer 2) Data Link (OSI)
within a single Standards Here Layer (Layer 2)
switched LAN
or WAN Physical (Layer 1) Physical OSI Layer
(Layer 1)
The TCP/IP-OSI Architecture draw its standards from two different

Standards architectures—TCP/IP and OSI
2-66
Figure 2-21: OSI and TCP/IP
OSI TCP/IP
Standards Agency ISO (International IETF (Internet
or Agencies Organization for Engineering Task Force)
Standardization)
ITU-T (International
Telecommunications
Union–
Telecommunications
Standards Sector)
Dominance Nearly 100% at physical 80% to 90% at the

and data link layers internet and transport
layers
Documents Are Various Mostly RFCs (requests
Called for comments)
2-68
2-22: OSI Layers Again, OSI Layers 1 and 2
Are almost universally used
Layer OSI Name Purpose Use
Number
1 Physical Physical connections between adjacent Nearly 100%
devices dominant
2 Data Link End-to-end transmission in a single switched Nearly 100%
network. Frame organization. Switch dominant
operation
3 Network Generally equivalent to the TCP/IP internet Rarely used
layer. However, OSI network layer standards
are not compatible with TCP/IP internet
layer standards
4 Transport Generally equivalent to the TCP/IP transport Rarely used

layer. However, OSI transport layer
standards are not compatible with TCP/IP
transport layer standards
Although Layers 3 and 4 are architecturally

Similar in TCP/IP and OSI, individual standards from
the two architectures are not compatible at these layers
2-70
2-22: OSI Layers
Layer OSI Name Purpose Use
Number
5 Session Initiates and maintains a connection Rarely used
between application programs on different
computers
If a session is broken, only have to go back
to the last rollback point
Brilliant idea, but few applications need it
and those that do have their own methods
for managing sessions
6 Presentation Designed to handle data formatting Rarely used as a
differences, data compression, and data layer. However, many
encryption file format standards
In practice, a category for general file are assigned to this
format standards used in multiple layer.
applications
7 Application Governs remaining application-specific Some OSI
matters applications are used
2-71
Standard Delivery Model
Source: 1 Collins St. (Mount Franklin)
7 CEO – Interacts with customers and his company. 50 L of
APP – Link between applications and the network. Allows Mineral
applications to use the network.
6 Secretary (Facilitator) – Translates, Secures, …
PRES - Translates into common Formats, defines, encryption and
compression
5 Manager – Engages, Disengages customers
SESS – Start, stop, pause, control and end application sessions
4 Customer Care – Insurance/No Insurance … Goods sent without problems 12345

and correct order, divide/bottle it, mark each bottle for reassembly, confirm 6 7 8 9 10
if received Each bottle is 5L
as defined by the
TRANS – Error recovery, segmentation, reassembly, ack. dispatch
3 Addressing – Confirms the address is valid, validates it knows the address |1

Sent to 223 King St.
from Melway and maps the trip
NET – IP Addressing & Routing. IP addresses live here.
2 Dispatch – Responsible for goods delivery and dept. Law-maker, packs the ||1|
goods, puts approx. weight. 5.00L
DL – packs data to be sent, CRC, in-charge of media access.
MAC addresses live here
1 Delivery – Transmits goods by normal post, speed post, courier, special Goods transmitted
by the preferred
messenger. method
PHY – Transmits data, connections, pins, signals
Dest: 223 Kings St(customer)
50L of Mineral Water
ACK TRANS 1 … 10
ACK, Reassembly
Segment
NET |1
Packet We are 223 King St
DL ||1|
Frame Actual weight 4.97L?!!!!
Actual weight 5.00L?!!!!
PHY Delivery Department
Receives goods unsure if same as
sent
2-23: Other Major Standards Architectures
• IPX/SPX
– Used by older Novell NetWare file servers for file and
print service
– Sometimes used in newer Novell NetWare file servers
for consistency with older NetWare servers
• SNA (Systems Network Architecture)

– Used by older IBM mainframe computers
• AppleTalk
– Used by Apple Macintosh desktops and notebooks to
talk to Macintosh servers
2-74
2-24: Characteristics of Protocols Discussed in
this Chapter
Layer Protocol Connection- Reliable or

Oriented or Unreliable?
Connectionless?
5 (Application) HTTP Connectionless Unreliable
4 (Transport) TCP Connection- Reliable

oriented
4 (Transport) UDP Connectionless Unreliable
3 (Internet) IP Connectionless Unreliable
2 (Data Link) Ethernet Connectionless Unreliable
2-75
9.
Topics Covered

Network Standards
• The Core of Networking

• Network Standards Govern
– Message order (turn taking, etc.)
– Message syntax (structure of messages)
• Header, data field, trailer
• Header is subdivided into header fields
– Message semantics (meaning)
– Reliable or unreliable operation
• Requires both error detection AND error correction
– Connection-oriented or connectionless operation
2-77
Architectures
• Hybrid TCP/IP-OSI Architecture

– Layer 5: Application
– Layer 4: Transport
– Layer 3: Internet
– Layer 2: Data Link
– Layer 1: Physical
• Connections
– Layer 1: Physical link between adjacent devices
– Layer 2: Data link through a single switched network
– Layer 3: route through a routed network (internet)
2-78
Syntax Examples
• Ethernet Frame
– 48-bit MAC address fields
– Error detection and discarding; not reliable
– Carries a packet in its data field
• Internet Protocol (IP) Packet

– 32-bit IP address fields
– Error detection and discarding; not reliable
– Usually carries a TCP or UDP message in its data field
– Can also carry an ICMP message
2-79
TCP and UDP
• The Only Protocols at the Transport Layer

• TCP is Reliable
– Reliability is expensive
– TCP fixes errors at all lower layers, giving the application
process clean data
– Error correction only has to be done once, on the source
and destination hosts
• UDP is Unreliable
– Low burden on the network and hosts
– Useful if application cannot use reliability or prefers not
to use it
2-80
Vertical Communication
2-81
Vertical and Horizontal Communication
2-82
All rights reserved. No part of this publication may be reproduced, stored in a
retrieval system, or transmitted, in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the prior written
permission of the publisher. Printed in the United States of America.
Copyright © 2009 Pearson Education, Inc.

Publishing as Prentice Hall

Panko Bdnt7e ch02

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Panko Bdnt7e ch02

Uploaded by

Copyright:

Available Formats

Network Standards

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

• Network Standards Govern

• General Message Syntax (Organization)

Trailer Data Field Header

• General Message Syntax (Organization)

Trailer Data Field Header

Data Field Header

Message without a trailer Other Destination

Error Detection and Correction

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

• The Transmission Control Protocol (TCP) is an

– If an acknowledgments is not received by the

Carry 5. ACK (4)

• HTTP is an unreliable protocol

• Some protocols detect errors, dropping incorrect

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

Messages During the Connection

Connection-oriented protocols have formal openings

Connection-Oriented Protocol Connectionless Protocol

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

• A Standards Architecture Is a Broad Plan for Creating

General Purpose Layer Specific Layer

© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2-21

A data link is a frame’s path though a single

A physical link is a connection between two devices:

Mobile Client Switch

• Internet and Transport Layers

– Internet and transport layer standards govern

The internet layer carries packets on the route

The internet layer carries packets on the route

• Application Layer Standards

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

• How Messages are Organized

Field Field Field Field Field Field

• Field length may be measured in bits

Start Preamble (7 octets)

Source MAC Address (48 bits)

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

Identification (16 bits) Flags Fragment Offset (13

The next line is bits 32

Data Field (dozens, hundreds, or thousands of bits)

Identification (16 bits) Flags Fragment Offset (13

Data Field (dozens, hundreds, or thousands of bits)

TCP versus UDP

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

• Not all applications need reliability

Comparison TCP UDP

Layer Transport* Transport*

Burden on the two hosts High Low

Traffic burden on the network High Low

*Note: TCP and UDP are the only transport-layer protocols

© 2009 Pearson Education, Inc. Publishing as Prentice Hall

Each layer requires

In this section, we will

Transport HTTP HTTP HTTP

If the application message is long,

Transport HTTP TCP

• When a layer process (N) creates a

© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2-55