Debian Codegraph @

rfc5640.html

raw
1 <pre>Network Working Group C. Filsfils
2 Request for Comments: 5640 P. Mohapatra
3 Category: Standards Track C. Pignataro
4 Cisco Systems
5 August 2009
6
7
8 <span class="h1">Load-Balancing for Mesh Softwires</span>
9
10 Abstract
11
12 Payloads transported over a Softwire mesh service (as defined by BGP
13 Encapsulation Subsequent Address Family Identifier (SAFI) information
14 exchange) often carry a number of identifiable, distinct flows. It
15 can, in some circumstances, be desirable to distribute these flows
16 over the equal cost multiple paths (ECMPs) that exist in the packet
17 switched network. Currently, the payload of a packet entering the
18 Softwire can only be interpreted by the ingress and egress routers.
19 Thus, the load-balancing decision of a core router is only based on
20 the encapsulating header, presenting much less entropy than available
21 in the payload or the encapsulated header since the Softwire
22 encapsulation acts in a tunneling fashion. This document describes a
23 method for achieving comparable load-balancing efficiency in a
24 network carrying Softwire mesh service over Layer Two Tunneling
25 Protocol - Version 3 (L2TPv3) over IP or Generic Routing
26 Encapsulation (GRE) encapsulation to what would be achieved without
27 such encapsulation.
28
29 Status of This Memo
30
31 This document specifies an Internet standards track protocol for the
32 Internet community, and requests discussion and suggestions for
33 improvements. Please refer to the current edition of the "Internet
34 Official Protocol Standards" (STD 1) for the standardization state
35 and status of this protocol. Distribution of this memo is unlimited.
36
37 Copyright Notice
38
39 Copyright (c) 2009 IETF Trust and the persons identified as the
40 document authors. All rights reserved.
41
42 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
43 Provisions Relating to IETF Documents in effect on the date of
44 publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
45 Please review these documents carefully, as they describe your rights
46 and restrictions with respect to this document.
47
48
49
50
51
52 <span class="grey">Filsfils, et al. 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="./rfc5640">RFC 5640</a> Load-Balancing for Mesh Softwires August 2009</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
60 <a href="#section-1.1">1.1</a>. Requirements Language . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
61 <a href="#section-2">2</a>. Load-Balancing Block sub-TLV . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
62 <a href="#section-2.1">2.1</a>. Applicability to Tunnel Types . . . . . . . . . . . . . . . <a href="#page-3">3</a>
63 <a href="#section-2.2">2.2</a>. Encapsulation Considerations . . . . . . . . . . . . . . . <a href="#page-4">4</a>
64 <a href="#section-3">3</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
65 <a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
66 <a href="#section-5">5</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
67 <a href="#section-6">6</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
68
69 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
70
71 Consider the case of a router R1 that encapsulates a packet P into a
72 Softwire bound to router R3. R2 is a router on the shortest path
73 from R1 to R3. R2's shortest path to R3 involves equal cost multiple
74 paths (ECMPs). The goal is for R2 to be able to choose which path to
75 use on the basis of the full entropy of packet P.
76
77 This is achieved by carrying in the encapsulation header a signature
78 of the inner header, hence enhancing the entropy of the flows as seen
79 by the core routers. The signature is carried as part of one of the
80 fields of the encapsulation header. To aid with better description
81 in the document, we define the generic term "load-balancing field" to
82 mean such a value that is specific to an encapsulation type. For
83 example, for L2TPv3-over-IP [<a href="./rfc3931" title="&quot;Layer Two Tunneling Protocol - Version 3 (L2TPv3)&quot;">RFC3931</a>] encapsulation, the load-
84 balancing field is the Session Identifier (Session ID). For GRE
85 [<a href="./rfc2784" title="&quot;Generic Routing Encapsulation (GRE)&quot;">RFC2784</a>] encapsulation, the Key field [<a href="./rfc2890" title="&quot;Key and Sequence Number Extensions to GRE&quot;">RFC2890</a>], if present,
86 represents the load-balancing field. This mechanism assumes that
87 core routers base their load-balancing decisions on a flow definition
88 that includes the load-balancing field. This is an obvious and
89 generic functionality as, for example, for L2TPv3-over-IP tunnels,
90 the Session ID is at the same well-known constant offset as the TCP/
91 UDP ports in the encapsulating header.
92
93 The Encapsulation SAFI [<a href="./rfc5512" title="&quot;The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute&quot;">RFC5512</a>] is extended such that a contiguous
94 block of the load-balancing field is bound to the Softwire advertised
95 by a BGP next-hop. On a per-inner-flow basis, the ingress Provider
96 Edge (PE) selects one value of the load-balancing field from the
97 block to preserve per-flow ordering and, at the same time, to enhance
98 the entropy across flows.
99
100 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
101
102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
104 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
105
106
107
108 <span class="grey">Filsfils, et al. 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="./rfc5640">RFC 5640</a> Load-Balancing for Mesh Softwires August 2009</span>
111
112
113 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Load-Balancing Block sub-TLV</span>
114
115 This document defines a new sub-TLV for use with the Tunnel
116 Encapsulation Attribute defined in [<a href="./rfc5512" title="&quot;The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute&quot;">RFC5512</a>]. The new sub-TLV is
117 referred to as the "Load-Balancing Block sub-TLV" and MAY be included
118 in any Encapsulation SAFI UPDATE message where load-balancing is
119 desired.
120
121 The sub-TLV type of the Load-Balancing Block sub-TLV is 5. The sub-
122 TLV length is 2 octets. The value represents the length of the block
123 in bits and MUST NOT exceed the size of the load-balancing field.
124 This format is very similar to the variable-length subnet masking
125 (VLSM) used in IP addresses to allow arbitrary length prefixes. The
126 block is determined by extracting the initial sequence of 'block
127 size' bits from the load-balancing field.
128
129 If a load-balancing field is not signaled (e.g., if the encapsulation
130 sub-TLV is not included in an advertisement as in the case of GRE
131 without a Key), then the Load-Balancing Block sub-TLV MUST NOT be
132 included.
133
134 The smaller the value field of the Load-Balancing Block sub-TLV, the
135 larger the space for per-flow identification, and hence the better
136 entropy for potential load-balancing in the core, as well as, the
137 lower the polarization when mapping flows to ECMP paths. However,
138 reducing the load-balancing block size consumes more L2TPv3 Session
139 IDs or GRE Keys, resulting in potentially less numbers of supported
140 services. A typical deployment would need to arbitrate between this
141 trade-off.
142
143 As an example, assume that there is a Softwire set up between R1 and
144 R3 with L2TPv3-over-IP tunnel type. Assume that R3 encodes the
145 Session ID with value 0x1234ABCD in the encapsulation sub-TLV. It
146 also includes the Load-Balancing Block sub-TLV and encodes the value
147 24. This should be interpreted as follows:
148
149 o If an ingress router does not understand the Load-Balancing Block
150 sub-TLV, it continues to use the Session ID 0x1234ABCD and
151 encapsulates all packets with that Session ID.
152
153 o If an ingress router understands the Load-Balancing Block sub-TLV,
154 it picks the first 24 bits out of the Session ID (0x1234AB) to be
155 used as the block and fills in the lower-order 8 bits with a per-
156 flow identifier (e.g., it can be determined based on the inner
157 packet's source, destination addresses, and TCP/UDP ports). This
158 selection preserves the per-flow ordering of packets.
159
160
161
162
163
164 <span class="grey">Filsfils, et al. 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="./rfc5640">RFC 5640</a> Load-Balancing for Mesh Softwires August 2009</span>
167
168
169 This requirement and solution applies equally to GRE where the Key
170 plays the same role as the Session ID in L2TPv3.
171
172 Needless to say, if an egress router does not support the Load-
173 Balancing Block sub-TLV, the Softwire continues to operate with a
174 single load-balancing field with which all ingress routers
175 encapsulate.
176
177 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Applicability to Tunnel Types</span>
178
179 The Load-Balancing Block sub-TLV is applicable to tunnel types that
180 define a load-balancing field. This document defines load-balancing
181 fields for tunnel types 1 (L2TPv3 over IP) and 2 (GRE) as follows:
182
183 o L2TPv3 over IP - Session ID. Special care needs to be taken to
184 always create a non-zero Session ID. When an egress router
185 includes a Load-Balancing Block sub-TLV, it MUST encode the
186 Session ID field of the encapsulation sub-TLV in a way that
187 ensures that the most significant bits of the Session ID, after
188 extracting the block, are non-zero.
189
190 o GRE - GRE Key
191
192 This document does not define a load-balancing field for the IP-in-IP
193 tunnel type (tunnel types 7). Future tunnel types that desire to use
194 the Load-Balancing Block sub-TLV MUST define a load-balancing field
195 that is part of the encapsulating header.
196
197 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Encapsulation Considerations</span>
198
199 Fields included in the encapsulation header besides the load-
200 balancing field are not affected by the Load-Balancing Block sub-TLV.
201 All other encapsulation fields are shared between variations of the
202 load-balancing field. For example, for the L2TPv3-over-IP tunnel
203 type, if the optional cookie is included in the encapsulation sub-TLV
204 by the egress router during Softwire signaling, it applies to all the
205 "Session ID" values derived at the ingress router after applying the
206 load-balancing block as described in this document.
207
208 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
209
210 IANA has assigned the value 5 for the Load-Balancing Block sub-TLV,
211 in the BGP Tunnel Encapsulation Attribute Sub-TLVs registry (number
212 space created as part of the publication of [<a href="./rfc5512" title="&quot;The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute&quot;">RFC5512</a>]):
213
214 Sub-TLV name Value
215 ------------- -----
216 Load-Balancing Block 5
217
218
219
220 <span class="grey">Filsfils, et al. 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="./rfc5640">RFC 5640</a> Load-Balancing for Mesh Softwires August 2009</span>
223
224
225 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
226
227 This document defines a new sub-TLV for the BGP Tunnel Encapsulation
228 Attribute. Security considerations for the BGP Encapsulation SAFI
229 and the BGP Tunnel Encapsulation Attribute are covered in [<a href="./rfc5512" title="&quot;The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute&quot;">RFC5512</a>].
230 There are no additional security risks introduced by this design.
231
232 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
233
234 The authors would like to thank Stewart Bryant, Mark Townsley, Rajiv
235 Asati, Kireeti Kompella, and Robert Raszuk for their review and
236 comments.
237
238 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
239
240 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
241 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
242
243 [<a id="ref-RFC2784">RFC2784</a>] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
244 Traina, "Generic Routing Encapsulation (GRE)", <a href="./rfc2784">RFC 2784</a>,
245 March 2000.
246
247 [<a id="ref-RFC2890">RFC2890</a>] Dommety, G., "Key and Sequence Number Extensions to GRE",
248 <a href="./rfc2890">RFC 2890</a>, September 2000.
249
250 [<a id="ref-RFC3931">RFC3931</a>] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling
251 Protocol - Version 3 (L2TPv3)", <a href="./rfc3931">RFC 3931</a>, March 2005.
252
253 [<a id="ref-RFC5512">RFC5512</a>] Mohapatra, P. and E. Rosen, "The BGP Encapsulation
254 Subsequent Address Family Identifier (SAFI) and the BGP
255 Tunnel Encapsulation Attribute", <a href="./rfc5512">RFC 5512</a>, April 2009.
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Filsfils, et al. 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="./rfc5640">RFC 5640</a> Load-Balancing for Mesh Softwires August 2009</span>
279
280
281 Authors' Addresses
282
283 Clarence Filsfils
284 Cisco Systems
285 Brussels,
286 Belgium
287
288 EMail: [email protected]
289
290
291 Pradosh Mohapatra
292 Cisco Systems
293 170 W. Tasman Drive
294 San Jose, CA 95134
295 USA
296
297 EMail: [email protected]
298
299
300 Carlos Pignataro
301 Cisco Systems
302 7200 Kit Creek Road, PO Box 14987
303 Research Triangle Park, NC 27709
304 USA
305
306 EMail: [email protected]
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332 Filsfils, et al. Standards Track [Page 6]
333 </pre>