HP 800 HP DLPI Programmer's Guide - Page 27

DA/SA MAC address, SAP/Ethertype, SNAP SAP = 0xAA, DA/SA, DSAP/SSAP, RIF, up to 18bytes]

Page 27 highlights

NOTE Chapter 1 Introduction to DLPI The Data Link Layer The basic DLSAP address format is as follows: | DA/SA MAC address | SAP/Ethertype | SNAP (SAP = 0xAA) | [RIF] | where, '[ ]' indicates that the information is optional. The three possible variations of the DLSAP address format based on the protocol value are as follows: • 802.2 SAP format | DA/SA | DSAP/SSAP | [RIF, up to 18bytes] | • Ethertype format | DA/SA | TYPE | • SNAP SAP format | DA/SA | 0xAA | SNAP | [RIF, up to 18bytes] | • HP Extended protocols (IEEESAP_HP/IEEESAP_NM) | DA/SA | DSAP/SSAP | DXSAP/SXSAP | where, '[ ]' indicates that the information is optional. For IP, the RIF information will be immediately following DA/SA and following that will be DSAP/SSAP. Certain DLS providers require the capability of binding on multiple DLSAP addresses. This can be achieved through subsequent binding of DLSAP addresses. DLPI supports peer and hierarchical binding of DLSAPs. When the user requests peer addressing, the DLSAP specified in a subsequent bind may be used in lieu of the DLSAP bound in the DL_BIND_REQ. This will allow for a choice to be made between a number of DLSAPs on a stream while determining traffic based on DLSAP values. 27

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

Introduction to DLPI
The Data Link Layer
Chapter 1
27
The basic DLSAP address format is as follows:
|
DA/SA MAC address
|
SAP/Ethertype
|
SNAP (SAP = 0xAA)
|
[RIF]
|
where,
[ ]
indicates that the information is optional.
The three possible variations of the DLSAP address format based on the
protocol value are as follows:
802.2 SAP format
|
DA/SA
|
DSAP/SSAP
|
[RIF, up to 18bytes]
|
Ethertype format
|
DA/SA
|
TYPE
|
SNAP SAP format
|
DA/SA
|
0xAA
|
SNAP
|
[RIF, up to 18bytes]
|
HP Extended protocols (IEEESAP_HP/IEEESAP_NM)
|
DA/SA
|
DSAP/SSAP
|
DXSAP/SXSAP
|
where,
[ ]
indicates that the information is optional.
NOTE
For IP, the RIF information will be immediately following DA/SA and
following that will be DSAP/SSAP.
Certain DLS providers require the capability of binding on multiple
DLSAP addresses. This can be achieved through subsequent binding of
DLSAP addresses. DLPI supports peer and hierarchical binding of
DLSAPs. When the user requests peer addressing, the DLSAP specified
in a subsequent bind may be used in lieu of the DLSAP bound in the
DL_BIND_REQ. This will allow for a choice to be made between a
number of DLSAPs on a stream while determining traffic based on
DLSAP values.