Debian Codegraph @

rfc1680.html

raw
1 <pre>Network Working Group C. Brazdziunas
2 Request for Comments: 1680 Bellcore
3 Category: Informational August 1994
4
5
6 <span class="h1">IPng Support for ATM Services</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 Executive Summary
22
23 This white paper describes engineering considerations for IPng as
24 solicited by <a href="./rfc1550">RFC 1550</a> [<a href="#ref-1" title="&quot;IP: Next Generation (IPng) White Paper Solicitation&quot;">1</a>]. IPng should provide support for existing
25 and emerging link technologies that it will be transported over. Link
26 technologies like Ethernet simply multiplex traffic from upper layer
27 protocols onto a single channel. "Sophisticated" link technologies
28 like ATM are emerging in the marketplace allowing several virtual
29 channels to be established over a single wire (or fiber) potentially
30 based on an applications' network performance objectives.
31
32 Support for both "sophisticated" (ATM) and existing link technologies
33 needs to be considered in an IPng candidate. End-to-end applications
34 will communicate through a network where IPng packets travel across
35 subnetworks such as Ethernet and Hippi and also more "sophisticated"
36 link levels such as ATM. Though initial support for IPng over ATM
37 subnetworks will not facilitate a virtual circuit per application,
38 the hooks to provide such a mapping should be in place while also
39 maintaining support for the transport of IPng packets across
40 conventional subnetworks. Application support for QOS-based link
41 level service requires that the following types of ATM information
42 be mappable (or derivable) from the higher level protocol(s) such as
43 IPng: source and destination(s) addresses, connection quality of
44 service parameters, connection state, and ATM virtual circuit
45 identifier. Some of these mappings may be derivable from information
46 provided by proposed resource reservation protocols supporting an
47 integrated services Internet [<a href="#ref-4" title="&quot;Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification&quot;">4</a>]. However, the ATM virtual circuit
48 identifier should be efficiently derivable from IPng packet
49
50
51
52 <span class="grey">Brazdziunas [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1680">RFC 1680</a> IPng Support for ATM Services August 1994</span>
55
56
57 information.
58
59 An IPng candidate should provide evidence that the mapping from an
60 applications' IPng packets to ATM virtual circuit(s) can be
61 accomplished in a heterogeneous Internet architecture keeping in
62 consideration the gigabit/sec rates that IPng/ATM subnetworks will
63 eventually be operating at.
64
65 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
66
67 This paper describes parameters that are needed to map IPng (or any
68 protocol operating above the link level) to ATM services. ATM is a
69 "sophisticated" link level technology which provides the potential
70 capability for applications at the TCP/UDP level to map to a single
71 ATM virtual circuit for transport across an ATM network(s) customized
72 to the network performance and traffic requirements for that
73 application. This is a step above many of today's existing link
74 technologies which can only support a single level of network
75 performance that must be shared by all applications operating on a
76 single endpoint.
77
78 The future Internet will be comprised of both conventional and
79 "sophisticated" link technologies. The "sophisticated" features of
80 link layers like ATM need to be incorporated into an internet where
81 data travels not only across an ATM network but also several other
82 existing LAN and WAN technologies. Future networks are likely to be a
83 combination of subnetworks providing best-effort link level service
84 such as Ethernet and also sophisticated subnetworks that can support
85 quality of service-based connections like ATM. One can envision data
86 originating from an Ethernet, passing through an ATM network, FDDI
87 network, another ATM network, and finally arriving at its destination
88 residing on a HIPPI network. IPng packets will travel through such a
89 list of interconnected network technologies as ATM is incorporated as
90 one of the components of the future Internet.
91
92 To support per application customizable link level connections, four
93 types of ATM information should be derivable from the higher level
94 protocol(s) like IPng. This ATM information includes: source and
95 destination ATM addresses, connection quality of service parameters,
96 connection state, and an ATM virtual circuit identifier which maps to
97 a single IPng application (i.e., single TCP/UDP application). Some of
98 these mapping could potentially be derivable through information
99 provided by proposed resource reservation protocols supporting an
100 integrated services Internet [<a href="#ref-4" title="&quot;Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification&quot;">4</a>]. However, the ATM virtual circuit
101 identifier needs to be efficiently mappable from IPng packet
102 information.
103
104
105
106
107
108 <span class="grey">Brazdziunas [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1680">RFC 1680</a> IPng Support for ATM Services August 1994</span>
111
112
113 Organization of this white paper is as follows. First the
114 characteristics of ATM are described focusing on functions that are
115 not provided in today's LAN technologies. This section provides
116 background information necessary for the following section describing
117 the parameters needed to map IPng services to ATM services.
118
119 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
120
121 In this white paper, the term "application" refers to a process or
122 set of collective processes operating at the TCP/UDP level or above
123 in the protocol stack. For example, each instance of "telnet" or
124 "ftp" session running on an end station is a distinct application.
125
126 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Characteristics of ATM Service</span>
127
128 ATM has several characteristics which differentiates it from current
129 link level technologies. First of all, ATM has the capability of
130 providing many virtual channels to transmit information over a single
131 wire (or fiber). This is very similar to X.25, where many logical
132 channels can be established over a single physical media. But unlike
133 X.25, ATM allows for each of these channels or circuits to have a
134 customizable set of performance and quality of service
135 characteristics. Link level technologies like Ethernet provide a
136 single channel with a single performance and quality of service
137 characteristic. In a sense, a single ATM link level media appears
138 like an array of of link level technologies each with customizable
139 characteristics.
140
141 ATM virtual circuits can be established dynamically utilizing its
142 signaling protocol. ATM signaling is a source initiated negotiation
143 process for connection establishment. This protocol informs elements
144 in the network of the characteristics for the desired connection. ATM
145 signaling does not provide any guidelines for how network elements
146 decide whether it can accept a call or where a signaling request
147 should be forwarded if the end destination (from the link level
148 perspective) has not been reached. In short, ATM signaling does not
149 support any routing functionality of network admission control.
150
151 ATM signaling establishes a "hard state" in the network for a call.
152 "Hard state" implies that the state of a connection in intermediate
153 switching equipment can be set and once established it will be
154 maintained until a message is received by one of the ends of the call
155 requesting a change in state for the connection [<a href="#ref-2" title="&quot;The Design Philosophy of the DARPA Internet Protocols&quot;">2</a>]. As a result, an
156 ATM end system (this could be a workstation with an ATM adapter or a
157 router with an ATM interface) receives guaranteed service from the
158 ATM network. The ATM network is responsible for maintaining the
159 connection state. The price the ATM termination points pay for this
160 guarantee is the responsibility of changing the state of the
161
162
163
164 <span class="grey">Brazdziunas [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1680">RFC 1680</a> IPng Support for ATM Services August 1994</span>
167
168
169 connection, specifically informing the ATM network to establish,
170 alter, or tear-down the connection.
171
172 Each ATM end point in a network has an ATM address associated with it
173 to support dynamic connection establishment via signaling. These
174 addresses are hierarchical in structure and globally unique [<a href="#ref-3" title="&quot;ATM User-Network Interface Specification, Version 3.0&quot;">3</a>]. As a
175 result, these addresses are routable. This allows ATM networks to
176 eventually support a large number of ATM endpoints once a routing
177 architecture and protocols to support it become available.
178
179 The ATM User-Network Interface (UNI) signaling protocol based on
180 ITU-TS Q.93B allows many different service parameters to be
181 specified for describing connection characteristics. [<a href="#ref-3" title="&quot;ATM User-Network Interface Specification, Version 3.0&quot;">3</a>] These
182 parameters can be grouped into several categories: ATM adaptation
183 layer (AAL) information, network QOS objectives, connection traffic
184 descriptor, and transit network selector. The AAL information
185 specifies negotiable parameters such as AAL type and maximum packet
186 sizes. The network QOS objectives describe the service that the ATM
187 user expects from the network. Q.93B allows for one of five service
188 classes to be selected by the ATM user. The service classes are
189 defined as general traffic types such as circuit emulation (class A),
190 variable bit rate audio and video (class B), connection-oriented data
191 transfer (class C), connectionless data transfer (class D), best
192 effort service (class X), and unspecified [<a href="#ref-3" title="&quot;ATM User-Network Interface Specification, Version 3.0&quot;">3</a>]. Each of these
193 categories are further specified through network provider objectives
194 for various ATM performance parameters. These parameters may include
195 cell transfer delay, cell delay variation, and cell loss ratio. The
196 connection traffic descriptor specifies characteristics of the data
197 generated by the user of the connection. This information allows the
198 ATM network to commit the resources necessary to support the traffic
199 flow with the quality of service the user expects. Characteristics
200 defined in the ATM Forum UNI specification include peak cell rate,
201 sustainable cell rate, and maximum and minimum burst sizes [<a href="#ref-3" title="&quot;ATM User-Network Interface Specification, Version 3.0&quot;">3</a>].
202 Lastly, the transit network selection parameter allows an ATM user to
203 select a preferred network provider to service the connection [<a href="#ref-3" title="&quot;ATM User-Network Interface Specification, Version 3.0&quot;">3</a>].
204
205 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Parameters Required to Map IPng to ATM</span>
206
207 There are several parameters required to map ATM services from a
208 higher level service like IPng. These ATM parameters can be
209 categorized in the following manner: addressing parameters,
210 connection QOS-related parameters, connection management information,
211 and ATM virtual circuit identifier. The first three categories
212 provide support for ATM signaling. The last parameter, a connection
213 identifier that maps IPng packets to ATM virtual circuits, provides
214 support for an ATM virtual circuit per application when the end-to-
215 end connection travels across an ATM subnetwork(s) (this does not
216 assume that ATM is the only type of subnetwork that this connection
217
218
219
220 <span class="grey">Brazdziunas [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1680">RFC 1680</a> IPng Support for ATM Services August 1994</span>
223
224
225 travels across). Below, mapping issues for each of these parameters
226 will be described.
227
228 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Addressing</span>
229
230 ATM supports routable addresses to each ATM endpoint to facilitate
231 the dynamic establishment of connections. These addresses need to be
232 derived from a higher level address such as an IPng address and IPng
233 routing information. This type of mapping is not novel. It is a
234 mapping that is currently done for support of current IP over link
235 technologies such as Ethernet. An IP over ATM address resolution
236 protocol (ARP) has been described in the Internet Standard,
237 "Classical IP over ATM" [<a href="#ref-5" title="&quot;Classical IP and ARP over ATM&quot;">5</a>]. In addition, support for IP routing over
238 large ATM networks is being worked in the IETF's "Routing over Large
239 Clouds" working group.
240
241 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Quality of Service</span>
242
243 As described in <a href="#section-3">section 3</a>, an ATM virtual circuit is established
244 based upon a user's traffic characteristics and network performance
245 objectives. These characteristics which include delay and throughput
246 requirements can only be defined by the application level (at the
247 transport level or above) as opposed to the internetworking (IPng)
248 level. For instance, a file transfer application transferring a 100
249 MB file has very different link level performance requirements than a
250 network time application. The former requires a high throughput and
251 low error rate connection whereas the latter could perhaps be
252 adequately serviced utilizing a best-effort service. Current IP does
253 not provide much support for a quality of service specification and
254 provides no support for the specification of link level performance
255 needs by an application directly. This is due to the fact that only a
256 single type of link level performance is available with link
257 technologies like Ethernet. As a result, all applications over IP
258 today receive the same level of link service.
259
260 IPng packets need not explicitly contain information parameters
261 describing an application's traffic characteristics and network
262 performance objectives (e.g., delay = low, throughput = 10 Mb/s).
263 This information could potentially be mapped from resource
264 reservation protocols that operate at the IP (and potentially IPng)
265 level [<a href="#ref-4" title="&quot;Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification&quot;">4</a>].
266
267 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Connection Management</span>
268
269 The establishment and release of ATM connections should ultimately be
270 controlled by the applications utilizing the circuits. As described
271 in <a href="#section-3">section 3</a>, ATM signaling establishes a "hard state" in the network
272 which is controlled by the ATM termination points [<a href="#ref-2" title="&quot;The Design Philosophy of the DARPA Internet Protocols&quot;">2</a>]. Currently, IP
273
274
275
276 <span class="grey">Brazdziunas [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1680">RFC 1680</a> IPng Support for ATM Services August 1994</span>
279
280
281 provides no explicit mechanism for link level connection management.
282 Future support for link level connection management could be
283 accomplished through resource reservation protocols and need not
284 necessarily be supported directly via information contained in the
285 IPng protocol.
286
287 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Connection Identifier</span>
288
289 A mapping function needs to exist between IPng packets and ATM so
290 that application flows map one-to-one to ATM virtual circuits.
291 Currently, application traffic flows are identified at the transport
292 level by UDP/TCP source and destination ports and IP protocol
293 identifiers. This level of identification should also be available
294 at the IPng level so that information in the IPng packets identify an
295 application's flow and map to an ATM virtual circuit supporting that
296 flow when the IPng packets travels across an ATM subnetwork(s).
297
298 Using the current IP protocol, identifying an application's traffic
299 flow requires the combination of the following five parameters:
300 source and destination IP addresses, source and destination UDP/TCP
301 ports, and IP protocol identifier. This application connection
302 identifier for IP is complex and could potentially be costly to
303 implement in IP end stations and routers. The IPng connection
304 identifier should be large enough so that all application level
305 traffic from an IPng end point can be mapped into the IPng packet.
306 Currently, ATM provides 24 bits for virtual circuit identification
307 (VPI and VCI). This provides sufficient capacity for 2^24
308 (16,777,216) connections [<a href="#ref-6" title="&quot;Asynchronous Transfer Mode (ATM) and ATM Adaptation Layer (AAL) Protocols Generic Requirements&quot;">6</a>]. The actual number of bits that are used
309 for the ATM virtual circuit however is established through
310 negotiation between the ATM endpoint and ATM network. This number is
311 useful as an upper bound for the number of mappings that are needed
312 to be supported by IPng.
313
314 An IPng candidate should be able to identify how IPng packets from an
315 application can map to an ATM virtual circuit. In addition, this
316 mapping should be large enough to support a mapping for every IPng
317 application on an end system to an ATM virtual circuit. Careful
318 consideration should be given to complexity of this mapping for IPng
319 to ATM since it needs to eventually support gigabit/sec rates.
320
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Brazdziunas [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1680">RFC 1680</a> IPng Support for ATM Services August 1994</span>
335
336
337 References
338
339 [<a id="ref-1">1</a>] Bradner, S., and A. Mankin, "IP: Next Generation (IPng) White
340 Paper Solicitation", <a href="./rfc1550">RFC 1550</a>, Harvard University, NRL, December
341 1993.
342
343 [<a id="ref-2">2</a>] Clark, D., "The Design Philosophy of the DARPA Internet
344 Protocols", Proc. ATM SIGCOMM '88, August 1988.
345
346 [<a id="ref-3">3</a>] "ATM User-Network Interface Specification, Version 3.0", ATM
347 Forum, September 10, 1993.
348
349 [<a id="ref-4">4</a>] Zhang, L., Estrin, D., Herzog, S., and S. Jamin, "Resource
350 ReSerVation Protocol (RSVP) - Version 1 Functional
351 Specification", Work in Progress, October 1993.
352
353 [<a id="ref-5">5</a>] Laubach, M., "Classical IP and ARP over ATM", <a href="./rfc1577">RFC 1577</a>, Hewlett-
354 Packard Laboratories, January 1994.
355
356 [<a id="ref-6">6</a>] "Asynchronous Transfer Mode (ATM) and ATM Adaptation Layer (AAL)
357 Protocols Generic Requirements", Bellcore Technical Advisory TA-
358 NWT-001113, Issue 1, June 1993.
359
360 Security Considerations
361
362 Security issues are not discussed in this memo.
363
364 Author's Address
365
366 Christina Brazdziunas
367 Bellcore
368 445 South Street
369 Morristown, NJ 07960
370
371 Phone: (201) 829-4173
372 EMail: [email protected]
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 Brazdziunas [Page 7]
389 </pre>