1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
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
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
|
Network Working Group R. Skelton
Request for Comments: 1673 EPRI
Category: Informational August 1994
Electric Power Research Institute Comments on IPng
Status of this Memo
This memo provides information for the Internet community. This memo
does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
Abstract
This document was submitted to the IETF IPng area in response to RFC
1550. Publication of this document does not imply acceptance by the
IPng area of any ideas expressed within. Comments should be
submitted to the big-internet@munnari.oz.au mailing list.
Executive Summary
The question of the future of the Internet protocol (IP) is an issue
of national if not international concern. It is critical to the
building of a National Information Infrastructure, comparable to the
adoption of basic standards for the industrial era such as railways,
highways and electricity.
The Electric Power Research Institute (EPRI) is a non-profit
organization, with 700 voluntary utility members, managing a
technical research and development program for the electric utility
industry to improve power production, distribution and use. The
electric power industry is a major user of computing and
communications and is fully committed to open systems.
While the industry is today a heavy user of the Internet Protocol
Suite (IPS) it is following a long term strategy based on
international standards developed by ISO and CCITT and national
standards developed by the IEEE, ANSI and other standards bodies that
employ formal review and voting procedures.
This strategy is based on a survey of needs in all aspects of the
electrical power supply enterprise. It concluded that these needs
are met more effectively by the current suite of OSI protocols and
international standards under development. Therefore, EPRI developed
the Utility Communications Architecture (UCA) specification for
communications and the Database Access Integrated Services
specification for data exchange both based on the OSI model and
Skelton [Page 1]
^L
RFC 1673 EPRI Comments on IPng August 1994
international standards.
These specifications have been incorporated into the Industry
Government Open Systems Specification (IGOSS). They are receiving
favorable response and application by the industry and its suppliers
as well as the support of the natural gas and waterworks industries.
The issues facing the Internet community concerning growth and the
address and routing limitations of IP in particular, provide an ideal
opportunity for creating the national uniform information transport
superhighway. This is critical to the NII Agenda and the only
proposal that will achieve this goal is one that is acceptable from
both private and public sector viewpoints with both a national and an
international perspective.
EPRI also believes it is critically important that new requirements
need to be achieved by convergence of efforts to develop additional
standards. Security, directory services, network management, and the
ability to support real-time applications are four examples of where
new convergent standards efforts are required.
Just as society could not in the past accept multiple standards for
the gauge of the nation's railways, we can no longer accept multiple
standards for information transport.
Engineering Considerations
1. Mandatory Requirement.
Inter networking must evolve to provide an industrial strength
computing and communications environment for multiple uses of
globally connected network resources. Specifically the underlying
transport must provide high integrity support for upper layer
industrial OSI applications including but not limited to MMS and
TP. Use of interface layers such as RFC 1006 is not acceptable
except as a transition strategy.
2. Basic Requirements.
- Scaleability
The addressing scheme must have essentially an unlimited address
space to encompass an arbitrarily large number of information
objects. Specifically it must solve the fundamental limitations
of 32 bit formats, a format for 20 octets and above is considered
suitable.
Skelton [Page 2]
^L
RFC 1673 EPRI Comments on IPng August 1994
- Routing table economy
Network addressing must achieve significant economy in routing
database size with very large networks.
- Support for the existing Internet
The existing internetworking paradigm and existing OSI and IPS
applications are to be supported.
3. Key Engineering Considerations - A pragmatic solution.
- Available now
The solution must be available now using mature, internationally
agreed standards and off-the-shelf implementations for hosts and
routers. The solution must leverage existing investments in
standards development, deployment and experience while at the
same time provide for all basic requirements.
- Ease of Transition
Any solution must provide an evolutionary transition path using
an OSI.
- IP dual network layer strategy.
This must be achievable without modifications to existing
inter-domain routing protocols while providing the ability to
support proprietary protocols such as IPX and Appletalk. The
scheme must provide the ability to encompass other addressing
schemes such as X.121 and E.164. Existing SNMP and CMIP MIBs
must be applicable and available. Internet domain names need
to be retained.
- Routing effectiveness
This key objective requires features such as route aggregation,
service selection, and low frequency host advertisements; host
routing intelligence should not be required.
- Flexible Efficient Administration
Operational needs will need to be met in an economic and
flexible manner. Addressing allocations can be either
geographically based or based on carrier ID or both and will be
administered by policy not network topology. Simplified and
robust configurability is required which includes the ability to
identify resources e.g., multi-homed hosts and applications,
instead of interfaces.
- Mobility
Dynamic addressing is required where hosts have the ability to
learn their own network address with the minimum of human
intervention.
Skelton [Page 3]
^L
RFC 1673 EPRI Comments on IPng August 1994
Security Considerations
Security isses are not discussed in this memo.
Author's Address
Ron Skelton
Member of Technical Staff
Advanced IT Group
Electric Power Research Institute
Palo Alto CA 94303
EMail: RSKELTON@msm.epri.com
Skelton [Page 4]
^L
|
