Debian Codegraph @

rfc1946.html

raw
1 <pre>Network Working Group S. Jackowski
2 Request for Comments: 1946 NetManage Incorporated
3 Category: Informational May 1996
4
5
6 <span class="h1">Native ATM Support for ST2+</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 As the demand for networked realtime services grows, so does the need
17 for shared networks to provide deterministic delivery services. Such
18 deterministic delivery services demand that both the source
19 application and the network infrastructure have capabilities to
20 request, setup, and enforce the delivery of the data. Collectively
21 these services are referred to as bandwidth reservation and Quality
22 of Service (QoS).
23
24 The IETF is currently working on an integrated services model to
25 support realtime services on the Internet The IETF has not yet
26 focused on the integration of ATM and its inherent QoS and bandwidth
27 allocation mechanisms for delivery of realtime traffic over shared
28 wires. (ATM hardware and interfaces provide the network
29 infrastructure for the determinitic data delivery, however the host
30 resident protocol stacks and applications need more attention.)
31
32 Current IETF efforts underway in the IP over ATM (ipatm) working
33 group rely on intserv, rsvp and ST2 to address QoS issues for ATM. As
34 such, <a href="./rfc1577">RFC 1577</a> and the ATM Forum's Lan Emulation do not provide
35 direct QoS and bandwidth allocation capabilities to network
36 applications. Without providing a mapping of reservations-style QoS
37 to ATM signalling, ATM will remain a 'wire' rather than a shared
38 media infrastructure component.
39
40 This memo describes a working implementation which enables
41 applications to directly invoke ATM services in the following
42 environments:
43
44 - ATM to internet,
45 - internet to ATM, and
46 - internet to internet across ATM.
47
48
49
50
51
52 <span class="grey">Jackowski Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
55
56
57 Table of Contents
58
59 <a href="#section-1.0">1.0</a> Introduction...............................................<a href="#page-2">2</a>
60 <a href="#section-2.0">2.0</a> ST-2 and ST-2+.............................................<a href="#page-5">5</a>
61 <a href="#section-3.0">3.0</a> Implementation Issues for Reservations over ATM............<a href="#page-6">6</a>
62 <a href="#section-3.1">3.1</a> Addressing.................................................<a href="#page-6">6</a>
63 <a href="#section-3.2">3.2</a> Changes to Bandwidth and QoS...............................<a href="#page-6">6</a>
64 <a href="#section-3.3">3.3</a> Multicasting...............................................<a href="#page-7">7</a>
65 <a href="#section-3.4">3.4</a> Receiver Initiated JOIN Requests to Multicast Groups.......<a href="#page-8">8</a>
66 <a href="#section-3.5">3.5</a> Computation of QoS Parameters..............................<a href="#page-8">8</a>
67 <a href="#section-3.6">3.6</a> Use of HELLOs..............................................<a href="#page-9">9</a>
68 <a href="#section-4.0">4.0</a> Reservation Signalling with ATM............................<a href="#page-9">9</a>
69 <a href="#section-4.1">4.1</a> Embedded Reservation Signalling within Q.2931.............<a href="#page-10">10</a>
70 <a href="#section-4.2">4.2</a> In-Band Reservation Signalling............................<a href="#page-11">11</a>
71 <a href="#section-4.3">4.3</a> Dedicated Virtual Circuits for Reservation Signalling.....<a href="#page-12">12</a>
72 <a href="#section-4.4">4.4</a> Reservation Signalling via IP over ATM or LAN Emulation...<a href="#page-13">13</a>
73 <a href="#section-4.5">4.5</a> Summary of Reservation Signalling Options.................<a href="#page-14">14</a>
74 <a href="#section-5.0">5.0</a> Mapping Reservation QoS to ATM QoS........................<a href="#page-15">15</a>
75 <a href="#section-5.1">5.1</a> CPCS-SDU Size Computation.................................<a href="#page-16">16</a>
76 <a href="#section-5.2">5.2</a> PCR Computation...........................................<a href="#page-17">17</a>
77 <a href="#section-5.3">5.3</a> Maximum End to End Transit Delay..........................<a href="#page-17">17</a>
78 <a href="#section-5.4">5.4</a> Maximum Bit Error Rate....................................<a href="#page-18">18</a>
79 <a href="#section-5.5">5.5</a> Accumulated Mean Delay....................................<a href="#page-18">18</a>
80 <a href="#section-5.6">5.6</a> Accumulated Delay Variance (jitter).......................<a href="#page-18">18</a>
81 <a href="#section-6.0">6.0</a> Data Stream Transmission..................................<a href="#page-18">18</a>
82 <a href="#section-7.0">7.0</a> Implementation Considerations and Conclusions.............<a href="#page-19">19</a>
83 <a href="#section-8.0">8.0</a> Security Considerations...................................<a href="#page-20">20</a>
84 <a href="#section-9.0">9.0</a> References................................................<a href="#page-20">20</a>
85 <a href="#section-10.0">10.0</a> Author's Address..........................................<a href="#page-21">21</a>
86
87 <span class="h3"><a class="selflink" id="section-1.0" href="#section-1.0">1.0</a> Introduction</span>
88
89 The ATM Forum and the IETF seem to approach ATM networking
90 differently.
91
92 The ATM forum appeaars to believe that host systems require no
93 protocols beyond OSI layer 2 to deal with ATM. They define a layer 2
94 API and Q.2931 signaling for all new applications.
95
96 LAN Emulation, a mechanism to make the ATM interface appear to be a
97 LAN/internet, is intended to support 'legacy' network applications.
98 LAN emulation does not provide applications any visibility of the ATM
99 features, nor does it provide a mechanism to allow applications to
100 request specific ATM services. With LAN Emulation, application
101 traffic shares virtual circuits with no policing or guarantees of
102 service. LAN Emulation simply extends LAN characteristics to ATM.
103
104
105
106
107
108 <span class="grey">Jackowski Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
111
112
113 Thus far, the IETF, through <a href="./rfc1577">RFC 1577</a>[<a href="#ref-1" title="&quot;Classical IP and ARP over ATM&quot;">1</a>] treats an ATM network as a
114 wire. The ipatm working group has explicitly left issues of specific
115 QoS handling out of their specifications and working documents.
116 Current approaches do not give the application access to individual
117 virtualcircuits and their associated guaranteed bandwidth and QoS.
118 Instead, all IP traffic between two hosts shares virtual circuits
119 with no granularity assigned to application-specific traffic or QoS
120 requirements.
121
122 Thus, neither LAN Emulation nor <a href="./rfc1577">RFC 1577</a> (IP over ATM) uses the
123 features of ATM that make it a unique and desirable technology. <a href="./rfc1821">RFC</a>
124 <a href="./rfc1821">1821</a> (Integration of Realtime Services in an IP-ATM Network
125 Architecture) [<a href="#ref-2" title="&quot;Integration of Real-time Services in an IP-ATM network Architecture&quot;">2</a>] raises many of the issues associated with current
126 IETF efforts towards integrating ATM into the Internet, but it does
127 not propose any solutions.
128
129 This document offers a framework for provision of native ATM
130 circuits for applications which require bandwidth guarantees and QoS.
131 It identifies the requirements of a native ATM protocol which is
132 complementary to standard IP and describes one working
133 implementation.
134
135 This document recognizes the fact that it is critical that such a
136 native ATM protocol is consistent in the four topologies described
137 in [<a href="#ref-2" title="&quot;Integration of Real-time Services in an IP-ATM network Architecture&quot;">2</a>]:
138
139 * Communication across an ATM-only network between two hosts
140 directly connected to the ATM network,
141 * Communication between ATM connected hosts which involves some
142 non-ATM subnets,
143 * Communication between a host on a non-ATM subnet and a host
144 directly connected to ATM,
145 * Communication between two hosts, neither of which has a direct
146 ATM connection, but which may make use of one or more ATM
147 networks for some part of the path.
148
149 That is, to the host systems, the underlying type of network remains
150 transparent even when QoS is involved in internet, ATM, and mixed
151 networking environments. To make this consistency possible, the
152 'native ATM' protocol must also be:
153
154 * Multicast capable, to optimize transmission overhead and
155 support ATM multipoint facilities,
156 * Routable, to enable transmissions across subnets and
157 internets,
158 * QoS knowledgeable, to take advantage of ATM QoS facilities,
159 * Capable of Bandwidth/QoS Reservation to allocate proper
160 facilities for application traffic as it travels across
161
162
163
164 <span class="grey">Jackowski Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
167
168
169 different types of networks: to effectively extend virtual
170 circuits across internets, and
171 * Capable of policing to ensure proper packet scheduling
172 behavior and to protect guaranteed services at merge points.
173
174 Clearly the protocol should support reservations. Reservation
175 protocols enable creation of 'virtual circuits' with guaranteed
176 bandwidth and QoS on the LAN or internet, and simultaneously can act
177 as signaling mechanisms to routers or ATM interfaces to request
178 provisioning of circuits. Use of a reservation protocol makes
179 characteristics of mixed networks (LANs, internet, ATM, ISDN)
180 transparent to the host systems. That is, a reservation will allow
181 the host or router to provision ATM circuits which match the
182 reservation, but in mixed networks, will allow routers and host to
183 provide bandwidth reservation and QoS across the non-ATM interfaces
184 as well. Effectively, the reservation maps ATM virtual circuits to
185 reservations on subnets and internets.
186
187 This creates a consistent End-to-End, QoS-guaranteed service for
188 mixed network topologies.
189
190 While it is beyond the scope of this document, the same requirements
191 apply to mixed ISDN networks and are currently being explored by the
192 ITU for their H.323, H.223, and T.123 standards.
193
194 Arguably, the reservation protocol that provides this end-to-end
195 guaranteed service should be connection-oriented to facilitate
196 mapping of real connections (ATM or ISDN) with virtual connections on
197 the LAN/internet. [<a href="#ref-2" title="&quot;Integration of Real-time Services in an IP-ATM network Architecture&quot;">2</a>] points out the shortcomings of IP and RSVP [<a href="#ref-3" title="&quot;Resource ReSerVation Protocol (RSVP Version 1 Functional Specification&quot;">3</a>]
198 in the ATM environment. Most notable among these are the difficulty
199 of mapping connectionless traffic to ATM connections, the constant
200 softstate refreshes of RSVP (and merging of RESV messages), the
201 receiver orientation of RSVP, and the dependence on IP multicast.
202
203 [<a id="ref-6">6</a>] is an excellent document that proposes solutions to many of the
204 issues raised in [<a href="#ref-2" title="&quot;Integration of Real-time Services in an IP-ATM network Architecture&quot;">2</a>], but the solutions recommend modifications to
205 the current RSVP and ATM implementations. Recently, issues of
206 incompatibility with the current IP over ATM model, VC explosions due
207 to use of multicast groups and VC explosions due to features
208 associated with heterogeneous receivers suggest that the current
209 version of RSVP may be inappropriate for ATM implementations.
210
211 Since ATM is connection-oriented, hard state, and origin-oriented for
212 transmission, signaling, and multicast, and is bandwidth and QoS
213 knowledgeable, perhaps the simplest and most elegant approach to a
214 native protocol for ATM would include a protocol that shares these
215 characteristics.
216
217
218
219
220 <span class="grey">Jackowski Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
223
224
225 In surveying protocols described in IETF RFCs and Internet Drafts,
226 only two seem to meet these requirements: Experimental Internet
227 Stream Protocol: Version 2 (<a href="./rfc1190">RFC 1190</a>) [<a href="#ref-4" title="&quot;Experimental Internet Stream Protocol: Version 2 (ST-II)&quot;">4</a>] and Internet STream
228 Protocol Version 2+ (<a href="./rfc1819">RFC 1819</a>) [<a href="#ref-5" title="&quot;Internet STream Protocol Version 2+&quot;">5</a>]; ST2 and ST2+ respectively.
229
230 <span class="h3"><a class="selflink" id="section-2.0" href="#section-2.0">2.0</a> ST2 and ST2+</span>
231
232 Both ST2 and ST2+ have been given the Internet Protocol Version 5
233 (IPv5) designation. In fact, ST2+ is an updated version of ST2.
234 Both protocols are origin-oriented reservation and multicast
235 protocols that provide bandwidth and QoS guarantees through
236 internets. Unlike IPv4 or IPv6, ST2 and ST2+ are connection-
237 oriented, subscribing to the philosophy that once a connection is
238 established, protocol and routing overhead can be substantially
239 reduced. This carries forward to QoS and Bandwidth Reservation as
240 well, simplifying the implementation of QoS guarantees. THESE
241 PROTOCOLS WERE INTENDED TO COMPLEMENT STANDARD CONNECTIONLESS IP,
242 RECOGNIZING THAT WHILE MOST INTERNET TRAFFIC BENEFITS FROM
243 CONNECTIONLESS NETWORKING, PERFORMANCE AND QoS GUARANTEES COULD BE
244 ACHIEVED MOST EASILY WITH INTERNET CONNECTIONS.
245
246 Both ST2 and ST2+ really consist of two protocols: SCMP and ST. SCMP
247 is analogous to ICMP in that it is the control and signaling
248 protocol, while ST is the low-overhead streaming protocol. ST-2
249 uses standard IP addresses during connection setup, but then reduces
250 header overhead by including a stream identifier in each data packet.
251
252 ST2+ includes simplification of many of the original ST2 features as
253 well as clarification of the ST2 specification. Among these
254 simplifications and clarifications are:
255
256 1) Much simpler connection setup.
257 2) Flow Specification independence and consolidation of experimental
258 Flow Specifications.
259 3) Clarification on the implementation of Groups of Streams.
260 4) Clarification of leaf-initiated JOINs in multicast trees (several
261 ST2 implementations had done this).
262
263 While there continues to be a dramatic increase in the use of ST2
264 for videoconferencing, video on demand, telemetry applications and
265 networked virtual reality, ST2+ has no commercial implementations
266 and is not yet supported by any router vendors. This is because ST2+
267 was released as an RFC late in the summer of 1995. It is expected
268 that several implementations will appear over the coming months. As
269 such, the approach described in this document applies to both
270 protocols, and, in fact, would be valid for any other similar
271 protocol used to establish 'native' ATM circuits. Since ST2 and ST2+
272 are so similar, this document will refer to 'the ST2 protocols'
273
274
275
276 <span class="grey">Jackowski Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
279
280
281 generically in describing an implementation approach to both. Where
282 particular features of ST2+ are required or affect implementation,
283 'ST2+ ' will be used specifically.
284
285 <span class="h3"><a class="selflink" id="section-3.0" href="#section-3.0">3.0</a> Implementation Issues for Reservations over ATM</span>
286
287 As described above, ST is a connection-oriented, hard state, origin-
288 oriented multicast protocol and thus maps fairly well to ATM.
289 However, ST-2 has several features that may be difficult to support
290 in the current version of ATM signaling with Q.2931 and UNI 3.1.
291 Among these are:
292
293 1) Addressing.
294 2) Changes to Bandwidth and QoS.
295 3) Multicasting.
296 4) Receiver initiated JOINs to multicast groups.
297 5) Computation of certain QoS parameters.
298 6) Use of HELLOs.
299
300 The degree of difficulty in supporting these functions is dependent
301 on the signaling mechanism chosen. See <a href="#section-4">Section 4</a> for descriptions of
302 possible signaling approaches and their respective impact on the
303 features listed above.
304
305 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Addressing</span>
306
307 Of course mapping an Internet address to ATM address is always
308 problematic. It would be possible to set up a well known ARP server
309 to resolve the IP addresses of targets. However, the widespread
310 deployment of IP over ATM and LAN emulation in host-based ATM
311 drivers, and the assumption that most host systems will be running
312 some IP applications that do not need specific QoS and bandwidth
313 provisioning, suggests that use of ARP facilities provided by IP
314 over ATM and LAN Emulation is the most obvious choice for address
315 resolution.
316
317 It should be noted that ATMARP returns the ATM address. For some
318 implementations (particularly kernel-based protocols), an NSAP
319 address is also required. Since these addresses are often difficult
320 to get from the ATM network itself in advance of the connection, it
321 may be necessary to invoke out-of-band signaling mechanisms to pass
322 this address, or it may be better to create an NSAP address server.
323
324 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Changes to Bandwidth and QoS</span>
325
326 Both ST-2 and ST-2+ allow the origin to dynamically change the QoS
327 and Bandwidth of a particular stream. At this time Q.2931 and UNI
328 3.1 do not support this feature. Until this capability is available,
329
330
331
332 <span class="grey">Jackowski Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
335
336
337 full support of the SCMP CHANGE message for dedicated ATM circuits
338 (one reservation = one ATM circuit) can only be implemented by
339 tearing down the existing VC for a stream and establishing a new one
340 if efficient use of ATM resources are to be preserved.
341
342 Of course, the CHANGE message can simply be passed across the ATM
343 virtual circuit to the hosts or routers. This would allow the hosts
344 to relax resource requirements locally, and permit routers to relax
345 access to downstream circuits, but the ATM VC itself, would still
346 retain excessive bandwidth.
347
348 In addition, if the implementation allows sharing of virtual circuits
349 by multiple streams, the bandwidth/QoS of individual streams within
350 the VC can be CHANGEd.
351
352 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Multicasting</span>
353
354 ST-2 and ST-2+ support origin-oriented multicasting. That is, the
355 origin of a stream explicitly specifies the addresses of the targets
356 it wants involved in the connection. In addition, the origin can Add
357 or drop targets as desired. Aside from receiver-initiated JOINs
358 (discussed in <a href="#section-3.4">section 3.4</a>), there is a one to one mapping between
359 ST-2 multicast and ATM multipoint connections. Origin-initiated
360 additions can be accomplished through an ADDPARTY, and drops can be
361 done through DROPPARTY.
362
363 A key goal in implementation of a native ATM protocol is to ensure
364 consistent implementation for unicast and multicast data transfers.
365 One difficulty in doing this with ATM Virtual Circuits is the fact
366 that point-to-point circuits are duplex, while multipoint circuits
367 are simplex. This means that for multicast connections to be mapped
368 to multipoint ATM Virtual Circuits, any two-way, end-to-end signaling
369 must be done out of band. An alternative is to let the local
370 reservation agent act as a split/merge point for the connection by
371 establishing point-to-point Virtual Circuits for each member of the
372 multicast group directly connected to the ATM network. For multicast
373 group members not directly connected to the ATM network, traffic can
374 be multicast to the router connected at the edge across a single
375 virtual circuit associated with the reservation.
376
377 <a href="#section-4">Section 4</a> describes alternative mechanisms for implementing
378 signaling.
379
380 Included in each discussion is the optimal means for mapping
381 multicast to ATM point-to-point or multipoint circuits.
382
383 Note that the fact that ST-2 does not rely on IP multicast is a
384 strong advantage in implementation of a native protocol for ATM. The
385
386
387
388 <span class="grey">Jackowski Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
391
392
393 one-to-one mapping of ST-2 multicast connections to ATM multipoint
394 virtual circuits minimizes the number of circuits required to support
395 large multicast groups.
396
397 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Receiver Initiated JOINs to Multicast Groups</span>
398
399 ST-2+ provides an in-band mechanism to permit receivers to join an
400 existing stream. Based on an origin-established authorization level,
401 the JOIN can be refused immediately, can be allowed with notification
402 of the origin, or can be allowed without notifying the origin. This
403 capability is made available through a new SCMP JOIN message. If the
404 receiver knows the IP address of the origin and the Stream ID, he can
405 join the stream if authorized to do so.
406
407 Note that since the JOIN flows from the receiver to the origin, there
408 will be issues in trying to support this feature with Q.2931 and UNI
409 3.1. The JOIN may have to be sent out of band depending on the
410 signaling mechanism chosen (<a href="#section-4">section 4</a>) because of the uni-directional
411 flow for point to multipoint ATM connections. This is supposed to
412 change with availability of UNI 4.0.
413
414 ST-2 did not support receiver initiated JOINs (unlike ST-2+).
415 However, most implementations created an out-of-band, or SCMP
416 extension to support this facility. Again, depending on the SCMP
417 signaling mechanism chosen, this feature may be difficult to support.
418
419 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> Computation of QoS Parameters</span>
420
421 The recommended flow specifications (flowspecs) for ST-2 and ST-2+
422 include parameters that are not currently available to ATM virtual
423 circuits through Q.2931 and UNI 3.1. The mapping of packet rate to
424 cell rate, packet delay to cell delay, and other translatable QoS
425 parameters is described in <a href="#section-5">section 5</a>. However, the ST-2 flowspecs
426 also include parameters like accumulated end-to-end delay and
427 accumulated jitter. These parameters assume that the SCMP messages
428 follow the same path as the data. Depending on the signaling
429 mechanism chosen, this may not be true with ATM and thus certain QoS
430 parameters may be rendered useless.
431
432 It should also be noted that since ST-2 connections are simplex, all
433 QoS parameters are specified separately for each direction of data
434 transfer. Thus two connections and two QoS negotiations are required
435 for a duplex connection. To take advantage of the full duplex nature
436 of point-to-point ATM connections, special multiplexing of ST
437 connections would be required by ST-2 agents.
438
439
440
441
442
443
444 <span class="grey">Jackowski Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
447
448
449 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a> Use of HELLOs</span>
450
451 Both ST-2 and ST-2+ support HELLO messages. HELLOs are intended to
452 assure that the neighboring agent is alive. Failure to respond to a
453 HELLO indicates that the connection is down and that the reservation
454 for that particular link should be freed.
455
456 While the ATM network will notify an ST-2 agent if the network
457 connection is down, there is still the possibility that the
458 connection is intact but that the ST-2 agent itself is down.
459 Knowledge of the neighboring agent's status is increasingly important
460 when multiple ST-2 connections share virtual circuits, when the
461 neighboring agents are routers, and when there are multiple dedicated
462 virtual circuits between agents.
463
464 As such, HELLO is a desirable feature. Note that some signaling
465 schemes (<a href="#section-4">section 4</a>), provide less than optimal support for HELLO.
466
467 <span class="h3"><a class="selflink" id="section-4.0" href="#section-4.0">4.0</a> Reservation Signaling with ATM</span>
468
469 Use of Permanent Virtual Circuits (PVCs) for reservation signaling
470 presents no problem for ST-2, ST-2+, or RSVP. Each circuit is
471 considered to be a dedicated link to the next hop. If the PVCs are
472 to be shared, reservation protocols can divide and regulate the
473 bandwidth just as they would with any other link type.
474
475 Where ATM connections become more interesting is when the ATM network
476 takes on the role of an extended LAN or internet. To do this,
477 Switched Virtual Circuits are used to establish dynamic connections
478 to various endpoints and routers. The ITU-TS Q.2931 SETUP message is
479 used to request a connection from the network with specific bandwidth
480 and QoS requirements, and a CONNECT message is received by the origin
481 to indicate that connection establishment is complete.
482
483 For IP over ATM and LAN Emulation, SVCs are established between
484 endpoints and data traffic for a given destination shares the SVCs.
485 There is no mechanism to allow specific QoS guarantees for the
486 traffic, nor is there a mechanism to set up virtual circuits with
487 specific bandwidth and QoS for a particular type of traffic. This is
488 what reservation protocols will attempt to do. The goal is to use
489 reservations to request establishment of individual virtual circuits
490 with matching bandwidth and QoS for each reservation. This will
491 guarantee the requirements of the application while taking full
492 advantage of the ATM network's capabilities.
493
494 There are four possible mechanisms to perform reservation signaling
495 over ATM:
496
497
498
499
500 <span class="grey">Jackowski Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
503
504
505 1) Embedding reservation signaling equivalents within the ATM Q.2931
506 controls.
507 2) Signaling in-band with the data.
508 3) Signaling over dedicated signaling VCs.
509 4) Implicitly sharing existing VCs for IP over ATM or LAN Emulation.
510
511 Note that ATM circuits are not necessarily reliable. As such, the
512 reliability mechanisms provided by SCMP must be maintained to assure
513 delivery of all reservation signaling messages.
514
515 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Embedded Reservation Signaling Equivalents within ATM Q.2931</span>
516 <span class="h3"> Controls</span>
517
518 The basic idea in embedding reservation signaling within the ATM
519 controls is to use the Q.2931 SETUP and CONNECT messages to establish
520 both reservations and dedicated data paths (virtual circuits) across
521 the ATM network. This eliminates the need for dedicated signaling
522 channels, in-band signaling, or out of band mechanisms to communicate
523 between endpoints. Since SETUP and CONNECT include bandwidth and QoS
524 information, the basic concept is sound. In fact, this approach will
525 speed network connection by preventing multiple passes at
526 establishing a reservation and associated connection. This normally
527 results from the fact that most higher layer protocols (network and
528 transport) first require a link to signal their connection
529 requirements. As such, with ATM, the ATM virtual circuit must be
530 established before the network and/or transport protocols can do
531 their own signaling.
532
533 Embedded reservation signaling allows the reservation information to
534 be carried in the SETUP and CONNECT messages, allowing the
535 reservation protocol to do its signaling simultaneously with the ATM
536 signaling.
537
538 [<a id="ref-7">7</a>] describes a clever way of combining the reservation signaling
539 with the ATM control plane signaling for ST-2. This 'simultaneous
540 connection establishment' process will optimize the establishment of
541 circuits and minimize connection setup time while simultaneously
542 eliminating unnecessary network layer signaling in ST-2. To be
543 effective, [<a href="#ref-7" title="&quot;Connection Oriented Protocols over ATM: A Case Study&quot;">7</a>] requires enhancements to Q.2931 signaling and to the
544 ST-2 protocol implementations. In addition, it currently only
545 applies to point-to-point connections and will not work with
546 multipoint largely due to the simplex nature of multipoint
547 communication in current ATM implementations.
548
549 Implementation of multicast for Embedded Reservation Signaling is
550 done as described above: the reservation agent at the edge of the ATM
551 network must create point-to-point virtual circuits for each target
552 that is directly connected to the ATM network, and for each router
553
554
555
556 <span class="grey">Jackowski Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
559
560
561 that supports downstream targets. This ensures two-way signaling
562 between targets and the origin.
563
564 Signaling itself is quite simple:
565
566 CONNECT maps directly to one or more (multicast) Q.2931
567 SETUPs and CONNECTs.
568 ACCEPT maps directly to Q.2931 CONNECTACK.
569 CHANGE/CHANGE REQUEST are not supported.
570 DISCONNECT maps directly to Q.2931 RELEASE.
571 HELLOs are not needed.
572
573 Unfortunately, the flowspec in the reservation protocol CONNECT
574 message cannot be passed across the ATM network in the signaling
575 messages and thus must be regenerated by the receiving agent.
576
577 In addition, User Data, which can be sent in most SCMP messages
578 cannot be supported without substantial changes to current Q.2931
579 signaling.
580
581 One of the additional complexities with embedding the reservation
582 signaling occurs in heterogeneous networks. Since ATM signaling only
583 operates point to point across the ATM network itself, if the
584 endpoints reside on other types of networks or subnets, the routers
585 at the edge of the ATM networks must generate and regenerate
586 endpoint-based signaling messages on behalf of the host reservation
587 agents. In particular, CONNECT and ACCEPT messages and their
588 associated flowspecs must be regenerated. Refer to <a href="#section-5">Section 5</a> for
589 details on the QoS mappings and on which QoS parameters can be
590 recreated for the generated flowspecs.
591
592 This approach is worth revisiting as an optimal signaling method in
593 pure ATM network environments once ATM signaling capabilities expand.
594
595 However, for heterogeneous networks, other signaling mechanisms may
596 be more appropriate.
597
598 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> In-Band Reservation Signaling</span>
599
600 In-Band Reservation Signaling is the easiest signaling mechanism to
601 implement. When the applications requests a reservation, the
602 reservation agent simply sets up ATM virtual circuits to the
603 endpoints with the QoS specified in the CONNECT request. When
604 ACCEPTed, all subsequent data transmissions proceed on the virtual
605 circuits.
606
607 Once again, to support multicast, the reservation agent must create
608 individual point-to-point virtual circuits to the targets which are
609
610
611
612 <span class="grey">Jackowski Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
615
616
617 directly connected to the ATM network, as well as to routers which
618 can access downstream targets.
619
620 Since signaling is done in-band, all reservation signaling messages
621 can be passed between agents. However, some minimal additional
622 bandwidth must be allocated in the Q.2931 SETUP to allow for the
623 signaling messages themselves.
624
625 Note that the primary disadvantage to In-Band Reservation Signaling
626 is the fact that it does not make use of the multipoint capabilities
627 of ATM and will thus overreserve ATM network bandwidth and create a
628 larger than necessary number of virtual circuits.
629
630 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Dedicated Reservation Signaling Virtual Circuits</span>
631
632 One mechanism that can be used to take advantage of the full data
633 transmission capabilities of ATM networks is to use Dedicated Virtual
634 Circuits for reservation signaling. This guarantees a two-way
635 signaling pipe between the endpoints in a connection while enabling
636 the data transmission to take advantage of the multipoint
637 capabilities of ATM. Data and Signaling are done over separate
638 virtual circuits.
639
640 When an application requests a reservation, the reservation agent
641 reviews the list of targets in the CONNECT request. For any targets
642 which have no current signaling virtual circuits established, the
643 agent establishes UBR (unspecified bit rate) virtual circuits and
644 forwards the CONNECT message to the targets over these virtual
645 circuits. ATMARP is used to resolve any endpoint addresses. For any
646 targets for which there already exist signaling virtual circuits, the
647 agent simply forwards the CONNECT message over the existing virtual
648 circuit.
649
650 Once an ACCEPT message is received, the agent issues a Q.2931 SETUP
651 to the associated target. Upon receipt of a CONNECTACK, data can
652 begin to flow. As additional ACCEPTs are received, the Q.2931
653 ADDPARTY message is used to add a target to the multicast and
654 multipoint connection. Depending on the cause of any ADDPARTY
655 failure, the agent may attempt to establish a dedicated point-to-
656 point virtual circuit to complete the multicast group.
657
658 DISCONNECT requests result in Q.2931 DROPPARTY messages and will
659 cause a member to be dropped from a multicast and multipoint
660 connection. When all targets are dropped from a multipoint
661 connection, a RELEASE can be issued to take down the virtual circuit.
662
663 Signaling virtual circuits are shared among reservations while data
664 circuits are dedicated to a particular reservation. Once all
665
666
667
668 <span class="grey">Jackowski Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
671
672
673 reservations to a given endpoint are terminated, the signaling
674 virtual circuit to that endpoint can be RELEASEd.
675
676 Note that this approach would allow the NSAP address to be passed as
677 user data in the ACCEPT message to enable a kernel-based reservation
678 protocol to establish the dedicated data circuit. In addition,
679 because the connectivity to the endpoint is identical to that of the
680 data circuit, this approach assures the fact that accumulated
681 information in the flowspecs retains it validity.
682
683 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> Reservation Signaling via IP over ATM or LAN Emulation</span>
684
685 As described in the previous section, it would be possible to set up
686 unique SVCs for SCMP signaling, however, since the streaming,
687 connection-oriented data transport offered by ST-2 is intended to be
688 complementary to IP and other connectionless protocol
689 implementations, it would be simpler and more elegant to simply use
690 classical IP over ATM (<a href="./rfc1577">RFC 1577</a>) mechanisms, or to use LAN Emulation.
691 The widespread deployment of IP over ATM and LAN emulation in host-
692 based ATM drivers, and the assumption that most host systems will be
693 running applications that do not need specific QoS and bandwidth
694 provisioning, makes this the most straightforward (if not performance
695 optimal) solution for signaling. Once an end-to-end acceptance of a
696 reservation request is completed via normal LAN or IP transmission,
697 then a unique direct virtual circuit can be established for each data
698 flow.
699
700 If LAN Emulation is used, as long as the ST-2 implementation allows
701 for different paths for SCMP and data, there would be no changes to
702 the signaling mechanisms employed by the reservation agent.
703
704 For IP over ATM, all SCMP messages would be encapsulated in IP as
705 described in both <a href="./rfc1190">RFC 1190</a> and <a href="./rfc1819">RFC 1819</a>. This is required because
706 current ATM drivers will not accept Ipv5 packets, and most drivers do
707 not provide direct access to the shared signaling virtual circuits
708 used for IP.
709
710 In either case, LAN Emulation or IP over ATM, the reservation agent
711 would handle SCMP messages as it normally does. However, once the
712 first ACCEPT is received for a reservation request, a dedicated
713 virtual circuit is established for the data flow. Subsequent ACCEPTs
714 will result in the use of ADDPARTY to add multicast targets to the
715 multipoint virtual circuit. In fact, processing of
716 multipoint/multicast is identical to that described in <a href="#section-4.3">section 4.3</a>.
717
718 Once again, the use of an out-of-band signaling mechanism makes it
719 possible to carry the NSAP address of the target in the ACCEPT
720 message.
721
722
723
724 <span class="grey">Jackowski Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
727
728
729 One potential drawback to using LAN Emulation or SCMP messages
730 encapsulated in IP over ATM, is the fact that there is no guarantee
731 that the connectivity achieved to reach the target via signaling has
732 any relationship to the data path. This means that accumulated
733 values in the flowspec may be rendered useless.
734
735 In addition, it is possible that the targets will actually reside
736 outside the ATM network. That is, there may be no direct ATM access
737 to the Targets and it may be difficult to identify ATM addresses of
738 the associated ATM connected routers. This approach will involve
739 some additional complexity in routing to the targets. However, since
740 ST-2 is intended to run with IP, if ATM vendors would accept IPv5
741 packets or would allow direct access to the IP over ATM signaling
742 virtual circuits, this approach would be optimal in minimizing the
743 number of virtual circuits required.
744
745 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a> Summary of Reservation </span>Signaling Approaches
746
747 Embedded Reservation Signaling (<a href="#section-4.1">section 4.1</a>) is ideal for homogeneous
748 ATM connections, but requires extensions to existing ATM signaling
749 to support multipoint connections. In-Band Reservation Signaling
750 (<a href="#section-4.2">section 4.2</a>) is the easiest to implement, but cannot employ
751 multipoint connections either.
752
753 Perhaps the simplest way to do this is similar to what is suggested
754 in [<a href="#ref-6" title="D. Kandlur">6</a>]: separate the reservation signaling from the actual data
755 flows, mapping the data flows directly to ATM circuits while doing
756 the signaling separately.
757
758 While there is significant complexity in doing this for IP traffic
759 and RSVP, the ST2 protocols lend themselves to this quite well. In
760 fact, because SCMP reservation signaling results in streaming,
761 multicast connections, the 'Shortcut' mechanism described in [<a href="#ref-6" title="D. Kandlur">6</a>],
762 which can bypass routers where direct ATM connections are possible,
763 is automatically available to ST2 streams.
764
765 Using Reservation Signaling over LAN Emulation or IP over ATM
766 (<a href="#section-4.4">section 4.4</a>) is one multipoint-capable approach to implement in
767 hosts since most ATM drivers shipping today provide both IP over ATM
768 and LAN Emulation, as well as associated address resolution
769 mechanisms. However, it is not complete in its ability to accurately
770 depict flowspec parameters or to resolve host ATM addresses. In
771 addition, to be optimal, ATM vendors would either have to support
772 IPv5 in their drivers or allow direct access to the IP signaling
773 virtual circuits. Thus the current ideal approach to implementation
774 of the ST2 protocols over ATM is to use shared Dedicated Reservation
775 Signaling Virtual Circuits (<a href="#section-4.3">section 4.3</a>) for signaling of
776 reservations, and then to establish appropriate multipoint ATM
777
778
779
780 <span class="grey">Jackowski Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
783
784
785 virtual circuits for the data flows.
786
787 <span class="h3"><a class="selflink" id="section-5.0" href="#section-5.0">5.0</a> Mapping of Reservation QoS to ATM QoS</span>
788
789 QoS negotiation in ST-2 (and ST-2+) is done via a two-way
790 negotiation.
791
792 The origin proposes a QoS for the connection in a Flow Specification
793 (Flowspec) associated with the CONNECT message. Most of the
794 network-significant QoS parameters in the Flowspec include both a
795 minimum and a desired value. Each ST agent along the path to the
796 Target validates its ability to provide the specified QoS (at least
797 the minimum value for each), updates certain values in the Flowspec,
798 and propagates the CONNECT until it reaches the Target. The Target
799 can either ACCEPT the Flowspec or REFUSE it if it cannot meet at
800 least the minimum QoS requirements. Negotiation takes place as part
801 of the process in that the Target can specify changes to the desired
802 QoS values as long as the new value meets at least the minimum
803 requirements specified by the Origin system. In addition, both the
804 Target and the Origin can assess actual network performance by
805 reviewing the values that are accumulated along the path.
806
807 The primary Reservation QoS parameters that impact an ATM network
808 are:
809
810 ST-2 (<a href="./rfc1190">RFC 1190</a>) ST-2+ (<a href="./rfc1819">RFC 1819</a>)
811
812 Desired PDU Bytes, Desired Message Size,
813 Limit on PDU Bytes (minimum). Limit on Message Size.
814
815 Desired PDU Rate, Desired Rate,
816 Limit on PDU Rate (minimum). Limit on Rate.
817 Minimum Transmission Rate in Bytes.
818
819 Limit on Delay (maximum). Desired Delay,
820 Limit on Delay.
821 Maximum Bit Error Rate.
822
823 Accumulated Delay.
824 Accumulated Delay Variance (Jitter).
825
826 <span class="h3"><a class="selflink" id="appendix-Q.2931" href="#appendix-Q.2931">Q.2931</a> ATM signaling offers the following QoS parameters:</span>
827
828 - Cumulative Transit Delay,
829 - Maximum End to End Transit Delay.
830
831 - Forward Peak Cell Rate (PCR),
832 - Backward Peak Cell Rate (PCR).
833
834
835
836 <span class="grey">Jackowski Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
839
840
841 - Forward Maximum CPCS-SDU size,
842 - Backward Maximum CPCS-SDU size.
843
844 - Forward QoS Class,
845 - Backward QoS Class.
846
847 - B-LLI (one byte user protocol information).
848
849 As previously noted, reservation protocols (ST and RSVP) make QoS
850 reservations in one direction only. Thus, depending on the type of
851 signaling used (see <a href="#section-4">Section 4</a>), the 'Backward' ATM parameters may not
852 be useful. In particular, if Multipoint ATM connections are used to
853 map multicast reservations, these parameters are not available.
854
855 However, it would be possible to implement a multiplexing scheme to
856 enable reservations to share bi-directional point-to-point ATM
857 connections if the reservation agent creates a split/merge point at
858 the ATM boundary and sets up only point-to-point VC connections to
859 targets.
860
861 The CPCS-SDU parameters are AAL Parameters which are used by the AAL
862 entity to break packets into cells. As such, these parameters are
863 not modified by the network and could conceivably be used for
864 additional end-to-end signaling, along with the B-LLI.
865
866 Finally, QoS Class is somewhat limited in its use and implementation.
867 While IP over ATM recommends use of Class 0 (Unspecified QoS), this
868 is not sufficient for guaranteed connections. Instead, Class 1 with
869 CLP=0 will provide at least minimum QoS services for the traffic.
870
871 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> CPCS-SDU Size Computation</span>
872
873 The CPCS-SDU size computation is the easiest QoS mapping. Since ST-2
874 does not require a Service Specific Convergence Sublayer (SSCS), if
875 AAL 5 is used, the ST packet size plus 8 bytes (for the AAL 5
876 Trailer) will be the CPCS-SDU size. Note that the ST-2 packet size
877 also includes an 8-byte header for ST-2. Thus the CPCS-SDU size is:
878
879 CPCS-SDUsize = PDUbytes + 8 + 8.
880
881 For ST-2+, the header is larger than for ST-2, so the CPCS-SDU size
882 is:
883
884 CPCS-SDUsize = PDUbytes + 12 + 8.
885
886
887
888
889
890
891
892 <span class="grey">Jackowski Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
895
896
897 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> PCR Computation</span>
898
899 The Peak Cell Rate (PCR) computation is only slightly more complex.
900 The PCR will be the peak packet rate divided by the ATM payload size.
901
902 Since PDU rates in ST-2 are specified in tenths of packets per
903 second, AAL 5 requires an 8 byte trailer, and the ATM payload size is
904 48 bytes, the computation for PCR proceeds as follows:
905
906 The requested maximum byte transmission rate for ST-2 is:
907
908 PDUbytes * PDUrate * 10.
909
910 Accounting for the AAL 5 and ST headers, the maximum byte rate
911 is:
912
913 Bytes per second = (PDUbytes + 8 + 8) * PDUrate * 10.
914
915 Translating into cells and eliminating the possibility of a
916 fractional PDU:
917
918 PCR = ((PDUbytes + 8 + 8 + 48) / 48) * PDUrate * 10.
919
920 For ST-2+, not only is the header size 12 bytes, but the Rate is in
921 messages per second, not tenths of packets per second. Thus, the PCR
922 for ST-2+ is:
923
924 PCR = ((PDUbytes + 12 + 8 + 48) / 48) * PDUrate.
925
926 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a> Maximum End to End Transit Delay.</span>
927
928 The End to End Transit Delay is a little more complex. The
929 requested end to end delay must account for not only the PDU size as
930 requested by the user, but the additional 8-byte AAL 5 header as
931 well. The translation of the user-requested LimitOn Delay is
932 preserved as long as the delay computation is based on the CPCS-SDU
933 size instead of the PDU size.
934
935 In addition to the end to end delay introduced by the ATM network,
936 there is additional delay created by the fragmentation of packets.
937 Reassembly of these packets can only be accomplished at the rate at
938 which they are received. The time (in milliseconds) required to
939 receive a cell (inter-cell arrival time) is:
940
941 T = 1000 / PCR.
942
943
944
945
946
947
948 <span class="grey">Jackowski Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
951
952
953 The number of cells in a CPCS-SDU is:
954
955 C = (CPCS-SDUsize + 48) / 48.
956
957 Thus the delay for a packet is:
958
959 LimitonDelay = (C - 1) * T + MaxCellTransitDelay.
960
961 Therefore, the requested Maximum End to End Transit delay is:
962
963 MaxCellTransitDelay = Limiton Delay - (C-1) * T.
964
965 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a> Maximum Bit Error Rate</span>
966
967 Q.2931 signaling does not offer the ability to directly specify the
968 requested bit error rate or a corresponding cell error rate.
969 Instead, this service is supposed to be offered through selection of
970 QoS class.
971
972 Since these classes have few actual implementations, at this time,
973 there is no effective mapping for bit error rate.
974
975 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a> Accumulated Mean Delay</span>
976
977 ST allows accumulation of the Mean Delay generated by each ST agent
978 node and intervening circuits. With an ATM circuit each agent should
979 factor in the overhead of the ATM connection. The delay associated
980 with the ATM circuit is reflected in the Q.2931 CONNECT message as
981 the Cummulative Transit Delay. Since this is a cell-based
982 computation, the delay experienced for an ST packet, including the
983 CPCS-SDU header and ST header is, as computed in <a href="#section-5.3">Section 5.3</a>:
984
985 Delay = (C - 1) * T + CummulativeTransit Delay.
986
987 <span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a> Accumulated Delay Variance (Jitter)</span>
988
989 Cell Delay Variance is not currently available as a Q.2931 parameter.
990
991 Thus, we can assume that the reassembly of cells into packets will
992 be consistent, since the cell transmission rate should be constant
993 for each packet. As such, except as noted by the specific ATM
994 service, the ST agent should use its standard mechanisms for tracking
995 packet arrival times and use this for Accumulated Delay Variance.
996
997 <span class="h3"><a class="selflink" id="section-6.0" href="#section-6.0">6.0</a> Data Stream Transmission</span>
998
999 Once virtual circuits for data transmission are established though
1000 one of the mechanisms described in <a href="#section-4">section 4</a>, the ST data must be
1001
1002
1003
1004 <span class="grey">Jackowski Informational [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
1007
1008
1009 transmitted over the connection. <a href="./rfc1483">RFC 1483</a> describes mechanisms for
1010 encapsulating packet transmissions over AAL5. While the LLC
1011 encapsulation could be used, it is not necessary. If it is used, the
1012 computations in <a href="#section-5">section 5</a> should be redone to include the LLC headers
1013 in addition to the AAL5 trailer currently used. These new values
1014 should be substituted for the QoS values in the SETUP message.
1015
1016 Instead, ST data packets can be encapsulated in standard AAL5 format
1017 with an 8 byte trailer and sent directly over the data virtual
1018 circuit. The mechanisms for computing the QoS values in the SETUP
1019 message are described in <a href="#section-5">section 5</a>.
1020
1021 <span class="h3"><a class="selflink" id="section-7.0" href="#section-7.0">7.0</a> Implementation Experience and Conclusions</span>
1022
1023 All of the signaling mechanisms described in <a href="#section-4">Section 4</a> were
1024 implemented and tested in a mixed ATM network/routed LAN environment.
1025
1026 Initially it appeared that the best approach was to do signaling via
1027 IP over ATM or LANE. However, because it required IP encapsulation
1028 of the SCMP packets (for IP over ATM), and because some applications
1029 use the accumulated values in the flowspecs (which are not guaranteed
1030 to be accurate in LANE and IP/ATM), using virtual circuits dedicated
1031 to SCMP signaling turned out to be the best implementation for
1032 taking full advantage of the ATM features.
1033
1034 Also, the issue of mapping ATM address to E.164 NSAP addresses was
1035 resolved through an external signaling mechanism (the User Data field
1036 of the ST-2 CONNECT and ACCEPT messages). It appears that ATM
1037 vendors need to implement a consistent addressing mechanism
1038 throughout their interfaces.
1039
1040 From a performance point of view, using ST over ATM provided more
1041 than triple the performance of raw IP. The differences became
1042 increasingly clear as more simultaneous applications were run. This
1043 resulted in dedicated virtual circuits for the ST traffic while the
1044 IP traffic suffered (saw inconsistent performance) over shared
1045 circuits. Even more dramatic were results in mixed network
1046 environments where all traffic shared the same LAN/router
1047 connections, and, when both IP and ST traffic was sent, the ST
1048 traffic maintained its quality while the IP traffic saw increasing
1049 variation in performance.
1050
1051 Clearly, using a connection-oriented, origin-oriented reservation
1052 protocol to provide consistent end-to-end guaranteed QoS and
1053 bandwidth in mixed ATM/internet environments is not only feasible, it
1054 results in dramatic performance and quality improvements for
1055 transmission of realtime traffic.
1056
1057
1058
1059
1060 <span class="grey">Jackowski Informational [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
1063
1064
1065 <span class="h3"><a class="selflink" id="section-8.0" href="#section-8.0">8.0</a> Security Considerations</span>
1066
1067 This memo raises no security considerations. However, with their
1068 connection-oriented and origin controlled natures, ST-2 and ST-2+
1069 lend themselves to better internet security. Discussion of this is
1070 beyond the scope of this document.
1071
1072 <span class="h3"><a class="selflink" id="section-9.0" href="#section-9.0">9.0</a> References</span>
1073
1074 [<a id="ref-1">1</a>] Laubach, M., "Classical IP and ARP over ATM", <a href="./rfc1577">RFC 1577</a>, Hewlett
1075 Packard Laboratories, December, 1993.
1076
1077 [<a id="ref-2">2</a>] Borden, M., Crawley, E., Davie, B., and S. Batsell, "Integration
1078 of Real-time Services in an IP-ATM network Architecture", <a href="./rfc1821">RFC</a>
1079 <a href="./rfc1821">1821</a>, August 1995.
1080
1081 [<a id="ref-3">3</a>] Braden, R., Zhang, L., Estrin, D., Herzog, S., and S. Jamin,
1082 "Resource ReSerVation Protocol (RSVP Version 1 Functional
1083 Specification", Work in Progress, November 1995.
1084
1085 [<a id="ref-4">4</a>] Topolcic, C., "Experimental Internet Stream Protocol: Version 2
1086 (ST-II)", <a href="./rfc1190">RFC 1190</a>, October 1990.
1087
1088 [<a id="ref-5">5</a>] DelGrossi, L., and L. Berger, "Internet STream Protocol Version
1089 2+", <a href="./rfc1819">RFC 1819</a>, July 1995.
1090
1091 [<a id="ref-6">6</a>] V. Firoiu, R. Guerin, D. Kandlur, A. Birman "Provisioning of
1092 RSVP-based Services over a Large ATM Network', IBM T.J. Watson
1093 Research Center, October 1995.
1094
1095 [<a id="ref-7">7</a>] S. Damaskos, A. Anastassios Gavras, "Connection Oriented
1096 Protocols over ATM: A Case Study", German National Research
1097 Corporation for Mathematics and Data Processing (GMD) and
1098 Research Centre for Open Communications Systems (FOKUS), February
1099 1994.
1100
1101 [<a id="ref-8">8</a>] Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation
1102 Layer 5", <a href="./rfc1483">RFC 1483</a>, July 1993.
1103
1104 [<a id="ref-9">9</a>] M. Graf, T. Kober, H. Stuttgen, "ST-II over ATM Implementation
1105 Issues", IBM European Networking Center, October 1995.
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Jackowski Informational [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1946">RFC 1946</a> Native ATM Support for ST2+ May 1996</span>
1119
1120
1121 <span class="h3"><a class="selflink" id="section-10.0" href="#section-10.0">10.0</a> Author's Address</span>
1122
1123 Steve Jackowski
1124 NetManage Incorporated
1125 269 Mt. Hermon Road, Suite 201
1126 Scotts Valley, Ca 95066
1127
1128 Phone: (408) 439-6834
1129 Fax: (408) 438-5115
1130 EMail: [email protected]
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 Jackowski Informational [Page 21]
1173 </pre>