$70(QFDSVXODWLRQ

0HWKRGV
A number o standards hae been deeloped which describe the
encapsulation o LAN and \AN protocols oer A1M. 1hese standards
allow users to integrate A1M into existing \ANs and,or LANs, thus
proiding arious cost-eectie upgrade routes. 1his chapter describes the
arious encapsulation methods in general, speciic inormation concerning
the analysis, or decoding o particular protocols may be ound in the
respectie protocol chapters.
1he ollowing methods are used or encapsulation or transporting LAN or
\AN protocols ia A1M:
VC-based Lncapsulation: uses predeined VPI,VCI alues or speciic
protocols. Used or \AN or LAN protocols.
Multiprotocol Lncapsulation oer A1M Adaptation Layer 5 ,IL1l
RlC1483,: coers encapsulation o LAN protocols oer A1M with the
use o the LLC header.
$70(QFDSVXODWLRQ0HWKRGV
Classical IP and ARP oer A1M ,IL1l RlC15,: coers ARP,RARP
encapsulation.
lrame Relay oer A1M: describes transmission o lrame Relay ia
A1M.
LAN Lmulation: emulates Lthernet or 1oken Ring LANs.
VC8ased (nu||) Mu|tip|exin 73
VC8ased (nu||) Mu|tip|exin
VC-based multiplexing uses one Virtual Channel ,VCI,VPI pair, or each
protocol. In this way, the protocol is carried directly oer the AAL5 PDU.
Since no additional inormation is added to the protocol, this is sometimes
called null encapsulation.
lor routed protocols e.g., 1CP,IP, IPX, the PDU is carried directly in the
payload o the AAL5 CPCS PDU. lor bridged protocols e.g., Lthernet,
1oken Ring, lDDI, all ields ollowing the PID ield are carried in the
payload o the AAL5 CPCS PDU.
$70(QFDSVXODWLRQ0HWKRGV
0XOWLSURWRFRORYHU$70
IL1l RlC 1483 http:,,www.cis.ohio-state.edu,htbin,rc,rc1483.html
One method o transmitting LAN protocols oer A1M is by using LLC
encapsulation. In this instance, the LLC and SNAP headers within the
AAL5 PDU are used to identiy the encapsulated protocol. 1his protocol
stack is shown in the ollowing illustration.
Upper-layer applications
Upper-layer protocols
Ethernet or TCP/IP
SNAP
802.2 LLC
AAL5
ATM
Physical
/$1SURWRFROVHQFDSVXODWHGRYHU$70
In multiprotocol encapsulation, the PDUs are carried in the Payload ield o
the Common Part Conergence Sublayer ,CPCS, PDU o A1M Adaptation
Layer type 5 ,AAL5,. In this encapsulation method, the LLC header is
always 0xAA-AA-03, which indicates that the LLC header is ollowed by a
SNAP header.
DSAP
AA
SSAP
AA
Ctrl
03
//&KHDGHU
1he ormat o the SNAP header is as ollows:
Organizationally Unique Identifier (OUI) Protocol Identifier (PID)
3 bytes 2 bytes
61$3KHDGHU
Non-ISO PDUs e.g., 1CP,IP, IPX, are identiied by an OUI alue o 0x00-
00-00, ollowed by the PID, which represents the 2-byte Lther1ype ield.
lor example, an Lther1ype alue o 0x08-00 identiies an IP PDU.
0XOWLSURWRFRORYHU$70
LLC 0xAA-AA-03
OUI 0x00-00-00
EtherType (2 bytes)
Non-ISO PDU
(up to 65527 bytes)
Pa,oaa forvat for rovtea vovO PD|.
Non-routed bridged protocols are identiied by an OUI alue o 0x00-80-C2
ollowed by the 2-byte PID which speciies the protocol which ollows. 1he
ollowing table lists some possible alues or the PID ield in this instance.
3,'9DOXH 3URWRFRO
0x00-01,0x00-0 Lthernet,802.3
0x00-03,0x00-09 1oken Ring,802.5
0x00-04,0x00-0A lDDI
1he ollowing diagrams represent the payload ormat or the Lthernet,
1oken Ring, lDDI and SMDS PDUs.
LLC 0xAA-AA-03 LLC 0xAA-AA-03
OUI 0x00-80-C2 OUI 0x00-80-C2
PID 0x00-01 or 0x00-07 PID 0x00-03 or 0x00-09
PAD 0x00-00 PAD 0x00-00-xx
MAC destination address Frame Control (1 byte)
MAC destination address
remainder of MAC frame remainder of MAC frame
LAN FCS (if PID is 0x00-01) LAN FCS (if PID is 0x00-03)
Pa,oaa forvat for briagea
tbervet,02. PD|.
Pa,oaa forvat for briagea 1oev
Rivg,02.: PD|.
$70(QFDSVXODWLRQ0HWKRGV
LLC 0xAA-AA-03 LLC 0xAA-AA-03
OUI 0x00-80-C2 OUI 0x00-80-C2
PID 0x00-04 or 0x00-
0A
PID 0x00-0B
PAD 0x00-00-00 Reserved BEtag Common PDU
Frame Control (1 byte) BAsize Header
MAC destination address MAC destination address
remainder of MAC frame remainder of MAC frame
LAN FCS (if PID is 0x00-
01)
LAN FCS (if PID is 0x00-
01)
3D\ORDGIRUPDWIRUEULGJHG
)'',3'8V
3D\ORDGIRUPDWIRUEULGJHG
60'63'8V
7KHIROORZLQJFDSWXUHGLVSOD\LQPXOWLSURWRFROPRGHOLVWVWKH//&SURWRFRO
IROORZHGE\HQFDSVXODWHG,3
'HFRGHRI//&ZLWKHQFDSVXODWHG,3
,3$GGUHVVLQJRYHU$70
,3$GGUHVVLQJRYHU$70
IL1l RlC 15 http:,,www.cis.ohio-state.edu,htbin,rc,rc15.html
A1MARP is a ersion o ARP and InARP which is appropriate or A1M.
In A1MARP the LLC and SNAP headers identiy the encapsulated protocol
as described aboe in Multiprotocol Lncapsulation oer A1M. 1he LLC
header has the alue 0xAA-AA-03, which indicates that the LLC header is
ollowed by a SNAP header. 1he OUI alue or ARP is 0x00-00-00,
ollowed by the Lther1ype ield o alue 0x08-06.
Internet addresses are assigned independently o A1M addresses. Lach host
implementation must know its own IP and A1M address,es, and must
respond to address resolution requests appropriately. IP members must also
use A1MARP and InA1MARP to resole IP addresses to A1M addresses
when needed.
1he A1MARP PDU is shown in the ollowing illustration.
8 16 24 32 bits
Hardware type Protocol type
Type and length
of source ATM
number
Type and length
of source ATM
subaddress
Operation
Length of source
protocol address
Type and length
of target ATM
number
Type and length
of target ATM
subaddress
Length of target
protocol address
Source ATM number (q bytes) Source ATM subaddress (r bytes)
Source protocol address (s bytes) (IP=4 bytes)
Target ATM number (x bytes) Target ATM subaddress (y bytes)
Target protocol address (z bytes) (IP=4 bytes)
3D\ORDGIRUPDWIRU$70$533'8
A1MARP and InA1MARP use the same hardware type, protocol type and
operation code data ormats as ARP and InARP. 1he location o these
ields within the A1MARP packet are in the same byte position as those in
ARP and InARP packets. A unique hardware type alue has been assigned
or A1MARP.
$70(QFDSVXODWLRQ0HWKRGV
)UDPH5HOD\RYHU$70
0XOWLSURWRFRO(QFDSVXODWLRQ
I.233, IL1l RlC 1294 http:,,www.cis.ohio-state.edu,htbin,rc,rc1294.html
In multiprotocol encapsulation, a lrame Relaying Serice Speciic
Conergence Sublayer ,lR-SSCS, is used on top o the Common Part
Conergence Sublayer ,CPCS, o the AAL type 5 or lrame Relay,A1M
internetworking. 1he serice, oered by lR-SSCS, corresponds to the Core
serice or lrame Relaying as described in I.233.
An lR-SSCS PDU consists o Q.922 Address ield ollowed by Q.922
Inormation ield. 1he Q.922 lags and the lCS are omitted, since the
corresponding unctions are proided by the AAL. 1he igure below shows
an lR-SSCS PDU embedded in the Payload o an AAL5 CPCS PDU.
Q.922 Address field
2-4 bytes
FR-SSCS PDU header
Q.922 Information field FR-SSCS PDU payload
AAL CPCS PDU trailer
)566&63'8LQSD\ORDGRI$$/&3&63'8
Routed and bridged PDUs are encapsulated inside the lR-SSCS PDU as
deined in IL1l RlC1294. 1he Q.922 Inormation ield starts with a Q.922
Control ield ollowed by an optional Pad octet that is used to align the
remainder o the rame to a conenient boundary or the sender. 1he
protocol o the carried PDU is then identiied by preixing the PDU by an
ISO,CCI11 Network Layer Protocol ID ,NLPID,.
In the speciic case o an IP PDU, the NLPID is 0xCC. According to IL1l
RlC1294 the Q.922 Address ield should be either 2 or 4 octets, i.e., a 3
octet Address ield is not supported. In the case o ISO protocols, the
NLPID ield orms the irst octet o the PDU itsel and should not be
repeated.
)UDPH5HOD\RYHU$70
Q.922 Address field
(2 or 4 bytes)
0x03 (Q.922 Control)
NLPID (OxCC)
IP PDU
(up to 2
16
-5 bytes)
)566&63'8IRUPDWIRUURXWHG,33'8V
1he aboe encapsulation applies only to those routed protocols that hae a
unique NLPID assigned. lor other routed protocols ,and or bridged
protocols,, it is necessary to proide another mechanism or easy protocol
identiication. 1his can be achieed by using an NLPID alue o 0x80 to
indicate an ILLL 802.1a SubNetwork Attachment Point ,SNAP, header.
)UDPH5HOD\$70,QWHUQHWZRUNLQJ
Mapping between A1M PDUs and lrame Relay PDUs requires examination
o the incoming A1M AAL5 CPCS PDU payload header or lrame Relay
Q.922 PDU payload header to determine the type, and then to oerwrite the
incoming header with the outgoing header.
1he ollowing diagram shows the translation between the lrame Relay
Q.922 PDU payload header and the A1M AAL5 CPCS PDU payload
header.
Control 0x03 Pad 0x00 LLC 0xAA-AA
NLPID 0x80 OUI 0x00 0x03 OUI 0x00
0x80-C2 0x80-C2
PID PID
Pad 0x00-00
Remainder of MAC frame
Remainder of MAC Frame
)UDPH5HOD\SD\ORDGKHDGHU $70$$/&3&63'8SD\ORDGKHDGHU
Reer to lrame Relay lorum lRl.8 or detailed inormation concerning the
proisions or traic management between the two protocols.
$70(QFDSVXODWLRQ0HWKRGV
/$1(PXODWLRQ
1he LAN emulation protocol uses control messages to set up the LAN.
LAN Lmulation proides or two possible data packet ormats: Lthernet
and 1oken Ring. 1he LAN emulation data rames presere all the
inormation contained in the original 802.3 or 802.5 rames, but add a 2-byte
LLC ID ,the source ID,, which is unique to each LLC.
Reer to Chapter 21 or a more detailed description o LAN Lmulation.