| 1 |
<pre>Network Working Group D. Heagerty |
| 2 |
Request for Comments: 1670 CERN |
| 3 |
Category: Informational August 1994 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Input to IPng Engineering Considerations</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. This memo |
| 11 |
does not specify an Internet standard of any kind. Distribution of |
| 12 |
this memo is unlimited. |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
This document was submitted to the IETF IPng area in response to <a href="./rfc1550">RFC</a> |
| 17 |
<a href="./rfc1550">1550</a>. Publication of this document does not imply acceptance by the |
| 18 |
IPng area of any ideas expressed within. Comments should be |
| 19 |
submitted to the [email protected] mailing list. |
| 20 |
|
| 21 |
Summary |
| 22 |
|
| 23 |
This white paper expresses some personal opinions on IPng engineering |
| 24 |
considerations, based on experience with DECnet Phase V transition. |
| 25 |
It suggests breaking down the IPng decisions and transition tasks |
| 26 |
into smaller parts so they can be tackled early by the relevant |
| 27 |
experts. |
| 28 |
|
| 29 |
Timescales |
| 30 |
|
| 31 |
In order to allow key decisions to be taken early, I would like to |
| 32 |
see IPng decisions and timescales broken down into into smaller |
| 33 |
parts, for example: |
| 34 |
|
| 35 |
- address structure and allocation mechanism |
| 36 |
- name service changes |
| 37 |
- host software and programming interface changes |
| 38 |
- routing protocol changes |
| 39 |
|
| 40 |
Although interrelated, not all details need to be defined by the same |
| 41 |
date. Identify which decisions will be hard to change and which can |
| 42 |
be allowed to evolve. All changes should be worked on in parallel, |
| 43 |
but the above list indicates a feeling for urgency of a decision. |
| 44 |
Our experience has been that administrative changes (as may be |
| 45 |
required for addressing changes) need the greatest elapse time for |
| 46 |
implementation, whereas routing protocol changes need the least. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Heagerty [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1670">RFC 1670</a> Input to IPng Engineering Considerations August 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
I would like to see an early decision on address structure and enough |
| 58 |
information for service managers to start planning their transition. |
| 59 |
Some hosts will never be upgraded and will need to be phased out or |
| 60 |
configured with reduced connectivity. A lead time of 10 years (or |
| 61 |
more) will help to take good long term technical decisions and ease |
| 62 |
financial and organisational constraints. |
| 63 |
|
| 64 |
Transition and deployment |
| 65 |
|
| 66 |
Transition requires intimate knowledge of the environment (financial, |
| 67 |
political as well as technical). The task needs to be broken down so |
| 68 |
that service managers close to their clients can take decisions and |
| 69 |
make them happen. |
| 70 |
|
| 71 |
Let the service managers adapt the solutions for their environment by |
| 72 |
providing them with a transition toolbox and scenarios of their uses |
| 73 |
based on real examples. Clearly state the merits and limitations of |
| 74 |
different transition strategies. |
| 75 |
|
| 76 |
Provide for transition autonomy. Let systems and sites transition at |
| 77 |
different times, as convenient for them. |
| 78 |
|
| 79 |
Identify what software needs to be changed and keep an up-to-date |
| 80 |
list. |
| 81 |
|
| 82 |
Identify what is essential to have in place so that service managers |
| 83 |
can transition at their own pace. |
| 84 |
|
| 85 |
Allow for a feedback loop to improve software based on experience. |
| 86 |
|
| 87 |
Configuration, Administration, Operation |
| 88 |
|
| 89 |
We run IP on a wide range of equipment and operating systems. We |
| 90 |
need an easy way to (re-)configure all our IP capable systems. The |
| 91 |
systems need to be sent their IP parameters (e.g., their address, |
| 92 |
address of their default router, address of their local name servers) |
| 93 |
and we need to obtain data from the system (e.g., contact information |
| 94 |
for owner, location and name of system). We also need an easy way to |
| 95 |
update DNS. |
| 96 |
|
| 97 |
In our environment systems are regularly moved between buildings and |
| 98 |
we therefore find the tight coupling of IP address to physical subnet |
| 99 |
over restrictive. Automatic configuration could help overcome this. |
| 100 |
|
| 101 |
We would like to efficiently load balance users of various IP based |
| 102 |
services (e.g., telnet, ftp, locally written applications) across a |
| 103 |
number of systems. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Heagerty [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1670">RFC 1670</a> Input to IPng Engineering Considerations August 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
The ability to break down addresses and routing into several levels |
| 114 |
of hierarchy is important to allow the delegation of network |
| 115 |
management into subdomains. As the network grows so does the desire |
| 116 |
to increase the number of levels of hierarchy. |
| 117 |
|
| 118 |
Disclaimer and acknowledgments |
| 119 |
|
| 120 |
This is a personal view and does not necessarily represent that of my |
| 121 |
employer. I have benefited from many transition discussions with my |
| 122 |
colleagues at CERN, other High Energy Physics DECnet managers and |
| 123 |
Digital Equipment Corporation engineers. |
| 124 |
|
| 125 |
Security Considerations |
| 126 |
|
| 127 |
Security issues are not discussed in this memo. |
| 128 |
|
| 129 |
Author's Address |
| 130 |
|
| 131 |
Denise Heagerty |
| 132 |
Communications Systems Group |
| 133 |
Computing and Networks Division |
| 134 |
CERN |
| 135 |
European Laboratory for Particle Physics |
| 136 |
1211 Geneva 23, Switzerland |
| 137 |
|
| 138 |
Phone: +41 22 767-4975 |
| 139 |
Fax: +41 22 767-7155 |
| 140 |
EMail: [email protected] |
| 141 |
|
| 142 |
|
| 143 |
|
| 144 |
|
| 145 |
|
| 146 |
|
| 147 |
|
| 148 |
|
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
Heagerty [Page 3] |
| 165 |
</pre> |