Beruflich Dokumente
Kultur Dokumente
Course Outline
1) Introduction
2) Background - Ethernet
3) Background HDLC
4) Background - PPP
5) Background - SONET/SDH
6) VCAT
7) LCAS
8) POS (PPP over SONET/SDH RFC 1619/2615)
9) LAPS
10) GFP
11) Alternatives
Y(J)S EoS Slide 2
Introduction
Motivation
Assume that you are a traditional operator
Ethernet handoff
I
W
F
A
D
M
SONET
RING
A
D
M
I
W
F
Ethernet
Switch
Option 3: ATM
Ethernet
Switch
A
T
M
A
D
M
SONET
RING
A
D
M
A
T
M
Ethernet
Switch
Option 4: EoS
Ethernet
Switch
I
W
F
SONET
RING
I
W
F
Ethernet
Switch
Worlds Apart
SONET/SDH is presently the most prevalent transport infrastructure
Ethernet is by far the most popular user data interface
So we need efficient methods for carrying Ethernet over SONET
But Ethernet
comes in bursty frames (packets)
uses basic rates of 10, 100, 1000 Mbps
While SONET/SDH
is constant bit rate
is designed for various rates such as 1.6, 2.176, 6.784 Mbps
So the job isnt easy !
Y(J)S EoS Slide 9
HDLC
RFC1661
RFC1662
RFC2615
G.707
G.709
OTN
G.7041
GFP
G.7042
G.7043
X.85
X.86
Background
Ethernet
Ethernet frame
For our purposes, Ethernet is any layer 2 protocol
using 1 of the following frame formats :
64 1518 B
DA (6B)
SA (6B)
T/L (2B)
data (0-1500B)
pad (0-46)
FCS (4B)
68 1522 B
DA(6B)
SA(6B)
VT(2B)
VLAN(2B)
T/L(2B)
data (0-1500B)
pad(0-46)
FCS(4B)
Background
HDLC
packet 2
packet 3
packet 4
packet 1
packet 2
packet 3
packet 4
HDLC flags
ISO developed High level Data Link C based on IBMs SDLC
HDLC inputs packets of bytes
HDLC uses hex 7E as its idle code (flag) 01111110
So an idle HDLC stream repeats 7E
01111110 01111110 01111110 packet 1 01111110 01111110 01111110 packet 2 01111110 01111110 01111110 01111110 packet 3 01111110
RFC1549
encoding/decoding is easy in SW
Y(J)S EoS Slide 19
HDLC framing
HDLC frame is bounded by flags, and has a particular structure
flag (8)
data
Many variants (SDLC, ISO, LAPB, LAPD, LAPF, LAPS, SS7, PPP-HDLC, Cisco-HDLC, etc)
Address:
There may be no address (e.g. SS7 HDLC)
SDLC always had 8 bit addresses
ISO 3309 HDLC has structured multibyte address
SAPI
C/R EA
EA
HDLC control
HDLC networks can be configured:
Balanced all stations have equal responsibility
Unbalanced primary and one or more secondary stations
and HDLC can operate :
Best effort (datagram)
uses Un-numbered (U) frames
Reliable (Asynchronous Balanced Mode)
uses frames with sequence numbers in control field
Information (I) frames (data + acknowledgement)
Supervisory (S) frames (only acknowledgement)
The various frame types are indicated by the control field
which varies widely between different protocols
HDLC FCS
HDLC uses a Frame Check Sequence to detect errors
The FCS is implemented as a shift-register
CRC-16 X16 + X12 + X5 + 1
CRC-32 X32 + X26 + X23 + X22 + X16 + X12 + X11 + X10 + X8 + X7 + X5 + X4 + X2 + X + 1
Some HDLC-based protocols require 32 bit FCS
others allow 16 bit but recommend 32 bit FCS
Background
PPP
information
padding
address
ctrl
protocol
7E
FF
03
(8/16b)
information
padding
FCS
flag
(optional)
(16/32b)
7E
X.85
flag
address
ctrl
protocol
7E
FF
03
(8/16b)
flag
address
ctrl
SAPI
7E
04
03
(16b)
information
padding
FCS
flag
(optional)
(16/32b)
7E
FCS
flag
(32b)
7E
IP Packet
Background
SONET/SDH
Note:
For more information see SONET/SDH course.
SONET architecture
ADM
regenerator
ADM
Path
Line
Section
Line
Path
Termination
Termination
Termination
Termination
Termination
path
line
section
line
section
line
section
section
multiplex section
regenerator section
9 rows
90 columns
9 rows
270 columns
SONET/SDH rates
SONET
SDH
STS-1
columns
rate
90
51.84M
STS-3
STM-1
270
155.52M
STS-12
STM-4
1080
622.080M
STS-48
STM-16
4320
2488.32M
STS-192
STM-64
17280
9953.28M
SONET/SDH tributaries
SONET
SDH
STS-1
T1
T3
E1
E3
28
21
E4
STS-3
STM-1
84
63
STS-12
STM-4
336
12
252
12
STS-48
STM-16
1344
48
1008
48
16
STS-192
STM-64
5376
192
4032
192 64
9 rows
6 rows
3 rows
90 columns
section + line
overhead
Transport
Overhead
TOH
Scrambling
Xn
Yn = Xn + Yn-43
Z-43
Y(J)S EoS Slide 36
2 bytes in the line overhead point to the STS path overhead POH
pointer (floating) allows frequency/phase compensation
(after re-arranging) POH is one column of 9 rows (9 bytes = 576 kbps)
Y(J)S EoS Slide 37
Path overhead
J1
B3
C2
G1
C2
(hex)
Payload type
00
unequipped
01
nonspecific
02
LOP (TUG)
04
E3/T3
F2
12
E4
H4
13
ATM
16
18
LAPS X.85
1A
10G Ethernet
1B
GFP
CF
PoS - RFC1619
F3
K3
N1
POH
STS-1 HOP
1
30
59
87
LOP
1
30
59
87
VTG
1 2 3 4 5 6 7
LOP
HOP
VC
column
rate
payload
VT 1.5
VC-11
1.728 DS1
(1.544)
4 per group
VT 2
VC-12
2.304 E1
(2.048)
3 per group
2 per group
6.912 DS2
1 per group
VT 3
VT 6
VC-2
12
STS-1
VC-3
48.384 E3
(34.368)
STS-1
VC-3
48.384 DS3
(44.736)
STS-3c
VC-4
149.760 E4
(6.312)
(139.264)
Payload capacity
VT1.5/VC-11 has 3 columns = 27 bytes = 1.728 Mbps
but 2 bytes are used for overhead
so actually only 25 bytes = 1.6 Mbps are available
Similarly
VT2/VC-12 has 4 columns = 36 bytes = 2.304 Mbps
but 2 bytes are used for overhead
So actually only 34 bytes = 2.176 Mbps are available
VCAT
Virtual Concatenation
Concatenation
Payloads that dont fit into standard VT/VC sizes can be accommodated
by concatenating of several VTs / VCs
For example, 10 Mbps doesnt fit into any VT or VC
so w/o concatenation we need to put it into an STS-1 (48.384 Mbps)
the remaining 38.384 Mbps can not be used
We would like to be able to divide the 10 Mbps among
7 VT1.5/VC-11 s = 7 * 1.600 = 11.20 Mbps or
5 VT2/VC-12 s = 5 * 2.176 = 10.88 Mbps
Concatenation
There are 2 ways to concatenate X VTs or VCs:
9 columns of
section and
line overhead
3 columns of
path overhead
STS-3
270 columns
9 rows
STS-3c
0.576 = 149.760 Mbps
1 column of
path overhead
260 columns *
Virtual Concatenation
H4
VC-12-Xv
VC-2-Xv
Capacity (Mbps)
1.600, 3.200,
1.600X
in VC-3 X 28 C 44.800
2.176, 4.352,
2.176X
in VC-3 X 21 C 45.696
6.784, 13.568, ,
6.784X
in VC-3 X 7
in VC-4 X 64 C 102.400
in VC-4 X 63 C 137.088
C 47.448
in VC-4 X 21 C 142.464
Capacity (Mbps)
X 28 C 44.800
in STS-3c X 64 C 102.400
VT2-Xv
in STS-1
X 21 C 45.696
in STS-3c X 63 C 137.088
VT3-Xv
in STS-1
X 14 C 46.592
in STS-3c X 42 C 139.776
VT6-Xv
in STS-1
X 7 C 47.448
in STS-3c X 21 C 142.464
So we have many permissible rates
1.600, 2.176, 3.200, 3.328, 4.352, 4.800, 6.400, 6.528, 6.656, 6.784,
Y(J)S EoS Slide 50
Efficiency comparison
rate
w/o VCAT
efficiency
with VCAT
efficiency
10
STS-1
21%
VT2-5v
92%
VC-12-5v
100
STS-3c
67%
VC-4
1000
STS-48c
VC-4-16c
STS-1-2v
100%
VC-3-2v
42%
STS-3c-7v
95%
VC-4-7v
PDH VCAT
VCAT
overhead
octet
1st
frame
of
4 E1s
TS0
time
Y(J)S EoS Slide 52
VCAT
overhead
octet
frames
of an
E1
TS0
Delay compensation
802.1ad Ethernet link aggregation cheats
each identifiable flow is restricted to one link
doesnt work if single high-BW flow
VCAT is completely general
works even with a single flow
VCG members may travel over completely separate paths
so the VCAT mechanism must compensate for differential delay
Requirement for over second compensation
Must compensate to the bit level
but since frames have Frame Alignment Signal
the VCAT mechanism only needs to identify individual frames
VCAT buffering
(4096*0.125m=512m)
For HOS SDH VCAT and PDH VCAT (H4 byte or PDH VCAT overhead)
The basic multiframe is 16 frames
So we need 256 multiframes in a superframe (256*16=4096)
The MultiFrame Indicator is divided into two parts:
LCAS
Link Capacity Adjustment Scheme
LCAS
LCAS is defined in G.7042 (also numbered Y.1305)
LCAS extends VCAT by allowing dynamic BW changes
LCAS is a protocol for dynamic adding/removing of VCAT members
hitless BW modification
similar to Link Aggregation Control Protocol for Ethernet links
LCAS is not a control plane or management protocol
it doesnt allocate the members
still need control protocols to perform actual allocation
LCAS is a handshake protocol
it enables the path ends to negotiate the additional / deletion
it guarantees that there will be no loss of data during change
it can determine that a proposed member is ill suited
it allows automatic removal of faulty member
Y(J)S EoS Slide 58
POH
H4 format
reserved fields
CTRL
GID
MST bits
RS-ACK
16 frame multiframe
reserved fields
MFI1
GID
single bit - cycles through 215-1 LFSR sequence
Y(J)S EoS Slide 62
VLI format
reserved fields
CTRL
GID
MST bits
RS-ACK
16 frame multiframe
reserved fields
MFI1
Initial state:
PoS
Packet over SONET
PoS architecture
IP
PPP
HDLC
SONET/SDH
IP
Ethernet
IP is a WAN technology
data transported in native IP
different L2 technologies for last segment
PoS Details
IP packet is encapsulated in PPP
default MTU is 1500 bytes
up to 64,000 bytes allowed if negotiated by PPP
FCS is generated and appended
PPP in HDLC framing with byte stuffing
43 bit scrambler is run over the SPE
byte stream is placed octet-aligned in SPE
(e.g. 149.760 Mbps of STM-1)
HDLC frames may cross SPE boundaries
Y(J)S EoS Slide 71
POS problems
PoS is BW efficient
but POS has its disadvantages
BW must be predetermined
LAPS
Link Access Protocol over SDH
X.85 and X.86
LAPS
In 2001 ITU-T introduced protocols for transporting packets over SDH
X.86
IP
IP
IP
LLC
LAPS
LLC
MAC
SDH
MAC
IP
IP
IP
LLC
LLC
LLC
MAC
MAC
MAC
LAPS
SDH
X.85
flag
address
ctrl
SAPI
7E
(16b)
03
(16b)
IP Packet
FCS
flag
(32b)
7E
MAC
X.86
reconciliation
MII/GMII
LAPS
rate adaptation
SDH
Similar to X.85 (IP over SDH using LAPS)
but transports the entire Ethernet frame
Provides a virtual MII/GMII interface
Transparent to all Ethernet features (VLAN, P bits, RPR, etc.)
Rate adaptation by adding hex DD (after byte stuffing 7D DD)
Ammendment specifies use of Ethernet PAUSE frames for rate limiting
flag
address
ctrl
SAPI
Ethernet frame
FCS
flag
7E
(16b)
03
FE01
(32b)
7E
Y(J)S EoS Slide 78
LAPS drawbacks
Only IP or Ethernet payloads
Single bit errors (e.g. in flags) may cause misalignment
Not very efficient
HDLC BW expansion
HDLC BW nondeterminacy
GFP
Generic Framing Procedure
GFP architecture
Defined in ITU-T G.7041 (also numbered Y.1303)
originally developed in T1X1 to fix ATM limitations
(like ATM) uses HEC protected frames instead of HDLC
GFP generically encapsulates client (e.g. IP, Ethernet)
onto transport network (e.g. SONET/SDH, OTN)
Ethernet
IP
HDLC
other
SDH
OTN
other
core
header
cHEC (2B)
payload header
(4-64B)
PLI (2B)
payload
area
payload
optional payload
FCS (4B)
type (2B)
tHEC (2B)
extension header
(0-58B)
eHEC (2B)
GFP modes
GFP-F - frame mapped GFP
Good for PDU-based protocols (Ethernet, IP, MPLS)
or HDLC-based ones (PPP)
Client PDU is placed in GFP payload field
GFP-T transparent GFP
Good for protocols that exploit physical layer capabilities
In particular
8B/10B line code
used in fiber channel, GbE, FICON, ESCON, DVB, etc
Were we to use GFP-F would lose control info, GFP-T is transparent to these codes
Also, GFP-T neednt wait for entire PDU to be received (adding delay!)
GFP-T
Main application Storage Area Networks (SAN)
SANs use 8B/10B line code and are very delay sensitive
8B/10B line code maps each of the 256 values of the 8-bit input
into 1 or 2 different 10 bit words
Maintains a running 0-1 balance and when encoding an input with 2 possibilities, it
chooses the one that improves the balance
spare 10b symbols are used as control codes (e.g. start/end of frame)
Were we to use GFP-F would lose control info, GFP-T is transparent to these codes
Also, GFP-T neednt wait for entire PDU to be received (adding delay!)
GFP-T maps 8B/10B line code into 64B/65B block code
GFP-F
Client packet/frame without un-needed overhead (e.g. flags, preamble, etc)
is placed in GFP payload field
Interface is at link layer
More BW efficient than GFP-T since idle periods are filtered out
preambles, frame-start, etc are also not transported
GFP-F must know the client protocol in order to detect frames
Can mux different client protocols on a frame to frame basis
If the client protocol has a good FCS, dont need to use GFPs FCS
GFP-F is used for EoS
Either IP in PPP or native Ethernet can be used
GFP advantages
Supports multiple protocols (not just Ethernet and IP)
For Ethernet, GFP can transparently transport entire frame
Robust single bit errors do not cause loss of alignment
Constant predictable overhead
Good efficiency (similar to LAPS best case)
GFP-T for SAN support
Can run over OTN (G.709) as well as SONET
Alternatives
WAN-PHY (10GBASE-W)
Copper technologies
OAM
Y(J)S EoS Slide 90
G.707 Annex F
There is a special case where Ethernet and SDH bit-rates are close
STM-64 is 9953.28Mbps
GbE 10GBASE-R (64B/66B coding) can be directly mapped
into a STM-64 (with contiguous concatenation) without need for GFP
MAC creates "stretched InterPacket Gap" to compensate for rate being < 10G
This is the fastest connection commonly used for Internet traffic
Complication: SDH clock accuracy is 4.6 ppm, GbE accuracy is 20 ppm
64*(270-9) = 16704
columns
J1
Ethernet PWs
Customer
Edge
(CE)
Customer
Edge
(CE)
Customer
Edge
Customer
Edge
MPLS network
Provider
Edge
Provider
Edge
(CE)
(PE)
(PE)
Customer
Edge
Ethernet
Ethernet
PseudoWires (PWs)
(CE)
MPLS
label
stack
PW
label
PWE
control
word
(CE)
Ethernet frame
(with or w/o FCS)
Y(J)S EoS Slide 93