| 1 |
<pre>Network Working Group ANSI X3S3.3 86-80 |
| 2 |
Request for Comments: 994 ISO TC97/SC6/N 3998 |
| 3 |
March 1986 |
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">I S O</span> |
| 10 |
<span class="h1">INTERNATIONAL ORGANIZATION FOR STANDARDIZATION</span> |
| 11 |
<span class="h1">ORGANISATION INTERNATIONALE DE NORMALISATION</span> |
| 12 |
|
| 13 |
______________________________________________________________________ |
| 14 |
| | |
| 15 |
| ISO/TC 97/SC 6 | |
| 16 |
| TELECOMMUNICATIONS AND INFORMATION | |
| 17 |
| EXCHANGE BETWEEN SYSTEMS | |
| 18 |
| Secretariat: USA (ANSI) | |
| 19 |
| | |
| 20 |
| | |
| 21 |
|_____________________________________________________________________| |
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
Title: Final Text of DIS 8473, Protocol for Providing the Connectionless- |
| 27 |
mode Network Service |
| 28 |
|
| 29 |
Source: DIS 8473 Editor |
| 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 |
<span class="grey">ISO 8473 [Page 1]</span></pre> |
| 56 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 57 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 58 |
|
| 59 |
|
| 60 |
Contents |
| 61 |
|
| 62 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Scope and Field of Application </span> 6 |
| 63 |
|
| 64 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> References </span> 7 |
| 65 |
|
| 66 |
|
| 67 |
SECTION ONE. GENERAL 9 |
| 68 |
|
| 69 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> Definitions </span> 9 |
| 70 |
<a href="#section-3.1">3.1</a> Reference Model Definitions . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 71 |
<a href="#section-3.2">3.2</a> Service Conventions Definitions . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 72 |
<a href="#section-3.3">3.3</a> Network Layer Architecture Definitions . . . . . . . . . . . . <a href="#page-9">9</a> |
| 73 |
<a href="#section-3.4">3.4</a> Network Layer Addressing Definitions . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 74 |
<a href="#section-3.5">3.5</a> Additional Definitions . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 75 |
|
| 76 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> Symbols and Abbreviations </span> 11 |
| 77 |
<a href="#section-4.1">4.1</a> Data Units . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 78 |
<a href="#section-4.2">4.2</a> Protocol Data Units . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 79 |
<a href="#section-4.3">4.3</a> Protocol Data Unit Fields . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 80 |
<a href="#section-4.4">4.4</a> Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 81 |
<a href="#section-4.5">4.5</a> Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 82 |
|
| 83 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> Overview of the Protocol </span> 12 |
| 84 |
<a href="#section-5.1">5.1</a> Internal Organization of the Network Layer . . . . . . . . . . <a href="#page-12">12</a> |
| 85 |
<a href="#section-5.2">5.2</a> Subsets of the Protocol . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a> |
| 86 |
<a href="#section-5.3">5.3</a> Addresses and Titles . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 87 |
<a href="#section-5.3.1">5.3.1</a> Addresses . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 88 |
<a href="#section-5.3.2">5.3.2</a> Network-entity Titles . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 89 |
<a href="#section-5.4">5.4</a> Service Provided by the Network Layer . . . . . . . . . . . . <a href="#page-14">14</a> |
| 90 |
<a href="#section-5.5">5.5</a> Underlying Service Assumed by the Protocol . . . . . . . . . . <a href="#page-14">14</a> |
| 91 |
<a href="#section-5.5.1">5.5.1</a> Subnetwork Points of Attachment . . . . . . . . . . . <a href="#page-15">15</a> |
| 92 |
<a href="#section-5.5.2">5.5.2</a> Subnetwork Quality of Service . . . . . . . . . . . . <a href="#page-15">15</a> |
| 93 |
<a href="#section-5.5.3">5.5.3</a> Subnetwork User Data . . . . . . . . . . . . . . . . <a href="#page-16">16</a> |
| 94 |
<a href="#section-5.5.4">5.5.4</a> Subnetwork Dependent Convergence Functions . . . . . . <a href="#page-16">16</a> |
| 95 |
<a href="#section-5.6">5.6</a> Service Assumed from Local Environment . . . . . . . . . . . . <a href="#page-16">16</a> |
| 96 |
|
| 97 |
|
| 98 |
SECTION TWO. SPECIFICATION OF THE PROTOCOL 18 |
| 99 |
|
| 100 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> Protocol Functions </span> 18 |
| 101 |
<a href="#section-6.1">6.1</a> PDU Composition Function . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a> |
| 102 |
<a href="#section-6.2">6.2</a> PDU Decomposition Function . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a> |
| 103 |
<a href="#section-6.3">6.3</a> Header Format Analysis Function . . . . . . . . . . . . . . . <a href="#page-19">19</a> |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
|
| 109 |
|
| 110 |
|
| 111 |
|
| 112 |
|
| 113 |
|
| 114 |
<span class="grey">ISO 8473 [Page 2]</span></pre> |
| 115 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 116 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 117 |
|
| 118 |
|
| 119 |
<a href="#section-6.4">6.4</a> PDU Lifetime Control Function . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 120 |
<a href="#section-6.5">6.5</a> Route PDU Function . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 121 |
<a href="#section-6.6">6.6</a> Forward PDU Function . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 122 |
<a href="#section-6.7">6.7</a> Segmentation Function . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 123 |
<a href="#section-6.8">6.8</a> Reassembly Function . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 124 |
<a href="#section-6.9">6.9</a> Discard PDU Function . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 125 |
<a href="#section-6.10">6.10</a> Error Reporting Function . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a> |
| 126 |
<a href="#section-6.10.1">6.10.1</a> Overview . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a> |
| 127 |
<a href="#section-6.10.2">6.10.2</a> Requirements . . . . . . . . . . . . . . . . . . . . . <a href="#page-25">25</a> |
| 128 |
<a href="#section-6.10.3">6.10.3</a> Processing of Error Reports . . . . . . . . . . . . . <a href="#page-25">25</a> |
| 129 |
<a href="#section-6.10.4">6.10.4</a> Relationship of Data PDU Options to Error Reports . . <a href="#page-26">26</a> |
| 130 |
<a href="#section-6.11">6.11</a> PDU Header Error Detection . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a> |
| 131 |
<a href="#section-6.12">6.12</a> Padding Function . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a> |
| 132 |
<a href="#section-6.13">6.13</a> Security . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a> |
| 133 |
<a href="#section-6.14">6.14</a> Source Routing Function . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a> |
| 134 |
<a href="#section-6.15">6.15</a> Record Route Function . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a> |
| 135 |
<a href="#section-6.16">6.16</a> Quality of Service Maintenance Function . . . . . . . . . . . <a href="#page-30">30</a> |
| 136 |
<a href="#section-6.17">6.17</a> Priority Function . . . . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a> |
| 137 |
<a href="#section-6.18">6.18</a> Congestion Notification Function . . . . . . . . . . . . . . . <a href="#page-31">31</a> |
| 138 |
<a href="#section-6.19">6.19</a> Classification of Functions . . . . . . . . . . . . . . . . . <a href="#page-31">31</a> |
| 139 |
|
| 140 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> Structure and Encoding of PDUs </span> 33 |
| 141 |
<a href="#section-7.1">7.1</a> Structure . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a> |
| 142 |
<a href="#section-7.2">7.2</a> Fixed Part . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a> |
| 143 |
<a href="#section-7.2.1">7.2.1</a> General . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a> |
| 144 |
<a href="#section-7.2.2">7.2.2</a> Network Layer Protocol Identifier . . . . . . . . . . <a href="#page-34">34</a> |
| 145 |
<a href="#section-7.2.3">7.2.3</a> Length Indicator . . . . . . . . . . . . . . . . . . <a href="#page-35">35</a> |
| 146 |
<a href="#section-7.2.4">7.2.4</a> Version/Protocol Identifier Extension . . . . . . . . <a href="#page-35">35</a> |
| 147 |
<a href="#section-7.2.5">7.2.5</a> PDU Lifetime . . . . . . . . . . . . . . . . . . . . <a href="#page-35">35</a> |
| 148 |
<a href="#section-7.2.6">7.2.6</a> Flags . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-35">35</a> |
| 149 |
<a href="#section-7.2.6.1">7.2.6.1</a> Segmentation Permitted . . . . . . . . . . . <a href="#page-35">35</a> |
| 150 |
<a href="#section-7.2.6.2">7.2.6.2</a> More Segments . . . . . . . . . . . . . . . <a href="#page-35">35</a> |
| 151 |
<a href="#section-7.2.6.3">7.2.6.3</a> Error Report . . . . . . . . . . . . . . . <a href="#page-36">36</a> |
| 152 |
<a href="#section-7.2.7">7.2.7</a> Type Code . . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a> |
| 153 |
<a href="#section-7.2.8">7.2.8</a> PDU Segment Length . . . . . . . . . . . . . . . . . <a href="#page-36">36</a> |
| 154 |
<a href="#section-7.2.9">7.2.9</a> PDU Checksum . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a> |
| 155 |
<a href="#section-7.3">7.3</a> Address Part . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a> |
| 156 |
<a href="#section-7.3.1">7.3.1</a> General . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a> |
| 157 |
<a href="#section-7.3.1.1">7.3.1.1</a> Destination and Source Addresses . . . . . . <a href="#page-37">37</a> |
| 158 |
<a href="#section-7.4">7.4</a> Segmentation Part . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a> |
| 159 |
<a href="#section-7.4.1">7.4.1</a> Data Unit Identifier . . . . . . . . . . . . . . . . . <a href="#page-38">38</a> |
| 160 |
<a href="#section-7.4.2">7.4.2</a> Segment Offset . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a> |
| 161 |
<a href="#section-7.4.3">7.4.3</a> PDU Total Length . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a> |
| 162 |
<a href="#section-7.5">7.5</a> Options Part . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a> |
| 163 |
<a href="#section-7.5.1">7.5.1</a> General . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a> |
| 164 |
<a href="#section-7.5.2">7.5.2</a> Padding . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a> |
| 165 |
<a href="#section-7.5.3">7.5.3</a> Security . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a> |
| 166 |
<a href="#section-7.5.3.1">7.5.3.1</a> Source Address Specific . . . . . . . . . . <a href="#page-41">41</a> |
| 167 |
<a href="#section-7.5.3.2">7.5.3.2</a> Destination Address Specific . . . . . . . . <a href="#page-41">41</a> |
| 168 |
<a href="#section-7.5.3.3">7.5.3.3</a> Globally Unique Security . . . . . . . . . . <a href="#page-41">41</a> |
| 169 |
<a href="#section-7.5.4">7.5.4</a> Source Routing . . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a> |
| 170 |
|
| 171 |
|
| 172 |
|
| 173 |
<span class="grey">ISO 8473 [Page 3]</span></pre> |
| 174 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 175 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 176 |
|
| 177 |
|
| 178 |
<a href="#section-7.5.5">7.5.5</a> Recording of Route . . . . . . . . . . . . . . . . . . <a href="#page-42">42</a> |
| 179 |
<a href="#section-7.5.6">7.5.6</a> Quality of Service Maintenance . . . . . . . . . . . . <a href="#page-43">43</a> |
| 180 |
<a href="#section-7.5.6.1">7.5.6.1</a> Source Address Specific . . . . . . . . . . <a href="#page-43">43</a> |
| 181 |
<a href="#section-7.5.6.2">7.5.6.2</a> Destination Address Specific . . . . . . . . <a href="#page-43">43</a> |
| 182 |
<a href="#section-7.5.6.3">7.5.6.3</a> Globally Unique QoS . . . . . . . . . . . . <a href="#page-43">43</a> |
| 183 |
<a href="#section-7.5.7">7.5.7</a> Priority . . . . . . . . . . . . . . . . . . . . . . <a href="#page-44">44</a> |
| 184 |
<a href="#section-7.6">7.6</a> Data Part . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-45">45</a> |
| 185 |
<a href="#section-7.7">7.7</a> Data (DT) PDU . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a> |
| 186 |
<a href="#section-7.7.1">7.7.1</a> Structure . . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a> |
| 187 |
<a href="#section-7.7.1.1">7.7.1.1</a> Fixed Part . . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 188 |
<a href="#section-7.7.1.2">7.7.1.2</a> Addresses . . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 189 |
<a href="#section-7.7.1.3">7.7.1.3</a> Segmentation . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 190 |
<a href="#section-7.7.1.4">7.7.1.4</a> Options . . . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 191 |
<a href="#section-7.7.1.5">7.7.1.5</a> Data . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 192 |
<a href="#section-7.8">7.8</a> Inactive Network Layer Protocol . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 193 |
<a href="#section-7.8.1">7.8.1</a> Network Layer Protocol Id . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 194 |
<a href="#section-7.8.2">7.8.2</a> Data Field . . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 195 |
<a href="#section-7.9">7.9</a> Error Report PDU (ER) . . . . . . . . . . . . . . . . . . . . <a href="#page-48">48</a> |
| 196 |
<a href="#section-7.9.1">7.9.1</a> Structure . . . . . . . . . . . . . . . . . . . . . . <a href="#page-48">48</a> |
| 197 |
<a href="#section-7.9.1.1">7.9.1.1</a> Fixed Part . . . . . . . . . . . . . . . . . <a href="#page-49">49</a> |
| 198 |
<a href="#section-7.9.1.2">7.9.1.2</a> Addresses . . . . . . . . . . . . . . . . . <a href="#page-49">49</a> |
| 199 |
<a href="#section-7.9.1.3">7.9.1.3</a> Options . . . . . . . . . . . . . . . . . . <a href="#page-49">49</a> |
| 200 |
<a href="#section-7.9.1.4">7.9.1.4</a> Reason for Discard . . . . . . . . . . . . . <a href="#page-50">50</a> |
| 201 |
<a href="#section-7.9.1.5">7.9.1.5</a> Error Report Data Field . . . . . . . . . . <a href="#page-51">51</a> |
| 202 |
|
| 203 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a> Conformance </span> 51 |
| 204 |
<a href="#section-8.1">8.1</a> Provision of Functions for Conformance . . . . . . . . . . . . <a href="#page-51">51</a> |
| 205 |
|
| 206 |
|
| 207 |
List of Tables |
| 208 |
|
| 209 |
<a href="#section-1">1</a> Service Primitives for Underlying Service . . . . . . . . . . . . <a href="#page-14">14</a> |
| 210 |
<a href="#section-2">2</a> Service Primitives for Underlying Service . . . . . . . . . . . . <a href="#page-14">14</a> |
| 211 |
<a href="#section-3">3</a> Timer Primitives . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 212 |
<a href="#section-4">4</a> Categorization of Protocol Functions . . . . . . . . . . . . . . . <a href="#page-32">32</a> |
| 213 |
<a href="#section-5">5</a> Valid PDU Types . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a> |
| 214 |
<a href="#section-6">6</a> Encoding of Option Parameters . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a> |
| 215 |
<a href="#section-7">7</a> Reason for Discard . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-50">50</a> |
| 216 |
<a href="#section-8">8</a> Categorization of Functions . . . . . . . . . . . . . . . . . . . <a href="#page-52">52</a> |
| 217 |
|
| 218 |
|
| 219 |
List of Figures |
| 220 |
|
| 221 |
<a href="#section-1">1</a> Interrelationship of Standards . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 222 |
<a href="#section-2">2</a> PDU Structure . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a> |
| 223 |
<a href="#section-3">3</a> PDU Header -- Fixed Part . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a> |
| 224 |
<a href="#section-4">4</a> PDU Header -- Address Part . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a> |
| 225 |
<a href="#section-5">5</a> Address Parameters . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a> |
| 226 |
<a href="#section-6">6</a> PDU Header -- Segmentation Part . . . . . . . . . . . . . . . . . <a href="#page-38">38</a> |
| 227 |
<a href="#section-7">7</a> PDU Header -- Options Part . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a> |
| 228 |
<a href="#section-8">8</a> PDU Header -- Data Field . . . . . . . . . . . . . . . . . . . . <a href="#page-45">45</a> |
| 229 |
|
| 230 |
|
| 231 |
|
| 232 |
<span class="grey">ISO 8473 [Page 4]</span></pre> |
| 233 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 234 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 235 |
|
| 236 |
|
| 237 |
<a href="#section-9">9</a> DT PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a> |
| 238 |
<a href="#section-10">10</a> Inactive Network Layer Protocol . . . . . . . . . . . . . . . . . <a href="#page-47">47</a> |
| 239 |
<a href="#section-11">11</a> Error Report PDU . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-48">48</a> |
| 240 |
|
| 241 |
|
| 242 |
|
| 243 |
|
| 244 |
|
| 245 |
|
| 246 |
|
| 247 |
|
| 248 |
|
| 249 |
|
| 250 |
|
| 251 |
|
| 252 |
|
| 253 |
|
| 254 |
|
| 255 |
|
| 256 |
|
| 257 |
|
| 258 |
|
| 259 |
|
| 260 |
|
| 261 |
|
| 262 |
|
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
|
| 277 |
|
| 278 |
|
| 279 |
|
| 280 |
|
| 281 |
|
| 282 |
|
| 283 |
|
| 284 |
|
| 285 |
|
| 286 |
|
| 287 |
|
| 288 |
|
| 289 |
|
| 290 |
|
| 291 |
<span class="grey">ISO 8473 [Page 5]</span></pre> |
| 292 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 293 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 294 |
|
| 295 |
|
| 296 |
<span class="h2"><a class="selflink" id="section-0" href="#section-0">0</a> Introduction</span> |
| 297 |
|
| 298 |
This Protocol Standard is one of a set of International Standards |
| 299 |
produced to facilitate the interconnection of open systems. The set |
| 300 |
of standards covers the services and protocols required to achieve |
| 301 |
such interconnection. |
| 302 |
|
| 303 |
This Protocol Standard is positioned with respect to other related |
| 304 |
standards by the layers defined in the Reference Model for Open Sys- |
| 305 |
tems Interconnection (ISO 7498). In particular, it is a protocol of |
| 306 |
the Network Layer. This Protocol may be used between network-entities |
| 307 |
in end systems or in Network Layer relay systems (or both). It pro- |
| 308 |
vides the Connectionless-mode Network Service as defined in Addendum |
| 309 |
1 to the Network Service Definition Covering Connectionless-mode |
| 310 |
Transmission (ISO 8348/AD1). |
| 311 |
|
| 312 |
The interrelationship of these standards is illustrated in Figure 1 |
| 313 |
below: |
| 314 |
|
| 315 |
|
| 316 |
--------------------+--- ISO NETWORK SERVICE PROVIDER -----^----------------- |
| 317 |
| | |
| 318 |
| | |
| 319 |
| | |
| 320 |
PROTOCOL | REFERENCE TO AIMS -----------------+ |
| 321 |
| |
| 322 |
SPECIFICATION | REFERENCE TO ASSUMPTIONS -----------+ |
| 323 |
| | |
| 324 |
| | |
| 325 |
| | |
| 326 |
--------------------+---SUBNETWORK SERVICE DEFINITION(S)---v----------------- |
| 327 |
|
| 328 |
Figure 1: Interrelationship of Standards |
| 329 |
|
| 330 |
|
| 331 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Scope and Field of Application</span> |
| 332 |
|
| 333 |
This International Standard specifies a protocol which is used to |
| 334 |
provide the Connectionless-mode Network Service as described in Ad- |
| 335 |
dendum 1 to the Network Service Definition Covering Connectionless- |
| 336 |
mode Transmission. The protocol relies upon the provision of an |
| 337 |
underlying connectionless-mode service by real subnetworks and/or |
| 338 |
data links. The underlying connectionless-mode service assumed by the |
| 339 |
protocol may be obtained either directly, from a connectionless-mode |
| 340 |
real subnetwork, or indirectly, through the operation of an appropri- |
| 341 |
ate Subnetwork Dependent Convergence Function (SNDCF) or Protocol |
| 342 |
(SNDCP) over a connection-mode real subnetwork as described in ISO |
| 343 |
8648, Internal Organization of the Network Layer. |
| 344 |
|
| 345 |
|
| 346 |
|
| 347 |
|
| 348 |
|
| 349 |
|
| 350 |
<span class="grey">ISO 8473 [Page 6]</span></pre> |
| 351 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 352 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 353 |
|
| 354 |
|
| 355 |
This Standard specifies: |
| 356 |
|
| 357 |
a) procedures for the connectionless transmission of data and |
| 358 |
control information from one network-entity to a peer |
| 359 |
network-entity; |
| 360 |
|
| 361 |
b) the encoding of the protocol data units (PDUs) used for the |
| 362 |
transmission of data and control information, comprising a |
| 363 |
variable-length protocol header format; |
| 364 |
|
| 365 |
c) procedures for the correct interpretation of protocol control |
| 366 |
information; and |
| 367 |
|
| 368 |
d) the functional requirements for implementations claiming |
| 369 |
conformance to the Standard. |
| 370 |
|
| 371 |
The procedures are defined in terms of: |
| 372 |
|
| 373 |
a) the interactions among peer network-entities through the |
| 374 |
exchange of protocol data units; |
| 375 |
|
| 376 |
b) the interactions between a network-entity and a Network Service |
| 377 |
user through the exchange of Network Service primitives; and |
| 378 |
|
| 379 |
c) the interactions between a network-entity and an underlying |
| 380 |
service provider through the exchange of service primitives. |
| 381 |
|
| 382 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> References</span> |
| 383 |
|
| 384 |
ISO 7498, Information Processing Systems --- Open Systems Intercon- |
| 385 |
nection --- Basic Reference Model |
| 386 |
|
| 387 |
DIS 7498/AD1, Information Processing Systems --- Open Systems In- |
| 388 |
terconnection --- Addendum to ISO 7498 Covering Connectionless-mode |
| 389 |
Transmission |
| 390 |
|
| 391 |
ISO 8348, Information Processing Systems --- Telecommunications and |
| 392 |
Information Exchange between Systems --- Network Service Definition |
| 393 |
|
| 394 |
ISO 8348/AD1, Information Processing Systems --- Telecommunications |
| 395 |
and Information Exchange between Systems --- Addendum to the Net- |
| 396 |
work Service Definition Covering Connectionless-mode Transmission |
| 397 |
|
| 398 |
ISO 8348/AD2, Information Processing Systems --- Telecommunications |
| 399 |
and Information Exchange between Systems --- Addendum to the Net- |
| 400 |
work Service Definition Covering Network Layer Addressing* |
| 401 |
|
| 402 |
DIS 8648, Information Processing Systems --- Telecommunications and |
| 403 |
Information Exchange between Systems --- Internal Organization of the |
| 404 |
Network Layer |
| 405 |
|
| 406 |
|
| 407 |
|
| 408 |
|
| 409 |
<span class="grey">ISO 8473 [Page 7]</span></pre> |
| 410 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 411 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 412 |
|
| 413 |
|
| 414 |
ISO 8509, Technical Report --- OSI Service Conventions |
| 415 |
|
| 416 |
ISO 9074, A Formal Description Technique based on an Extended State |
| 417 |
Transition Model |
| 418 |
________________________________ |
| 419 |
*At present, at the stage of Draft; publication anticipated in |
| 420 |
due course. |
| 421 |
|
| 422 |
|
| 423 |
|
| 424 |
|
| 425 |
|
| 426 |
|
| 427 |
|
| 428 |
|
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
|
| 445 |
|
| 446 |
|
| 447 |
|
| 448 |
|
| 449 |
|
| 450 |
|
| 451 |
|
| 452 |
|
| 453 |
|
| 454 |
|
| 455 |
|
| 456 |
|
| 457 |
|
| 458 |
|
| 459 |
|
| 460 |
|
| 461 |
|
| 462 |
|
| 463 |
|
| 464 |
|
| 465 |
|
| 466 |
|
| 467 |
|
| 468 |
<span class="grey">ISO 8473 [Page 8]</span></pre> |
| 469 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 470 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 471 |
|
| 472 |
|
| 473 |
SECTION ONE. GENERAL |
| 474 |
|
| 475 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> Definitions</span> |
| 476 |
|
| 477 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Reference Model Definitions</span> |
| 478 |
|
| 479 |
This document makes use of the following concepts defined in ISO 7498: |
| 480 |
|
| 481 |
(a) End system |
| 482 |
|
| 483 |
(b) Network entity |
| 484 |
|
| 485 |
(c) Network layer |
| 486 |
|
| 487 |
(d) Network protocol |
| 488 |
|
| 489 |
(e) Network protocol data unit |
| 490 |
|
| 491 |
(f) Network relay |
| 492 |
|
| 493 |
(g) Network service |
| 494 |
|
| 495 |
(h) Network service access point |
| 496 |
|
| 497 |
(i) Network service access point address |
| 498 |
|
| 499 |
(j) Routing |
| 500 |
|
| 501 |
(k) Service |
| 502 |
|
| 503 |
(l) Service data unit |
| 504 |
|
| 505 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Service Conventions Definitions</span> |
| 506 |
|
| 507 |
This Protocol Standard makes use of the following terms from the OSI |
| 508 |
Service Conventions Technical Report (ISO TR 8509): |
| 509 |
|
| 510 |
(a) Service provider |
| 511 |
|
| 512 |
(b) Service user |
| 513 |
|
| 514 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Network Layer Architecture Definitions</span> |
| 515 |
|
| 516 |
This Protocol Standard makes use of the following terms from the |
| 517 |
Internal Organization of the Network Layer (ISO 8648): |
| 518 |
|
| 519 |
(a) Intermediate system |
| 520 |
|
| 521 |
(b) Relay system |
| 522 |
|
| 523 |
(c) Subnetwork |
| 524 |
|
| 525 |
|
| 526 |
|
| 527 |
<span class="grey">ISO 8473 [Page 9]</span></pre> |
| 528 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 529 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 530 |
|
| 531 |
|
| 532 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Network Layer Addressing Definitions</span> |
| 533 |
|
| 534 |
This Protocol Standard makes use of the following terms from ISO 8348/AD2, |
| 535 |
Addendum to the Network Service Definition Covering Network Layer |
| 536 |
addressing: |
| 537 |
|
| 538 |
(a) Network addressing domain |
| 539 |
|
| 540 |
(b) Network protocol address information |
| 541 |
|
| 542 |
(c) Subnetwork point of attachment |
| 543 |
|
| 544 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> Additional Definitions</span> |
| 545 |
|
| 546 |
For the purposes of this Protocol Standard, the following definitions |
| 547 |
apply: |
| 548 |
|
| 549 |
(a) derived PDU --- a protocol data unit whose fields are identical |
| 550 |
to those of an initial PDU, except that it carries only a segment |
| 551 |
of the user data from an N-UNITDATA request. |
| 552 |
|
| 553 |
(b) initial PDU --- a protocol data unit carrying the whole of the |
| 554 |
userq data from an N-UNITDATA request. |
| 555 |
|
| 556 |
(c) local matter --- a decision made by a system concerning its |
| 557 |
behavior in the Network Layer that is not prescribed or |
| 558 |
constrained by this Protocol Standard. |
| 559 |
|
| 560 |
(d) network-entity title --- an identifier for a network-entity |
| 561 |
which has the same abstract syntax as an NSAP address, and which |
| 562 |
can be used to unambiguously identify a network-entity in an end |
| 563 |
or intermediate system. |
| 564 |
|
| 565 |
(e) reassembly --- the act of regenerating an initial PDU from two |
| 566 |
or more derived PDUs. |
| 567 |
|
| 568 |
(f) segment --- a distinct unit of data consisting of part or all |
| 569 |
of the user data provided in the N-UNITDATA request and delivered |
| 570 |
in the N-UNITDATA indication. |
| 571 |
|
| 572 |
(g) segmentation --- the act of generating two or more derived PDUs |
| 573 |
from an initial or derived PDU. The derived PDUs together carry |
| 574 |
the entire user data of the initial or derived PDU from which they |
| 575 |
were generated. |
| 576 |
|
| 577 |
Note: |
| 578 |
It is possible that such an initial PDU will never actually be |
| 579 |
generated for a particular N-UNITDATA request, owing to the |
| 580 |
immediate application of segmentation. |
| 581 |
|
| 582 |
|
| 583 |
|
| 584 |
|
| 585 |
|
| 586 |
<span class="grey">ISO 8473 [Page 10]</span></pre> |
| 587 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 588 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 589 |
|
| 590 |
|
| 591 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> Symbols and Abbreviations</span> |
| 592 |
|
| 593 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Data Units</span> |
| 594 |
|
| 595 |
NSDU Network Service Data Unit |
| 596 |
PDU Protocol Data Unit |
| 597 |
SNSDU Subnetwork Service Data Unit |
| 598 |
|
| 599 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Protocol Data Units</span> |
| 600 |
<span class="h3"> DT PDU Data Protocol Data Unit</span> |
| 601 |
ER PDU Error Report Protocol Data Unit |
| 602 |
|
| 603 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Protocol Data Unit Fields</span> |
| 604 |
|
| 605 |
CS Checksum |
| 606 |
DA Destination Address |
| 607 |
DAL Destination Address Length |
| 608 |
DUID Data Unit Identifier |
| 609 |
E/R Error Report Flag |
| 610 |
LI Length Indicator |
| 611 |
LT Lifetime |
| 612 |
MS More Segments Flag |
| 613 |
NLPID Network Layer Protocol Identifier |
| 614 |
SA Source Address |
| 615 |
SAL Source Address Length |
| 616 |
SL Segment Length |
| 617 |
SO Segment Offset |
| 618 |
SP Segmentation Permitted Flag |
| 619 |
TL Total Lengt |
| 620 |
TP Type |
| 621 |
V/P Version/Protocol Identifier Extension |
| 622 |
|
| 623 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> Parameters</span> |
| 624 |
|
| 625 |
DA Destination Address |
| 626 |
QOS Quality of Service |
| 627 |
SA Source Address |
| 628 |
|
| 629 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a> Miscellaneous</span> |
| 630 |
|
| 631 |
CLNP Connectionless-mode Network Protocol |
| 632 |
NS Network Service |
| 633 |
NPAI Network Protocol Address Information |
| 634 |
NSAP Network Service Access Point |
| 635 |
SDU Service Data Uni |
| 636 |
SN Subnetwork |
| 637 |
SNDCF Subnetwork Dependent Convergence Function |
| 638 |
SNDCP Subnetwork Dependent Convergence Protocol |
| 639 |
SNICP Subnetwork Independent Convergence Protocol |
| 640 |
SNPA Subnetwork Point of Attachment |
| 641 |
|
| 642 |
|
| 643 |
|
| 644 |
|
| 645 |
<span class="grey">ISO 8473 [Page 11]</span></pre> |
| 646 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 647 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 648 |
|
| 649 |
|
| 650 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> Overview of the Protocol</span> |
| 651 |
|
| 652 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Internal Organization of the Network Layer</span> |
| 653 |
|
| 654 |
The architectural organization of the Network Layer is described in a |
| 655 |
separate document, Internal Organization of the Network Layer (ISO |
| 656 |
8648). ISO 8648 identifies and categorizes the way in which functions |
| 657 |
can be performed within the Network Layer by Network Layer protocols, |
| 658 |
thus providing a uniform framework for describing how protocols |
| 659 |
operating either individually or cooperatively in the Network Layer |
| 660 |
can be used to provide the OSI Network Service. This protocol is |
| 661 |
designed to be used in the context of the internetworking protocol |
| 662 |
approach to the provision of the Connectionless-mode Network Service |
| 663 |
defined in that Standard. |
| 664 |
|
| 665 |
This protocol is intended for use in the Subnetwork Independent Con- |
| 666 |
vergence Protocol (SNICP) role. A protocol which fulfills the SNICP |
| 667 |
role operates to construct the OSI Network Service over a defined set |
| 668 |
of underlying services, performing functions which are necessary to |
| 669 |
support the uniform appearance of the OSI Connectionless-mode Network |
| 670 |
Service over a homogeneous or heterogeneous set of interconnected |
| 671 |
subnetworks. This protocol is defined to accommodate variability |
| 672 |
where Subnetwork Dependent Convergence Protocols and/or Subnetwork |
| 673 |
Access Protocols do not provide all of the functions necessary to |
| 674 |
support the Connectionless-mode Network Service over all or part of |
| 675 |
the path from one NSAP to another. |
| 676 |
|
| 677 |
As described in ISO 8648, a protocol at the Network Layer may fulfill |
| 678 |
different roles in different configurations. Although this protocol |
| 679 |
is designed particularly to be suitable for a SNICP role in the con- |
| 680 |
text of the internetworking protocol approach to the provision of the |
| 681 |
Connectionless-mode Network Service, it may also be used to fulfill |
| 682 |
other roles and may therefore be used in the context of other ap- |
| 683 |
proaches to subnetwork interconnection. |
| 684 |
|
| 685 |
The specification of this protocol begins with a definition of the |
| 686 |
underlying service which it assumes. This service is made available |
| 687 |
by the operation of other Network Layer protocols or through provi- |
| 688 |
sion of the Data Link Service. The underlying service assumed by this |
| 689 |
protocol is described in Clause 5.5. |
| 690 |
|
| 691 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> Subsets of the Protocol</span> |
| 692 |
|
| 693 |
Two proper subsets of the full protocol are defined which permit the |
| 694 |
use of known subnetwork characteristics and are therefore not subnet- |
| 695 |
work independent. |
| 696 |
|
| 697 |
The Inactive Network Layer protocol subset is a null-function subset |
| 698 |
which can be used when it is known that the source and destination |
| 699 |
end-systems are connected by a single subnetwork, and when none of |
| 700 |
the functions performed by the full protocol is required to provide |
| 701 |
|
| 702 |
|
| 703 |
|
| 704 |
<span class="grey">ISO 8473 [Page 12]</span></pre> |
| 705 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 706 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 707 |
|
| 708 |
|
| 709 |
the Connectionless-mode Network Service between any pair of end- |
| 710 |
systems. |
| 711 |
|
| 712 |
The Non-segmenting protocol subset permits simplification of the |
| 713 |
header where it is known that the source and destination end-systems |
| 714 |
are connected by subnetworks whose service data unit sizes are |
| 715 |
greater than or equal to a known bound which is large enough so that |
| 716 |
segmentation is not required. This subset is selected by setting the |
| 717 |
Segmentation Permitted flag to zero. |
| 718 |
|
| 719 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a> Addresses and Titles</span> |
| 720 |
|
| 721 |
The following Clauses describe the addresses and titles used by this |
| 722 |
Protocol. |
| 723 |
|
| 724 |
<span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a> Addresses</span> |
| 725 |
|
| 726 |
The Source Address and Destination Address parameters referred to in |
| 727 |
Clause 7.3 of this International Standard are OSI Network Service Ac- |
| 728 |
cess Point Addresses. The syntax and semantics of an OSI Network |
| 729 |
Service Access Point Address are described in a separate document, |
| 730 |
ISO 8348/AD2, Addendum to the Network Service Definition Covering |
| 731 |
Network Layer Addressing. |
| 732 |
|
| 733 |
The encoding used by this protocol to convey NSAP Addresses shall be |
| 734 |
the preferred binary encoding specified in ISO 8348/AD2; the entire |
| 735 |
NSAP address, taken as a whole, is represented explicitly as a string |
| 736 |
of binary octets. This string is conveyed in its entirety in the ad- |
| 737 |
dress fields described in Clause 7.3. The rules governing the genera- |
| 738 |
tion of the preferred binary encoding are described in ISO 8348/AD2. |
| 739 |
|
| 740 |
<span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a> Network-entity Titles</span> |
| 741 |
|
| 742 |
A network-entity title is an identifier for a network-entity in an |
| 743 |
endsystem or intermediate-system. Network-entity titles are allocated |
| 744 |
from the same name space as NSAP addresses, and the determination of |
| 745 |
whether an address is an NSAP address or a network-entity title |
| 746 |
depends on the context in which the address is interpreted. The en- |
| 747 |
tries in the Source Routing and Recording of Route parameters defined |
| 748 |
in Clauses 7.5.4 and 7.5.5 are network-entity titles. The Source Ad- |
| 749 |
dress and Destination Address parameters in the Error Report PDU de- |
| 750 |
fined in Clause 7.9.1.2 are also network-entity titles. |
| 751 |
|
| 752 |
The encoding used by this protocol to convey network-entity titles |
| 753 |
shall also be the preferred binary encoding; again, the entire |
| 754 |
network-entity title, taken as a whole, is represented explicitly as |
| 755 |
a string of binary octets. This string is conveyed in its entirety |
| 756 |
in the fields described in Clauses 7.5.4, 7.5.5, and 7.9.1.2. |
| 757 |
|
| 758 |
|
| 759 |
|
| 760 |
|
| 761 |
|
| 762 |
|
| 763 |
<span class="grey">ISO 8473 [Page 13]</span></pre> |
| 764 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 765 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 766 |
|
| 767 |
|
| 768 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a> Service Provided by the Network Layer</span> |
| 769 |
|
| 770 |
The service provided by this protocol is the Connectionless-mode Net- |
| 771 |
work Service described in ISO 8348/AD1, Addendum to the Network Ser- |
| 772 |
vice Definition Covering Connectionless-mode Transmission. The Net- |
| 773 |
work Service primitives provided are summarized in Table 1: |
| 774 |
|
| 775 |
_____________________________________________________________ |
| 776 |
| PRIMITIVES PARAMETERS | |
| 777 |
|____________________________________________________________ | |
| 778 |
| N_UNITDATA .Request | N_Source_Address, | |
| 779 |
| .Indication | N_Destination_Address, | |
| 780 |
| | N_Quality_of_Service, | |
| 781 |
| | N_Userdata | |
| 782 |
|_________________________________|___________________________| |
| 783 |
|
| 784 |
Table 1: Service Primitives for Underlying Service |
| 785 |
|
| 786 |
|
| 787 |
The Addendum to the Network Service Definition Covering |
| 788 |
Connectionless-mode Transmission (ISO 8348/AD1) states that the max- |
| 789 |
imum size of a connectionless-mode Network-service-data-unit (NSDU) |
| 790 |
is limited to 64512 octets. |
| 791 |
|
| 792 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a> Underlying Service Assumed by the Protocol</span> |
| 793 |
|
| 794 |
The underlying service required to support this protocol is defined |
| 795 |
by the following primitives: |
| 796 |
|
| 797 |
_____________________________________________________________ |
| 798 |
| PRIMITIVES PARAMETERS | |
| 799 |
|____________________________________________________________ | |
| 800 |
| SN_UNITDATA .Request | SN_Source_Address, | |
| 801 |
| .Indication | SN_Destination_Address, | |
| 802 |
| | SN_Quality_of_Service, | |
| 803 |
| | SN_Userdata | |
| 804 |
|_________________________________|___________________________| |
| 805 |
|
| 806 |
Table 2: Service Primitives for Underlying Service |
| 807 |
|
| 808 |
|
| 809 |
Note: |
| 810 |
These service primitives are used to describe the abstract interface |
| 811 |
which exists between the ISO 8473 protocol machine and an underlying |
| 812 |
real subnetwork or a Subnetwork Dependent Convergence Function which |
| 813 |
operates over a real subnetwork or real data link to provide the |
| 814 |
required underlying service. |
| 815 |
|
| 816 |
|
| 817 |
|
| 818 |
|
| 819 |
|
| 820 |
|
| 821 |
|
| 822 |
<span class="grey">ISO 8473 [Page 14]</span></pre> |
| 823 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 824 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 825 |
|
| 826 |
|
| 827 |
<span class="h4"><a class="selflink" id="section-5.5.1" href="#section-5.5.1">5.5.1</a> Subnetwork Points of Attachment</span> |
| 828 |
|
| 829 |
The source and destination addresses specify the points of attachment |
| 830 |
to a public or private subnetwork(s) involved in the transmission. |
| 831 |
Subnetwork Point of Attachment addresses (SNPAs) are defined by each |
| 832 |
individual subnetwork authority. |
| 833 |
|
| 834 |
The syntax and semantics of SNPAs are not defined in this Standard. |
| 835 |
|
| 836 |
<span class="h4"><a class="selflink" id="section-5.5.2" href="#section-5.5.2">5.5.2</a> Subnetwork Quality of Service</span> |
| 837 |
|
| 838 |
Subnetwork Quality of Service describes aspects of an underlying |
| 839 |
connectionless-mode service which are attributable solely to the |
| 840 |
underlying service. |
| 841 |
|
| 842 |
Associated with each connectionless-mode transmission, certain meas- |
| 843 |
ures of Quality of Service are requested when the primitive action is |
| 844 |
initiated. These requested measures (or parameter values and op- |
| 845 |
tions) are based on a priori knowledge of the service(s) made avail- |
| 846 |
able to it by the subnetwork. Knowledge of the nature and type of |
| 847 |
service available is typically obtained prior to an invocation of the |
| 848 |
underlying connectionless-mode service. |
| 849 |
|
| 850 |
The Quality of Service parameters identified for the underlying |
| 851 |
connectionless-mode service may in some circumstances be directly |
| 852 |
derivable from or mappable onto those identified in the |
| 853 |
Connectionless-mode Network Service. The following parameters as de- |
| 854 |
fined in ISO 8348/AD1, Addendum to the Network Service Definition |
| 855 |
Covering Connectionlessmode Transmission, may be employed: |
| 856 |
|
| 857 |
(a) transit delay; |
| 858 |
|
| 859 |
(b) protection against unauthorized access; |
| 860 |
|
| 861 |
(c) cost determinants; |
| 862 |
|
| 863 |
(d) priority; and |
| 864 |
|
| 865 |
(e) residual error probability. |
| 866 |
|
| 867 |
|
| 868 |
Note: |
| 869 |
For those subnetworks which do not inherently provide Quality of |
| 870 |
Service as a parameter when the primitive action is initiated, it |
| 871 |
is a local matter as to how the semantics of the service requested |
| 872 |
might be preserved. In particular, there may be instances in which |
| 873 |
the Quality of Service requested cannot be maintained. In such |
| 874 |
circumstances, an attempt shall be made to deliver the protocol |
| 875 |
data unit at whatever Quality of Service is available. |
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
<span class="grey">ISO 8473 [Page 15]</span></pre> |
| 882 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 883 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 884 |
|
| 885 |
|
| 886 |
<span class="h4"><a class="selflink" id="section-5.5.3" href="#section-5.5.3">5.5.3</a> Subnetwork User Data</span> |
| 887 |
|
| 888 |
The SN-Userdata is an ordered multiple of octets, and is transferred |
| 889 |
transparently between the specified subnetwork points of attachment. |
| 890 |
|
| 891 |
The underlying service assumed by the CLNP is required to support a |
| 892 |
service data unit size of at least 512 octets. |
| 893 |
|
| 894 |
If the minimum service data unit sizes supported by all of the sub- |
| 895 |
networks involved in the transmission of a particular PDU are known |
| 896 |
to be large enough that segmentation is not required, then the Non- |
| 897 |
segmenting protocol subset may be used. |
| 898 |
|
| 899 |
|
| 900 |
<span class="h4"><a class="selflink" id="section-5.5.4" href="#section-5.5.4">5.5.4</a> Subnetwork Dependent Convergence Functions</span> |
| 901 |
|
| 902 |
Subnetwork Dependent Convergence Functions may be performed to pro- |
| 903 |
vide an underlying connectionless-mode service in the case where a |
| 904 |
real subnetwork does not inherently provide the connectionless-mode |
| 905 |
service assumed by the protocol. If a subnetwork inherently provides |
| 906 |
a connection-mode service, a Subnetwork Dependent Convergence Func- |
| 907 |
tion provides a mapping into the required underlying service. Sub- |
| 908 |
network Dependent Convergence Functions may also be required in those |
| 909 |
cases where functions assumed from the underlying service are not |
| 910 |
performed. In some cases, this may require the operation of an ex- |
| 911 |
plicit protocol (i.e., a protocol involving explicit exchanges of |
| 912 |
protocol control information between peer network-entities) in the |
| 913 |
Subnetwork Dependent Convergence Protocol (SNDCP) role. However, |
| 914 |
there may also be cases where the functionality required to fulfill |
| 915 |
the SNDCP role consists simply of a set of rules for manipulating the |
| 916 |
underlying service. |
| 917 |
|
| 918 |
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a> Service Assumed from Local Environment</span> |
| 919 |
|
| 920 |
A timer service must be provided to allow the protocol entity to |
| 921 |
schedule events. |
| 922 |
|
| 923 |
There are three primitives associated with the S-TIMER service: |
| 924 |
|
| 925 |
1. the S--TIMER Request, |
| 926 |
2. the S--TIMER Response, and |
| 927 |
3. the S--TIMER Cancel. |
| 928 |
|
| 929 |
The S--TIMER Request primitive indicates to the local environment |
| 930 |
that it should initiate a timer of the specified name and subscript |
| 931 |
and maintain it for the duration specified by the time parameter. |
| 932 |
|
| 933 |
The S--TIMER Response primitive is initiated by the local environment |
| 934 |
to indicate that the delay requested by the corresponding S-TIMER Re- |
| 935 |
quest primitive has elapsed. |
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
<span class="grey">ISO 8473 [Page 16]</span></pre> |
| 941 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 942 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 943 |
|
| 944 |
|
| 945 |
The S--TIMER Cancel primitive is an indication to the local environ- |
| 946 |
ment that the specified timer(s) should be canceled. If the subscript |
| 947 |
parameter is not specified, then all timers with the specified name |
| 948 |
are canceled; otherwise, the timer of the given name and subscript is |
| 949 |
cancelled. If no timers correspond to the parameters specified, the |
| 950 |
local environment takes no action. |
| 951 |
|
| 952 |
The parameters of the S--TIMER service primitives are specified in |
| 953 |
Table 3. |
| 954 |
|
| 955 |
__________________________________________________ |
| 956 |
| PRIMITIVES PARAMETERS | |
| 957 |
|_________________________________________________| |
| 958 |
| S--TIMER .Request | S-Time, | |
| 959 |
| | S-Name, | |
| 960 |
| | S-Subscript | |
| 961 |
| | | |
| 962 |
| .Response | S-Name, | |
| 963 |
| | S-Subscript | |
| 964 |
|___________________________|_____________________| |
| 965 |
|
| 966 |
Table 3: Timer Primitives |
| 967 |
|
| 968 |
|
| 969 |
The time parameter indicates the time duration of the specified ti- |
| 970 |
mer. An identifiying label is associated with a timer by means of |
| 971 |
the name parameter. The subscript parameter specifies a value to dis- |
| 972 |
tinguish timers with the same name. The name and subscript taken to- |
| 973 |
gether constitute a unique reference to the timer. |
| 974 |
|
| 975 |
Timers used in association with a specific protocol funtion are de- |
| 976 |
fined under that protocol function. |
| 977 |
|
| 978 |
|
| 979 |
Note: |
| 980 |
This International Standard does not define specific values for |
| 981 |
the timers. Any derivations described in this Standard are not |
| 982 |
mandatory. Timer values should be chosen so that the requested |
| 983 |
Quality of Service can be provided, given the known characteristics |
| 984 |
of the underlying service. |
| 985 |
|
| 986 |
|
| 987 |
|
| 988 |
|
| 989 |
|
| 990 |
|
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
<span class="grey">ISO 8473 [Page 17]</span></pre> |
| 1000 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 1001 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1002 |
|
| 1003 |
|
| 1004 |
SECTION TWO. SPECIFICATION OF THE PROTOCOL |
| 1005 |
|
| 1006 |
|
| 1007 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> Protocol Functions</span> |
| 1008 |
|
| 1009 |
This Clause describes the functions performed as part of the Proto- |
| 1010 |
col. |
| 1011 |
|
| 1012 |
Not all of the functions must be performed by every implementation. |
| 1013 |
Clause 6.17 specifies which functions may be omitted, and the correct |
| 1014 |
behavior when requested functions are not implemented. |
| 1015 |
|
| 1016 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a> PDU Composition Function</span> |
| 1017 |
|
| 1018 |
This function is responsible for the construction of a protocol data |
| 1019 |
unit according to the rules governing the encoding of PDUs given in |
| 1020 |
Clause 7. Protocol Control Information required for delivering the |
| 1021 |
data unit to its destination is determined from current state and lo- |
| 1022 |
cal information and from the parameters associated with the N- |
| 1023 |
UNITDATA Request. |
| 1024 |
|
| 1025 |
Network Protocol Address Information (NPAI) for the Source Address |
| 1026 |
and Destination Address fields of the PDU header is derived from the |
| 1027 |
NS-Source-Address and NS-Destination-Address parameters. The NS- |
| 1028 |
Destination-Address and NS-Quality-of-Service parameters, together |
| 1029 |
with current state and local information, are used to determine which |
| 1030 |
optional functions are to be selected. User data passed from the Net- |
| 1031 |
work Service User (NS-Userdata) forms the Data field of the protocol |
| 1032 |
data unit. |
| 1033 |
|
| 1034 |
During the composition of the protocol data unit, a Data Unit Iden- |
| 1035 |
tifier is assigned to distinguish this request to transmit NS- |
| 1036 |
Userdata to a particular destination NS User from other such re- |
| 1037 |
quests. The originator of the PDU must choose the Data Unit Identif- |
| 1038 |
ier so that it remains unique (for this Source and Destination ad- |
| 1039 |
dress pair) for the maximum lifetime of the Initial PDU in the net- |
| 1040 |
work; this rule applies for any PDUs derived from the Initial PDU as |
| 1041 |
a result of the application of the Segmentation Function (see Clause |
| 1042 |
6.7). Derived PDUs are considered to correspond to the same Initial |
| 1043 |
PDU, and hence the same N-UNITDATA Request, if they have the same |
| 1044 |
Source Address, Destination Address, and Data Unit Identifier. |
| 1045 |
|
| 1046 |
The Data Unit Identifier is also available for ancillary functions |
| 1047 |
such as error reporting (see Clause 6.10). |
| 1048 |
|
| 1049 |
The total length of the PDU in octets is determined by the originator |
| 1050 |
and placed in the Total Length field of the PDU header. This field is |
| 1051 |
not changed in any Derived PDU for the lifetime of the protocol data |
| 1052 |
unit. |
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
<span class="grey">ISO 8473 [Page 18]</span></pre> |
| 1059 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1060 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1061 |
|
| 1062 |
|
| 1063 |
When the Non-segmenting protocol subset is employed, neither the To- |
| 1064 |
tal Length field nor the Data Unit Identifier field is present. The |
| 1065 |
rules governing the PDU composition function are modified in this |
| 1066 |
case as follows. During the composition of the protocol data unit, |
| 1067 |
the total length of the PDU in octets is determined by the originator |
| 1068 |
and placed in the Segment Length field of the PDU header. This field |
| 1069 |
is not changed for the lifetime of the PDU. No Data Unit Identifica- |
| 1070 |
tion is provided. |
| 1071 |
|
| 1072 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a> PDU Decomposition Function</span> |
| 1073 |
|
| 1074 |
This function is responsible for removing the Protocol Control Infor- |
| 1075 |
mation from the protocol data unit. During this process, information |
| 1076 |
pertinent to the generation of the N-UNITDATA Indication is deter- |
| 1077 |
mined as follows. The NS-Source-Address and NS-Destination-Address |
| 1078 |
parameters of the N-UNITDATA Indication are recovered from the NPAI |
| 1079 |
in the Source and Destination Address fields of the PDU header. The |
| 1080 |
data field of the PDU received is reserved until all segments of the |
| 1081 |
original service data unit have been received; collectively, these |
| 1082 |
form the NS-Userdata parameter of the N-UNITDATA Indication. Infor- |
| 1083 |
mation relating to the Quality of Service provided during the |
| 1084 |
transmission of the PDU is determined from the Quality of Service and |
| 1085 |
other information contained in the Options Part of the PDU header. |
| 1086 |
This information constitutes the NS-Quality-of-Service parameter of |
| 1087 |
the N-UNITDATA Indication. |
| 1088 |
|
| 1089 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a> Header Format Analysis Function</span> |
| 1090 |
|
| 1091 |
This function determines whether the full protocol described in this |
| 1092 |
Standard is employed, or one of the defined proper subsets thereof. |
| 1093 |
If the protocol data unit has a Network Layer Protocol Identifier in- |
| 1094 |
dicating that this is a standard version of the Protocol, this func- |
| 1095 |
tion determines whether a received PDU has reached its destination, |
| 1096 |
using the Destination Address provided in the PDU. If the Destination |
| 1097 |
Address provided in the PDU identifies an NSAP served by this |
| 1098 |
network-entity, then the PDU has reached its destination; if not, it |
| 1099 |
must be forwarded. |
| 1100 |
|
| 1101 |
If the protocol data unit has a Network Layer Protocol Identifier in- |
| 1102 |
dicating that the Inactive Network Layer Protocol subset is in use, |
| 1103 |
then no further analysis of the PDU header is required. The network- |
| 1104 |
entity in this case determines that either the Subnetwork Point of |
| 1105 |
Attachment address encoded as network protocol address information in |
| 1106 |
the supporting subnetwork protocol corresponds directly to an NSAP |
| 1107 |
address serviced by this network-entity or that an error has oc- |
| 1108 |
curred. If the subnetwork protocol data unit has been delivered |
| 1109 |
correctly, then the PDU may be decomposed according to the procedures |
| 1110 |
described for that particular subnetwork protocol. |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
|
| 1117 |
<span class="grey">ISO 8473 [Page 19]</span></pre> |
| 1118 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1119 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1120 |
|
| 1121 |
|
| 1122 |
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a> PDU Lifetime Control Function</span> |
| 1123 |
|
| 1124 |
This function is used to enforce the maximum PDU lifetime. It is |
| 1125 |
closely associated with the Header Format Analysis function. This |
| 1126 |
function determines whether a PDU received may be forwarded or wheth- |
| 1127 |
er its assigned lifetime has expired, in which case it must be dis- |
| 1128 |
carded. |
| 1129 |
|
| 1130 |
The operation of the PDU Lifetime Control function depends upon the |
| 1131 |
Lifetime field in the PDU header. This field contains, at any time, |
| 1132 |
the remaining lifetime of the PDU (represented in units of 500 mil- |
| 1133 |
liseconds). The Lifetime of the Initial PDU is determined by the ori- |
| 1134 |
ginating network-entity, and placed in the Lifetime field of the PDU. |
| 1135 |
When the Segmentation function is applied to a PDU, the value of the |
| 1136 |
Lifetime field of the Initial PDU is copied into all of the Derived |
| 1137 |
PDUs. |
| 1138 |
|
| 1139 |
The Lifetime of the PDU is decremented by every network-entity which |
| 1140 |
processes the PDU. When a network-entity processes a PDU, it decre- |
| 1141 |
ments the PDU Lifetime by at least one. The value of the PDU Life- |
| 1142 |
time field shall be decremented by more than one if the sum of: |
| 1143 |
|
| 1144 |
1. the transit delay in the underlying service from which the PDU |
| 1145 |
was received; and |
| 1146 |
|
| 1147 |
2. the delay within the system processing the PDU |
| 1148 |
|
| 1149 |
exceeds or is estimated to exceed 500 milliseconds. In this case, |
| 1150 |
the lifetime field should be decremented by one for each additional |
| 1151 |
500 milliseconds of delay. The determination of delay need not be |
| 1152 |
precise, but where a precise value cannot be ascertained, the value |
| 1153 |
used shall be an overestimate, not an underestimate. |
| 1154 |
|
| 1155 |
If the Lifetime field reaches a value of zero before the PDU is |
| 1156 |
delivered to the destination, the PDU must be discarded. The Error |
| 1157 |
Reporting function shall be invoked as described in Clause 6.10, Er- |
| 1158 |
ror Reporting Function, and may result in the generation of an Error |
| 1159 |
Report PDU. It is a local matter whether the destination network- |
| 1160 |
entity performs the Lifetime Control function. |
| 1161 |
|
| 1162 |
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a> Route PDU Function</span> |
| 1163 |
|
| 1164 |
This function determines the network-entity to which a protocol data |
| 1165 |
unit should be forwarded and the underlying service that must be used |
| 1166 |
to reach that network-entity, using the Destination Address and the |
| 1167 |
total length of the PDU. Where segmentation is required, the Route |
| 1168 |
PDU function further determines over which underlying service Derived |
| 1169 |
PDUs/segments must be sent in order to reach that network-entity. The |
| 1170 |
results of the Route PDU function are passed to the Forward PDU func- |
| 1171 |
tion (along with the PDU itself) for further processing. Selection |
| 1172 |
of the underlying service that must be used to reach the "next" sys- |
| 1173 |
|
| 1174 |
|
| 1175 |
|
| 1176 |
<span class="grey">ISO 8473 [Page 20]</span></pre> |
| 1177 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1178 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1179 |
|
| 1180 |
|
| 1181 |
tem in the route is initially influenced by the NS-Quality-of- Ser- |
| 1182 |
vice parameter of the N-UNITDATA Request, which specifies the QoS re- |
| 1183 |
quested by the sending NS User. Whether this QoS is to be provided |
| 1184 |
directly by the CLNP, through the selection of the Quality of Service |
| 1185 |
Maintenance parameter and other optional parameters, or through the |
| 1186 |
QoS facilities offered by each of the underlying services is deter- |
| 1187 |
mined prior to invocation of the Forward PDU function. Route selec- |
| 1188 |
tion by intermediate systems may subsequently be influenced by the |
| 1189 |
values of the Quality of Service Maintenance parameter (if present), |
| 1190 |
and other optional parameters (if present). |
| 1191 |
|
| 1192 |
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a> Forward PDU Function</span> |
| 1193 |
|
| 1194 |
This function issues an SN-UNITDATA Request primitive (see Clause |
| 1195 |
5.5), supplying the subnetwork or SNDCF identified by the Route PDU |
| 1196 |
function with the protocol data unit as user data to be transmitted, |
| 1197 |
the address information required by that subnetwork or SNDCF to iden- |
| 1198 |
tify the "next" system within the subnetwork-specific addressing |
| 1199 |
domain (this may be an intermediate-system or the destination end- |
| 1200 |
system), and Quality of Service constraints (if any) to be considered |
| 1201 |
in the processing of the user data. |
| 1202 |
|
| 1203 |
When the PDU to be forwarded is longer than the maximum service data |
| 1204 |
user size provided by the underlying service, the Segmentation func- |
| 1205 |
tion is applied (See Clause 6.7, which follows). |
| 1206 |
|
| 1207 |
<span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a> Segmentation Function</span> |
| 1208 |
|
| 1209 |
Segmentation is performed when the size of the protocol data unit is |
| 1210 |
greater than the maximum service data unit size supported by the |
| 1211 |
underlying service to be used to transmit the PDU. |
| 1212 |
|
| 1213 |
Segmentation consists of composing two or more new PDUs (Derived |
| 1214 |
PDUs) from the PDU received. The PDU received may be the Initial PDU, |
| 1215 |
or it may be a Derived PDU. All of the header information from the |
| 1216 |
PDU to be segmented, with the exception of the segment length and |
| 1217 |
checksum fields of the fixed part, and the segment offset of the seg- |
| 1218 |
mentation part, is duplicated in each Derived PDU, including all of |
| 1219 |
the address part, the data unit identifier and total length of the |
| 1220 |
segmentation part, and the options part (if present). |
| 1221 |
|
| 1222 |
Note: |
| 1223 |
The rules for forwarding and segmentation guarantee that the |
| 1224 |
header length is the same for all segments (Derived PDUs) of |
| 1225 |
the Initial PDU, and is the same as the header length of the |
| 1226 |
Initial PDU. The size of a PDU header will not change due to |
| 1227 |
operation of any protocol function. |
| 1228 |
|
| 1229 |
The user data encapsulated within the PDU received are divided such |
| 1230 |
that the Derived PDUs satisfy the size requirements of the user data |
| 1231 |
parameter field of the primitive used to access the underlying ser- |
| 1232 |
|
| 1233 |
|
| 1234 |
|
| 1235 |
<span class="grey">ISO 8473 [Page 21]</span></pre> |
| 1236 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1237 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1238 |
|
| 1239 |
|
| 1240 |
vice. |
| 1241 |
|
| 1242 |
Derived PDUs are identified as being from the same Initial PDU by |
| 1243 |
means of |
| 1244 |
|
| 1245 |
(a) the source address, |
| 1246 |
|
| 1247 |
(b) the destination address, and |
| 1248 |
|
| 1249 |
(c) the data unit identifier. |
| 1250 |
|
| 1251 |
Segmentation shall not result in the generation of a Derived PDU con- |
| 1252 |
taining less than eight (8) octets of user data. |
| 1253 |
|
| 1254 |
The following fields of the PDU header are used in conjunction with |
| 1255 |
the Segmentation function: |
| 1256 |
|
| 1257 |
(a) Segment Offset --- identifies, with respect to the start |
| 1258 |
of the Initial PDU, the octet at which the segment begins; |
| 1259 |
|
| 1260 |
(b) Segment Length --- specifies the number of octets in the |
| 1261 |
Derived PDU, including both header and data; |
| 1262 |
|
| 1263 |
(c) More Segments Flag --- is set to one if this Derived PDU |
| 1264 |
does not contain, as its final octet of user data, the final |
| 1265 |
octet of the Initial PDU; and |
| 1266 |
|
| 1267 |
(d) Total Length --- specifies the entire length of the Initial |
| 1268 |
PDU, including both header and data. |
| 1269 |
|
| 1270 |
|
| 1271 |
Derived PDUs may be further segmented without constraining the rout- |
| 1272 |
ing of the individual Derived PDUs. The Segmentation Permitted flag |
| 1273 |
is set to one to indicate that segmentation is permitted. If the Ini- |
| 1274 |
tial PDU is not to be segmented at any point during its lifetime in |
| 1275 |
the network, the flag is set to zero by the source network-entity. |
| 1276 |
The setting of the Segmentation Permitted flag cannot be changed by |
| 1277 |
any other network-entity for the lifetime of the Initial PDU and any |
| 1278 |
Derived PDUs. |
| 1279 |
|
| 1280 |
<span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a> Reassembly Function</span> |
| 1281 |
|
| 1282 |
The Reassembly function reconstructs the Initial PDU from the Derived |
| 1283 |
PDUs generated by the operation of the Segmentation Function on the |
| 1284 |
Initial PDU (and, recursively, on subsequent Derived PDUs). A bound |
| 1285 |
on the time during which segments (Derived PDUs) of an Initial PDU |
| 1286 |
will be held at a reassembly point before being discarded is provid- |
| 1287 |
ed, so that reassembly resources may be released when it is no longer |
| 1288 |
expected that any outstanding segments of the Initial PDU will arrive |
| 1289 |
at the reassembly point. Upon reception of a Derived PDU, a reassem- |
| 1290 |
bly timer is initiated with a value which indicates the amount of |
| 1291 |
|
| 1292 |
|
| 1293 |
|
| 1294 |
<span class="grey">ISO 8473 [Page 22]</span></pre> |
| 1295 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1296 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1297 |
|
| 1298 |
|
| 1299 |
time which must elapse before any outstanding segments of the Initial |
| 1300 |
PDU shall be assumed to be lost. When this timer expires, all seg- |
| 1301 |
ments (Derived PDUs) of the Initial PDU held at the reassembly point |
| 1302 |
are discarded, the resources allocated for those segments are freed, |
| 1303 |
and if selected, an Error Report is generated (see Clause 6.10). |
| 1304 |
While the exact relationship between reassembly lifetime and PDU |
| 1305 |
lifetime is a local matter, the Reassembly Function must preserve the |
| 1306 |
intent of the PDU lifetime. Consequently, the reassembly function |
| 1307 |
must discard PDUs whose lifetime would otherwise have expired had |
| 1308 |
they not been under the control of the reassembly function. |
| 1309 |
|
| 1310 |
Note: |
| 1311 |
|
| 1312 |
1. Methods of bounding reassembly lifetime are discussed in |
| 1313 |
Annex B. |
| 1314 |
|
| 1315 |
2. The Segmentation and Reassembly functions are intended to |
| 1316 |
be used in such a way that the fewest possible segments are |
| 1317 |
generated at each segmentation point and reassembly takes |
| 1318 |
place at the final destination of a PDU. However, other |
| 1319 |
schemes which |
| 1320 |
|
| 1321 |
(a) interact with the routing algorithm to favor paths on |
| 1322 |
which fewer segments are generated; |
| 1323 |
|
| 1324 |
(b) generate more segments than absolutely required in |
| 1325 |
order to avoid additional segmentation at some subsequent |
| 1326 |
point; or |
| 1327 |
|
| 1328 |
(c) allow partial or full reassembly at some intermediate |
| 1329 |
point along the route |
| 1330 |
|
| 1331 |
are not precluded. The information necessary to enable the |
| 1332 |
use of one of these alternative strategies may be made |
| 1333 |
available through the operation of a Network Layer Management |
| 1334 |
function or by other means. |
| 1335 |
|
| 1336 |
3. The originator of the Initial PDU determines the value of the |
| 1337 |
Segmentation Permitted flag in the Initial PDU and all Derived |
| 1338 |
PDUs (if any). Partial or full reassembly in an intermediate |
| 1339 |
system (Note 2 (c) above) cannot change this value in the |
| 1340 |
Initial PDU or any PDU derived from it, and cannot therefore |
| 1341 |
add or remove the segmentation part of the header. |
| 1342 |
|
| 1343 |
<span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a> Discard PDU Function</span> |
| 1344 |
|
| 1345 |
This function performs all of the actions necessary to free the |
| 1346 |
resources reserved by the network-entity when any of the following |
| 1347 |
situations is encountered (Note: the list is not exhaustive): |
| 1348 |
|
| 1349 |
(a) A violation of protocol procedure has occurred. |
| 1350 |
|
| 1351 |
|
| 1352 |
|
| 1353 |
<span class="grey">ISO 8473 [Page 23]</span></pre> |
| 1354 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1355 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1356 |
|
| 1357 |
|
| 1358 |
(b) A PDU is received whose checksum is inconsistent with its |
| 1359 |
contents. |
| 1360 |
|
| 1361 |
(c) A PDU is received, but due to local congestion, it cannot be |
| 1362 |
processed. |
| 1363 |
|
| 1364 |
(d) A PDU is received whose header cannot be analyzed. |
| 1365 |
|
| 1366 |
(e) A PDU is received which cannot be segmented and cannot be |
| 1367 |
forwarded because its length exceeds the maximum service data |
| 1368 |
unit size supported by any underlying service available for |
| 1369 |
transmission of the PDU to the next network-entity on the |
| 1370 |
chosen route. |
| 1371 |
|
| 1372 |
(f) A PDU is received whose destination address is unreachable or |
| 1373 |
unknown. |
| 1374 |
|
| 1375 |
(g) Incorrect or invalid source routing was specified. This may |
| 1376 |
include a syntax error in the source routing field, an unknown |
| 1377 |
or unreachable address in the source routing field, or a path |
| 1378 |
which is not acceptable for other reasons. |
| 1379 |
|
| 1380 |
(h) A PDU is received whose PDU lifetime has expired or whose |
| 1381 |
lifetime expires during reassembly. |
| 1382 |
|
| 1383 |
(i) A PDU is received which contains an unsupported option. |
| 1384 |
|
| 1385 |
<span class="h3"><a class="selflink" id="section-6.10" href="#section-6.10">6.10</a> Error Reporting Function</span> |
| 1386 |
|
| 1387 |
<span class="h4"><a class="selflink" id="section-6.10.1" href="#section-6.10.1">6.10.1</a> Overview</span> |
| 1388 |
|
| 1389 |
This function causes an attempt to return an Error Report PDU to the |
| 1390 |
source network-entity when a protocol data unit is discarded in ac- |
| 1391 |
cordance with Clause 6.9. |
| 1392 |
|
| 1393 |
The Error Report PDU identifies the discarded PDU, specifies the type |
| 1394 |
of error detected, and identifies the location in the header of the |
| 1395 |
discarded PDU at which the error was detected. At least the entire |
| 1396 |
header of the Discarded PDU (and, at the discretion of the originator |
| 1397 |
of the Error Report PDU none, all, or part of the data field) is |
| 1398 |
placed in the data field of the Error Report PDU. |
| 1399 |
|
| 1400 |
The originator of a Data PDU may control the generation of Error Re- |
| 1401 |
port PDUs. An Error Report flag in the original PDU is set by the |
| 1402 |
source network-entity to indicate that an Error Report PDU is to be |
| 1403 |
returned if the Initial PDU or any PDUs derived from it are discard- |
| 1404 |
ed; if the flag is not set, Error Reports are to be suppressed. |
| 1405 |
|
| 1406 |
Note: |
| 1407 |
|
| 1408 |
1. The suppression of Error Report PDUs is controlled by the |
| 1409 |
|
| 1410 |
|
| 1411 |
|
| 1412 |
<span class="grey">ISO 8473 [Page 24]</span></pre> |
| 1413 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1414 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1415 |
|
| 1416 |
|
| 1417 |
originating network-entity and not by the NS User. Care |
| 1418 |
should be exercised by the originator with regard to |
| 1419 |
suppressing ER PDUs so that error reporting is not suppressed |
| 1420 |
for every PDU generated. |
| 1421 |
|
| 1422 |
2. Non-receipt of an Error Report PDU does not imply correct |
| 1423 |
delivery of a PDU issued by a source network-entity. |
| 1424 |
|
| 1425 |
<span class="h4"><a class="selflink" id="section-6.10.2" href="#section-6.10.2">6.10.2</a> Requirements</span> |
| 1426 |
|
| 1427 |
An Error Report PDU shall not be generated to report the discard of |
| 1428 |
an Error Report PDU. |
| 1429 |
|
| 1430 |
An Error Report PDU shall not be generated to report the discard of a |
| 1431 |
Data PDU unless that PDU has the Error Report flag set to allow Error |
| 1432 |
Reports. |
| 1433 |
|
| 1434 |
If a Data PDU is discarded, and the Error Report flag has been set to |
| 1435 |
allow Error Reports, an Error Report PDU shall be generated if the |
| 1436 |
reason for discard is one of the reasons for discard enumerated in |
| 1437 |
Clause 6.9, subject to the conditions described in Clause 6.10.4. |
| 1438 |
|
| 1439 |
Note: |
| 1440 |
If a Data PDU with the E/R flag set to allow Error Reports is |
| 1441 |
discarded for any other reason, an ER PDU may be generated (as |
| 1442 |
an implementation option). |
| 1443 |
|
| 1444 |
<span class="h4"><a class="selflink" id="section-6.10.3" href="#section-6.10.3">6.10.3</a> Processing of Error Reports</span> |
| 1445 |
|
| 1446 |
An Error Report PDU is composed from information contained in the |
| 1447 |
header of the discarded Data PDU to which the Error Report refers. |
| 1448 |
The contents of the Source Address field of the discarded Data PDU |
| 1449 |
are used as the Destination Address of the Error Report PDU. This |
| 1450 |
value, which in the context of the Data PDU was used as an NSAP Ad- |
| 1451 |
dress, is used in the context of the Error Report PDU as the |
| 1452 |
network-entity title of the network-entity that originated the Data |
| 1453 |
PDU. The network- entity title of the originator of the Error Report |
| 1454 |
PDU is conveyed in the Source Address field of the header of the Er- |
| 1455 |
ror Report PDU. The value of the Lifetime field is determined in ac- |
| 1456 |
cordance with Clause 6.4. Optional parameters are selected in accor- |
| 1457 |
dance with Clause 6.10.4. |
| 1458 |
|
| 1459 |
Segmentation of Error Report PDUs is not permitted; hence, no Segmen- |
| 1460 |
tation Part is present. The total length of the ER PDU in octets is |
| 1461 |
placed in the Segment Length field of the ER PDU header. This field |
| 1462 |
is not changed during the lifetime of the ER PDU. If the originator |
| 1463 |
of the ER PDU determines that the size of the ER PDU exceeds the max- |
| 1464 |
imum service data unit size of the underlying service, the ER PDU |
| 1465 |
shall be truncated to the maximum service data unit size (see Clause |
| 1466 |
5.5.3) and forwarded with no other change. Error Report PDUs are |
| 1467 |
routed and forwarded by intermediate-system network-entities in the |
| 1468 |
|
| 1469 |
|
| 1470 |
|
| 1471 |
<span class="grey">ISO 8473 [Page 25]</span></pre> |
| 1472 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1473 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1474 |
|
| 1475 |
|
| 1476 |
same way as Data PDUs. |
| 1477 |
|
| 1478 |
Note: |
| 1479 |
The requirement that the underlying service assumed by the CLNP |
| 1480 |
must be capable of supporting a service data unit size of at least |
| 1481 |
512 octets guarantees that the entire header of the discarded Data |
| 1482 |
PDU can be conveyed in the data field of any ER PDU. |
| 1483 |
|
| 1484 |
When an ER PDU is decomposed upon reaching its destination, informa- |
| 1485 |
tion that may be used to interpret and act upon the Error Report is |
| 1486 |
obtained as follows. The network-entity title recovered from the NPAI |
| 1487 |
in the Source Address field of the ER PDU header is used to identify |
| 1488 |
the network-entity which generated the Error Report. The reason for |
| 1489 |
generating the Error Report is extracted from the Options Part of the |
| 1490 |
PDU header. The entire header of the discarded Data PDU (and part or |
| 1491 |
all of the original user data) is extracted from the data field of |
| 1492 |
the ER PDU to assist in determining the nature of the error. |
| 1493 |
|
| 1494 |
<span class="h4"><a class="selflink" id="section-6.10.4" href="#section-6.10.4">6.10.4</a> Relationship of Data PDU Options to Error Reports</span> |
| 1495 |
|
| 1496 |
The generation of an Error Report is affected by options that are |
| 1497 |
present in the corresponding Data PDU. The presence of options in the |
| 1498 |
original Data PDU that are not supported by the system which has dis- |
| 1499 |
carded that PDU may cause the suppression of an Error Report even if |
| 1500 |
the original Data PDU indicated that an Error Report should be gen- |
| 1501 |
erated in the event of a discard. |
| 1502 |
|
| 1503 |
The processing of an Error Report is also affected by options which |
| 1504 |
are present in the corresponding Data PDU. In particular, options |
| 1505 |
selected for the original Data PDU affect which options are included |
| 1506 |
in the corresponding Error Report PDU. The selection of options for |
| 1507 |
an Error Report PDU is governed by the following requirements: |
| 1508 |
|
| 1509 |
(a) If the Priority Option or the QoS Maintenance Option is selected |
| 1510 |
in the original Data PDU, and the system generating the Error |
| 1511 |
Report PDU supports the option, then the Error Report PDU shall |
| 1512 |
specify the option. |
| 1513 |
|
| 1514 |
(b) If the Security Option is selected in the Data PDU, and the system |
| 1515 |
generating the Error Report supports this option, then the Error |
| 1516 |
Report PDU shall specify the option using the value that was |
| 1517 |
specified in the original Data PDU. If the system does not support |
| 1518 |
the Security Option, an Error Report must not be generated for |
| 1519 |
a Data PDU that selects the Security Option. |
| 1520 |
|
| 1521 |
(c) If the Complete Source Route Option is selected in the original |
| 1522 |
Data PDU, and the system generating the Error Report PDU supports |
| 1523 |
this option, then the error Report shall specify the Complete Source |
| 1524 |
Route option. The Source Route parameter value is obtained by |
| 1525 |
extracting from the original Data PDU that portion of the complete |
| 1526 |
source route that has already been traversed, and reversing the |
| 1527 |
|
| 1528 |
|
| 1529 |
|
| 1530 |
<span class="grey">ISO 8473 [Page 26]</span></pre> |
| 1531 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1532 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1533 |
|
| 1534 |
|
| 1535 |
order of network-entity titles which comprise the list. |
| 1536 |
If the system does not support the Complete Source Route Option, |
| 1537 |
an Error Report must not be generated for a Data PDU that selects |
| 1538 |
the Complete Source Route option. |
| 1539 |
|
| 1540 |
(d) The Padding, Partial Source Routing, and Record Route Options, |
| 1541 |
if supported, may be specified in the Error Report PDU. |
| 1542 |
|
| 1543 |
Note: |
| 1544 |
The values of the optional parameters in (d) above may be |
| 1545 |
derived as a local matter, or they may be based upon the |
| 1546 |
corresponding values in the original Data PDU. |
| 1547 |
|
| 1548 |
<span class="h3"><a class="selflink" id="section-6.11" href="#section-6.11">6.11</a> PDU Header Error Detection</span> |
| 1549 |
|
| 1550 |
The PDU Header Error Detection function protects against failure of |
| 1551 |
intermediate or end-system network-entities due to the processing of |
| 1552 |
erroneous information in the PDU header. The function is realized by |
| 1553 |
a checksum computed on the entire PDU header. The checksum is veri- |
| 1554 |
fied at each point at which the PDU header is processed. If the |
| 1555 |
checksum calculation fails, the PDU must be discarded. If PDU header |
| 1556 |
fields are modified (for example, due to operation of the lifetime |
| 1557 |
function), then the checksum is modified so that the checksum remains |
| 1558 |
valid. |
| 1559 |
|
| 1560 |
The use of the Header Error Detection function is optional, and is |
| 1561 |
selected by the originating network-entity. If the function is not |
| 1562 |
used, the checksum field of the PDU header is set to zero. |
| 1563 |
|
| 1564 |
If the function is selected by the originating network-entity, the |
| 1565 |
value of the checksum field causes the following formulae to be sa- |
| 1566 |
tisfied: |
| 1567 |
|
| 1568 |
(The Sum from i=1 to L of a(i)) (mod 255) = 0 |
| 1569 |
|
| 1570 |
(The Sum from i=1 to L of (L - i + 1) * a(i)) (mod 255) = 0 |
| 1571 |
|
| 1572 |
|
| 1573 |
where L = the number of octets in the PDU header, and a(i) = the |
| 1574 |
value of the octet at position i. The first octet in the PDU header |
| 1575 |
is considered to occupy position i = 0. |
| 1576 |
|
| 1577 |
When the function is in use, neither octet of the checksum field may |
| 1578 |
be set to zero. |
| 1579 |
|
| 1580 |
Note: |
| 1581 |
|
| 1582 |
1. To ensure that inadvertent modification of a header while a |
| 1583 |
PDU is being processed by an intermediate system (for |
| 1584 |
example, due to a memory fault) may still be detected by the |
| 1585 |
PDU Header Error function, an intermediate system network- |
| 1586 |
|
| 1587 |
|
| 1588 |
|
| 1589 |
<span class="grey">ISO 8473 [Page 27]</span></pre> |
| 1590 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1591 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1592 |
|
| 1593 |
|
| 1594 |
entity must not recompute the checksum for the entire header, |
| 1595 |
even if fields are modified. |
| 1596 |
|
| 1597 |
2. Annex C contains descriptions of algorithms which may be |
| 1598 |
used to calculate the correct value of the checksum field |
| 1599 |
when the PDU is created, and to update the value of the |
| 1600 |
checksum field when the header is modified. |
| 1601 |
|
| 1602 |
<span class="h3"><a class="selflink" id="section-6.12" href="#section-6.12">6.12</a> Padding Function</span> |
| 1603 |
|
| 1604 |
The padding function is provided to allow space to be reserved in the |
| 1605 |
PDU header which is not used to support any other function. Octet |
| 1606 |
alignment must be maintained. |
| 1607 |
|
| 1608 |
Note: |
| 1609 |
An example of the use of this function is to cause the data field |
| 1610 |
of a PDU to begin on a convenient boundary for the originating |
| 1611 |
network-entity, such as a computer word boundary. |
| 1612 |
|
| 1613 |
<span class="h3"><a class="selflink" id="section-6.13" href="#section-6.13">6.13</a> Security</span> |
| 1614 |
|
| 1615 |
The provision of protection services (e.g., data origin authentica- |
| 1616 |
tion, data confidentiality, and data integrity of a single |
| 1617 |
connectionless-mode NSDU) is performed by the Security Function. |
| 1618 |
|
| 1619 |
The Security Function is related to the Protection from Unauthorized |
| 1620 |
Access Quality of Service parameter described in ISO 8348/AD1, Adden- |
| 1621 |
dum to the Network Service Definition Covering Connectionless-mode |
| 1622 |
Transmission. The function is realized through selection of the secu- |
| 1623 |
rity parameter in the options part of the PDU header. |
| 1624 |
|
| 1625 |
This Standard does not specify the way in which protection services |
| 1626 |
are to be provided; it only provides for the encoding of security in- |
| 1627 |
formation in the PDU header. To facilitate interoperation between |
| 1628 |
end-systems and network relay-systems by avoiding different interpre- |
| 1629 |
tations of the same encoding, a means to distinguish user-defined |
| 1630 |
security encodings from standardized security encodings is described |
| 1631 |
in Clause 7.5.3. |
| 1632 |
|
| 1633 |
|
| 1634 |
Note: |
| 1635 |
As an implementation consideration, data origin authentication |
| 1636 |
may be provided through the use of a cryptographically generated |
| 1637 |
or enciphered checksum (unique from the PDU Header Error Detection |
| 1638 |
mechanism); data confidentiality and data integrity may be |
| 1639 |
provided via route control mechanisms. |
| 1640 |
|
| 1641 |
<span class="h3"><a class="selflink" id="section-6.14" href="#section-6.14">6.14</a> Source Routing Function</span> |
| 1642 |
|
| 1643 |
The Source Routing function allows the originator to specify the path |
| 1644 |
a generated PDU must take. Source routing may only be selected by the |
| 1645 |
|
| 1646 |
|
| 1647 |
|
| 1648 |
<span class="grey">ISO 8473 [Page 28]</span></pre> |
| 1649 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1650 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1651 |
|
| 1652 |
|
| 1653 |
originator of a PDU. Source Routing is accomplished using a list of |
| 1654 |
network-entity titles held in a parameter within the options part of |
| 1655 |
the PDU header. The length of this parameter is determined by the |
| 1656 |
originating network-entity, and does not change as the PDU traverses |
| 1657 |
the network. |
| 1658 |
|
| 1659 |
The Source Route parameter includes information used by the originat- |
| 1660 |
ing end-system when determining the initial route of the PDU. Only |
| 1661 |
the titles of intermediate system network-entities are included in |
| 1662 |
the list; the network-entity title of the destination of the PDU is |
| 1663 |
not included in the list. |
| 1664 |
|
| 1665 |
Associated with the list of network-entity titles is an indicator |
| 1666 |
which identifies the next entry in the list to be used; this indica- |
| 1667 |
tor is advanced by the receiver of the PDU when the next title in the |
| 1668 |
list matches its own. The indicator is updated as the PDU is forward- |
| 1669 |
ed so as to identify the appropriate entry at each stage of relaying. |
| 1670 |
|
| 1671 |
Two forms of the Source Routing function are provided. The first |
| 1672 |
form, referred to as Complete Source Routing, requires that the |
| 1673 |
specified path must be taken; that is, only those systems identified |
| 1674 |
in the list may be visited by the PDU while en route to the destina- |
| 1675 |
tion, and each system must be visited in the order specified. If the |
| 1676 |
specified path cannot be taken, the PDU must be discarded. Clause |
| 1677 |
6.10 describes the circumstances in which an attempt shall be made to |
| 1678 |
inform the originator of the discard using the Error Reporting func- |
| 1679 |
tion. |
| 1680 |
|
| 1681 |
The second form is referred to as Partial Source Routing. Again, each |
| 1682 |
system identified in the list must be visited in the order specified |
| 1683 |
while en route to the destination. However, with this form of source |
| 1684 |
routing the PDU may take any path necessary to arrive at the next in- |
| 1685 |
termediate system in the list, which may include visiting intermedi- |
| 1686 |
ate systems that are not identified in the list. The PDU will not be |
| 1687 |
discarded (for source routing related reasons) unless one of the sys- |
| 1688 |
tems specified cannot be reached by any available route. |
| 1689 |
|
| 1690 |
<span class="h3"><a class="selflink" id="section-6.15" href="#section-6.15">6.15</a> Record Route Function</span> |
| 1691 |
|
| 1692 |
The Record Route function records the path(s) taken by a PDU as it |
| 1693 |
traverses a series of intermediate systems. A recorded route consists |
| 1694 |
of a list of network-entity titles held in a parameter within the op- |
| 1695 |
tions part of the PDU header. The length of this parameter is deter- |
| 1696 |
mined by the originating network-entity, and does not change as the |
| 1697 |
PDU traverses the network. |
| 1698 |
|
| 1699 |
The list is constructed as the PDU is forwarded along a path towards |
| 1700 |
its destination. Only the titles of intermediate system network- |
| 1701 |
entities are included in the recorded route. The network-entity title |
| 1702 |
of the originator of the PDU is not recorded in the list. |
| 1703 |
|
| 1704 |
|
| 1705 |
|
| 1706 |
|
| 1707 |
<span class="grey">ISO 8473 [Page 29]</span></pre> |
| 1708 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1709 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1710 |
|
| 1711 |
|
| 1712 |
When an intermediate system network-entity processes a PDU containing |
| 1713 |
the Record Route parameter, the system adds its own networkentity ti- |
| 1714 |
tle at the end of the list of recorded network-entity titles. An in- |
| 1715 |
dicator is maintained to identify the next available octet to be used |
| 1716 |
for recording of route. This indicator is updated as entries are ad- |
| 1717 |
ded to the list as follows. The length of the entry to be added to |
| 1718 |
the list is added to the value of the next available octet indicator, |
| 1719 |
and this sum is compared with the length of the Record Route parame- |
| 1720 |
ter. If the addition of the entry to the list would exceed the size |
| 1721 |
of the parameter, the next available octet indicator is set to indi- |
| 1722 |
cate that route recording has been terminated. The network-entity ti- |
| 1723 |
tle is not added to the list. The PDU may still be forwarded to its |
| 1724 |
final destination, without further addition of network-entity titles. |
| 1725 |
|
| 1726 |
If the addition of the entry would not exceed the size of the Record |
| 1727 |
Route parameter, the next available octet indicator is updated with |
| 1728 |
the new value, and the network-entity title is added to the head of |
| 1729 |
the list after the other entries have been moved. |
| 1730 |
|
| 1731 |
Two forms of the Record Route function are provided. The first form |
| 1732 |
is referred to as Complete Route Recording. It requires that the |
| 1733 |
list of network-entity titles be a complete and accurate record of |
| 1734 |
all intermediate systems visited by a PDU (including Derived PDUs), |
| 1735 |
except when a shortage of space in the record route option field |
| 1736 |
causes termination of recording of route, as described above. When |
| 1737 |
Complete Route Recording is selected, PDU reassembly at intermediate |
| 1738 |
systems is performed only when the Derived PDUs that are reassembled |
| 1739 |
all took the same route; otherwise, the PDU is discarded, and if |
| 1740 |
selected, an Error Report is generated (see Clause 6.10). |
| 1741 |
|
| 1742 |
The second form is referred to as Partial Route Recording. It also |
| 1743 |
requires a record of intermediate systems visited by a PDU. When Par- |
| 1744 |
tial Route Recording is selected, PDU reassembly at intermediate sys- |
| 1745 |
tems is always permitted. When reassembly is performed at an inter- |
| 1746 |
mediate system, the route recorded in any of the Derived PDUs may be |
| 1747 |
placed in the PDU resulting from the reassembly. |
| 1748 |
|
| 1749 |
Note: |
| 1750 |
The Record Route function is intended to be used in the diagnosis |
| 1751 |
of subnetwork problems and/or to provide a return path that could |
| 1752 |
be used as a source route in a subsequent PDU. |
| 1753 |
|
| 1754 |
<span class="h3"><a class="selflink" id="section-6.16" href="#section-6.16">6.16</a> Quality of Service Maintenance Function</span> |
| 1755 |
|
| 1756 |
The Quality of Service Maintenance function provides information to |
| 1757 |
network-entities in intermediate systems which may be used to make |
| 1758 |
routing decisions where such decisions affect the overall QoS provid- |
| 1759 |
ed to NS users. This information is conveyed to intermediate system |
| 1760 |
network- entities in a parameter in the options part of the PDU |
| 1761 |
header. |
| 1762 |
|
| 1763 |
|
| 1764 |
|
| 1765 |
|
| 1766 |
<span class="grey">ISO 8473 [Page 30]</span></pre> |
| 1767 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1768 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1769 |
|
| 1770 |
|
| 1771 |
In those instances where the QoS requested cannot be maintained, in- |
| 1772 |
termediate system network-entities shall attempt to deliver the PDU |
| 1773 |
at a QoS different from the QoS requested. Intermediate system |
| 1774 |
network-entities do not necessarily provide a notification of failure |
| 1775 |
to meet the requested Quality of Service. |
| 1776 |
|
| 1777 |
|
| 1778 |
<span class="h3"><a class="selflink" id="section-6.17" href="#section-6.17">6.17</a> Priority Function</span> |
| 1779 |
|
| 1780 |
The Priority function allows a PDU with a numerically higher priority |
| 1781 |
value to be processed preferentially with respect to other PDUs with |
| 1782 |
numerically lower priority values. The function is realized through |
| 1783 |
selection of a parameter in the options part of the PDU header. |
| 1784 |
|
| 1785 |
The lowest priority value is zero; a source network-entity that does |
| 1786 |
not support the Priority function must set the Priority value to |
| 1787 |
zero. The Priority function provides a means whereby the resources |
| 1788 |
of end and intermediate system network-entities, such as outgoing |
| 1789 |
transmission queues and buffers, can be used preferentially to pro- |
| 1790 |
cess higher-priority PDUs ahead of lower-priority PDUs. The specific |
| 1791 |
action taken by an individual network-entity to support the Priority |
| 1792 |
function is a local matter. |
| 1793 |
|
| 1794 |
<span class="h3"><a class="selflink" id="section-6.18" href="#section-6.18">6.18</a> Congestion Notification Function</span> |
| 1795 |
|
| 1796 |
To allow NS Users to take appropriate action when congestion is ex- |
| 1797 |
perienced within the NS provider, intermediate systems may inform the |
| 1798 |
destination network-entity of congestion through the use of a flag in |
| 1799 |
the QoS Maintenance parameter in the options part of the PDU header. |
| 1800 |
The value of this flag is initially set to zero (0) by the originator |
| 1801 |
of the PDU and may be set to one (1) by any intermediate system which |
| 1802 |
processes the PDU to indicate that it is experiencing congestion. The |
| 1803 |
criteria for determining when this action is to be taken are a local |
| 1804 |
matter. |
| 1805 |
|
| 1806 |
Note: |
| 1807 |
Congestion typically corresponds to inavailability of buffer space |
| 1808 |
to maintain output queues. An appropriate policy for indicating |
| 1809 |
congestion may be based upon the depth of the output queue selected |
| 1810 |
for a PDU (according to its destination address or other routing |
| 1811 |
information). When the depth of a particular output queue exceeds |
| 1812 |
a certain proportion of the depth of that queue, an intermediate |
| 1813 |
system will start to discard PDUs. The intermediate system will set |
| 1814 |
the Congestion Experienced flag in the next PDU to be forwarded |
| 1815 |
and may continue to do so until the condition is alleviated. |
| 1816 |
|
| 1817 |
<span class="h3"><a class="selflink" id="section-6.19" href="#section-6.19">6.19</a> Classification of Functions</span> |
| 1818 |
|
| 1819 |
Implementations are not required to support all of the functions |
| 1820 |
described in Clauses 6.1 through 6.18. Functions are divided into |
| 1821 |
three categories: |
| 1822 |
|
| 1823 |
|
| 1824 |
|
| 1825 |
<span class="grey">ISO 8473 [Page 31]</span></pre> |
| 1826 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1827 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1828 |
|
| 1829 |
|
| 1830 |
Type 1: These functions must be supported. |
| 1831 |
|
| 1832 |
Type 2: These functions may or may not be supported. |
| 1833 |
If an implementation does not support a Type 2 function, and the |
| 1834 |
function is selected in a PDU, then that PDU must be discarded, |
| 1835 |
and an Error Report PDU must be generated and forwarded to the |
| 1836 |
originating network-entity, providing that the Error Report flag is |
| 1837 |
set and the conditions of Clause 6.10.4 are satisfied. |
| 1838 |
|
| 1839 |
Type 3: These functions may or may not be supported. |
| 1840 |
If an implementation does not support a Type 3 function, and the |
| 1841 |
function is selected in a PDU, then the function is not performed, |
| 1842 |
and the PDU is processed exactly as though the function had not |
| 1843 |
been selected. The protocol data unit shall not be discarded for |
| 1844 |
this reason. |
| 1845 |
|
| 1846 |
Table 4 shows how the functions are divided into these three categories: |
| 1847 |
|
| 1848 |
_____________________________________________________________________________ |
| 1849 |
| | FULL | NON | INACTIVE | |
| 1850 |
| FUNCTION | PROTOCOL | SEGMENTING | SUBSET | |
| 1851 |
| | | SUBSET | | |
| 1852 |
|________________________________|_____________|_________________|____________| |
| 1853 |
|PDU Composition | 1 | 1 | 1 | |
| 1854 |
|PDU Composition | 1 | 1 | 1 | |
| 1855 |
|Header Format Analysis | 1 | 1 | 1 | |
| 1856 |
|PDU Lifetime Control | 1 | 1 | N/A | |
| 1857 |
|Route PDU | 1 | 1 | N/A | |
| 1858 |
|Forward PDU | 1 | 1 | N/A | |
| 1859 |
|Segment PDU | 1 | N/A | N/A | |
| 1860 |
|Reassemble PDU | 1 | N/A | N/A | |
| 1861 |
|Discard PDU | 1 | 1 | N/A | |
| 1862 |
|Error Reporting (Note 1) | 1 | 1 | N/A | |
| 1863 |
|Header Error Detection (Note 1) | 1 | 1 | N/A | |
| 1864 |
|Security | 1 | 2 | N/A | |
| 1865 |
|Complete Source Routing | 1 | 2 | N/A | |
| 1866 |
|Complete Route Recording | 2 | 2 | N/A | |
| 1867 |
|Partial Source Routing | 3 | 3 | N/A | |
| 1868 |
|Partial Route Recording | 3 | 3 | N/A | |
| 1869 |
|Priority | 3 | 3 | N/A | |
| 1870 |
|QoS Maintenance | 3 | 3 | N/A | |
| 1871 |
|Congestion Notification | 3 | 3 | N/A | |
| 1872 |
|Padding | 3 | 3 | N/A | |
| 1873 |
|________________________________|_____________|_________________|____________| |
| 1874 |
|
| 1875 |
Table 4: Categorization of Protocol Functions |
| 1876 |
|
| 1877 |
|
| 1878 |
|
| 1879 |
|
| 1880 |
|
| 1881 |
|
| 1882 |
|
| 1883 |
|
| 1884 |
<span class="grey">ISO 8473 [Page 32]</span></pre> |
| 1885 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1886 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1887 |
|
| 1888 |
|
| 1889 |
Note: |
| 1890 |
|
| 1891 |
1. While the Error Reporting and Header Error Detection functions |
| 1892 |
must be provided, they are provided only when selected |
| 1893 |
by the sending Network Service user. |
| 1894 |
|
| 1895 |
2. The rationale for the inclusion of type 3 functions is that in |
| 1896 |
the case of some functions it is more important to forward |
| 1897 |
the PDUs between intermediate systems or deliver them to |
| 1898 |
an end-system than it is to support the functions. Type 3 |
| 1899 |
functions should be used in those cases where they are of an |
| 1900 |
advisory nature; they cannot cause a PDU to be discarded |
| 1901 |
when they are not supported. |
| 1902 |
|
| 1903 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> Structure and Encoding of PDUs</span> |
| 1904 |
|
| 1905 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a> Structure</span> |
| 1906 |
|
| 1907 |
All Protocol Data Units shall contain an integral number of octets. |
| 1908 |
The octets in a PDU are numbered starting from one (1) and increasing |
| 1909 |
in the order in which they are submitted to the underlying service. |
| 1910 |
The bits in an octet are numbered from one (1) to eight (8), where |
| 1911 |
bit one (1) is the low-order (least significant) bit. |
| 1912 |
|
| 1913 |
When consecutive octets are used to represent a binary number, the |
| 1914 |
lower octet number has the most significant value. |
| 1915 |
|
| 1916 |
Any implementation supporting this protocol is required to state in |
| 1917 |
its specification the way in which octets are transferred, using the |
| 1918 |
terms "most significant bit" and "least significant bit". The PDUs of |
| 1919 |
this protocol are defined using the terms "most significant bit" and |
| 1920 |
"least significant bit". |
| 1921 |
|
| 1922 |
Note: |
| 1923 |
When the encoding of a PDU is represented using a diagram in this |
| 1924 |
Clause the following representation is used: |
| 1925 |
|
| 1926 |
a) octets are shown with the lowest numbered octet to the left, |
| 1927 |
higher number octets being further to the right; |
| 1928 |
b) within an octet, bits are shown with bit eight (8) to the left |
| 1929 |
and bit one (1) to the right. |
| 1930 |
|
| 1931 |
PDUs shall contain, in the following order: |
| 1932 |
|
| 1933 |
1. the fixed part; |
| 1934 |
2. the address part; |
| 1935 |
3. the segmentation part, if present; |
| 1936 |
4. the Options part, if present; |
| 1937 |
|
| 1938 |
and the data field, if present. This structure is illustrated in Figure 2: |
| 1939 |
|
| 1940 |
|
| 1941 |
|
| 1942 |
|
| 1943 |
<span class="grey">ISO 8473 [Page 33]</span></pre> |
| 1944 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1945 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 1946 |
|
| 1947 |
|
| 1948 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a> Fixed Part</span> |
| 1949 |
|
| 1950 |
<span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a> General</span> |
| 1951 |
|
| 1952 |
The fixed part of the PDU header contains frequently occurring param- |
| 1953 |
eters including the type code (DT or ER) of the protocol data unit. |
| 1954 |
The length and the structure of the fixed part are defined by the PDU |
| 1955 |
code. |
| 1956 |
|
| 1957 |
The fixed part has the following format: |
| 1958 |
|
| 1959 |
Part Described in |
| 1960 |
___________________________________ |
| 1961 |
| Fixed Part | <a href="#section-7.2">Section 7.2</a> |
| 1962 |
|_________________________________| |
| 1963 |
| Address Part | <a href="#section-7.3">Section 7.3</a> |
| 1964 |
|_________________________________| |
| 1965 |
| Segmentation Part | <a href="#section-7.4">Section 7.4</a> |
| 1966 |
|_________________________________| |
| 1967 |
| Options Part | <a href="#section-7.5">Section 7.5</a> |
| 1968 |
|_________________________________| |
| 1969 |
| Data | <a href="#section-7.6">Section 7.6</a> |
| 1970 |
|_________________________________| |
| 1971 |
|
| 1972 |
Figure 2: PDU Structure |
| 1973 |
|
| 1974 |
|
| 1975 |
Octet |
| 1976 |
________________________________________ |
| 1977 |
| Network Layer Protocol Identifier | 1 |
| 1978 |
|______________________________________| |
| 1979 |
| Length Indicator | 2 |
| 1980 |
|______________________________________| |
| 1981 |
| Version/Protocol Id Extension | 3 |
| 1982 |
|______________________________________| |
| 1983 |
| Lifetime | 4 |
| 1984 |
|______________________________________| |
| 1985 |
| SP vline M S vline e/R | Type | 5 |
| 1986 |
|______________________________________| |
| 1987 |
| Segment Length | 6,7 |
| 1988 |
|______________________________________| |
| 1989 |
| Checksum | 8,9 |
| 1990 |
|______________________________________| |
| 1991 |
|
| 1992 |
Figure 3: PDU Header -- Fixed Part |
| 1993 |
|
| 1994 |
<span class="h4"><a class="selflink" id="section-7.2.2" href="#section-7.2.2">7.2.2</a> Network Layer Protocol Identifier</span> |
| 1995 |
|
| 1996 |
The value of this field is set to binary 1000 0001 to identify this |
| 1997 |
Network Layer protocol as ISO 8473, Protocol for Providing the |
| 1998 |
Connectionless- mode Network Service. The value of this field is set |
| 1999 |
|
| 2000 |
|
| 2001 |
|
| 2002 |
<span class="grey">ISO 8473 [Page 34]</span></pre> |
| 2003 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 2004 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2005 |
|
| 2006 |
|
| 2007 |
to binary 0000 0000 to identify the Inactive Network Layer protocol |
| 2008 |
subset. |
| 2009 |
|
| 2010 |
<span class="h4"><a class="selflink" id="section-7.2.3" href="#section-7.2.3">7.2.3</a> Length Indicator</span> |
| 2011 |
|
| 2012 |
The length is indicated by a binary number, with a maximum value of |
| 2013 |
254 (1111 1110). The length indicated is the length in octets of the |
| 2014 |
header, as described in Clause 7.1. The value 255 (1111 1111) is |
| 2015 |
reserved for possible future extensions. |
| 2016 |
|
| 2017 |
Note: |
| 2018 |
The rules for forwarding and segmentation guarantee that the header |
| 2019 |
length is the same for all segments (Derived PDUs) of the Initial |
| 2020 |
PDU, and is the same as the header length of the Initial PDU. |
| 2021 |
The size of a PDU header will not change due to operation of any |
| 2022 |
protocol function. |
| 2023 |
|
| 2024 |
<span class="h4"><a class="selflink" id="section-7.2.4" href="#section-7.2.4">7.2.4</a> Version/Protocol Identifier Extension</span> |
| 2025 |
|
| 2026 |
The value of this field is binary 0000 0001, which identifies the |
| 2027 |
standard Version 1 of ISO 8473, Protocol for Providing the |
| 2028 |
Connectionless-mode Network Service. |
| 2029 |
|
| 2030 |
<span class="h4"><a class="selflink" id="section-7.2.5" href="#section-7.2.5">7.2.5</a> PDU Lifetime</span> |
| 2031 |
|
| 2032 |
The PDU Lifetime field is encoded as a binary number representing the |
| 2033 |
remaining lifetime of the PDU, in units of 500 milliseconds. |
| 2034 |
|
| 2035 |
<span class="h4"><a class="selflink" id="section-7.2.6" href="#section-7.2.6">7.2.6</a> Flags</span> |
| 2036 |
|
| 2037 |
<span class="h5"><a class="selflink" id="section-7.2.6.1" href="#section-7.2.6.1">7.2.6.1</a> Segmentation Permitted</span> |
| 2038 |
|
| 2039 |
The Segmentation Permitted flag indicates whether segmentation is |
| 2040 |
permitted. Its value is determined by the originator of the PDU and |
| 2041 |
cannot be changed by any other network-entity for the lifetime of the |
| 2042 |
Initial PDU and any Derived PDUs. |
| 2043 |
|
| 2044 |
A value of one (1) indicates that segmentation is permitted. A value |
| 2045 |
of zero (0) indicates that the non-segmenting protocol subset is em- |
| 2046 |
ployed. When the value of zero is selected, the segmentation part of |
| 2047 |
the PDU header is not present, and the Segment Length field serves as |
| 2048 |
the Total Length field (see Clause 7.2.8). |
| 2049 |
|
| 2050 |
<span class="h5"><a class="selflink" id="section-7.2.6.2" href="#section-7.2.6.2">7.2.6.2</a> More Segments</span> |
| 2051 |
|
| 2052 |
The More Segments flag indicates whether the data segment in this PDU |
| 2053 |
contains (as its last octet) the last octet of the User Data in the |
| 2054 |
NSDU. When the More Segments flag is set to one (1), segmentation |
| 2055 |
has taken place and the last octet of the NSDU is not contained in |
| 2056 |
this PDU. The More Segments flag cannot be set to one (1) if the Seg- |
| 2057 |
mentation Permitted flag is not set to one (1). |
| 2058 |
|
| 2059 |
|
| 2060 |
|
| 2061 |
<span class="grey">ISO 8473 [Page 35]</span></pre> |
| 2062 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 2063 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2064 |
|
| 2065 |
|
| 2066 |
When the More Segments flag is set to zero (0), the last octet of the |
| 2067 |
Data Part of the PDU is the last octet of the NSDU. |
| 2068 |
|
| 2069 |
<span class="h5"><a class="selflink" id="section-7.2.6.3" href="#section-7.2.6.3">7.2.6.3</a> Error Report</span> |
| 2070 |
|
| 2071 |
When the Error Report flag is set to one, the rules in Clause 6.10 |
| 2072 |
are used to determine whether to generate an Error Report PDU if it |
| 2073 |
is necessary to discard this Data PDU. |
| 2074 |
|
| 2075 |
When the Error Report flag is set to zero, discard of the Data PDU |
| 2076 |
will not cause the generation of an Error Report PDU. |
| 2077 |
|
| 2078 |
<span class="h4"><a class="selflink" id="section-7.2.7" href="#section-7.2.7">7.2.7</a> Type Code</span> |
| 2079 |
|
| 2080 |
The Type code field identifies the type of the protocol data unit. |
| 2081 |
Allowed values are given in Table 5: |
| 2082 |
|
| 2083 |
__________________________________________________ |
| 2084 |
| | Bits 5 4 3 2 1 | |
| 2085 |
|_________|______________________________________| |
| 2086 |
| DT PDU | 1 1 1 0 0 | |
| 2087 |
|_________|______________________________________| |
| 2088 |
| ER PDU | 0 0 0 0 1 | |
| 2089 |
|_________|______________________________________| |
| 2090 |
|
| 2091 |
Table 5: Valid PDU Types |
| 2092 |
|
| 2093 |
<span class="h4"><a class="selflink" id="section-7.2.8" href="#section-7.2.8">7.2.8</a> PDU Segment Length</span> |
| 2094 |
|
| 2095 |
The Segment Length field specifies the entire length, in octets, of |
| 2096 |
the Derived PDU, including both header and data (if present). When |
| 2097 |
the full protocol is employed and a PDU is not segmented, the value |
| 2098 |
of this field is identical to the value of the Total Length field lo- |
| 2099 |
cated in the Segmentation Part of the header. |
| 2100 |
|
| 2101 |
When the non-segmenting protocol subset is employed, no segmentation |
| 2102 |
part is present in the header. In this subset, the Segment Length |
| 2103 |
field specifies the entire length of the Initial PDU, including both |
| 2104 |
header and data (if present). The Segment Length field is not changed |
| 2105 |
for the lifetime of the PDU. |
| 2106 |
|
| 2107 |
<span class="h4"><a class="selflink" id="section-7.2.9" href="#section-7.2.9">7.2.9</a> PDU Checksum</span> |
| 2108 |
|
| 2109 |
The checksum is computed on the entire PDU header. For the Data PDU, |
| 2110 |
this includes the segmentation and options parts (if present). For |
| 2111 |
the Error Report PDU, this includes the reason for discard field as |
| 2112 |
well. |
| 2113 |
|
| 2114 |
A checksum value of zero is reserved to indicate that the checksum is |
| 2115 |
to be ignored. The operation of the PDU Header Error Detection func- |
| 2116 |
tion (Clause 6.11) ensures that the value zero does not represent a |
| 2117 |
|
| 2118 |
|
| 2119 |
|
| 2120 |
<span class="grey">ISO 8473 [Page 36]</span></pre> |
| 2121 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2122 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2123 |
|
| 2124 |
|
| 2125 |
valid checksum. A non-zero value indicates that the checksum must be |
| 2126 |
processed. If the checksum calculation fails, the PDU must be dis- |
| 2127 |
carded. |
| 2128 |
|
| 2129 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a> Address Part</span> |
| 2130 |
|
| 2131 |
<span class="h4"><a class="selflink" id="section-7.3.1" href="#section-7.3.1">7.3.1</a> General</span> |
| 2132 |
|
| 2133 |
Address parameters are distinguished by their location, immediately |
| 2134 |
following the fixed part of the PDU header. The address part is il- |
| 2135 |
lustrated Figure 4: |
| 2136 |
|
| 2137 |
|
| 2138 |
Octet |
| 2139 |
____________________________________________ |
| 2140 |
| Destination Address Length Indicator | 10 |
| 2141 |
|___________________________________________| |
| 2142 |
| | 11 |
| 2143 |
: Destination Address : |
| 2144 |
| | m - 1 |
| 2145 |
|___________________________________________| |
| 2146 |
| Source Address Length Indicator | m |
| 2147 |
|___________________________________________| |
| 2148 |
| | m + 1 |
| 2149 |
: Source Address : |
| 2150 |
| | n - 1 |
| 2151 |
|___________________________________________| |
| 2152 |
|
| 2153 |
Figure 4: PDU Header -- Address Part |
| 2154 |
|
| 2155 |
<span class="h5"><a class="selflink" id="section-7.3.1.1" href="#section-7.3.1.1">7.3.1.1</a> Destination and Source Addresses</span> |
| 2156 |
|
| 2157 |
The Destination and Source addresses used by this protocol are Net- |
| 2158 |
work Service Access Point addresses as defined in ISO 8348/AD2, Ad- |
| 2159 |
dendum to the Network Service Definition Covering Network Layer Ad- |
| 2160 |
dressing. |
| 2161 |
|
| 2162 |
The Destination and Source Addresses are variable length. The Desti- |
| 2163 |
nation and Source Address fields are encoded as Network Protocol Ad- |
| 2164 |
dress Information using the Preferred Binary Encoding defined in |
| 2165 |
Clause 8.3.1 of ISO 8348/AD2. |
| 2166 |
|
| 2167 |
The Destination Address Length Indicator field specifies the length |
| 2168 |
of the Destination Address in octets. The Destination Address field |
| 2169 |
follows the Destination Address Length Indicator field. |
| 2170 |
|
| 2171 |
The Source Address Length Indicator field specifies the length of the |
| 2172 |
Source Address in octets. The Source Address Length Indicator field |
| 2173 |
follows the Destination Address field. The Source Address field fol- |
| 2174 |
lows the Source Address Length Indicator field. |
| 2175 |
|
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
<span class="grey">ISO 8473 [Page 37]</span></pre> |
| 2180 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2181 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2182 |
|
| 2183 |
|
| 2184 |
Each address parameter is encoded as illustrated in Table 5: |
| 2185 |
|
| 2186 |
______________________________________________ |
| 2187 |
| Octet | Address parameter Length Indicator | |
| 2188 |
| n | (e.g., 'm') | |
| 2189 |
|________|____________________________________| |
| 2190 |
| Octets | | |
| 2191 |
| n + 1 | Address Parameter Value | |
| 2192 |
| thru | | |
| 2193 |
| n + m | | |
| 2194 |
|________|____________________________________| |
| 2195 |
|
| 2196 |
Figure 5: Address Parameters |
| 2197 |
|
| 2198 |
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a> Segmentation Part</span> |
| 2199 |
|
| 2200 |
If the Segmentation Permitted Flag in the Fixed Part of the PDU |
| 2201 |
Header (Octet 4, Bit 8) is set to one, the segmentation part of the |
| 2202 |
header, illustrated in Figure 6, must be present: |
| 2203 |
|
| 2204 |
If the Segmentation Permitted flag is set to zero, the non-segmenting |
| 2205 |
protocol subset is in use. |
| 2206 |
|
| 2207 |
Octet |
| 2208 |
________________________ |
| 2209 |
| Data Unit Identifier | n, n + 1 |
| 2210 |
|______________________| |
| 2211 |
| Segment Offset | n + 2, n + 3 |
| 2212 |
|______________________| |
| 2213 |
| Total Length | n + 4, n + 5 |
| 2214 |
|______________________| |
| 2215 |
|
| 2216 |
Figure 6: PDU Header -- Segmentation Part |
| 2217 |
|
| 2218 |
<span class="h4"><a class="selflink" id="section-7.4.1" href="#section-7.4.1">7.4.1</a> Data Unit Identifier</span> |
| 2219 |
|
| 2220 |
The Data Unit Identifier identifies an Initial PDU (and hence, its |
| 2221 |
Derived PDUs) so that a segmented data unit may be correctly reassem- |
| 2222 |
bled. The Data Unit Identifier size is two octets. |
| 2223 |
|
| 2224 |
<span class="h4"><a class="selflink" id="section-7.4.2" href="#section-7.4.2">7.4.2</a> Segment Offset</span> |
| 2225 |
|
| 2226 |
For each Derived PDU, the Segment Offset field specifies the relative |
| 2227 |
position of the segment contained in the data field of the Derived |
| 2228 |
PDU with respect to the start of the data field of the Initial PDU. |
| 2229 |
The offset is measured in units of octets. The offset of the first |
| 2230 |
segment (and hence, the Initial PDU) is zero; an unsegmented (Initial |
| 2231 |
PDU) has a segment offset value of zero (0). The value of this field |
| 2232 |
shall be a multiple of eight 8). |
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
|
| 2237 |
|
| 2238 |
<span class="grey">ISO 8473 [Page 38]</span></pre> |
| 2239 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2240 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2241 |
|
| 2242 |
|
| 2243 |
<span class="h4"><a class="selflink" id="section-7.4.3" href="#section-7.4.3">7.4.3</a> PDU Total Length</span> |
| 2244 |
|
| 2245 |
The Total Length field specifies the entire length of the Initial |
| 2246 |
PDU, including both the header and data. This field is not changed |
| 2247 |
for the lifetime of the Initial PDU (and hence, its Derived PDUs). |
| 2248 |
|
| 2249 |
<span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a> Options Part</span> |
| 2250 |
|
| 2251 |
<span class="h4"><a class="selflink" id="section-7.5.1" href="#section-7.5.1">7.5.1</a> General</span> |
| 2252 |
|
| 2253 |
The options part is used to convey optional parameters. The options |
| 2254 |
part of the PDU header is illustrated below: |
| 2255 |
|
| 2256 |
Octet |
| 2257 |
___________________________________________________ |
| 2258 |
| | n + 6 |
| 2259 |
: Options : |
| 2260 |
| | p |
| 2261 |
|__________________________________________________| |
| 2262 |
|
| 2263 |
Figure 7: PDU Header -- Options Part |
| 2264 |
|
| 2265 |
If the options part is present, it may contain one or more parame- |
| 2266 |
ters. The number of parameters that may be contained in the options |
| 2267 |
part is constrained by the length of the options part, which is |
| 2268 |
determined by the following formula: |
| 2269 |
|
| 2270 |
PDU Header Length -(length of fixed part+length of address |
| 2271 |
part+length of segmentation part) |
| 2272 |
|
| 2273 |
and by the length of the individual optional parameters. |
| 2274 |
|
| 2275 |
Parameters defined in the options part may appear in any order. Du- |
| 2276 |
plication of options is not permitted. Receipt of a Protocol Data |
| 2277 |
Unit with an option duplicated should be treated as a protocol error. |
| 2278 |
The rules governing the treatment of protocol errors are described in |
| 2279 |
Clause 6.10, Error Reporting Function. |
| 2280 |
|
| 2281 |
The encoding of parameters contained within the options part of the |
| 2282 |
PDU header is illustrated in Table 6: |
| 2283 |
|
| 2284 |
Octets |
| 2285 |
___________________________________________ |
| 2286 |
| n | Parameter Code | |
| 2287 |
|____________|____________________________| |
| 2288 |
| n + 1 | Parameter Length (e.g.m) | |
| 2289 |
|____________|____________________________| |
| 2290 |
| n + 2 | | |
| 2291 |
| to | Parameter Value | |
| 2292 |
| n + m + 1 | | |
| 2293 |
|____________|____________________________| |
| 2294 |
|
| 2295 |
|
| 2296 |
|
| 2297 |
<span class="grey">ISO 8473 [Page 39]</span></pre> |
| 2298 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2299 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2300 |
|
| 2301 |
|
| 2302 |
Table 6: Encoding of Parameters |
| 2303 |
|
| 2304 |
The parameter code field is coded in binary and, without extensions, |
| 2305 |
provides a maximum of 255 different parameters. No parameter codes |
| 2306 |
use bits 8 and 7 with the value 00, so the actual maximum number of |
| 2307 |
parameters is lower. A parameter code of 255 (binary 1111 1111) is |
| 2308 |
reserved for possible future extensions. |
| 2309 |
|
| 2310 |
The parameter length field indicates the length, in octets, of the |
| 2311 |
parameter value field. The length is indicated by a positive binary |
| 2312 |
number, m, with a theoretical maximum value of 254. The practical |
| 2313 |
maximum value of m is lower. For example, in the case of a single |
| 2314 |
parameter contained within the options part, two octets are required |
| 2315 |
for the parameter code and the parameter length indicators. Thus, the |
| 2316 |
value of m is limited to: |
| 2317 |
|
| 2318 |
m = 252-(length of fixed part +length of address part +length of seg- |
| 2319 |
mentation part) |
| 2320 |
|
| 2321 |
For each succeeding parameter the maximum value of m decreases. The |
| 2322 |
parameter value field contains the value of the parameter identified |
| 2323 |
in the parameter code field. |
| 2324 |
|
| 2325 |
The following parameters are permitted in the options part. |
| 2326 |
|
| 2327 |
<span class="h4"><a class="selflink" id="section-7.5.2" href="#section-7.5.2">7.5.2</a> Padding</span> |
| 2328 |
|
| 2329 |
The padding parameter is used to lengthen the PDU header to a con- |
| 2330 |
venient size (See Clause 6.12). |
| 2331 |
|
| 2332 |
Parameter Code: 1100 1100 |
| 2333 |
|
| 2334 |
Parameter Length: variable |
| 2335 |
|
| 2336 |
Parameter Value: any value is allowed |
| 2337 |
|
| 2338 |
<span class="h4"><a class="selflink" id="section-7.5.3" href="#section-7.5.3">7.5.3</a> Security</span> |
| 2339 |
|
| 2340 |
This parameter allows a unique and unambiguous security level to be |
| 2341 |
assigned to a protocol data unit. |
| 2342 |
|
| 2343 |
Parameter Code: 1100 0101 |
| 2344 |
|
| 2345 |
Parameter Length: variable |
| 2346 |
|
| 2347 |
Parameter Value: The high order two bits of the first octet |
| 2348 |
specify the Security Format Code, where: |
| 2349 |
|
| 2350 |
Security Type of Security Field: |
| 2351 |
Format Code |
| 2352 |
|
| 2353 |
|
| 2354 |
|
| 2355 |
|
| 2356 |
<span class="grey">ISO 8473 [Page 40]</span></pre> |
| 2357 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2358 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2359 |
|
| 2360 |
|
| 2361 |
00 Reserved |
| 2362 |
01 Source Address Specific |
| 2363 |
10 Destination Address Specific |
| 2364 |
11 Globally Unique |
| 2365 |
|
| 2366 |
The rest of the first octet is reserved and must be zero. The |
| 2367 |
remainder of the Parameter Value field specifies the security |
| 2368 |
level as described in the following Clauses. |
| 2369 |
<span class="h5"><a class="selflink" id="section-7.5.3.1" href="#section-7.5.3.1">7.5.3.1</a> Source Address Specific</span> |
| 2370 |
|
| 2371 |
The Security Format Code value of binary "01" indicates that the |
| 2372 |
remaining octets of the parameter value field specify a security lev- |
| 2373 |
el which is unique and unambiguous in the context of the security |
| 2374 |
classification system employed by the authority responsible for as- |
| 2375 |
signing the source NSAP Address. |
| 2376 |
|
| 2377 |
<span class="h5"><a class="selflink" id="section-7.5.3.2" href="#section-7.5.3.2">7.5.3.2</a> Destination Address Specific</span> |
| 2378 |
|
| 2379 |
The Security Format Code value of binary "10" indicates that the |
| 2380 |
remaining octets of the parameter value field specify a security lev- |
| 2381 |
el which is unique and unambiguous in the context of the security |
| 2382 |
classification system employed by the authority responsible for as- |
| 2383 |
signing the destination NSAP Address. |
| 2384 |
|
| 2385 |
<span class="h5"><a class="selflink" id="section-7.5.3.3" href="#section-7.5.3.3">7.5.3.3</a> Globally Unique Security</span> |
| 2386 |
|
| 2387 |
The Security Format Code value of binary "11" indicates that the |
| 2388 |
remaining octets of the parameter value field specify a globally |
| 2389 |
unique and unambiguous security level. This security classification |
| 2390 |
system is not specified in this Standard. |
| 2391 |
|
| 2392 |
<span class="h4"><a class="selflink" id="section-7.5.4" href="#section-7.5.4">7.5.4</a> Source Routing</span> |
| 2393 |
|
| 2394 |
The source routing parameter specifies, either completely or partial- |
| 2395 |
ly, the route to be taken from Source Network Address to Destination |
| 2396 |
Network Address. |
| 2397 |
|
| 2398 |
Parameter Code: 1100 0101 |
| 2399 |
|
| 2400 |
Parameter Length: variable |
| 2401 |
|
| 2402 |
Parameter Value: 2 octets of control information succeeded by a |
| 2403 |
concatenation of ordered network-entity title entries (ordered |
| 2404 |
from source to destination) |
| 2405 |
|
| 2406 |
The first octet of the parameter value is the type code, and has the |
| 2407 |
following significance: |
| 2408 |
|
| 2409 |
0000 0000 partial source routing |
| 2410 |
0000 0001 complete source routing |
| 2411 |
<all other values reserved> |
| 2412 |
|
| 2413 |
|
| 2414 |
|
| 2415 |
<span class="grey">ISO 8473 [Page 41]</span></pre> |
| 2416 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2417 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2418 |
|
| 2419 |
|
| 2420 |
The second octet indicates the octet offset of the next network- |
| 2421 |
entity title entry to be processed in the list. It is relative to |
| 2422 |
the start of the parameter, such that a value of three (3) indicates |
| 2423 |
that the next network-entity title entry begins immediately after |
| 2424 |
this control octet. Successive octets are indicated by corresponding- |
| 2425 |
ly larger values of this indicator. |
| 2426 |
|
| 2427 |
The third octet begins the network-entity title list. The list con- |
| 2428 |
sists of variable length network-entity title entries. The first oc- |
| 2429 |
tet of entry identifies the length of the network-entity title which |
| 2430 |
comprises the re- mainder of the entry. |
| 2431 |
|
| 2432 |
<span class="h4"><a class="selflink" id="section-7.5.5" href="#section-7.5.5">7.5.5</a> Recording of Route</span> |
| 2433 |
|
| 2434 |
The recording of route parameter identifies the route of intermediate |
| 2435 |
systems traversed by the PDU. |
| 2436 |
|
| 2437 |
Parameter Code: 1100 1011 |
| 2438 |
|
| 2439 |
Parameter Length: variable |
| 2440 |
|
| 2441 |
Parameter Value: 2 octets of control information succeeded by a |
| 2442 |
con catenation of ordered network-entity title entries (ordered |
| 2443 |
from destination to source) |
| 2444 |
|
| 2445 |
The first octet of the parameter value is the type code, and has the |
| 2446 |
following significance: |
| 2447 |
|
| 2448 |
0000 0000 Partial Recording of Route in progress |
| 2449 |
0000 0001 Complete Recording of Route in progress |
| 2450 |
<all other values reserved> |
| 2451 |
|
| 2452 |
The second octet identifies the first octet not currently used for a |
| 2453 |
recorded network-entity title, and therefore also the end of the |
| 2454 |
list. It is encoded relative to the start of the parameter value, |
| 2455 |
such that a value of three (3) indicates that no network-entity ti- |
| 2456 |
tles have yet been recorded. A value of all ones is used to indicate |
| 2457 |
that route recording has been terminated. |
| 2458 |
|
| 2459 |
The third octet begins the network-entity title list. The list con- |
| 2460 |
sists of variable length network-entity title entries. The first oc- |
| 2461 |
tet of each entry specifies the length of the network-entity title |
| 2462 |
comprising the remainder of the entry. Network-entity title entries |
| 2463 |
are always added to the beginning of the list; that is, the most re- |
| 2464 |
cently added entry will begin in the third octet of the parameter |
| 2465 |
value. |
| 2466 |
|
| 2467 |
Note: |
| 2468 |
The length of the Record Route parameter is determined by the |
| 2469 |
originator of the PDU and is not changed during the lifetime of |
| 2470 |
the PDU; hence, the operation of the Record Route function does |
| 2471 |
|
| 2472 |
|
| 2473 |
|
| 2474 |
<span class="grey">ISO 8473 [Page 42]</span></pre> |
| 2475 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2476 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2477 |
|
| 2478 |
|
| 2479 |
not affect the length of the header. |
| 2480 |
|
| 2481 |
<span class="h4"><a class="selflink" id="section-7.5.6" href="#section-7.5.6">7.5.6</a> Quality of Service Maintenance</span> |
| 2482 |
|
| 2483 |
The Quality of Service parameter conveys information about the quali- |
| 2484 |
ty of service requested by the originating Network Service user. |
| 2485 |
Network-entities in intermediate systems may (but are not required |
| 2486 |
to) make use of this information as an aid in selecting a route when |
| 2487 |
more than one route satisfying other routing criteria is available |
| 2488 |
and the available routes are known to differ with respect to Quality |
| 2489 |
of Service see Clause 6.16). |
| 2490 |
|
| 2491 |
Parameter Code: 1100 0011 |
| 2492 |
Parameter Length: variable |
| 2493 |
Parameter Value: The high order two bits of the first octet |
| 2494 |
specify the QoS Format Code, where: |
| 2495 |
|
| 2496 |
QoS Format Type of QoS |
| 2497 |
Code Field |
| 2498 |
00 Reserved |
| 2499 |
01 Source Address Specific |
| 2500 |
10 Destination Address Specific |
| 2501 |
11 Globally Unique |
| 2502 |
|
| 2503 |
The rest of the first octet is reserved and must be zero. The |
| 2504 |
remainder of the Parameter Value field specifies the QoS as described |
| 2505 |
in the following Clauses. |
| 2506 |
|
| 2507 |
<span class="h5"><a class="selflink" id="section-7.5.6.1" href="#section-7.5.6.1">7.5.6.1</a> Source Address Specific</span> |
| 2508 |
|
| 2509 |
The QoS Format Code value of binary "01" indicates that the remaining |
| 2510 |
octets of the parameter value field specify a QoS which is unique and |
| 2511 |
unambiguous in the context of the QoS Maintenance system employed by |
| 2512 |
the authority responsible for assigning the source NSAP Address. |
| 2513 |
|
| 2514 |
<span class="h5"><a class="selflink" id="section-7.5.6.2" href="#section-7.5.6.2">7.5.6.2</a> Destination Address Specific</span> |
| 2515 |
|
| 2516 |
The QoS Format Code value of binary "10" indicates that the remaining |
| 2517 |
octets of the parameter value field specify a QoS which is unique and |
| 2518 |
unambiguous in the context of the QoS Maintenance system employed by |
| 2519 |
the authority responsible for assigning the destination NSAP Address. |
| 2520 |
|
| 2521 |
<span class="h5"><a class="selflink" id="section-7.5.6.3" href="#section-7.5.6.3">7.5.6.3</a> Globally Unique QoS</span> |
| 2522 |
|
| 2523 |
The QoS Format Code value of binary "11" indicates that the remainder |
| 2524 |
of the parameter value field specifies a globally unique QoS Mainte- |
| 2525 |
nance field. When the globally unique QoS Maintenance function is em- |
| 2526 |
ployed, the parameter value field must have a total length of one oc- |
| 2527 |
tet, which is assigned the following values: |
| 2528 |
|
| 2529 |
Bits 8 and 7: QoS Format Code of binary "11" |
| 2530 |
|
| 2531 |
|
| 2532 |
|
| 2533 |
<span class="grey">ISO 8473 [Page 43]</span></pre> |
| 2534 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2535 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2536 |
|
| 2537 |
|
| 2538 |
Bit 6: Reserved |
| 2539 |
Bit 5: sequencing vs. transit delay |
| 2540 |
Bit 4: congestion experienced |
| 2541 |
Bit 3: transit delay vs. cost |
| 2542 |
Bit 2: residual error probability vs. transit delay |
| 2543 |
Bit 1: residual error probability vs. cost |
| 2544 |
|
| 2545 |
Bit 5 is set to one to indicate that, where possible, routing deci- |
| 2546 |
sions should favor sending all PDUs to the specified destination NSAP |
| 2547 |
address over a single path (in order to maintain sequence) over |
| 2548 |
minimizing transit delay. A value of zero (0) indicates that, where |
| 2549 |
possible, routing decisions should favor low transit delay over se- |
| 2550 |
quence preservation. |
| 2551 |
|
| 2552 |
Bit 4 is set to zero by the network-entity which originates the pro- |
| 2553 |
tocol data unit. It is set to one by an intermiediate system to indi- |
| 2554 |
cate that this PDU has visited a congested intermediate system, and |
| 2555 |
appropriate action should be taken by the destination network-entity. |
| 2556 |
Once the congestion experienced bit is set by an intermediate system, |
| 2557 |
it may not be reset by any intermediate system traversed by the PDU |
| 2558 |
further along the path towards the destination. |
| 2559 |
|
| 2560 |
Bit 3 is set to one to indicate that, where possible, routing deci- |
| 2561 |
sions should favor low transit delay over low cost. A value of 0 in- |
| 2562 |
dicates that routing decisions should favor low cost over low transit |
| 2563 |
delay. |
| 2564 |
|
| 2565 |
Bit 2 set to one to indicate that, where possible, routing decisions |
| 2566 |
should favor low residual error probability over low transit delay. |
| 2567 |
A value of zero indicates that routing decisions should favor low |
| 2568 |
transit delay over low residual error probability. |
| 2569 |
|
| 2570 |
Bit 1 is set to one to indicate that, where possible, routing deci- |
| 2571 |
sions should favor low residual error probability over low cost. A |
| 2572 |
value of 0 indicates that routing decisions should favor low cost |
| 2573 |
over low residual error probability. |
| 2574 |
|
| 2575 |
<span class="h4"><a class="selflink" id="section-7.5.7" href="#section-7.5.7">7.5.7</a> Priority</span> |
| 2576 |
|
| 2577 |
The value of the Priority parameter indicates the relative priority |
| 2578 |
of the protocol data unit. Intermediate systems that support this |
| 2579 |
option shall make use of this information in routing and in ordering |
| 2580 |
PDUs for transmission. |
| 2581 |
|
| 2582 |
Parameter Code: 1100 1101 |
| 2583 |
|
| 2584 |
Parameter Length: one octet |
| 2585 |
|
| 2586 |
Parameter Value: 0000 0000 - Normal (Default) through |
| 2587 |
0000 1110 - Highest |
| 2588 |
<all other values reserved> |
| 2589 |
|
| 2590 |
|
| 2591 |
|
| 2592 |
<span class="grey">ISO 8473 [Page 44]</span></pre> |
| 2593 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2594 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2595 |
|
| 2596 |
|
| 2597 |
The values 0000 0001 through 0000 1110 are to be used for higher |
| 2598 |
priority protocol data units. If an intermediate system does not sup- |
| 2599 |
port this option, all PDUs shall be treated as if the field had the |
| 2600 |
value 0000 0000. |
| 2601 |
|
| 2602 |
<span class="h3"><a class="selflink" id="section-7.6" href="#section-7.6">7.6</a> Data Part</span> |
| 2603 |
|
| 2604 |
The Data part of the PDU is structured as an ordered multiple of oc- |
| 2605 |
tets, which is identical to the same ordered multiple of octets |
| 2606 |
specified for the NS-Userdata parameter of the N-UNITDATA Request and |
| 2607 |
Indication primitives. The data field is illustrated in Figure 8: |
| 2608 |
|
| 2609 |
|
| 2610 |
Octet |
| 2611 |
___________________________________________________ |
| 2612 |
| | p + 1 |
| 2613 |
: Data : |
| 2614 |
| | z |
| 2615 |
|__________________________________________________| |
| 2616 |
|
| 2617 |
Figure 8: PDU Header -- Data Field |
| 2618 |
|
| 2619 |
|
| 2620 |
|
| 2621 |
|
| 2622 |
|
| 2623 |
|
| 2624 |
|
| 2625 |
|
| 2626 |
|
| 2627 |
|
| 2628 |
|
| 2629 |
|
| 2630 |
|
| 2631 |
|
| 2632 |
|
| 2633 |
|
| 2634 |
|
| 2635 |
|
| 2636 |
|
| 2637 |
|
| 2638 |
|
| 2639 |
|
| 2640 |
|
| 2641 |
|
| 2642 |
|
| 2643 |
|
| 2644 |
|
| 2645 |
|
| 2646 |
|
| 2647 |
|
| 2648 |
|
| 2649 |
|
| 2650 |
|
| 2651 |
<span class="grey">ISO 8473 [Page 45]</span></pre> |
| 2652 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2653 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2654 |
|
| 2655 |
|
| 2656 |
<span class="h3"><a class="selflink" id="section-7.7" href="#section-7.7">7.7</a> Data (DT) PDU</span> |
| 2657 |
|
| 2658 |
<span class="h4"><a class="selflink" id="section-7.7.1" href="#section-7.7.1">7.7.1</a> Structure</span> |
| 2659 |
|
| 2660 |
The DT PDU has the following format: |
| 2661 |
|
| 2662 |
__________________________________________ |
| 2663 |
| Network Layer Protocol Identifier | 1 |
| 2664 |
|________________________________________| |
| 2665 |
| Length Indicator | 2 |
| 2666 |
|________________________________________| |
| 2667 |
| Version/Protocol Id Extension | 3 |
| 2668 |
|________________________________________| |
| 2669 |
| Lifetime | 4 |
| 2670 |
|________________________________________| |
| 2671 |
| S P vline M S vline e/R | Type | 5 |
| 2672 |
|____________________________|___________| |
| 2673 |
| Segment Length | 6,7 |
| 2674 |
|________________________________________| |
| 2675 |
| Checksum | 8,9 |
| 2676 |
|________________________________________| |
| 2677 |
| Destination Address Length Indicator | 10 |
| 2678 |
|________________________________________| |
| 2679 |
| | 11 |
| 2680 |
: Destination Address : |
| 2681 |
|________________________________________| m - 1 |
| 2682 |
| Source Address Length Indicator | m |
| 2683 |
|________________________________________| |
| 2684 |
| | m + 1 |
| 2685 |
: Source Address : |
| 2686 |
| | n - 1 |
| 2687 |
|________________________________________| |
| 2688 |
| Data Unit Identifier | n, n + 1 |
| 2689 |
|________________________________________| |
| 2690 |
| Segment Offset | n + 2, n + 3 |
| 2691 |
|________________________________________| |
| 2692 |
| Total Length | n + 4, n + 5 |
| 2693 |
|________________________________________| |
| 2694 |
| | n + 6 |
| 2695 |
| Options | |
| 2696 |
| | p |
| 2697 |
|________________________________________| |
| 2698 |
| | p + 1 |
| 2699 |
| Data | |
| 2700 |
| | z |
| 2701 |
|________________________________________| |
| 2702 |
|
| 2703 |
Figure 9: DT PDU |
| 2704 |
|
| 2705 |
|
| 2706 |
|
| 2707 |
|
| 2708 |
|
| 2709 |
|
| 2710 |
<span class="grey">ISO 8473 [Page 46]</span></pre> |
| 2711 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span> |
| 2712 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2713 |
|
| 2714 |
|
| 2715 |
<span class="h5"><a class="selflink" id="section-7.7.1.1" href="#section-7.7.1.1">7.7.1.1</a> Fixed Part</span> |
| 2716 |
|
| 2717 |
1) Network Layer Protocol Identifier See Clause 7.2.2 |
| 2718 |
2) Length Indicator See Clause 7.2.3 |
| 2719 |
3) Version/Protocol Id Extension See Clause 7.2.4 |
| 2720 |
4) Lifetime See Clause 7.2.5 |
| 2721 |
5) SP, MS, E/R See Clause 7.2.6 |
| 2722 |
6) Type Code See Clause 7.2.7 |
| 2723 |
7) Segment Length See Clause 7.2.8 |
| 2724 |
8) Checksum See Clause 7.2.9 |
| 2725 |
|
| 2726 |
<span class="h5"><a class="selflink" id="section-7.7.1.2" href="#section-7.7.1.2">7.7.1.2</a> Addresses</span> |
| 2727 |
|
| 2728 |
See Clause 7.3. |
| 2729 |
|
| 2730 |
<span class="h5"><a class="selflink" id="section-7.7.1.3" href="#section-7.7.1.3">7.7.1.3</a> Segmentation</span> |
| 2731 |
|
| 2732 |
See Clause 7.4. |
| 2733 |
|
| 2734 |
<span class="h5"><a class="selflink" id="section-7.7.1.4" href="#section-7.7.1.4">7.7.1.4</a> Options</span> |
| 2735 |
|
| 2736 |
See Clause 7.5. |
| 2737 |
|
| 2738 |
<span class="h5"><a class="selflink" id="section-7.7.1.5" href="#section-7.7.1.5">7.7.1.5</a> Data</span> |
| 2739 |
|
| 2740 |
See Clause 7.7. |
| 2741 |
|
| 2742 |
<span class="h3"><a class="selflink" id="section-7.8" href="#section-7.8">7.8</a> Inactive Network Layer Protocol</span> |
| 2743 |
|
| 2744 |
Octet |
| 2745 |
____________________________________ |
| 2746 |
|Network Layer Protocol Identifier | 1 |
| 2747 |
|__________________________________| |
| 2748 |
| | 2 |
| 2749 |
| Data | |
| 2750 |
| | 2 - n |
| 2751 |
|__________________________________| |
| 2752 |
|
| 2753 |
Figure 10: Inactive Network Layer Protocol |
| 2754 |
|
| 2755 |
|
| 2756 |
<span class="h4"><a class="selflink" id="section-7.8.1" href="#section-7.8.1">7.8.1</a> Network Layer Protocol Id</span> |
| 2757 |
|
| 2758 |
The value of the Network Layer Protocol Identifier field is binary |
| 2759 |
zero (0000 0000). |
| 2760 |
|
| 2761 |
<span class="h4"><a class="selflink" id="section-7.8.2" href="#section-7.8.2">7.8.2</a> Data Field</span> |
| 2762 |
|
| 2763 |
The length of the NS-Userdata parameter is constrained to be less |
| 2764 |
than or equal to the value of the length of the SN-Userdata parameter |
| 2765 |
minus one (see Clause 7.7). |
| 2766 |
|
| 2767 |
|
| 2768 |
|
| 2769 |
<span class="grey">ISO 8473 [Page 47]</span></pre> |
| 2770 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span> |
| 2771 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2772 |
|
| 2773 |
|
| 2774 |
<span class="h3"><a class="selflink" id="section-7.9" href="#section-7.9">7.9</a> Error Report PDU (ER)</span> |
| 2775 |
|
| 2776 |
<span class="h4"><a class="selflink" id="section-7.9.1" href="#section-7.9.1">7.9.1</a> Structure</span> |
| 2777 |
|
| 2778 |
The ER PDU has the following format: |
| 2779 |
|
| 2780 |
Octet |
| 2781 |
______________________________________________ |
| 2782 |
| Network Layer Protocol Identifier | 1 |
| 2783 |
|____________________________________________| |
| 2784 |
| Length Indicator | 2 |
| 2785 |
|____________________________________________| |
| 2786 |
| Version/Protocol Id Extension | 3 |
| 2787 |
|____________________________________________| |
| 2788 |
| Lifetime | 4 |
| 2789 |
|____________________________________________| |
| 2790 |
| SP= 0 vline MS= 0 vline Reserved | Type | 5 |
| 2791 |
|_____________________________________|______| |
| 2792 |
| Segment Length | 6,7 |
| 2793 |
|____________________________________________| |
| 2794 |
| Checksum | 8,9 |
| 2795 |
|____________________________________________| |
| 2796 |
| Destination Address Length Indicator | 10 |
| 2797 |
|____________________________________________| |
| 2798 |
| | 11 |
| 2799 |
: Destination Address : |
| 2800 |
| | m - 1 |
| 2801 |
|____________________________________________| |
| 2802 |
| Source Address Length Indicator | m |
| 2803 |
|____________________________________________| |
| 2804 |
| | m + 1 |
| 2805 |
: Source Address : |
| 2806 |
| | n - 1 |
| 2807 |
|____________________________________________| |
| 2808 |
| | n |
| 2809 |
| Options | |
| 2810 |
| | p - 1 |
| 2811 |
|____________________________________________| |
| 2812 |
| | p |
| 2813 |
| Reason for Discard | |
| 2814 |
| | q - 1 |
| 2815 |
|____________________________________________| |
| 2816 |
| | q |
| 2817 |
| Error Report Data Field | |
| 2818 |
| | z |
| 2819 |
|____________________________________________| |
| 2820 |
|
| 2821 |
Figure 11: Error Report PDU |
| 2822 |
|
| 2823 |
|
| 2824 |
|
| 2825 |
|
| 2826 |
|
| 2827 |
|
| 2828 |
<span class="grey">ISO 8473 [Page 48]</span></pre> |
| 2829 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span> |
| 2830 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2831 |
|
| 2832 |
|
| 2833 |
<span class="h5"><a class="selflink" id="section-7.9.1.1" href="#section-7.9.1.1">7.9.1.1</a> Fixed Part</span> |
| 2834 |
|
| 2835 |
The fixed part of the Error Report Protocol Data Unit is composed in |
| 2836 |
the same way as a new (Initial) Data PDU. References are provided to |
| 2837 |
previous Clauses describing the encoding of the fields comprising the |
| 2838 |
fixed part: |
| 2839 |
|
| 2840 |
1) Network Layer Protocol Identifier See Clause 7.2.2 |
| 2841 |
2) Length Indicator See Clause 7.2.3 |
| 2842 |
3) Version/Protocol Id Extension See Clause 7.2.4 |
| 2843 |
4) Lifetime See Clause 7.2.5 |
| 2844 |
5) SP, MS, E/R Always set to zero, |
| 2845 |
(See Clause 6.10) |
| 2846 |
6) Type Code See Clause 7.2.7 |
| 2847 |
7) Segment Length See Clause 7.2.8 |
| 2848 |
8) Checksum See Clause 7.2.9 |
| 2849 |
|
| 2850 |
|
| 2851 |
<span class="h5"><a class="selflink" id="section-7.9.1.2" href="#section-7.9.1.2">7.9.1.2</a> Addresses</span> |
| 2852 |
|
| 2853 |
See Clause 7.3. |
| 2854 |
|
| 2855 |
The Destination Address specifies the network-entity title of the origi- |
| 2856 |
nator of the discarded PDU. The Source Address specifies the title of the |
| 2857 |
intermediate-system or end-system network-entity initiating the Error |
| 2858 |
Report PDU. |
| 2859 |
|
| 2860 |
<span class="h5"><a class="selflink" id="section-7.9.1.3" href="#section-7.9.1.3">7.9.1.3</a> Options</span> |
| 2861 |
|
| 2862 |
See Clause 7.5. |
| 2863 |
|
| 2864 |
|
| 2865 |
|
| 2866 |
|
| 2867 |
|
| 2868 |
|
| 2869 |
|
| 2870 |
|
| 2871 |
|
| 2872 |
|
| 2873 |
|
| 2874 |
|
| 2875 |
|
| 2876 |
|
| 2877 |
|
| 2878 |
|
| 2879 |
|
| 2880 |
|
| 2881 |
|
| 2882 |
|
| 2883 |
|
| 2884 |
|
| 2885 |
|
| 2886 |
|
| 2887 |
<span class="grey">ISO 8473 [Page 49]</span></pre> |
| 2888 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span> |
| 2889 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2890 |
|
| 2891 |
|
| 2892 |
<span class="h5"><a class="selflink" id="section-7.9.1.4" href="#section-7.9.1.4">7.9.1.4</a> Reason for Discard</span> |
| 2893 |
|
| 2894 |
This parameter is valid only for the Error Report PDU. |
| 2895 |
|
| 2896 |
|
| 2897 |
Parameter Code: 1100 0001 |
| 2898 |
Parameter Length: two octets |
| 2899 |
Parameter Value: type of error encoded in binary. Values are listed |
| 2900 |
in Table 7: |
| 2901 |
_______________________________________________________________________________ |
| 2902 |
| Parameter Value | Class of | Meaning | |
| 2903 |
| Octet 1 Octet 2| Error | | |
| 2904 |
|__________________|_____________|_____________________________________________| |
| 2905 |
| 0000 0000 | | Reason not specified | |
| 2906 |
| 0001 | | Protocol Procedure Error | |
| 2907 |
| 0010 | | Incorrect Checksum | |
| 2908 |
| 0011 | General | PDU Discarded due to Congestion | |
| 2909 |
| 0100 | | Header Syntax Error (cannot be parsed) | |
| 2910 |
| 0101 | | Segmentation needed but not permitted | |
| 2911 |
| 0110 | | Incomplete PDU Received | |
| 2912 |
| 0111 | | Duplicate Option | |
| 2913 |
|__________________|_____________|_____________________________________________| |
| 2914 |
| 1000 0000 | Address | Destination Address Unreachable | |
| 2915 |
| 0001 | | Destination Address Unknown | |
| 2916 |
|__________________|_____________|_____________________________________________| |
| 2917 |
| 1001 0000 | | Unspecified Source Routing Error | |
| 2918 |
| 0001 | Source | Syntax Error in Source Routing Field | |
| 2919 |
| 0010 | Routing | Unknown Address in Source Routing Field | |
| 2920 |
| 0011 | | Path not Acceptable | |
| 2921 |
|__________________|_____________|_____________________________________________| |
| 2922 |
| 1010 0000 | Lifetime | Lifetime Expired while Data Unit in Transit | |
| 2923 |
| 0001 | | Lifetime Expired during Reassembly | |
| 2924 |
|__________________|_____________|_____________________________________________| |
| 2925 |
| 1011 0000 | | Unsupported Option not Specified | |
| 2926 |
| 0001 | PDU | Unsupported Protocol Version | |
| 2927 |
| 0010 | Discarded | Unsupported Security Option | |
| 2928 |
| 0011 | | Unsupported Source Routing Option | |
| 2929 |
| 0100 | | Unsupported Recording of Route Option | |
| 2930 |
|__________________|_____________|_____________________________________________| |
| 2931 |
| 1100 0000 | Reassembly | Reassembly interference | |
| 2932 |
|__________________|_____________|_____________________________________________| |
| 2933 |
|
| 2934 |
Table 7: Reasons for Discard |
| 2935 |
|
| 2936 |
The first octet of the parameter value contains an error type code. |
| 2937 |
If the error in the discarded Data PDU can be localized to a particu- |
| 2938 |
lar field, the number of the first octet of that field is stored in |
| 2939 |
the second octet of the reason for discard parameter field. If the |
| 2940 |
error cannot be localized to a particular field, or if the error is a |
| 2941 |
checksum error, then the value zero is stored in the second octet of |
| 2942 |
the reason for discard parameter field. |
| 2943 |
|
| 2944 |
|
| 2945 |
|
| 2946 |
<span class="grey">ISO 8473 [Page 50]</span></pre> |
| 2947 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span> |
| 2948 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 2949 |
|
| 2950 |
|
| 2951 |
<span class="h5"><a class="selflink" id="section-7.9.1.5" href="#section-7.9.1.5">7.9.1.5</a> Error Report Data Field</span> |
| 2952 |
|
| 2953 |
This field contains the entire header of the discarded Data PDU, and |
| 2954 |
may contain some or all of the data field of the discarded PDU. |
| 2955 |
|
| 2956 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a> Conformance</span> |
| 2957 |
|
| 2958 |
For conformance to this International Standard, the ability to ori- |
| 2959 |
ginate, manipulate, and receive PDUs in accordance with the full pro- |
| 2960 |
tocol (as opposed to the non-segmenting or Inactive Network Layer |
| 2961 |
Protocol subsets) is required. |
| 2962 |
|
| 2963 |
Additionally, conformance to the Standard requires provision of the |
| 2964 |
protocol functions described in Clause 6. Provision of the optional |
| 2965 |
functions described in Clause 6.18 and enumerated in Table 9-1 must |
| 2966 |
meet the requirements described therein. Exceptions to this require- |
| 2967 |
ment are described in Clause 8.1 below. |
| 2968 |
|
| 2969 |
Additionally, conformance to the Standard requires adherence to the |
| 2970 |
structure and encoding of PDUs of Clause 7. |
| 2971 |
|
| 2972 |
If and only if the above requirements are met is there conformance to |
| 2973 |
this International Standard. |
| 2974 |
|
| 2975 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a> Provision of Functions for Conformance</span> |
| 2976 |
|
| 2977 |
The following table categorizes the functions in Clause 6 with |
| 2978 |
respect to the type of system providing the function: |
| 2979 |
|
| 2980 |
Note: |
| 2981 |
|
| 2982 |
1. The support of the PDU Composition and Forward PDU functions |
| 2983 |
is necessary for the generation of Error Report PDUs. |
| 2984 |
|
| 2985 |
2. The Segment PDU function is in general mandatory for an |
| 2986 |
intermediate system. However, a system which is to be |
| 2987 |
connected only to subnetworks all offering the same maximum |
| 2988 |
SDU size (such as identical Local Area Networks) will not |
| 2989 |
need to perform this function and therefore does not need to |
| 2990 |
implement it. |
| 2991 |
|
| 2992 |
If this function is not implemented, this shall be stated |
| 2993 |
as part of the specification of the implementation. |
| 2994 |
|
| 2995 |
3. The correct treatment of the padding function requires no |
| 2996 |
processing. A conforming implementation shall support the |
| 2997 |
function, to the extent of ignoring this parameter wherever |
| 2998 |
it may appear. |
| 2999 |
|
| 3000 |
4. This function may or may not be supported. If an |
| 3001 |
implementation does not support this function, and the |
| 3002 |
|
| 3003 |
|
| 3004 |
|
| 3005 |
<span class="grey">ISO 8473 [Page 51]</span></pre> |
| 3006 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span> |
| 3007 |
<span class="grey"><a href="./rfc994">RFC 994</a> December 1986</span> |
| 3008 |
|
| 3009 |
|
| 3010 |
function is selected in a PDU, then the PDU shall be discarded, |
| 3011 |
and an ER PDU shall be generated and forwarded to the |
| 3012 |
originating network-entity if the Error Report flag is set |
| 3013 |
and the conditions of Clause 6.10.4 are satisfied. |
| 3014 |
|
| 3015 |
5. This function may or may not be supported. If an implementation |
| 3016 |
does not support this function, and the function is selected |
| 3017 |
in a PDU, then the function is not performed and the PDU is |
| 3018 |
processed exactly as though the function had not been |
| 3019 |
selected. The PDU shall not be discarded for this reason. |
| 3020 |
|
| 3021 |
___________________________________________________________________ |
| 3022 |
| Function | Send | Forward | Receive | |
| 3023 |
|____________________________|____________|___________|___________| |
| 3024 |
| PDU Composition | M | (Note 1) | (Note 1) | |
| 3025 |
| PDU Decomposition | M | - | M | |
| 3026 |
| Header Format Analysis | - | M | M | |
| 3027 |
| PDU Lifetime Control | | M | I | |
| 3028 |
| Route PDU | - | M | - | |
| 3029 |
| Forward PDU | M | M | (Note 1) | |
| 3030 |
| Segment PDU | M | (Note 2) | - | |
| 3031 |
| Reassemble PDU | - | I | M | |
| 3032 |
| Discard PDU | - | M | M | |
| 3033 |
| Error Reporting | M | M | M | |
| 3034 |
| Header Error Detection | (Note 3) | M | M | |
| 3035 |
| | | | | |
| 3036 |
| Security | - | (Note 3) | (Note 4) | |
| 3037 |
| Complete Source Routing | - | (Note 4) | - | |
| 3038 |
| Complete Route Recording | - | (Note 4) | - | |
| 3039 |
| Partial Source Routing | - | (Note 5) | - | |
| 3040 |
| Partial Route Recording | - | (Note 5) | - | |
| 3041 |
| Priority | - | (Note 5) | - | |
| 3042 |
| QoS Maintenance | - | (Note 5) | - | |
| 3043 |
| Congestion Notification | - | (Note 5) | - | |
| 3044 |
| Padding | - | (Note 5) | (Note 3) | |
| 3045 |
|____________________________|____________|___________|___________| |
| 3046 |
|
| 3047 |
|
| 3048 |
Table 8: Categorization of Functions |
| 3049 |
Key: |
| 3050 |
|
| 3051 |
M: Mandatory Function; this function must be implemented. |
| 3052 |
|
| 3053 |
-: Not applicable. |
| 3054 |
|
| 3055 |
I: Implementation option, as described in the text. |
| 3056 |
|
| 3057 |
NOTE: See notes above |
| 3058 |
|
| 3059 |
|
| 3060 |
|
| 3061 |
|
| 3062 |
|
| 3063 |
|
| 3064 |
ISO 8473 [Page 52] |
| 3065 |
</pre> |