| 1 |
<pre>Network Working Group D. Katz |
| 2 |
Request for Comments: 1377 cisco |
| 3 |
November 1992 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">The PPP OSI Network Layer Control Protocol (OSINLCP)</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This RFC specifies an IAB standards track protocol for the Internet |
| 11 |
community, and requests discussion and suggestions for improvements. |
| 12 |
Please refer to the current edition of the "IAB Official Protocol |
| 13 |
Standards" for the standardization state and status of this protocol. |
| 14 |
Distribution of this memo is unlimited. |
| 15 |
|
| 16 |
Abstract |
| 17 |
|
| 18 |
The Point-to-Point Protocol (PPP) [<a href="#ref-1" title=""The Point-to-Point Protocol (PPP)"">1</a>] provides a standard method of |
| 19 |
encapsulating Network Layer protocol information over point-to-point |
| 20 |
links. PPP also defines an extensible Link Control Protocol, and |
| 21 |
proposes a family of Network Control Protocols (NCPs) for |
| 22 |
establishing and configuring different network-layer protocols. |
| 23 |
|
| 24 |
This document defines the NCP for establishing and configuring OSI |
| 25 |
Network Layer Protocols. |
| 26 |
|
| 27 |
This memo is the product of the Point-to-Point Protocol Working Group |
| 28 |
of the Internet Engineering Task Force (IETF). Comments on this memo |
| 29 |
should be submitted to the [email protected] mailing list. |
| 30 |
|
| 31 |
Table of Contents |
| 32 |
|
| 33 |
<a href="#section-1">1</a>. Introduction .......................................... <a href="#page-2">2</a> |
| 34 |
<a href="#section-1.1">1.1</a> OSI Network Layer Protocols over PPP .................. <a href="#page-2">2</a> |
| 35 |
<a href="#section-2">2</a>. A PPP Network Control Protocol (NCP) for OSI .......... <a href="#page-5">5</a> |
| 36 |
<a href="#section-2.1">2.1</a> Sending OSI NPDUs ..................................... <a href="#page-6">6</a> |
| 37 |
<a href="#section-2.2">2.2</a> NPDU Alignment ........................................ <a href="#page-6">6</a> |
| 38 |
<a href="#section-2.3">2.3</a> Network Layer Addressing Information .................. <a href="#page-6">6</a> |
| 39 |
<a href="#section-3">3</a>. OSINLCP Configuration Options ......................... <a href="#page-7">7</a> |
| 40 |
<a href="#section-3.1">3.1</a> Align-NPDU ............................................ <a href="#page-7">7</a> |
| 41 |
REFERENCES ................................................... <a href="#page-9">9</a> |
| 42 |
ACKNOWLEDGEMENTS ............................................. <a href="#page-9">9</a> |
| 43 |
SECURITY CONSIDERATIONS ...................................... <a href="#page-10">10</a> |
| 44 |
CHAIR'S ADDRESS .............................................. <a href="#page-10">10</a> |
| 45 |
AUTHOR'S ADDRESS ............................................. <a href="#page-10">10</a> |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Katz [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
PPP has three main components: |
| 60 |
|
| 61 |
1. A method for encapsulating datagrams over serial links. |
| 62 |
|
| 63 |
2. A Link Control Protocol (LCP) for establishing, configuring, |
| 64 |
and testing the data-link connection. |
| 65 |
|
| 66 |
3. A family of Network Control Protocols (NCPs) for establishing |
| 67 |
and configuring different network-layer protocols. |
| 68 |
|
| 69 |
In order to establish communications over a point-to-point link, each |
| 70 |
end of the PPP link must first send LCP packets to configure and test |
| 71 |
the data link. After the link has been established and optional |
| 72 |
facilities have been negotiated as needed by the LCP, PPP must send |
| 73 |
NCP packets to choose and configure one or more network-layer |
| 74 |
protocols. Once each of the chosen network-layer protocols has been |
| 75 |
configured, datagrams from each network-layer protocol can be sent |
| 76 |
over the link. |
| 77 |
|
| 78 |
The link will remain configured for communications until explicit LCP |
| 79 |
or NCP packets close the link down, or until some external event |
| 80 |
occurs (an inactivity timer expires or network administrator |
| 81 |
intervention). |
| 82 |
|
| 83 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. OSI Network Layer Protocols over PPP</span> |
| 84 |
|
| 85 |
A number of protocols have been defined for the Network Layer of OSI, |
| 86 |
including the Connectionless Network Layer Protocol (CLNP, ISO 8473) |
| 87 |
[<a href="#ref-3" title=""Information processing systems -- Data communications -- Protocol for providing the connectionless-mode network service"">3</a>], the End System to Intermediate System routing protocol (ES-IS, |
| 88 |
ISO 9542) [<a href="#ref-4" title=""Information processing systems -- Telecommunications and information exchange between systems -- End system to Intermediate system Routeing exchange protocol for use in conjunction with the protocol for providing the connectionless- mode network service (ISO 8473)"">4</a>], the Intermediate System to Intermediate System routing |
| 89 |
protocol (IS-IS, ISO 10589) [<a href="#ref-5" title=""Information processing systems -- Telecommunications and information exchange between systems -- Intermediate system to Intermediate system Intra-Domain routeing exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)"">5</a>], and the Inter-Domain Routeing |
| 90 |
Protocol (IDRP, CD 10747) [<a href="#ref-6" title=""Protocol for Exchange of Inter-domain Routeing Information among Intermediate Systems to Support Forwarding of ISO 8473 PDUs"">6</a>]. Generally, these protocols were |
| 91 |
designed to run over non-reliable data link protocols such as PPP. |
| 92 |
|
| 93 |
Network Layer Protocol Identifier (NLPID) |
| 94 |
|
| 95 |
OSI Network Layer protocols can be discriminated according to the |
| 96 |
first octet in each Network Protocol Data Unit (NPDU, that is, |
| 97 |
packet), known as the Network Layer Protocol Identifier (NLPID), |
| 98 |
which is defined in ISO/TR 9577 [<a href="#ref-7" title=""Information technology -- Telecommunications and information exchange between systems -- Protocol identification in the network layer"">7</a>]. This allows the various |
| 99 |
protocols to be run over a common data link without any |
| 100 |
discriminator below the network layer. |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Katz [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 111 |
|
| 112 |
|
| 113 |
Inactive Network Layer Protocol |
| 114 |
|
| 115 |
ISO/TR 9577 reserves a NLPID value of zero to represent the |
| 116 |
"Inactive Network Layer Protocol", as defined in ISO 8473. The |
| 117 |
inactive network layer protocol MUST NOT be used over PPP. This |
| 118 |
assures that whichever OSI network layer protocol is used will |
| 119 |
have a non-zero NLPID value. |
| 120 |
|
| 121 |
Connection-Oriented Network Protocol |
| 122 |
|
| 123 |
The OSI Connection-Oriented Network Protocol (ISO 8208) [<a href="#ref-8" title=""Information processing systems -- Data communications -- X.25 packet level protocol for Data terminal equipment"">8</a>], |
| 124 |
effectively the Packet Layer of CCITT X.25, is intended to be run |
| 125 |
over a reliable data link, such as IEEE 802.2 type II or LAPB. |
| 126 |
Therefore, the unreliable data link service provided by PPP is not |
| 127 |
appropriate for use with ISO 8208. |
| 128 |
|
| 129 |
ConnectionLess Network Protocol (CLNP) |
| 130 |
|
| 131 |
The ConnectionLess Network Protocol offers a simple non-reliable |
| 132 |
datagram service very similar to IP, and is designed to run over a |
| 133 |
non-reliable data link service, such as provided by PPP. |
| 134 |
|
| 135 |
End-System to Intermediate-System Protocol (ES-IS) |
| 136 |
|
| 137 |
ES Hellos and IS Hellos are retransmitted on a periodic timer- |
| 138 |
driven basis (based on expiration of the "Configuration Timer"). |
| 139 |
The resulting ES and IS configuration information is invalidated |
| 140 |
on a timer driven basis, based on expiration of the "Holding |
| 141 |
Timer" for each piece of information. The value of a Holding |
| 142 |
Timer is set by the source of the information, and transmitted in |
| 143 |
the Holding Time field of the appropriate ES-IS packet. ISO 9542 |
| 144 |
recommends that the holding time field is set to approximately |
| 145 |
twice the Configuration Timer parameter, such that even if every |
| 146 |
other Hello packet is lost the configuration information will be |
| 147 |
retained (implying that the Holding Timer is actually set to |
| 148 |
slightly more than twice the Configuration Timer). |
| 149 |
|
| 150 |
Generally, the recommendation in ISO 9542 is sufficient for PPP |
| 151 |
links. For very unreliable links, it may be necessary to set the |
| 152 |
Holding Timer to be slightly more than three times the |
| 153 |
Configuration Timer to ensure that loss of configuration |
| 154 |
information is an unusual event. |
| 155 |
|
| 156 |
Redirect information is not transmitted on point-to-point links, |
| 157 |
but may be transmitted on general topology subnetworks, which in |
| 158 |
turn may make use of PPP. Redirect information is sent on a |
| 159 |
event-driven basis (based on a CLNP packet being forwarded by a |
| 160 |
router out the incoming interface), but redirect information is |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Katz [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 167 |
|
| 168 |
|
| 169 |
invalidated on a timer-driven basis. Loss of a single redirect |
| 170 |
may result in a subsequent data packet being sent to the same |
| 171 |
incorrect router, which will re-issue the redirect. This operates |
| 172 |
in the same manner as ICMP redirects for IP packets, and does not |
| 173 |
pose any problem for operation over PPP links. |
| 174 |
|
| 175 |
Intermediate-System to Intermediate-System Protocol (IS-IS) |
| 176 |
|
| 177 |
IS-IS allows for broadcast links (typically LANs), point-to-point |
| 178 |
links (such as PPP), and general topology links (such as X.25 |
| 179 |
networks) which are modelled as a collection of point-to-point |
| 180 |
links. |
| 181 |
|
| 182 |
There are four types of IS-IS packets: IS-IS Hello Packets, Link |
| 183 |
State Packets (LSPs), Complete Sequence Number Packets (CSNPs), |
| 184 |
and Partial Sequence Number Packets (PSNPs). |
| 185 |
|
| 186 |
IS-IS Hello messages are transmitted periodically on point-to- |
| 187 |
point links (based on expiration of the "ISISHello" timer). |
| 188 |
Routers expect to receive IS-IS Hello packets periodically. |
| 189 |
Specifically, the IS-IS Hello packet specifies a "Holding Time". |
| 190 |
If no subsequent IS-IS Hello is received over the corresponding |
| 191 |
link for the specified time period, then the neighboring router is |
| 192 |
assumed to have been disconnected or to be down. It is highly |
| 193 |
undesireable for links to "flap" up and down unnecessarily, which |
| 194 |
implies that the holding time needs to be large enough that a link |
| 195 |
is very unlikely to be declared down due to a failure to receive |
| 196 |
an IS-IS Hello. This implies that running IS-IS over unreliable |
| 197 |
data links requires the Holding time to be greater than "k" times |
| 198 |
the ISISHello timer, where k is chosen such that the loss of k |
| 199 |
consecutive IS-IS Hello's is rare. If the quality of the link is |
| 200 |
poor, then the Holding Time will need to be increased or the |
| 201 |
"ISISHello" time decreased. |
| 202 |
|
| 203 |
LSPs are acknowledged by the IS-IS protocol (via use of partial |
| 204 |
sequence number packets). A lost LSP will be recovered from with |
| 205 |
no problem provided that PPP links are treated the same way as |
| 206 |
other point-to-point links. On those rare occasions where a |
| 207 |
partial sequence number packet is lost, this might result in the |
| 208 |
retransmission of a link state packet over a single link, but will |
| 209 |
not impact the correct operation of the routing algorithm. |
| 210 |
|
| 211 |
CSNPs are sent upon link startup on a point-to-point link. This |
| 212 |
does not need to be changed for PPP. If a CSNP fragment is lost |
| 213 |
upon startup it is merely loss of an optimization -- LSPs that did |
| 214 |
not need to be transmitted over the link will be transmitted. If |
| 215 |
a periodic CSNP fragment is lost it merely means that detection of |
| 216 |
low probability database corruption will take longer. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Katz [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 223 |
|
| 224 |
|
| 225 |
PSNPs function as ACKs. Loss of a PSNP may result in an |
| 226 |
unnecessary retransmission of an LSP, but does not prevent correct |
| 227 |
operation of the routing protocol. |
| 228 |
|
| 229 |
Inter-Domain Routeing Protocol (IDRP) |
| 230 |
|
| 231 |
IDRP expects to run over datagram links, but requires reliable |
| 232 |
exchange of IDRP information. For this reason, IDRP contains |
| 233 |
built-in reliability mechanisms which ensure that packets will be |
| 234 |
received correctly. |
| 235 |
|
| 236 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. A PPP Network Control Protocol (NCP) for OSI</span> |
| 237 |
|
| 238 |
The OSI Network Layer Control Protocol (OSINLCP) is responsible for |
| 239 |
configuring, enabling, and disabling the OSI protocol modules on both |
| 240 |
ends of the point-to-point link. OSINLCP uses the same packet |
| 241 |
exchange machanism as the Link Control Protocol (LCP). OSINLCP |
| 242 |
packets may not be exchanged until PPP has reached the Network-Layer |
| 243 |
Protocol phase. OSINLCP packets received before this phase is |
| 244 |
reached should be silently discarded. |
| 245 |
|
| 246 |
The OSI Network Layer Control Protocol is exactly the same as the |
| 247 |
Link Control Protocol [<a href="#ref-1" title=""The Point-to-Point Protocol (PPP)"">1</a>] with the following exceptions: |
| 248 |
|
| 249 |
Frame Modifications |
| 250 |
|
| 251 |
The packet may utilize any modifications to the basic frame format |
| 252 |
which have been negotiated during the Link Establishment phase. |
| 253 |
|
| 254 |
Data Link Layer Protocol Field |
| 255 |
|
| 256 |
Exactly one OSINLCP packet is encapsulated in the Information |
| 257 |
field of a PPP Data Link Layer frame where the Protocol field |
| 258 |
indicates type hex 8023 (OSI Network Layer Control Protocol). |
| 259 |
|
| 260 |
Code field |
| 261 |
|
| 262 |
Only Codes 1 through 7 (Configure-Request, Configure-Ack, |
| 263 |
Configure-Nak, Configure-Reject, Terminate-Request, Terminate-Ack |
| 264 |
and Code-Reject) are used. Other Codes should be treated as |
| 265 |
unrecognized and should result in Code-Rejects. |
| 266 |
|
| 267 |
Timeouts |
| 268 |
|
| 269 |
OSINLCP packets may not be exchanged until PPP has reached the |
| 270 |
Network-Layer Protocol phase. An implementation should be |
| 271 |
prepared to wait for Authentication and Link Quality Determination |
| 272 |
to finish before timing out waiting for a Configure-Ack or other |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Katz [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 279 |
|
| 280 |
|
| 281 |
response. It is suggested that an implementation give up only |
| 282 |
after user intervention or a configurable amount of time. |
| 283 |
|
| 284 |
Configuration Option Types |
| 285 |
|
| 286 |
OSINLCP has one Configuration Option, which is defined below. |
| 287 |
|
| 288 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Sending OSI NPDUs</span> |
| 289 |
|
| 290 |
Before any Network Protocol Data Units (NPDUs) may be communicated, |
| 291 |
PPP must reach the Network-Layer Protocol phase, and the OSI Network |
| 292 |
Layer Control Protocol must reach the Opened state. |
| 293 |
|
| 294 |
Exactly one OSI NPDU is encapsulated in the Information field of a |
| 295 |
PPP Data Link Layer frame where the Protocol field indicates type hex |
| 296 |
0023 (OSI Network Layer). |
| 297 |
|
| 298 |
The maximum length of an OSI NPDU transmitted over a PPP link is the |
| 299 |
same as the maximum length of the Information field of a PPP data |
| 300 |
link layer frame. Larger NPDUs must be segmented as necessary. If a |
| 301 |
system wishes to avoid segmentation and reassembly, it should use |
| 302 |
transport layer mechanisms to discourage others from sending large |
| 303 |
PDUs. |
| 304 |
|
| 305 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. NPDU Alignment</span> |
| 306 |
|
| 307 |
OSI protocols have peculiar alignment problems due to the fact that |
| 308 |
they are often encapsulated in data link protocols with odd-length |
| 309 |
headers, while PPP defaults to even-length headers. A router |
| 310 |
switching an OSI packet may find that the beginning of the packet |
| 311 |
falls on an inconvenient memory boundary when the hardware used to |
| 312 |
transmit the packet to its next hop requires a particular alignment. |
| 313 |
This situation can be addressed by the use of leading zero padding. |
| 314 |
|
| 315 |
When sending, an implementation MAY insert one to three octets of |
| 316 |
zero between the PPP header and the OSI NPDU. These zero octets |
| 317 |
correspondingly reduce the maximum length of the NPDU that may be |
| 318 |
transmitted. |
| 319 |
|
| 320 |
On reception, any such leading zero octets (if present) MUST be |
| 321 |
removed. Regardless of whether leading zero padding is used, an |
| 322 |
implementation MUST also be able to receive a PPP packet with any |
| 323 |
arbitrary alignment of the NPDU. |
| 324 |
|
| 325 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Network Layer Addressing Information</span> |
| 326 |
|
| 327 |
OSINLCP does not define a separate configuration option for the |
| 328 |
exchange of OSI Network Layer address information. Instead, the ES- |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Katz [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 335 |
|
| 336 |
|
| 337 |
IS protocol, ISO 9542, should be used. This protocol provides a |
| 338 |
mechanism for determining the Network Layer address(es) of the |
| 339 |
neighbor on the link, as well as determining if the neighbor is an |
| 340 |
End System or an Intermediate System. |
| 341 |
|
| 342 |
A draft addendum to ES-IS [<a href="#ref-9" title=""Addendum to ISO 9542 (PDAM 1 - Dynamic Discovery of OSI NSAP Addresses by End Systems)"">9</a>] is being defined in ISO to add support |
| 343 |
for dynamic address assignment. This addendum has currently passed |
| 344 |
the formal "Committee Draft" (CD) letter ballot. |
| 345 |
|
| 346 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. OSINLCP Configuration Options</span> |
| 347 |
|
| 348 |
OSINLCP Configuration Options allow negotiatiation of desirable |
| 349 |
Internet Protocol parameters. OSINLCP uses the same Configuration |
| 350 |
Option format defined for LCP [<a href="#ref-1" title=""The Point-to-Point Protocol (PPP)"">1</a>], with a separate set of Options. |
| 351 |
|
| 352 |
The most up-to-date values of the OSINLCP Option Type field are |
| 353 |
specified in the most recent "Assigned Numbers" RFC [<a href="#ref-2" title=""Assigned Numbers"">2</a>]. Current |
| 354 |
values are assigned as follows: |
| 355 |
|
| 356 |
1 Align-NPDU |
| 357 |
|
| 358 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Align-NPDU</span> |
| 359 |
|
| 360 |
Description |
| 361 |
|
| 362 |
This Configuration Option provides a way for the receiver to |
| 363 |
negotiate a particular alignment of the OSI NPDU. Empirical |
| 364 |
evidence suggests that the greatest time deficit for re-alignment |
| 365 |
exists at the receiver. |
| 366 |
|
| 367 |
The alignment is accomplished through combination of PPP header |
| 368 |
compression with leading zero padding (see above). It is |
| 369 |
recommended that alignment be entirely through header compression |
| 370 |
combinations whenever possible. For example, an alignment of 3 |
| 371 |
could be achieved by combining uncompressed PPP Address and |
| 372 |
Control fields (2 octets) with a compressed PPP Protocol field (1 |
| 373 |
octet). |
| 374 |
|
| 375 |
This option is negotiated separately in each direction. A |
| 376 |
receiver which does not need alignment MUST NOT request the |
| 377 |
option. A sender which desires alignment prior to sending SHOULD |
| 378 |
Configure-Nak with an appropriate value. |
| 379 |
|
| 380 |
Implementation Note: In a complex environment, there might be |
| 381 |
several conflicting needs for alignment. It is recommended |
| 382 |
that the receiver request alignment based on the needs of the |
| 383 |
highest speed next hop link. Also, greater efficiency might be |
| 384 |
obtained by negotiating upstream the values requested by |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Katz [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 391 |
|
| 392 |
|
| 393 |
downstream PPP links, since those packets will not need a |
| 394 |
change in alignment on transit. |
| 395 |
|
| 396 |
The alignment request is advisory, and failure to agree on an |
| 397 |
alignment MUST NOT prevent the OSINLCP from reaching the Opened |
| 398 |
state. By default, the alignment is done according to the needs |
| 399 |
of the sender, and all receivers MUST be capable of accepting |
| 400 |
packets with any alignment. |
| 401 |
|
| 402 |
Vernacular: If you don't like this option, you can refuse to |
| 403 |
negotiate it, and you can send whatever alignment you want. |
| 404 |
However, if you accept the peer's alignment option, then you |
| 405 |
MUST transmit packets with the agreed alignment. |
| 406 |
|
| 407 |
A summary of the Align-NPDU Configuration Option format is shown |
| 408 |
below. The fields are transmitted from left to right. |
| 409 |
|
| 410 |
0 1 2 |
| 411 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 |
| 412 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 413 |
| Type | Length | Alignment | |
| 414 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 415 |
|
| 416 |
Type |
| 417 |
|
| 418 |
1 |
| 419 |
|
| 420 |
Length |
| 421 |
|
| 422 |
3 |
| 423 |
|
| 424 |
Alignment |
| 425 |
|
| 426 |
This field specifies the offset of the beginning of the OSI NPDU |
| 427 |
relative to the beginning of the PPP packet header (not including |
| 428 |
any leading Flag Sequences). |
| 429 |
|
| 430 |
A value of 1 through 4 requires an offset of that specific length, |
| 431 |
modulo 4. For example, a value of 1 would require no padding when |
| 432 |
the PPP Address, Control, and Protocol fields are compressed. One |
| 433 |
octet of leading zero padding would be necessary when the PPP |
| 434 |
header is full sized. |
| 435 |
|
| 436 |
A value of 255 requests an offset of an odd length (1 or 3). A |
| 437 |
value of 254 requests an offset of an even length (2 or 4). If |
| 438 |
the sender is not capable of dynamically varying the amount of |
| 439 |
padding, it MUST NAK with one of the two specific values. |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Katz [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 447 |
|
| 448 |
|
| 449 |
References |
| 450 |
|
| 451 |
[<a id="ref-1">1</a>] Simpson, W., "The Point-to-Point Protocol (PPP)", <a href="./rfc1331">RFC 1331</a>, |
| 452 |
Daydreamer, May 1992. |
| 453 |
|
| 454 |
[<a id="ref-2">2</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1340">RFC 1340</a>, |
| 455 |
USC/Information Sciences Institute, July 1992. |
| 456 |
|
| 457 |
[<a id="ref-3">3</a>] ISO, "Information processing systems -- Data communications -- |
| 458 |
Protocol for providing the connectionless-mode network |
| 459 |
service", ISO 8473, 1988. |
| 460 |
|
| 461 |
[<a id="ref-4">4</a>] ISO, "Information processing systems -- Telecommunications and |
| 462 |
information exchange between systems -- End system to |
| 463 |
Intermediate system Routeing exchange protocol for use in |
| 464 |
conjunction with the protocol for providing the connectionless- |
| 465 |
mode network service (ISO 8473)", ISO 9542, 1988. |
| 466 |
|
| 467 |
[<a id="ref-5">5</a>] ISO, "Information processing systems -- Telecommunications and |
| 468 |
information exchange between systems -- Intermediate system to |
| 469 |
Intermediate system Intra-Domain routeing exchange protocol for |
| 470 |
use in conjunction with the protocol for providing the |
| 471 |
connectionless-mode network service (ISO 8473)", ISO 10589, |
| 472 |
1990. |
| 473 |
|
| 474 |
[<a id="ref-6">6</a>] ISO, "Protocol for Exchange of Inter-domain Routeing |
| 475 |
Information among Intermediate Systems to Support Forwarding of |
| 476 |
ISO 8473 PDUs", ISO CD 10747, 1991. |
| 477 |
|
| 478 |
[<a id="ref-7">7</a>] ISO, "Information technology -- Telecommunications and |
| 479 |
information exchange between systems -- Protocol identification |
| 480 |
in the network layer", ISO/IEC TR9577:1990. |
| 481 |
|
| 482 |
[<a id="ref-8">8</a>] ISO, "Information processing systems -- Data communications -- |
| 483 |
X.25 packet level protocol for Data terminal equipment", ISO |
| 484 |
8208, 1984. |
| 485 |
|
| 486 |
[<a id="ref-9">9</a>] Taylor, E., "Addendum to ISO 9542 (PDAM 1 - Dynamic Discovery |
| 487 |
of OSI NSAP Addresses by End Systems)", SC6/N7248. |
| 488 |
|
| 489 |
Acknowledgments |
| 490 |
|
| 491 |
Some of the text in this document is taken from previous documents |
| 492 |
produced by the Point-to-Point Protocol Working Group of the Internet |
| 493 |
Engineering Task Force (IETF). |
| 494 |
|
| 495 |
Special thanks to Ross Callon (DEC), and Cyndi Jung (3Com), for |
| 496 |
contributions of text and design suggestions based on implementation |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Katz [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1377">RFC 1377</a> PPP OSINLCP November 1992</span> |
| 503 |
|
| 504 |
|
| 505 |
experience. |
| 506 |
|
| 507 |
Thanks also to Bill Simpson for his editing and formatting efforts, |
| 508 |
both for this document and for PPP in general. |
| 509 |
|
| 510 |
Security Considerations |
| 511 |
|
| 512 |
Security issues are not discussed in this memo. |
| 513 |
|
| 514 |
Chair's Address |
| 515 |
|
| 516 |
The working group can be contacted via the current chair: |
| 517 |
|
| 518 |
Brian Lloyd |
| 519 |
Lloyd & Associates |
| 520 |
3420 Sudbury Road |
| 521 |
Cameron Park, California 95682 |
| 522 |
|
| 523 |
Phone: (916) 676-1147 |
| 524 |
EMail: [email protected] |
| 525 |
|
| 526 |
Author's Address |
| 527 |
|
| 528 |
Questions about this memo can also be directed to: |
| 529 |
|
| 530 |
Dave Katz |
| 531 |
cisco Systems, Inc. |
| 532 |
1525 O'Brien Dr. |
| 533 |
Menlo Park, CA 94025 |
| 534 |
|
| 535 |
Phone: (415) 688-8284 |
| 536 |
EMail: [email protected] |
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
Katz [Page 10] |
| 557 |
</pre> |