| 1 |
<pre>Network Working Group IETF-OSI Working Group |
| 2 |
Request for Comments: 1139 R. Hagens |
| 3 |
January 1990 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">An Echo Function for ISO 8473</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo defines an echo function for the connection-less network |
| 11 |
layer protocol. This memo is not intended to compete with an ISO |
| 12 |
standard. This is a Proposed Elective Standard for the Internet. |
| 13 |
Distribution of this memo is unlimited. |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
This memo defines an echo function for the connection-less network |
| 18 |
layer protocol. Two mechanisms are introduced that may be used to |
| 19 |
implement the echo function. The first mechanism is recommended as |
| 20 |
an interim solution for the Internet community. The second mechanism |
| 21 |
will be progressed to the ANSI X3S3.3 working group for consideration |
| 22 |
as a work item. |
| 23 |
|
| 24 |
When an ISO standard is adopted that provides functionality similar |
| 25 |
to that described by this memo, then this memo will become obsolete |
| 26 |
and superceded by the ISO standard. |
| 27 |
|
| 28 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 29 |
|
| 30 |
The OSI Connection-less network layer protocol (ISO 8473) defines a |
| 31 |
means for transmitting and relaying data and error report PDUs |
| 32 |
through an OSI internet. Unfortunately, the world that these packets |
| 33 |
travel through is imperfect. Gateways and links may fail. This memo |
| 34 |
defines an echo function to be used in the debugging and testing of |
| 35 |
the OSI network layer. |
| 36 |
|
| 37 |
Network management protocols can be used to determine the state of a |
| 38 |
gateway or link. However, since these protocols themselves utilize a |
| 39 |
protocol that may experience packet loss, it cannot be guaranteed |
| 40 |
that the network management applications can be utilized. A simple |
| 41 |
mechanism in the network layer is required so that systems can be |
| 42 |
probed to determine if the lowest levels of the networking software |
| 43 |
are operating correctly. This mechanism is not intended to compete |
| 44 |
with or replace network management; rather it should be viewed as an |
| 45 |
addition to the facilities offered by network management. |
| 46 |
|
| 47 |
There are three important issues to consider when defining an echo |
| 48 |
extension to ISO 8473: complexity, code-path divergence, and backward |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">IETF-OSI Working Group [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1139">RFC 1139</a> An Echo Function for ISO 8473 January 1990</span> |
| 55 |
|
| 56 |
|
| 57 |
compatibility. The complexity of the echo facility must be kept low. |
| 58 |
If it is not, then there is a good chance that the facility will not |
| 59 |
be universally provided. The code-path consideration requires that |
| 60 |
the echo path through a system is identical (or very close) to the |
| 61 |
path used by normal data. An echo path must succeed and fail in |
| 62 |
unison with the normal data path or else it will not provide a useful |
| 63 |
diagnostic tool. |
| 64 |
|
| 65 |
Backward compatibility is an important consideration whenever a |
| 66 |
change is made to a protocol. For this reason, this memo defines two |
| 67 |
implementation mechanisms: the short term approach and the long term |
| 68 |
approach. The short term approach will produce echo packets that are |
| 69 |
indistinguishable from normal data ISO 8473 PDUs. These echo packets |
| 70 |
may be switched through ISO 8473 routers that do not implement the |
| 71 |
echo function. The short term approach will be adopted as an |
| 72 |
Elective Internet Standard because it is backward compatible with ISO |
| 73 |
8473. However, due to its nature, the short term approach will never |
| 74 |
be incorporated into future versions of ISO 8473. |
| 75 |
|
| 76 |
The long term approach will produce echo packets that are not |
| 77 |
compatible with the existing standard. However, the long term |
| 78 |
approach may be acceptable by ISO as an addendum to ISO 8473. In |
| 79 |
this event, backward compatibility will no longer be an issue. At |
| 80 |
that juncture, the short term approach defined by this memo will be |
| 81 |
obsolete and superseded by the ISO addendum. |
| 82 |
|
| 83 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Generic Echo Function</span> |
| 84 |
|
| 85 |
The following section will describe the echo function in a generic |
| 86 |
fashion. This memo defines an echo-request entity. The function of |
| 87 |
the echo-request entity is to accept an incoming echo-request PDU, |
| 88 |
perform some processing, and generate an echo-reply PDU. Depending |
| 89 |
on the echo implementation, the echo-request entity may be thought of |
| 90 |
as an entity that exists above the network layer, or as an entity |
| 91 |
that co-exists with the network layer. Subsequent sections will |
| 92 |
detail the short and long term implementation mechanisms. |
| 93 |
|
| 94 |
For the purposes of this memo, the term "ping" shall be used to mean |
| 95 |
the act of transmitting an echo-request PDU to a remote system (with |
| 96 |
the expectation that an echo-reply PDU will be sent back to the |
| 97 |
transmitter). |
| 98 |
|
| 99 |
2.1 The Echo Request |
| 100 |
|
| 101 |
When a system decides to ping a remote system, an echo-request is |
| 102 |
built. All fields of the PDU header are assigned normal values |
| 103 |
(see implementation specific sections for more information). The |
| 104 |
address of the system to be pinged is inserted as the destination |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">IETF-OSI Working Group [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1139">RFC 1139</a> An Echo Function for ISO 8473 January 1990</span> |
| 111 |
|
| 112 |
|
| 113 |
NSAP address. The rules of segmentation defined for a DT PDU also |
| 114 |
apply to the echo-request PDU. |
| 115 |
|
| 116 |
The echo-request is switched through the network toward its |
| 117 |
destination. Upon reaching the destination system, the PDU is |
| 118 |
processed according to normal processing rules. At the end of the |
| 119 |
input processing, the echo-request PDU is delivered to the echo- |
| 120 |
request entity. |
| 121 |
|
| 122 |
The echo-request entity will build and dispatch the echo-reply |
| 123 |
PDU. This is a new PDU. Except as noted below, this second PDU |
| 124 |
is built using the normal construction procedures. The |
| 125 |
destination address of the echo-reply PDU is taken from the source |
| 126 |
address of the echo-request PDU. Most options present in the |
| 127 |
echo-request PDU are copied into the echo-reply PDU (see |
| 128 |
implementation notes for more information). |
| 129 |
|
| 130 |
2.2 The Echo Reply |
| 131 |
|
| 132 |
The entire echo-request PDU is included in the data portion of the |
| 133 |
echo-reply PDU. This includes the echo-request PDU header as well |
| 134 |
as the any data that accompanies the echo-request PDU. The entire |
| 135 |
echo-request PDU is included in the echo-reply so that fields such |
| 136 |
as the echo-request lifetime may be examined when the reply is |
| 137 |
received. After the echo-reply PDU is built, it is transmitted |
| 138 |
toward the new destination (the original source of the echo- |
| 139 |
request). The rules of segmentation defined for a DT PDU also |
| 140 |
apply to the echo-reply PDU. |
| 141 |
|
| 142 |
The echo-reply PDU is relayed through the network toward its |
| 143 |
destination. Upon reaching its destination, it is processed by |
| 144 |
the PDU input function and delivered to the entity that created |
| 145 |
the echo-request. |
| 146 |
|
| 147 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Short Term Implementation Mechanism</span> |
| 148 |
|
| 149 |
The short term implementation mechanism will use an ISO 8473 normal |
| 150 |
data PDU as the echo-request and echo-reply PDU. A special NSAP |
| 151 |
selector value will be used to identify the echo-request and insure |
| 152 |
that it reaches the echo-request entity. This selector value is |
| 153 |
known as the echo-request selector. In addition, an echo-reply |
| 154 |
selector is defined so that the echo-reply PDU may be identified at |
| 155 |
the destination system. It is important to note that (except for the |
| 156 |
NSAP selector) the echo-request PDU and the echo-reply PDU are |
| 157 |
indistinguishable from a DT PDU. |
| 158 |
|
| 159 |
This approach has the advantage that it is simple and does not allow |
| 160 |
any code-path divergence. In addition, this approach requires that |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">IETF-OSI Working Group [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1139">RFC 1139</a> An Echo Function for ISO 8473 January 1990</span> |
| 167 |
|
| 168 |
|
| 169 |
only the systems which wish to generate an echo-reply PDU must |
| 170 |
change. Systems that do not adhere to this memo will not generate an |
| 171 |
echo-reply PDU, but will still switch other echo-request and echo- |
| 172 |
reply PDUs. |
| 173 |
|
| 174 |
3.1 The Echo Request |
| 175 |
|
| 176 |
An echo-request is built using the normal DT PDU construction |
| 177 |
procedures. All fields of the PDU header are assigned normal |
| 178 |
values (see implementation notes). The address of the system to |
| 179 |
be pinged is inserted as the destination NSAP address. The |
| 180 |
selector field of the destination NSAP address must contain the |
| 181 |
echo-request selector. The selector field of the source NSAP |
| 182 |
address must contain the echo-reply selector. |
| 183 |
|
| 184 |
3.2 The Echo Reply |
| 185 |
|
| 186 |
Except as noted below (see implementation notes), an echo-reply is |
| 187 |
built using the normal DT PDU construction procedures. The |
| 188 |
destination NSAP address is taken from the source address of the |
| 189 |
echo-request PDU. |
| 190 |
|
| 191 |
3.3 Use of NSAP Selectors |
| 192 |
|
| 193 |
The choice of echo-request and echo-reply NSAP selectors is a |
| 194 |
local matter. However, to insure interoperability, and as an |
| 195 |
interim measure until use of the directory service becomes |
| 196 |
widespread, this memo will recommend the following default values |
| 197 |
(specified in decimal): |
| 198 |
|
| 199 |
Echo Request Selector - 30 |
| 200 |
Echo Reply Selector - 31 |
| 201 |
|
| 202 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The Long Term Implementation Mechanism</span> |
| 203 |
|
| 204 |
The long term implementation mechanism will define two new 8473 PDU |
| 205 |
types: ERQ (echo-request) and ERP (echo-reply). With the exception |
| 206 |
of a new type code, these PDUs will be identical to the DT PDU in |
| 207 |
every respect. |
| 208 |
|
| 209 |
4.1 The Echo Request |
| 210 |
|
| 211 |
The type code for the ERQ PDU is decimal 30. |
| 212 |
|
| 213 |
4.2 The Echo Reply |
| 214 |
|
| 215 |
The type code for the ERP PDU is decimal 31. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">IETF-OSI Working Group [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1139">RFC 1139</a> An Echo Function for ISO 8473 January 1990</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Implementation Notes</span> |
| 226 |
|
| 227 |
The following notes are an integral part of memo. It is important |
| 228 |
that implementors take heed of these points. |
| 229 |
|
| 230 |
5.1 Discarding PDUs |
| 231 |
|
| 232 |
The rules used for discarding a DT PDU (8473, sec 6.9 - sec 6.10) |
| 233 |
are applied when an echo-request or echo-reply is discarded. |
| 234 |
|
| 235 |
5.2 Error Report Flag |
| 236 |
|
| 237 |
The error report flag may be set on the echo-request PDU, the |
| 238 |
echo-reply PDU, or both. If an echo-request is discarded, the |
| 239 |
associated ER PDU will be sent to the echo-request source address |
| 240 |
on the originating machine. If an echo-reply is discarded, the |
| 241 |
associated ER PDU will be sent to the echo-reply source address. |
| 242 |
In general, this will be the address of the echo-request entity. |
| 243 |
It should be noted that the echo-request entity and the originator |
| 244 |
of the echo-request PDU are not required to process ER PDUs. |
| 245 |
|
| 246 |
5.3 Use of the Lifetime Field |
| 247 |
|
| 248 |
The lifetime field of the echo-request and echo-reply PDU should |
| 249 |
be set to the value normally used for a DT PDU. Note: although |
| 250 |
this memo does not prohibit the generation of a PDU with a |
| 251 |
smaller-than-normal lifetime field, this memo explicitly does not |
| 252 |
attempt to define a mechanism for varying the lifetime field set |
| 253 |
in the echo-reply PDU. This memo recommends that the normal DT |
| 254 |
lifetime value should be set in the echo-request and echo-reply |
| 255 |
PDU. |
| 256 |
|
| 257 |
5.4 Transfer of Options from the echo-request |
| 258 |
PDU to the echo-reply PDU |
| 259 |
|
| 260 |
With two exceptions, all options present in the echo-request |
| 261 |
header are copied directly into the echo-reply header. The two |
| 262 |
exceptions are the record route option and the source route |
| 263 |
option. A record route option present in an echo-request PDU is |
| 264 |
copied into the echo-reply PDU, but the routes recorded in the |
| 265 |
option are "erased" by resetting the second octet of the option to |
| 266 |
3. This allows the entire record route option space to be used by |
| 267 |
the echo-reply PDU. Note: the record route present on the echo- |
| 268 |
request is not lost because the echo-request PDU is wholly |
| 269 |
contained in the data part of the echo-reply PDU. |
| 270 |
|
| 271 |
The second exception concerns the source route option. A source |
| 272 |
route option present on the echo-request PDU is not copied into |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">IETF-OSI Working Group [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1139">RFC 1139</a> An Echo Function for ISO 8473 January 1990</span> |
| 279 |
|
| 280 |
|
| 281 |
the echo-reply PDU. |
| 282 |
|
| 283 |
5.5 Use of the Priority Option |
| 284 |
|
| 285 |
If the priority option is included, it will normally be set to |
| 286 |
value 0 (default priority). This memo allows for priority values |
| 287 |
higher than 0 to be set in the echo-request or echo-reply header, |
| 288 |
but cautions against this practice. |
| 289 |
|
| 290 |
5.6 Use of the Source Route Option |
| 291 |
|
| 292 |
Use of the source route option in ISO 8473 may cause packets to |
| 293 |
loop until their lifetime expires. For this reason, this memo |
| 294 |
recommends against the use of the source route option in either an |
| 295 |
echo-request or echo-reply PDU. If the source route option is |
| 296 |
used to specify the route that the echo-request PDU takes toward |
| 297 |
its destination, this memo does not recommend the use of an |
| 298 |
automatically generated source route on the echo-reply PDU. |
| 299 |
|
| 300 |
5.7 Transmission of Multiple Echo Requests |
| 301 |
|
| 302 |
The echo function may be utilized by more than one process on any |
| 303 |
individual machine. The mechanism by which multiple echo-requests |
| 304 |
and echo-replies are correlated between multiple processes on a |
| 305 |
single machine is a local matter and not defined by this memo. |
| 306 |
|
| 307 |
Security Considerations |
| 308 |
|
| 309 |
Security issues are not addressed in this memo. |
| 310 |
|
| 311 |
Author's Address |
| 312 |
|
| 313 |
Robert A. Hagens |
| 314 |
Computer Science Department |
| 315 |
1210 West Dayton Street |
| 316 |
Madison, WI 53706 |
| 317 |
|
| 318 |
Phone: (608) 262-1204 |
| 319 |
|
| 320 |
EMail: [email protected] |
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
IETF-OSI Working Group [Page 6] |
| 333 |
</pre> |