| 1 |
<pre>Network Working Group S.E. Hardcastle-Kille |
| 2 |
Requests for Comments 1277 University College London |
| 3 |
November 1991 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Encoding Network Addresses</span> |
| 7 |
<span class="h1">to support operation over non-OSI lower layers</span> |
| 8 |
|
| 9 |
|
| 10 |
|
| 11 |
|
| 12 |
Status of this Memo |
| 13 |
This RFC specifies an IAB standards track protocol for the |
| 14 |
Internet community, and requests discussion and suggestions for |
| 15 |
improvements. Please refer to the current edition of the ``IAB |
| 16 |
Official Protocol Standards'' for the standardization state and |
| 17 |
status of this protocol. Distribution of this memo is unlimited. |
| 18 |
Abstract |
| 19 |
|
| 20 |
The OSI Directory specifies an encoding of Presentation Address, |
| 21 |
which utilises OSI Network Addresses as defined in the OSI |
| 22 |
Network Layer standards [<a href="#ref-CCI88" title="models and services">CCI88</a>] [<a href="#ref-ISO87a">ISO87a</a>]. The OSI Directory, and |
| 23 |
any OSI application utilising the OSI Directory must be able use |
| 24 |
these Network Addresses to identify end systems. Currently, OSI |
| 25 |
applications are often run over lower layers other than the OSI |
| 26 |
Network Service. It is neither reasonable nor desirable for |
| 27 |
groups wishing to investigate and use OSI Applications in |
| 28 |
conjunction with the OSI Directory to be dependent on a global |
| 29 |
OSI Network Service. This document defines a new network address |
| 30 |
format, and rules for using some existing network address |
| 31 |
formats. The scope of this document is: |
| 32 |
|
| 33 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Any TCP/IP network supporting COTS using <a href="./rfc1006">RFC 1006</a>.</span> |
| 34 |
|
| 35 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Any mapping of COTS onto X.25 (usually X.25(80)), where X.25 is</span> |
| 36 |
<span class="h2"> not used to provide CONS (i.e., only DTE and not Network address</span> |
| 37 |
is carried). |
| 38 |
|
| 39 |
|
| 40 |
The approach could also be extended to use with other means of |
| 41 |
providing COTS (or CLTS). It is not appropriate for use where |
| 42 |
CONS or CLNS is used to provide COTS (or CLTS).</pre> |
| 43 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 44 |
|
| 45 |
|
| 46 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Introduction</span> |
| 47 |
|
| 48 |
The OSI Directory specifies an encoding of Presentation Address, which |
| 49 |
utilises OSI Network Addresses as defined in the OSI Network Layer |
| 50 |
standards [<a href="#ref-CCI88" title="models and services">CCI88</a>] [<a href="#ref-ISO87a">ISO87a</a>]. The OSI Directory, and any OSI |
| 51 |
application utilising the OSI Directory must be able use these Network |
| 52 |
Addresses to identify end systems. |
| 53 |
Currently, OSI applications are often run over lower layers other than |
| 54 |
the OSI Network Service. It is neither reasonable nor desirable for |
| 55 |
groups wishing to investigate and use OSI Applications in conjunction |
| 56 |
with the OSI Directory to be dependent on a global OSI Network |
| 57 |
Service. This RFCdefines mechanisms to encode addressing information |
| 58 |
within Network Addresses, in order to support this type of working. |
| 59 |
In particular, support is defined for <a href="./rfc1006">RFC 1006</a> mapping of COTS onto |
| 60 |
TCP/IP and COTS mapped onto X.25(1980) [<a href="#ref-RC87" title="Northrop Corporation Technology Center">RC87</a>, <a href="#ref-CCI80" title="interface between DTE and DCE for packet mode terminals">CCI80</a>]. |
| 61 |
|
| 62 |
Where an OSI application is run over CLNS on the internet, the NSAP |
| 63 |
Guidelines of <a href="./rfc1237">RFC 1237</a> should be followed [<a href="#ref-CGC91" title="E. Gardner">CGC91</a>]. |
| 64 |
This document must be read in the context of ISO 8348 Addendum 2 |
| 65 |
[<a href="#ref-ISO87b">ISO87b</a>]. It will not be meaningful on its own. |
| 66 |
|
| 67 |
|
| 68 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Historical Note</span> |
| 69 |
|
| 70 |
This document was originally published as UCL Research Note RN/89/13 |
| 71 |
and as a project THORN internal document [<a href="#ref-Kil89" title=" University College London">Kil89</a>]. It was devised in |
| 72 |
response to two projects which faced this requirement, and was agreed |
| 73 |
as a common approach. The projects were: |
| 74 |
|
| 75 |
|
| 76 |
o The THORN project, which is an Esprit Project building an OSI |
| 77 |
Directory [<a href="#ref-SA88">SA88</a>]. |
| 78 |
|
| 79 |
o The ISODE project [<a href="#ref-Ros90">Ros90</a>], and in particular the QUIPU directory |
| 80 |
being developed at UCL [<a href="#ref-Kil88" title="pages 173--186. North Holland Publishing">Kil88</a>]. |
| 81 |
|
| 82 |
The proposal has been implemented, and the viability of the solution |
| 83 |
demonstrated. |
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
Hardcastle-Kille Page 1</pre> |
| 92 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 93 |
|
| 94 |
|
| 95 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> Problem Statement</span> |
| 96 |
|
| 97 |
When utilising the OSI Directory, the OSI location of an End System |
| 98 |
will be determined by a Network Address, which is taken from a |
| 99 |
Presentation Address, looked up in the OSI Directory. |
| 100 |
OSI applications are currently operated over the following lower |
| 101 |
layers. |
| 102 |
|
| 103 |
|
| 104 |
o An international X.25 network, which routes on the basis of X.121 |
| 105 |
addresses. By and large this is X.25(80), but some parts are now |
| 106 |
X.25(84) and will carry Network Addresses as user data. OSI |
| 107 |
Transport is mapped onto the variant of X.25 which is available. |
| 108 |
|
| 109 |
o Large private X.25 networks, which do not have DNICs, but are |
| 110 |
otherwise similar to the previous (in particular Janet). |
| 111 |
|
| 112 |
o Isolated networks running Connection Oriented Network Service |
| 113 |
(e.g., Pink Book Ethernets). |
| 114 |
|
| 115 |
o Isolated networks running Connectionless Network Service (e.g., |
| 116 |
MAP LANs). |
| 117 |
|
| 118 |
o The Connectionless Network Service Protocol (CLNP) pilot, |
| 119 |
currently taking place in the NSFNet and NORDUNet communities. |
| 120 |
|
| 121 |
o Isolated TCP/IP LANs, utilising <a href="./rfc1006">RFC 1006</a> to support the OSI |
| 122 |
Transport Service[RC87]. |
| 123 |
|
| 124 |
o The DARPA/NSF Internet, using <a href="./rfc1006">RFC 1006</a>. |
| 125 |
|
| 126 |
In general, these systems need to be interconnected by the use of |
| 127 |
transport bridging or application relaying. Operation of transport |
| 128 |
bridges causes a number of problems which it is desirable to avoid. |
| 129 |
Only some applications can support relaying, and this is not always |
| 130 |
satisfactory. |
| 131 |
|
| 132 |
|
| 133 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> The ``Right Solution''</span> |
| 134 |
|
| 135 |
It is worth noting briefly what the intended (OSI) solution is. There |
| 136 |
is a single global network service. Network Addresses are globally |
| 137 |
allocated, and do not imply anything about routing or location. An |
| 138 |
|
| 139 |
|
| 140 |
Hardcastle-Kille Page 2</pre> |
| 141 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 142 |
|
| 143 |
|
| 144 |
End System is attached to one or more subnetworks at Subnetwork Points |
| 145 |
of Attachment (SNPAs). Intermediate Systems join subnetworks, again |
| 146 |
being attached at SNPAs. Routing is achieved by repeated binding of |
| 147 |
Network Address to SNPA (initially at the Originating End System, and |
| 148 |
then at each Intermediate System). This binding is achieved by |
| 149 |
network level routing mechanisms. |
| 150 |
This can only work in a pure OSI environment with a single ubiquitous |
| 151 |
network service (either connectionless or connection-oriented), and so |
| 152 |
is not sufficient for the problem being addressed by this note. |
| 153 |
|
| 154 |
|
| 155 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> General Approach</span> |
| 156 |
|
| 157 |
This section describes the use of network addresses, and gives a |
| 158 |
functional overview of the problem being takceled. The means of |
| 159 |
connecting to a remote Application Entity is broadly as follows. |
| 160 |
|
| 161 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Look up the Application Entity in the OSI Directory to obtain the</span> |
| 162 |
<span class="h2"> Presentation Address 1.</span> |
| 163 |
|
| 164 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Extract each Network Address from the Presentation Address, and</span> |
| 165 |
<span class="h2"> determine if it can be used (and how).</span> |
| 166 |
|
| 167 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Determine an order of preference for the Network Addresses.</span> |
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Attempt to connect to one or more of the Network Addresses.</span> |
| 170 |
|
| 171 |
|
| 172 |
This note is concerned with the second step, and will probably have |
| 173 |
implications on the third. There is currently no directory service to |
| 174 |
provide step 2, and so this (interim) approach must be algorithmic. |
| 175 |
All addressing information required for the network must be extracted |
| 176 |
from the network address. |
| 177 |
This note describes the use of Network Addresses for networks which do |
| 178 |
not provide the OSI Network Service (CLNS or CONS), and places |
| 179 |
constraints on the use of X.121 form network addresses when used for |
| 180 |
an OSI Network Service. The following types of Network Address are |
| 181 |
discussed in this note: |
| 182 |
|
| 183 |
---------------------------- |
| 184 |
1. Strictly an Application Entity should have only one |
| 185 |
Presentation Address. In practice it may have several, and the |
| 186 |
network addresses of each Presentation Address should be considered. |
| 187 |
|
| 188 |
|
| 189 |
Hardcastle-Kille Page 3</pre> |
| 190 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 191 |
|
| 192 |
|
| 193 |
o Use of X.121 form Network Addresses. |
| 194 |
|
| 195 |
o A special encoding of Telex form Network Addresses. |
| 196 |
|
| 197 |
|
| 198 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> Network addresses with X.121 AFI</span> |
| 199 |
|
| 200 |
This note defines an approach for use of network addresses with the |
| 201 |
<span class="h3"><a class="selflink" id="appendix-X.121" href="#appendix-X.121">X.121</a> AFI.</span> |
| 202 |
The IDP of network addresses is used to allow worldwide administration |
| 203 |
of the NSAP address space. As such, not all values of the IDP will in |
| 204 |
practice have topological significance (which implies that in some |
| 205 |
cases the IDP will not be sufficient for network layer routing). |
| 206 |
However, it is recommended that any End System using the Connection |
| 207 |
Oriented Network Service and with access to the international X.25 |
| 208 |
service uses the X.121 form of NSAP address relative to its access |
| 209 |
point. This allows routing across the worldwide X.25 based public |
| 210 |
data networks to be based on the X.121 addresses. Allocation of DSP |
| 211 |
(Domain Specific Part) within this form of address is a private issue. |
| 212 |
|
| 213 |
The IDP is primarily an allocation mechanism, and the user (end |
| 214 |
system) cannot in principle assume any implied routing. However, due |
| 215 |
to the lack of a network directory service, it is recommended that any |
| 216 |
End System with Connection Oriented Network Service and access to the |
| 217 |
international X.25 service uses X.121 form relative to its access |
| 218 |
point. Allocation of DSP (Domain Specific Part) is a private issue. |
| 219 |
Conversely it is recommended that if an X.121 IDP (Initial Domain |
| 220 |
Part) form Network Address is interpreted, then the X.121 address will |
| 221 |
provide a route (by defining an SNPA on the international X.25 |
| 222 |
network). There may be additional and perhaps preferable routes which |
| 223 |
can be determined by private means. |
| 224 |
If the DSP is absent, the form should be interpreted as implying a |
| 225 |
mapping of Transport onto X.25(80). |
| 226 |
|
| 227 |
|
| 228 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> New Network Address Format</span> |
| 229 |
|
| 230 |
|
| 231 |
This section defines a new network address format. The scope of this |
| 232 |
format is currently: |
| 233 |
|
| 234 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Any TCP/IP network supporting COTS using <a href="./rfc1006">RFC 1006</a>.</span> |
| 235 |
|
| 236 |
|
| 237 |
|
| 238 |
Hardcastle-Kille Page 4</pre> |
| 239 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 240 |
|
| 241 |
|
| 242 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Any mapping of COTS onto X.25 (usually X.25(80)), where X.25 is</span> |
| 243 |
<span class="h2"> not used to provide CONS (i.e., only DTE and not Network address</span> |
| 244 |
is carried), except where the international X.25 service is used |
| 245 |
and no PID or CUDF is required. |
| 246 |
These exceptions are the cases which are handled by use of X.121 |
| 247 |
AFI (<a href="#section-3">Section 3</a>). The intention is to use the X.121 AFI wherever |
| 248 |
possible, and the formats defined in this section are for the |
| 249 |
remaining cases. |
| 250 |
|
| 251 |
The approach could also be extended to use with other means of |
| 252 |
providing COTS (or CLTS). It is not appropriate for use where CONS or |
| 253 |
CLNS is used to provide COTS (or CLTS). |
| 254 |
|
| 255 |
|
| 256 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Requirements</span> |
| 257 |
|
| 258 |
The requirements for use of OSI over existing networks not supporting |
| 259 |
CONS or CLNS, when using the OSI Directory are: |
| 260 |
|
| 261 |
|
| 262 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The information for the layers below Transport must be obtained</span> |
| 263 |
<span class="h2"> from the Network Address. This is essential, because we wish to</span> |
| 264 |
use the OSI Directory in a standard manner, and the Network |
| 265 |
Address is the information available. |
| 266 |
|
| 267 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Network Addresses must be globally unique, as they can be</span> |
| 268 |
<span class="h2"> looked up by anyone with access to the Directory.</span> |
| 269 |
|
| 270 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Network Address should be allocated so that confusion with a</span> |
| 271 |
``real'' Network Address (i.e., one which defines an NSAP using |
| 272 |
CONS or CLNS as opposed to X.25(80) or <a href="./rfc1006">RFC 1006</a>) is unlikely. |
| 273 |
|
| 274 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Network Addresses must be interpretable on the basis of a well</span> |
| 275 |
<span class="h2"> known information, or on information which can be obtained from</span> |
| 276 |
the (application level) OSI Directory. (This RFConly uses well |
| 277 |
known information). |
| 278 |
|
| 279 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The identity of the network in question must be deducible from the</span> |
| 280 |
<span class="h2"> Network Address</span> |
| 281 |
|
| 282 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. All network specific addressing information (including the SNPA)</span> |
| 283 |
<span class="h2"> must be deducible from the Network Address</span> |
| 284 |
|
| 285 |
|
| 286 |
|
| 287 |
Hardcastle-Kille Page 5</pre> |
| 288 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 289 |
|
| 290 |
|
| 291 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> IDP Choice</span> |
| 292 |
|
| 293 |
The IDP is used with Telex AFI. The Telex AFI is used because: |
| 294 |
|
| 295 |
o It gives the largest DSP |
| 296 |
|
| 297 |
o It is less likely than other forms to be used for ``real'' Network |
| 298 |
Addresses |
| 299 |
|
| 300 |
|
| 301 |
The following AFIs might have been chosen, but are not used for the |
| 302 |
reasons given: |
| 303 |
|
| 304 |
o Local (the values must be globally unique) |
| 305 |
|
| 306 |
o X.121 (because it may be confused with other uses of OSI network |
| 307 |
addresses) |
| 308 |
|
| 309 |
o DCC and ICD (because it may be confused with other uses of OSI |
| 310 |
network addresses) |
| 311 |
|
| 312 |
The IDI should be assigned in a manner appropriate to the use of the |
| 313 |
encoding. For example, for operation on a private network within an |
| 314 |
organisation, the telex number of that organisation would be a good |
| 315 |
choice. Some well known networks are given assignments in <a href="#appendix-A">Appendix A</a>. |
| 316 |
|
| 317 |
|
| 318 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> The DSP Encoding</span> |
| 319 |
|
| 320 |
The network address is used as follows. |
| 321 |
|
| 322 |
|
| 323 |
o A (sub)network is identified by the IDP and a small part of the |
| 324 |
DSP. |
| 325 |
|
| 326 |
o The remainder of the DSP encodes network specific information |
| 327 |
|
| 328 |
The DSP format is now defined. The top level format is independent of |
| 329 |
the means used to provde COTS. Two formats for the remainder of the |
| 330 |
DSP are then defined, for specific means of providing COTS. |
| 331 |
|
| 332 |
A decimal abstract encoding is defined for the DSP. The ECMA 117 |
| 333 |
format might have been used, but it is not suitable. [<a href="#ref-TC386" title="ECMA">TC386</a>]. Use of |
| 334 |
a binary encoding, with the DSP structured in ASN.1 would have been a |
| 335 |
|
| 336 |
Hardcastle-Kille Page 6</pre> |
| 337 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 338 |
|
| 339 |
|
| 340 |
very attractive approach. However, there is insufficient space in the |
| 341 |
Network Address for this to be feasible. |
| 342 |
The following structure is defined: |
| 343 |
|
| 344 |
____________________________________ |
| 345 |
|_Digit___||1-2__|______3-27_______|_ |
| 346 |
|_Meaning_||PrefixN|etwork_Specific_| |
| 347 |
|
| 348 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> digits Prefix. </span>This allows for multiple usage of the same DSP, by |
| 349 |
not consuming it all. It also allows for the DSP to be used with |
| 350 |
different encodings. |
| 351 |
|
| 352 |
Network Specific The network specific allocation should be less than |
| 353 |
20 digits if this DSP structure is to be used with any IDI format. |
| 354 |
This is increased to 27 for the Telex format. |
| 355 |
|
| 356 |
|
| 357 |
The IDP + 2 digit prefix identify a subnetwork in which the value of |
| 358 |
the remainder of the DSP (Network Specific Part) is to be interpreted. |
| 359 |
|
| 360 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> X.25(80) Network Specific Format</span> |
| 361 |
|
| 362 |
The IDP/Prefix identifies an X.25(80) subnetwork. There is a need to |
| 363 |
represent a DTE Number, and optionally an X.25 Protocol ID or CUDF |
| 364 |
(many implementations require these due to shortage of X.121 address |
| 365 |
space) in the DSP. This is structured in one of two possible ways: |
| 366 |
|
| 367 |
________________________ |
| 368 |
|_Digit___||1R|emainder_| |
| 369 |
|_Meaning_||0_|_DTE____|_ |
| 370 |
|
| 371 |
____________________________________________________________ |
| 372 |
|_Digit___||_1___|_______2________|3_--_(n*3)+2_|Remainder_|_ |
| 373 |
|_Meaning_||Type__|PID/CUDF_Length_|_PID/CUDF___|___DTE____|_ |
| 374 |
|_Values__||1_or_2_|_____n________|_____________|__________|_ |
| 375 |
|
| 376 |
The network specific part is structured as follows: |
| 377 |
|
| 378 |
|
| 379 |
Type This has the following values |
| 380 |
|
| 381 |
0 DTE only |
| 382 |
|
| 383 |
1 DTE + PID |
| 384 |
|
| 385 |
Hardcastle-Kille Page 7</pre> |
| 386 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 387 |
|
| 388 |
|
| 389 |
2 DTE + CUDF |
| 390 |
|
| 391 |
3-9 Reserved |
| 392 |
|
| 393 |
PID/CUDF Length The length of the PID/CUDF in octets |
| 394 |
|
| 395 |
PID/CUDF The PID/CUDF takes as many digits as indicated by 3 times |
| 396 |
octet 2. Each octet of the PID/CUDF is encoded as three decimal |
| 397 |
digits, representing the decimal value of the octet. |
| 398 |
|
| 399 |
DTE The DTE is terminated by the end of the Network Address. |
| 400 |
|
| 401 |
|
| 402 |
|
| 403 |
For example, the JANET DTE 000005111600 with ASCII CUDF ``12'' would |
| 404 |
be encoded in the following way. The first lines describe the |
| 405 |
abstract notation. Note that where the IDI is not of maximum length, |
| 406 |
that the translation to concrete decimal is not mechanical |
| 407 |
|
| 408 |
|
| 409 |
_______________________________________________________________________________ |
| 410 |
|Part___|_|_____IDP_________|_______________________DSP_______________________|_ |
| 411 |
|Comp___|_|AFI__|___IDI_____|Prefix_|Dte+Cudf_|Len|________CUDF_+_DTE_________|_ |
| 412 |
|Octet__|_|____|____________|_1-2___|___3_____|_4_|___________5-20____________|_ |
| 413 |
|Value__|T|elex_|007_28722__|__02___|___2_____|_2_|____049050_000005111600____|__ |
| 414 |
|Ct_Dec_|_|54___|007_28722__|__02___|___2_____|_2_|____049050_000005111600____|_ |
| 415 |
|Ct_Bin_|_|54___|00_72_87_22_|_02___|_____22______|04_90_50_00_00_51_11_60_0f_|_ |
| 416 |
|
| 417 |
Note that concrete binary is representing octets in hexadecimal. This |
| 418 |
is the syntax most likely to be used in practice. The CUDF is |
| 419 |
represented by two octets 049 and 050 (decimal), which map to six |
| 420 |
digits. |
| 421 |
|
| 422 |
|
| 423 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a> TCP/IP (<a href="./rfc1006">RFC 1006</a>) Network Specific Format</span> |
| 424 |
|
| 425 |
The IDP and 2 digit prefix identifies a TCP/IP network where <a href="./rfc1006">RFC 1006</a> |
| 426 |
is applied. It is necessary to use an IP Address, as there are |
| 427 |
insufficient bits to fit in a domain. It is structured as follows: |
| 428 |
|
| 429 |
__________________________________________________________ |
| 430 |
|_Digit___||_1-12____|13-17_(optional)_|18-22_(optional)_|_ |
| 431 |
|_Meaning_||IP_Address_|____port_______|__Transport_Set__|_ |
| 432 |
|
| 433 |
|
| 434 |
Hardcastle-Kille Page 8</pre> |
| 435 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 436 |
|
| 437 |
|
| 438 |
For TCP/IP there shall be a 20 digit long network-specific part. |
| 439 |
First 12 digits are for the IP address. The port number can be up to |
| 440 |
65535, and needs 5 digits (this is optional, and is defaulted as |
| 441 |
defined in <a href="./rfc1006">RFC 1006</a>). Finally, there is a third part to the address, |
| 442 |
which is defined here as ``transport set'' that indicates what kind of |
| 443 |
IP-based transport protocols is used. This is a decimal number from |
| 444 |
0-65535 which is really a 16-bit flag word. 1 is TCP, 2 is UDP. |
| 445 |
Further values of this code are assigned by the IANA. If the transport |
| 446 |
set is not there or no bits are set, it means ``default'' which is |
| 447 |
TCP. This is encoded in 5 digits. |
| 448 |
For example, the IP Address 10.0.0.6 with port 9 over UDP is encoded |
| 449 |
as: |
| 450 |
|
| 451 |
|
| 452 |
____________________________________________________________________________ |
| 453 |
|Part______|_|_____IDP_________|____________________DSP____________________|_ |
| 454 |
|Component_|_|AFI__|___IDI_____|Prefix_|___IP_Address_____|_Port__|_T_Set__|_ |
| 455 |
|Octet_____|_|____|____________|_1-2___|______3-14________|_15-19_|_20-24__|_ |
| 456 |
|Value_____|T|elex_|007_28722__|__03___|_010_000_000_006__|_00009_|_00002__|__ |
| 457 |
|Cncrt_Dec_|_|54___|007_28722__|__03___|_010_000_000_006__|_00009_|_00002__|_ |
| 458 |
|Cncrt_Bin_|_|54___|00_72_87_22_|_03___|01_00_00_00_00_06_|00_00_9|0_00_02_|_ |
| 459 |
|
| 460 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> Encoding</span> |
| 461 |
|
| 462 |
|
| 463 |
This document describes allocation of Network Addresses, with the DSP |
| 464 |
considered in Abstract Decimal. The encoding of this for use in |
| 465 |
protocols (typically as Concrete Binary) is described in ISO 8348 |
| 466 |
Addendum 2 [<a href="#ref-ISO87a">ISO87a</a>]. |
| 467 |
|
| 468 |
|
| 469 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> References</span> |
| 470 |
|
| 471 |
References |
| 472 |
|
| 473 |
[<a id="ref-CCI80">CCI80</a>] CCITT. Recommendation X.25, interface between DTE and DCE |
| 474 |
for packet mode terminals, 1980. |
| 475 |
|
| 476 |
[<a id="ref-CCI88">CCI88</a>] The Directory --- overview of concepts, models and services, |
| 477 |
December 1988. CCITT X.500 Series Recommendations. |
| 478 |
|
| 479 |
[<a id="ref-CGC91">CGC91</a>] R. Colella, E. Gardner, and R. Callon. Guidelines for OSI |
| 480 |
NSAP Allocation in the Internet. Request for Comments 1237, |
| 481 |
|
| 482 |
|
| 483 |
Hardcastle-Kille Page 9</pre> |
| 484 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 485 |
|
| 486 |
|
| 487 |
NIST, July 1991. |
| 488 |
|
| 489 |
[<a id="ref-ISO87a">ISO87a</a>] Information processing systems - data communications - |
| 490 |
network services definition: Addendum 2 - network layer |
| 491 |
addressing, March 1987. ISO TC 97/SC 6. |
| 492 |
|
| 493 |
[<a id="ref-ISO87b">ISO87b</a>] ISO DIS 7498-3 on naming and addressing, May 1987. |
| 494 |
ISO/IEC/JTC-1/SC 21. |
| 495 |
|
| 496 |
[<a id="ref-Kil88">Kil88</a>] S.E. Kille. The QUIPU directory service. In IFIP WG 6.5 |
| 497 |
Conference on Message Handling Systems and Distributed |
| 498 |
Applications, pages 173--186. North Holland Publishing, |
| 499 |
October 1988. |
| 500 |
|
| 501 |
[<a id="ref-Kil89">Kil89</a>] S.E. Kille. An interim approach to use of network addresses. |
| 502 |
Research Note RN/89/13, Department of Computer Science, |
| 503 |
University College London, February 1989. |
| 504 |
|
| 505 |
[<a id="ref-RC87">RC87</a>] Marshall T. Rose and Dwight E. Cass. ISO Transport Services |
| 506 |
on top of the TCP. Request for Comments 1006, Northrop |
| 507 |
Corporation Technology Center, May 1987. |
| 508 |
|
| 509 |
[<a id="ref-Ros90">Ros90</a>] M.T. Rose. The ISO development environment: User's manual |
| 510 |
(version 6.0), January 1990. |
| 511 |
|
| 512 |
[<a id="ref-SA88">SA88</a>] F. Sirovich and M. Antonellini. The THORN X.500 distributed |
| 513 |
directory environment. In Esprit Conference Week, November |
| 514 |
1988. |
| 515 |
|
| 516 |
[<a id="ref-TC386">TC386</a>] ECMA TC32. Domain specific part of network layer addresses. |
| 517 |
ECMA Standard 117, ECMA, June 1986. |
| 518 |
|
| 519 |
|
| 520 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> Security Considerations</span> |
| 521 |
|
| 522 |
Security considerations are not discussed in this memo. |
| 523 |
|
| 524 |
|
| 525 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a> Author's Address</span> |
| 526 |
|
| 527 |
Steve Hardcastle-Kille |
| 528 |
Department of Computer Science |
| 529 |
University College London |
| 530 |
|
| 531 |
|
| 532 |
Hardcastle-Kille Page 10</pre> |
| 533 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 534 |
|
| 535 |
|
| 536 |
Gower Street |
| 537 |
WC1E 6BT |
| 538 |
England |
| 539 |
|
| 540 |
Phone: +44-71-380-7294 |
| 541 |
|
| 542 |
|
| 543 |
EMail: [email protected] |
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
|
| 557 |
|
| 558 |
|
| 559 |
|
| 560 |
|
| 561 |
|
| 562 |
|
| 563 |
|
| 564 |
|
| 565 |
|
| 566 |
|
| 567 |
|
| 568 |
|
| 569 |
|
| 570 |
|
| 571 |
|
| 572 |
|
| 573 |
|
| 574 |
|
| 575 |
|
| 576 |
|
| 577 |
|
| 578 |
|
| 579 |
|
| 580 |
|
| 581 |
Hardcastle-Kille Page 11</pre> |
| 582 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1277">RFC 1277</a> Encoding Network Addresses November 1991 |
| 583 |
|
| 584 |
|
| 585 |
A Allocations for well known networks |
| 586 |
|
| 587 |
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a> Values</span> |
| 588 |
|
| 589 |
|
| 590 |
This appendix gives an allocation for three well known networks. All |
| 591 |
are allocated on the basis of the supposed Telex number 00728722. |
| 592 |
This number is being used in pilot operations, and so is retained |
| 593 |
here. |
| 594 |
_______________________________________ |
| 595 |
|_________Net__________Telex____Prefix_| |
| 596 |
| International X.25 |007 28722 01 | |
| 597 |
| Janet |007 28722 02 | |
| 598 |
| Darpa/NSF Internet |007 28722 03 | |
| 599 |
|_IXI________________|007_28722_06_____| |
| 600 |
|
| 601 |
The international X.25 allocation is only used where a CUDF or PID is |
| 602 |
needed. In other cases, an X.121 form Network Address with no DSP |
| 603 |
should be used. |
| 604 |
|
| 605 |
|
| 606 |
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a> Delegation</span> |
| 607 |
|
| 608 |
The values assigned in this document are now in widespread use. As |
| 609 |
the number is arbitrary, it would be undesirable to change the numbers |
| 610 |
without a sound technical reason. However, it is important to |
| 611 |
guarantee that the numbers are stable. |
| 612 |
|
| 613 |
This Internet Draft commits UCL not to reassign the portions of the |
| 614 |
number space allocated here. |
| 615 |
The DARPA/NSF Internet space (Prefix 03) is delegated to the IANA. |
| 616 |
|
| 617 |
|
| 618 |
|
| 619 |
|
| 620 |
|
| 621 |
|
| 622 |
|
| 623 |
|
| 624 |
|
| 625 |
|
| 626 |
|
| 627 |
|
| 628 |
|
| 629 |
|
| 630 |
Hardcastle-Kille Page 12 |
| 631 |
</pre> |