Debian Codegraph @

rfc2380.html

raw
1 <pre>Network Working Group L. Berger
2 Request for Comments: 2380 FORE Systems
3 Category: Standards Track August 1998
4
5
6 <span class="h1">RSVP over ATM Implementation Requirements</span>
7
8 Status of this Memo
9
10 This document specifies an Internet standards track protocol for the
11 Internet community, and requests discussion and suggestions for
12 improvements. Please refer to the current edition of the "Internet
13 Official Protocol Standards" (STD 1) for the standardization state
14 and status of this protocol. Distribution of this memo is unlimited.
15
16 Copyright Notice
17
18 Copyright (C) The Internet Society (1998). All Rights Reserved.
19
20 Abstract
21
22 This memo presents specific implementation requirements for running
23 RSVP over ATM switched virtual circuits (SVCs). It presents
24 requirements that ensure interoperability between multiple
25 implementations and conformance to the RSVP and Integrated Services
26 specifications. A separate document [<a href="#ref-5" title="&quot;RSVP over ATM Implementation Guidelines&quot;">5</a>] provides specific guidelines
27 for running over today's ATM networks. The general problem is
28 discussed in [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>]. Integrated Services to ATM service mappings are
29 covered in [<a href="#ref-6" title="&quot;Interoperation of Controlled-Load and Guaranteed-Service with ATM&quot;">6</a>]. The full set of documents present the background and
30 information needed to implement Integrated Services and RSVP over
31 ATM.
32
33 Table of Contents
34
35 <a href="#section-1">1</a>. Introduction ................................................. <a href="#page-2">2</a>
36 <a href="#section-1.1">1.1</a> Terms .................................................... <a href="#page-2">2</a>
37 <a href="#section-1.2">1.2</a> Assumptions .............................................. <a href="#page-3">3</a>
38 <a href="#section-2">2</a>. General RSVP Session Support ................................. <a href="#page-4">4</a>
39 <a href="#section-2.1">2.1</a> RSVP Message VC Usage .................................... <a href="#page-4">4</a>
40 <a href="#section-2.2">2.2</a> VC Initiation ............................................ <a href="#page-4">4</a>
41 <a href="#section-2.3">2.3</a> VC Teardown .............................................. <a href="#page-5">5</a>
42 <a href="#section-2.4">2.4</a> Dynamic QoS .............................................. <a href="#page-6">6</a>
43 <a href="#section-2.5">2.5</a> Encapsulation ............................................ <a href="#page-6">6</a>
44 <a href="#section-3">3</a>. Multicast RSVP Session Support ............................... <a href="#page-7">7</a>
45 <a href="#section-3.1">3.1</a> Data VC Management for Heterogeneous Sessions ............ <a href="#page-7">7</a>
46 <a href="#section-3.2">3.2</a> Multicast End-Point Identification ....................... <a href="#page-8">8</a>
47 <a href="#section-3.3">3.3</a> Multicast Data Distribution .............................. <a href="#page-9">9</a>
48 <a href="#section-3.4">3.4</a> Receiver Transitions ..................................... <a href="#page-11">11</a>
49
50
51
52 <span class="grey">Berger Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
55
56
57 <a href="#section-4">4</a>. Security Considerations ...................................... <a href="#page-11">11</a>
58 <a href="#section-5">5</a>. Acknowledgments .............................................. <a href="#page-11">11</a>
59 <a href="#section-6">6</a>. Author's Address ............................................. <a href="#page-12">12</a>
60 REFERENCES ...................................................... <a href="#page-13">13</a>
61 FULL COPYRIGHT STATEMENT ........................................ <a href="#page-14">14</a>
62
63 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
64
65 This memo discusses running IP over ATM in an environment where SVCs
66 are used to support QoS flows and RSVP is used as the internet level
67 QoS signaling protocol. It applies when using CLIP/ION, LANE2.0 and
68 MPOA [<a href="#ref-4" title="&quot;MPOA Baseline Version 1&quot;">4</a>] methods for supporting IP over ATM. The general issues
69 related to running RSVP [<a href="#ref-8" title="&quot;Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification&quot;">8</a>] over ATM have been covered in several
70 papers including [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>] and other earlier work. This document is
71 intended as a companion to [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>,<a href="#ref-5" title="&quot;RSVP over ATM Implementation Guidelines&quot;">5</a>]. The reader should be familiar with
72 both documents.
73
74 This document defines the specific requirements for implementations
75 using ATM UNI3.x and 4.0. These requirements must be adhered to by
76 all RSVP over ATM implementations to ensure interoperability.
77 Further recommendations to guide implementers of RSVP over ATM are
78 provided in [<a href="#ref-5" title="&quot;RSVP over ATM Implementation Guidelines&quot;">5</a>].
79
80 The rest of this section will define terms and assumptions. <a href="#section-2">Section 2</a>
81 will cover implementation guidelines common to all RSVP session.
82 <a href="#section-3">Section 3</a> will cover implementation guidelines specific to multicast
83 sessions.
84
85 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Terms</span>
86
87 The terms "reservation" and "flow" are used in many contexts, often
88 with different meaning. These terms are used in this document with
89 the following meaning:
90
91 o Reservation is used in this document to refer to an RSVP
92 initiated request for resources. RSVP initiates requests for
93 resources based on RESV message processing. RESV messages that
94 simply refresh state do not trigger resource requests. Resource
95 requests may be made based on RSVP sessions and RSVP reservation
96 styles. RSVP styles dictate whether the reserved resources are
97 used by one sender or shared by multiple senders. See [<a href="#ref-8" title="&quot;Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification&quot;">8</a>] for
98 details of each. Each new request is referred to in this
99 document as an RSVP reservation, or simply reservation.
100
101
102
103
104
105
106
107
108 <span class="grey">Berger Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
111
112
113 o Flow is used to refer to the data traffic associated with a
114 particular reservation. The specific meaning of flow is RSVP
115 style dependent. For shared style reservations, there is one
116 flow per session. For distinct style reservations, there is one
117 flow per sender (per session).
118
119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
121 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-7" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">7</a>].
122
123 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a> Assumptions</span>
124
125 The following assumptions are made:
126
127 o RSVP
128
129 We assume RSVP as the internet signaling protocol which is
130 described in [<a href="#ref-8" title="&quot;Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification&quot;">8</a>]. The reader is assumed to be familiar with
131 [<a href="#ref-8" title="&quot;Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification&quot;">8</a>].
132
133 o IPv4 and IPv6
134
135 RSVP support has been defined for both IPv4 and IPv6. The
136 guidelines in this document are intended to be used to support
137 RSVP with either IPv4 or IPv6. This document does not require
138 one version over the other.
139
140 o Best effort service model
141
142 The current Internet only supports best effort service. We
143 assume that as additional components of the Integrated Services
144 model are defined, best effort service must continue to be
145 supported.
146
147 o ATM UNI 3.x and 4.0
148
149 We assume ATM service as defined by UNI 3.x and 4.0. ATM
150 provides both point-to-point and point-to-multipoint Virtual
151 Circuits (VCs) with a specified Quality of Service (QoS). ATM
152 provides both Permanent Virtual Circuits (PVCs) and Switched
153 Virtual Circuits (SVCs). In the Permanent Virtual Circuit (PVC)
154 environment, PVCs are typically used as point-to-point link
155 replacements. So the support issues are similar to point-to-
156 point links. This memo assumes that SVCs are used to support
157 RSVP over ATM.
158
159
160
161
162
163
164 <span class="grey">Berger Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
167
168
169 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. General RSVP Session Support</span>
170
171 This section provides implementation requirements that are common for
172 all (both unicast and multicast) RSVP sessions. The section covers
173 VC usage, QoS VC initiation, VC teardown, handling requested changes
174 in QoS, and encapsulation.
175
176 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> RSVP Message VC Usage</span>
177
178 There are several RSVP Message VC Usage options available to
179 implementers. Implementers must select which VC to use for RSVP
180 messages and how to aggregate RSVP sessions over QoS VCs. These
181 options have been covered in [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>] and some specific implementation
182 guidelines are stated in [<a href="#ref-5" title="&quot;RSVP over ATM Implementation Guidelines&quot;">5</a>]. In order to ensure interoperability
183 between implementations that follow different options, RSVP over ATM
184 implementations MUST NOT send RSVP (control) messages on the same QoS
185 VC as RSVP associated data packets. RSVP over ATM implementations
186 MAY send RSVP messages on either the best effort data path or on a
187 separate control VC.
188
189 Since RSVP (control) messages and RSVP associated data packets are
190 not sent on the same VCs, it is possible for a VC supporting one type
191 of traffic to fail while the other remains in place. When the VC
192 associated with data packets fails and cannot be reestablished, RSVP
193 SHOULD treat this as an allocation failure. When the VC used to
194 forward RSVP control messages is abnormally released and cannot be
195 reestablished, the RSVP associated QoS VCs MUST also be released.
196 The release of the associated data VCs is required to maintain the
197 synchronization between forwarding and reservation states for the
198 associated data flows.
199
200 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> VC Initiation</span>
201
202 There is an apparent mismatch between RSVP and ATM. Specifically,
203 RSVP control is receiver oriented and ATM control is sender oriented.
204 This initially may seem like a major issue but really is not. While
205 RSVP reservation (RESV) requests are generated at the receiver,
206 actual allocation of resources takes place at the subnet sender.
207
208 For data flows, this means that subnet senders MUST establish all QoS
209 VCs and the RSVP enabled subnet receiver MUST be able to accept
210 incoming QoS VCs. These restrictions are consistent with RSVP
211 version 1 processing rules and allow senders to use different flow to
212 VC mappings and even different QoS renegotiation techniques without
213 interoperability problems. All RSVP over ATM approaches that have
214 VCs initiated and controlled by the subnet senders will interoperate.
215 Figure 1 shows this model of data flow VC initiation.
216
217
218
219
220 <span class="grey">Berger Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
223
224
225 Data Flow ==========&gt;
226
227 +-----+
228 | | --------------&gt; +----+
229 | Src | --------------&gt; | R1 |
230 | *| --------------&gt; +----+
231 +-----+ QoS VCs
232 /\
233 ||
234 VC ||
235 Initiator
236
237 Figure 1: Data Flow VC Initiation
238
239 RSVP over ATM implementations MAY send data in the backwards
240 direction on an RSVP initiated QoS point-to-point VC. When sending
241 in the backwards data path, the sender MUST ensure that the data
242 conforms to the backwards direction traffic parameters. Since the
243 traffic parameters are set by the VC initiator, it is quite likely
244 that no resources will be requested for traffic originating at the
245 called party. It should be noted that the backwards data path is not
246 available with point-to-multipoint VCs.
247
248 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> VC Teardown</span>
249
250 VCs supporting IP over ATM data are typically torndown based on
251 inactivity timers. This mechanism is used since IP is connectionless
252 and there is therefore no way to know when a VC is no longer needed.
253 Since RSVP provides explicit mechanisms (messages and timeouts) to
254 determine when an associated data VC is no longer needed, the
255 traditional VC timeout mechanisms are not needed. Additionally, under
256 normal operations RSVP implementations expect to be able to allocate
257 resources and have those resources remain allocated until released at
258 the direction of RSVP. Therefore, data VCs set up to support RSVP
259 controlled flows should only be released at the direction of RSVP.
260 Such VCs must not be timed out due to inactivity by either the VC
261 initiator or the VC receiver. This conflicts with VCs timing out as
262 described in <a href="./rfc1755">RFC 1755</a> [<a href="#ref-11" title="&quot;ATM Signalling Support for IP over ATM&quot;">11</a>], section 3.4 on VC Teardown. <a href="./rfc1755">RFC 1755</a>
263 recommends tearing down a VC that is inactive for a certain length of
264 time. Twenty minutes is recommended. This timeout is typically
265 implemented at both the VC initiator and the VC receiver. Although,
266 <a href="#section-3.1">section 3.1</a> of the update to <a href="./rfc1755">RFC 1755</a> [<a href="#ref-12" title="&quot;ATM Signalling Support for IP over ATM - UNI 4.0 Update&quot;">12</a>] states that inactivity
267 timers must not be used at the VC receiver.
268
269 In RSVP over ATM implementations, the configurable inactivity timer
270 mentioned in [<a href="#ref-11" title="&quot;ATM Signalling Support for IP over ATM&quot;">11</a>] MUST be set to "infinite" for VCs initiated at the
271 request of RSVP. Setting the inactivity timer value at the VC
272 initiator should not be problematic since the proper value can be
273
274
275
276 <span class="grey">Berger Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
279
280
281 relayed internally at the originator. Setting the inactivity timer
282 at the VC receiver is more difficult, and would require some
283 mechanism to signal that an incoming VC was RSVP initiated. To avoid
284 this complexity and to conform to [<a href="#ref-12" title="&quot;ATM Signalling Support for IP over ATM - UNI 4.0 Update&quot;">12</a>], RSVP over ATM implementations
285 MUST not use an inactivity timer to clear any received connections.
286
287 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Dynamic QoS</span>
288
289 As stated in [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>], there is a mismatch in the service provided by RSVP
290 and that provided by ATM UNI3.x and 4.0. RSVP allows modifications
291 to QoS parameters at any time while ATM does not support any
292 modifications to QoS parameters post VC setup. See [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>] for more
293 detail.
294
295 The method for supporting changes in RSVP reservations is to attempt
296 to replace an existing VC with a new appropriately sized VC. During
297 setup of the replacement VC, the old VC MUST be left in place
298 unmodified. The old VC is left unmodified to minimize interruption of
299 QoS data delivery. Once the replacement VC is established, data
300 transmission is shifted to the new VC, and only then is the old VC
301 closed.
302
303 If setup of the replacement VC fails, then the old QoS VC MUST
304 continue to be used. When the new reservation is greater than the
305 old reservation, the reservation request MUST be answered with an
306 error. When the new reservation is less than the old reservation, the
307 request MUST be treated as if the modification was successful. While
308 leaving the larger allocation in place is suboptimal, it maximizes
309 delivery of service to the user. The behavior is also required in
310 order to conform to RSVP error handling as defined in sections <a href="#section-2.5">2.5</a>,
311 3.1.8 and 3.11.2 of [<a href="#ref-8" title="&quot;Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification&quot;">8</a>]. Implementations SHOULD retry replacing a
312 too large VC after some appropriate elapsed time.
313
314 One additional issue is that only one QoS change can be processed at
315 one time per reservation. If the (RSVP) requested QoS is changed
316 while the first replacement VC is still being setup, then the
317 replacement VC SHOULD BE released and the whole VC replacement
318 process is restarted. Implementations MAY also limit number of
319 changes processed in a time period per [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>].
320
321 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a> Encapsulation</span>
322
323 There are multiple encapsulation options for data sent over RSVP
324 triggered QoS VCs. All RSVP over ATM implementations MUST be able to
325 support LLC encapsulation per <a href="./rfc1483">RFC 1483</a> [<a href="#ref-10" title="&quot;Multiprotocol Encapsulation over ATM Adaptation Layer 5&quot;">10</a>] on such QoS VCs.
326 Implementations MAY negotiate alternative encapsulations using the
327 B-LLI negotiation procedures defined in ATM Signalling, see [<a href="#ref-11" title="&quot;ATM Signalling Support for IP over ATM&quot;">11</a>] for
328
329
330
331
332 <span class="grey">Berger Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
335
336
337 details. When a QoS VC is only being used to carry IP packets,
338 implementations SHOULD negotiate VC based multiplexing to avoid
339 incurring the overhead of the LLC header.
340
341 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Multicast RSVP Session Support</span>
342
343 There are several aspects to running RSVP over ATM that are unique to
344 multicast sessions. This section addresses multicast end-point
345 identification, multicast data distribution, multicast receiver
346 transitions and next-hops requesting different QoS values
347 (heterogeneity) which includes the handling of multicast best effort
348 receivers. Handling of best effort receivers is not strictly an RSVP
349 issue, but needs to be addressed by any RSVP over ATM implementation
350 in order to maintain expected best effort internet service.
351
352 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Data VC Management for Heterogeneous Sessions</span>
353
354 The issues relating to data VC management of heterogeneous sessions
355 are covered in detail in [<a href="#ref-9" title="&quot;A Framework for Integrated Services and RSVP over ATM&quot;">9</a>]. In summary, heterogeneity occurs when
356 receivers request different levels of QoS within a single session,
357 and also when some receivers do not request any QoS. Both types of
358 heterogeneity are shown in figure 2.
359
360 +----+
361 +------&gt; | R1 |
362 | +----+
363 |
364 | +----+
365 +-----+ -----+ +--&gt; | R2 |
366 | | ---------+ +----+ Receiver Request Types:
367 | Src | ----&gt; QoS 1 and QoS 2
368 | | .........+ +----+ ....&gt; Best-Effort
369 +-----+ .....+ +..&gt; | R3 |
370 : +----+
371 /\ :
372 || : +----+
373 || +......&gt; | R4 |
374 || +----+
375 Single
376 IP Mulicast
377 Group
378
379 Figure 2: Types of Multicast Receivers
380
381 [<a id="ref-9">9</a>] provides four models for dealing with heterogeneity: full
382 heterogeneity, limited heterogeneity, homogeneous, and modified
383 homogeneous models. No matter which model or combination of models
384 is used by an implementation, implementations MUST NOT normally send
385
386
387
388 <span class="grey">Berger Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
391
392
393 more than one copy of a particular data packet to a particular next-
394 hop (ATM end-point). Some transient duplicate transmission is
395 acceptable, but only during VC setup and transition.
396
397 Implementations MUST also ensure that data traffic is sent to best
398 effort receivers. Data traffic MAY be sent to best effort receivers
399 via best effort or QoS VCs as is appropriate for the implemented
400 model. In all cases, implementations MUST NOT create VCs in such a
401 way that data cannot be sent to best effort receivers. This includes
402 the case of not being able to add a best effort receiver to a QoS VC,
403 but does not include the case where best effort VCs cannot be setup.
404 The failure to establish best effort VCs is considered to be a
405 general IP over ATM failure and is therefore beyond the scope of this
406 document.
407
408 There is an interesting interaction between dynamic QoS and
409 heterogeneous requests when using the limited heterogeneity,
410 homogeneous, or modified homogeneous models. In the case where a
411 RESV message is received from a new next-hop and the requested
412 resources are larger than any existing reservation, both dynamic QoS
413 and heterogeneity need to be addressed. A key issue is whether to
414 first add the new next-hop or to change to the new QoS. This is a
415 fairly straight forward special case. Since the older, smaller
416 reservation does not support the new next-hop, the dynamic QoS
417 process SHOULD be initiated first. Since the new QoS is only needed
418 by the new next-hop, it SHOULD be the first end-point of the new VC.
419 This way signaling is minimized when the setup to the new next-hop
420 fails.
421
422 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Multicast End-Point Identification</span>
423
424 Implementations must be able to identify ATM end-points participating
425 in an IP multicast group. The ATM end-points will be IP multicast
426 receivers and/or next-hops. Both QoS and best effort end-points must
427 be identified. RSVP next-hop information will usually provide QoS
428 end-points, but not best effort end-points.
429
430 There is a special case where RSVP next-hop information will not
431 provide the appropriate end-points. This occurs when a next-hop is
432 not RSVP capable and RSVP is being automatically tunneled. In this
433 case a PATH message travels through a non-RSVP egress router on the
434 way to the next-hop RSVP node. When the next-hop RSVP node sends a
435 RESV message it may arrive at the source via a different route than
436 used by the PATH message. The source will get the RESV message, but
437 will not know which ATM end-point should be associated with the
438 reservation. For unicast sessions, there is no problem since the ATM
439 end-point will be the IP next-hop router. There is a problem with
440
441
442
443
444 <span class="grey">Berger Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
447
448
449 multicast, since multicast routing may not be able to uniquely
450 identify the IP next-hop router. It is therefore possible for a
451 multicast end-point to not be properly identified.
452
453 In certain cases it is also possible to identify the list of all best
454 effort end-points. Some multicast over ATM control mechanisms, such
455 as MARS in mesh mode, can be used to identify all end-points of a
456 multicast group. Also, some multicast routing protocols can provide
457 all next-hops for a particular multicast group. In both cases, RSVP
458 over ATM implementations can obtain a full list of end-points, both
459 QoS and non-QoS, using the appropriate mechanisms. The full list can
460 then be compared against the RSVP identified end-points to determine
461 the list of best effort receivers.
462
463 While there are cases where QoS and best effort end-points can be
464 identified, there is no straightforward solution to uniquely
465 identifying end-points of multicast traffic handled by non-RSVP
466 next-hops. The preferred solution is to use multicast control
467 mechanisms and routing protocols that support unique end-point
468 identification. In cases where such mechanisms and routing protocols
469 are unavailable, all IP routers that will be used to support RSVP
470 over ATM should support RSVP. To ensure proper behavior, baseline
471 RSVP over ATM implementations MUST only establish RSVP-initiated VCs
472 to RSVP capable end-points. It is permissible to allow a user to
473 override this behavior.
474
475 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Multicast Data Distribution</span>
476
477 Two basic models exist for IP multicast data distribution over ATM.
478 In one model, senders establish point-to-multipoint VCs to all ATM
479 attached destinations, and data is then sent over these VCs. This
480 model is often called "multicast mesh" or "VC mesh" mode
481 distribution. In the second model, senders send data over point-to-
482 point VCs to a central point and the central point relays the data
483 onto point-to-multipoint VCs that have been established to all
484 receivers of the IP multicast group. This model is often referred to
485 as "multicast server" mode distribution. Figure 3 shows data flow for
486 both modes of IP multicast data distribution.
487
488
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Berger Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
503
504
505 _________
506 / \
507 / Multicast \
508 \ Server /
509 \_________/
510 ^ | |
511 | | +--------+
512 +-----+ | | |
513 | | -------+ | | Data Flow:
514 | Src | ...+......|....+ V ----&gt; Server
515 | | : | : +----+ ....&gt; Mesh
516 +-----+ : | +...&gt;| R1 |
517 : | +----+
518 : V
519 : +----+
520 +..&gt; | R2 |
521 +----+
522
523 Figure 3: IP Multicast Data Distribution Over ATM
524
525 The goal of RSVP over ATM solutions is to ensure that IP multicast
526 data is distributed with appropriate QoS. Current multicast servers
527 [<a href="#ref-1" title="&quot;Support for Multicast over UNI 3.0/3.1 based ATM Networks,&quot;">1</a>,<a href="#ref-2" title="&quot;LAN Emulation Over ATM Specification&quot;">2</a>] do not support any mechanisms for communicating QoS
528 requirements to a multicast server. For this reason, RSVP over ATM
529 implementations SHOULD support "mesh-mode" distribution for RSVP
530 controlled multicast flows. When using multicast servers that do not
531 support QoS requests, a sender MUST set the service, not global,
532 break bit(s). Use of the service-specific break bit tells the
533 receiver(s) that RSVP and Integrated Services are supported by the
534 router but that the service cannot be delivered over the ATM network
535 for the specific request.
536
537 In the case of MARS [<a href="#ref-1" title="&quot;Support for Multicast over UNI 3.0/3.1 based ATM Networks,&quot;">1</a>], the selection of distribution modes is
538 administratively controlled. Therefore network administrators that
539 desire proper RSVP over ATM operation MUST appropriately configure
540 their network to support mesh mode distribution for multicast groups
541 that will be used in RSVP sessions. For LANE1.0 networks the only
542 multicast distribution option is over the LANE Broadcast and Unknown
543 Server which means that the break bit MUST always be set. For
544 LANE2.0 [<a href="#ref-3" title="&quot;LAN Emulation over ATM Version 2 - LUNI Specification&quot;">3</a>] there are provisions that allow for non-server solutions
545 with which it may be possible to ensure proper QoS delivery.
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Berger Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
559
560
561 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Receiver Transitions</span>
562
563 When setting up a point-to-multipoint VCs there will be a time when
564 some receivers have been added to a QoS VC and some have not.
565
566 During such transition times it is possible to start sending data on
567 the newly established VC. If data is sent both on the new VC and the
568 old VC, then data will be delivered with proper QoS to some receivers
569 and with the old QoS to all receivers. Additionally, the QoS
570 receivers would get duplicate data. If data is sent just on the new
571 QoS VC, the receivers that have not yet been added will miss data.
572 So, the issue comes down to whether to send to both the old and new
573 VCs, or to just send to one of the VCs. In one case duplicate data
574 will be received, in the other some data may not be received. This
575 issue needs to be considered for three cases: when establishing the
576 first QoS VC, when establishing a VC to support a QoS change, and
577 when adding a new end-point to an already established QoS VC.
578
579 The first two cases are essentially the same. In both, it is
580 possible to send data on the partially completed new VC. In both,
581 there is the option of duplicate or lost data. In order to ensure
582 predictable behavior and to conform to the requirement to deliver
583 data to all receivers, data MUST NOT be sent on new VCs until all
584 parties have been added. This will ensure that all data is only
585 delivered once to all receivers.
586
587 The last case differs from the others and occurs when an end-point
588 must be added to an existing QoS VC. In this case the end-point must
589 be both added to the QoS VC and dropped from a best effort VC. The
590 issue is which to do first. If the add is first requested, then the
591 end-point may get duplicate data. If the drop is requested first,
592 then the end-point may miss data. In order to avoid loss of data,
593 the add MUST be completed first and then followed by the drop. This
594 behavior requires receivers to be prepared to receive some duplicate
595 packets at times of QoS setup.
596
597 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
598
599 The same considerations stated in [<a href="#ref-8" title="&quot;Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification&quot;">8</a>] and [<a href="#ref-11" title="&quot;ATM Signalling Support for IP over ATM&quot;">11</a>] apply to this
600 document. There are no additional security issues raised in this
601 document.
602
603 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
604
605 This work is based on earlier drafts and comments from the ISSLL
606 working group. The author would like to acknowledge their
607 contribution, most notably Steve Berson who coauthored one of the
608 drafts.
609
610
611
612 <span class="grey">Berger Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
615
616
617 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Author's Address</span>
618
619 Lou Berger
620 FORE Systems
621 1595 Spring Hill Road
622 5th Floor
623 Vienna, VA 22182
624
625 Phone: +1 703-245-4527
626 EMail: [email protected]
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Berger Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
671
672
673 REFERENCES
674
675 [<a id="ref-1">1</a>] Armitage, G., "Support for Multicast over UNI 3.0/3.1 based ATM
676 Networks," <a href="./rfc2022">RFC 2022</a>, November 1996.
677
678 [<a id="ref-2">2</a>] The ATM Forum, "LAN Emulation Over ATM Specification", Version
679 1.0.
680
681 [<a id="ref-3">3</a>] The ATM Forum, "LAN Emulation over ATM Version 2 - LUNI
682 Specification", April 1997.
683
684 [<a id="ref-4">4</a>] The ATM Forum, "MPOA Baseline Version 1", May 1997.
685
686 [<a id="ref-5">5</a>] Berger, L., "RSVP over ATM Implementation Guidelines", <a href="https://www.rfc-editor.org/bcp/bcp24">BCP 24</a>,
687 <a href="./rfc2379">RFC 2379</a>, August 1998.
688
689 [<a id="ref-6">6</a>] Borden, M., and M. Garrett, "Interoperation of Controlled-Load
690 and Guaranteed-Service with ATM", <a href="./rfc2381">RFC 2381</a>, August 1998.
691
692 [<a id="ref-7">7</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
693 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
694
695 [<a id="ref-8">8</a>] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. Jamin,
696 "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional
697 Specification", <a href="./rfc2205">RFC 2205</a>, September 1997.
698
699 [<a id="ref-9">9</a>] Crawley, E., Berger, L., Berson, S., Baker, F., Borden, M., and
700 J. Krawczyk, "A Framework for Integrated Services and RSVP over
701 ATM", <a href="./rfc2382">RFC 2382</a>, August 1998.
702
703 [<a id="ref-10">10</a>] Heinanen, J., "Multiprotocol Encapsulation over ATM Adaptation
704 Layer 5", <a href="./rfc1483">RFC 1483</a>, July 1993.
705
706 [<a id="ref-11">11</a>] Perez, M., Liaw, F., Grossman, D., Mankin, A., Hoffman, E., and
707 A. Malis, "ATM Signalling Support for IP over ATM", <a href="./rfc1755">RFC 1755</a>,
708 February 1995.
709
710 [<a id="ref-12">12</a>] Maher, M., "ATM Signalling Support for IP over ATM - UNI 4.0
711 Update", <a href="./rfc2331">RFC 2331</a>, April 1998.
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Berger Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2380">RFC 2380</a> RSVP over ATM Implementation Requirements August 1998</span>
727
728
729 Full Copyright Statement
730
731 Copyright (C) The Internet Society (1998). All Rights Reserved.
732
733 This document and translations of it may be copied and furnished to
734 others, and derivative works that comment on or otherwise explain it
735 or assist in its implementation may be prepared, copied, published
736 and distributed, in whole or in part, without restriction of any
737 kind, provided that the above copyright notice and this paragraph are
738 included on all such copies and derivative works. However, this
739 document itself may not be modified in any way, such as by removing
740 the copyright notice or references to the Internet Society or other
741 Internet organizations, except as needed for the purpose of
742 developing Internet standards in which case the procedures for
743 copyrights defined in the Internet Standards process must be
744 followed, or as required to translate it into languages other than
745 English.
746
747 The limited permissions granted above are perpetual and will not be
748 revoked by the Internet Society or its successors or assigns.
749
750 This document and the information contained herein is provided on an
751 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
752 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
753 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
754 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
755 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780 Berger Standards Track [Page 14]
781 </pre>