1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
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
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Internet Engineering Task Force (IETF) P. Yegani
Request for Comments: 6245 Juniper Networks
Category: Standards Track K. Leung
ISSN: 2070-1721 Cisco Systems
A. Lior
Bridgewater Systems
K. Chowdhury
J. Navali
Cisco Systems
May 2011
<span class="h1">Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4</span>
Abstract
The Generic Routing Encapsulation (GRE) specification contains a Key
field, which MAY contain a value that is used to identify a
particular GRE data stream. This specification defines a new Mobile
IP extension that is used to exchange the value to be used in the GRE
Key field. This extension further allows the Mobility Agents to set
up the necessary protocol interfaces prior to receiving the mobile
node traffic. The new extension allows a Foreign Agent to request
GRE tunneling without disturbing the Home Agent behavior specified
for Mobile IPv4. GRE tunneling with the Key field allows the
operators to have home networks that consist of multiple Virtual
Private Networks (VPNs), which may have overlapping home addresses.
When the tuple <Care of Address, Home Address, and Home Agent
Address> is the same across multiple subscriber sessions, GRE
tunneling will provide a means for the Foreign Agent and Home Agent
to identify data streams for the individual sessions based on the GRE
key. In the absence of this key identifier, the data streams cannot
be distinguished from each other -- a significant drawback when using
IP-in-IP tunneling.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6245">http://www.rfc-editor.org/info/rfc6245</a>.
<span class="grey">Yegani, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6245">RFC 6245</a> GRE Key Ext. for MIP4 May 2011</span>
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. GRE Key Extension ...............................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. Operation and Use of the GRE Key Extension ......................<a href="#page-3">3</a>
<a href="#section-4.1">4.1</a>. Foreign Agent Requirements for GRE Tunneling Support .......<a href="#page-3">3</a>
<a href="#section-4.2">4.2</a>. Home Agent Requirements for GRE Tunneling Support ..........<a href="#page-4">4</a>
<a href="#section-4.3">4.3</a>. Mobile Node Requirements for GRE Tunneling Support .........<a href="#page-5">5</a>
<a href="#section-5">5</a>. GRE Key Extension and Tunneling Procedures ......................<a href="#page-5">5</a>
<a href="#section-6">6</a>. IANA Considerations .............................................<a href="#page-6">6</a>
<a href="#section-7">7</a>. Security Considerations .........................................<a href="#page-6">6</a>
<a href="#section-8">8</a>. Acknowledgements ................................................<a href="#page-7">7</a>
<a href="#section-9">9</a>. Normative References ............................................<a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies a new extension for use by a Foreign Agent
(FA) operating Mobile IP for IPv4. The new extension allows a
Foreign Agent to request Generic Routing Encapsulation (GRE)
[<a href="./rfc2784" title=""Generic Routing Encapsulation (GRE)"">RFC2784</a>] tunneling without disturbing the Home Agent (HA) behavior
specified for Mobile IPv4 [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>]. This extension contains the GRE
key [<a href="./rfc2890" title=""Key and Sequence Number Extensions to GRE"">RFC2890</a>] required for establishing a GRE tunnel between the FA
and the HA.
GRE tunneling with the Key field allows the operators to have home
networks that consist of multiple Virtual Private Networks (VPNs),
which may have overlapping home addresses. When the tuple <Care of
Address, Home Address, and Home Agent Address> is the same across
<span class="grey">Yegani, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6245">RFC 6245</a> GRE Key Ext. for MIP4 May 2011</span>
multiple subscriber sessions, GRE tunneling will provide a means for
the FA and the HA to identify data streams for the individual
sessions based on the GRE key. In the absence of this key
identifier, the data streams cannot be distinguished from each other
-- a significant drawback when using IP-in-IP tunneling.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. Other
terminology is used as already defined in [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. GRE Key Extension</span>
The format of the GRE Key Extension conforms to the extension format
specified for Mobile IPv4 [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>]. This extension option is used
by the Foreign Agent to supply GRE key and other necessary
information to the Home Agent to establish a GRE tunnel between the
FA and the HA.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Operation and Use of the GRE Key Extension</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Foreign Agent Requirements for GRE Tunneling Support</span>
The FA MUST support IP-in-IP tunneling of datagrams for Mobile IPv4
[<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>]. The FA may support GRE tunneling that can be used, for
example, to allow for overlapping private home IP addresses
(Section 4.2.2.5 of [<a href="#ref-X.S0011-E" title=""cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services"">X.S0011-E</a>]). If the FA is capable of supporting
GRE encapsulation, it should set the 'G' (GRE encapsulation) bit in
the Flags field in the Agent Advertisement message sent to the Mobile
Node (MN) during the Mobile IP session establishment.
If the MN does not set the 'G' bit, the FA MAY fall back to using
IP-in-IP encapsulation for the session per [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>].
If the MN does not set the 'G' bit and does not set the 'D'
(Decapsulation by mobile node) bit (i.e., the mobile node does not
request GRE tunneling and is not using a co-located care-of address),
and the local policy allows the FA to override the 'G' bit setting
received from the MN, the FA MUST include the GRE Key Extension as
defined in this memo in the Registration Request (RRQ) that it
propagates to the HA. The presence of this extension is a request
for GRE encapsulation that takes precedence over the setting of the
'G' bit in the Registration Request. The FA MUST NOT modify the 'G'
bit in the Registration Request because it is protected by the
Mobile-Home Authentication extension.
<span class="grey">Yegani, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6245">RFC 6245</a> GRE Key Ext. for MIP4 May 2011</span>
If the FA does not support GRE encapsulation, the FA MUST reset the
'G' bit in the Agent Advertisement message. In this case, if the MN
sets the 'G' bit in the Registration Request message, the FA returns
a Registration Reply (RRP) message to the MN with code 'requested
encapsulation unavailable' (72) per [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>].
If the FA allows GRE encapsulation, and either the MN requested GRE
encapsulation or local policy dictates using GRE encapsulation for
the session, and the 'D' bit is not set (i.e., the mobile node is not
using a co-located care-of address), the FA MUST include the GRE Key
in the GRE Key Extension in all Mobile IP Registration Requests
(including initial, renewal, and de-registration requests) before
forwarding the request to the HA. The FA may include a GRE key of
value zero in the GRE Key Extension to signal that the HA assigns GRE
keys in both directions. The GRE key assignment in the FA and the HA
is outside the scope of this memo.
The GRE Key Extension SHALL follow the format defined in [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>].
This extension SHALL be added after the MN-HA and MN-FA Challenge and
MN-AAA (Mobile Node - Authentication, Authorization, and Accounting)
extensions (if any) and before the FA-HA Auth extension (if any).
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Home Agent Requirements for GRE Tunneling Support</span>
The HA MUST follow the procedures specified in [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>] in
processing this extension in Registration Request messages.
If the HA receives the GRE Key Extension in a Registration Request
and does not recognize this non-skippable extension, it MUST silently
discard the message. The HA MUST use other alternative forms of
encapsulation (e.g., IP-in-IP tunneling), when requested by the
mobile node per [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>].
If the HA receives the GRE Key Extension in a Registration Request
and recognizes the GRE Key Extension but is not configured to support
GRE encapsulation, it MUST send an RRP with code 'requested
encapsulation unavailable (139)' [<a href="./rfc3024" title=""Reverse Tunneling for Mobile IP, revised"">RFC3024</a>].
If the HA receives a Registration Request with a GRE Key Extension
but without the 'G' bit set, the HA SHOULD treat this as if the 'G'
bit is set in the Registration Request; i.e., the presence of a GRE
Key Extension indicates a request for GRE encapsulation.
If the HA receives the GRE Key Extension in a Registration Request,
and it recognizes the GRE Key Extension as well as supports GRE
encapsulation, the following procedures should apply:
<span class="grey">Yegani, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6245">RFC 6245</a> GRE Key Ext. for MIP4 May 2011</span>
o The HA SHOULD accept the RRQ and send an RRP with code
'registration accepted (0)'.
o The HA MUST assign a GRE key and include the GRE Key Extension in
the RRP before sending it to the FA.
o The HA MUST include the GRE Key Extension in all RRPs in response
to any RRQ that included the GRE Key Extension, when a GRE key is
available for the registration.
If the HA receives the GRE Key Extension in the initial Registration
Request and recognizes the GRE Key Extension carrying a GRE key value
of zero, it SHOULD accept the RRQ and send an RRP with code
'registration accepted (0)', and the following procedures apply:
o The HA MUST assign GRE keys for both directions and include these
keys in the GRE Key Extension in the RRP before sending it to
the FA.
o The HA MUST include the GRE Key Extension in the RRP in response
to the initial RRQ that included the GRE Key Extension, when a GRE
key is available for the registration.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Mobile Node Requirements for GRE Tunneling Support</span>
If the MN is capable of supporting GRE encapsulation, it SHOULD set
the 'G' bit in the Flags field in the Registration Request per
[<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. GRE Key Extension and Tunneling Procedures</span>
GRE tunneling support for Mobile IP will permit asymmetric GRE
keying; i.e., the FA assigns a GRE key for use in encapsulated
traffic, and the HA can assign its own GRE key. Once the GRE keys
have been exchanged, the FA uses the HA-assigned key in the
encapsulating GRE header for reverse tunneling, and the HA uses the
FA-assigned key in the encapsulating GRE header.
The format of the GRE Key Extension is as shown below.
The GRE Key Extension MAY be included in Registration Requests or
Registration Replies [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>]. The GRE Key Extension is used to
inform the recipient of the Mobile IP request of the value to be used
in the GRE Key field.
<span class="grey">Yegani, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6245">RFC 6245</a> GRE Key Ext. for MIP4 May 2011</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Sub-Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: GRE Key Extension
Type
48 - An 8-bit identifier of the GRE Key Extension type
(non-skippable)
Sub-Type
0
Length
4
Key Identifier
This is a four-octet value assigned during registration and
inserted in every GRE packet of the user traffic.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
The GRE Key Extension defined in this memo is a Mobile IP extension
as defined in [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>]. IANA has assigned a Type value (48) for
this extension from the non-skippable range (0-127).
The GRE Key Extension introduces a new sub-type numbering space,
where the value 0 has been assigned from the range 0 to 255.
Approval of new GRE Key Extension sub-type values is to be made
through Expert Review with Specification Required.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
This specification does not introduce any new security
considerations, beyond those described in [<a href="./rfc5944" title=""IP Mobility Support for IPv4, Revised"">RFC5944</a>].
<span class="grey">Yegani, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6245">RFC 6245</a> GRE Key Ext. for MIP4 May 2011</span>
Despite its name, the GRE Key Extension has little to do with
security. The word "Key" here is not used in the cryptographic sense
of a shared secret that must be protected but rather in the sense of
an "index" or demultiplexing value that can be used to distinguish
packets belonging to a given flow within a GRE tunnel.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
Thanks to Jun Wang, Gopal Dommety, and Sri Gundavelli for their
helpful comments, offline discussions, and review of the initial
draft version of this document. Also, Pete McCann and Simon
Mizikovsky provided valuable review comments.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2784">RFC2784</a>] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
Traina, "Generic Routing Encapsulation (GRE)", <a href="./rfc2784">RFC 2784</a>,
March 2000.
[<a id="ref-RFC2890">RFC2890</a>] Dommety, G., "Key and Sequence Number Extensions to
GRE", <a href="./rfc2890">RFC 2890</a>, September 2000.
[<a id="ref-RFC3024">RFC3024</a>] Montenegro, G., Ed., "Reverse Tunneling for Mobile IP,
revised", <a href="./rfc3024">RFC 3024</a>, January 2001.
[<a id="ref-RFC5944">RFC5944</a>] Perkins, C., Ed., "IP Mobility Support for IPv4,
Revised", <a href="./rfc5944">RFC 5944</a>, November 2010.
[<a id="ref-X.S0011-E">X.S0011-E</a>] 3rd Generation Partnership Project 2, "cdma2000 Wireless
IP Network Standard: Simple IP and Mobile IP Access
Services", 3GPP2 X.S0011-002-E Version 1.0,
November 2009, <<a href="http://www.3gpp2.org/Public_html/specs/X.S0011-002-E_v1.0_091116.pdf">http://www.3gpp2.org/Public_html/specs/</a>
<a href="http://www.3gpp2.org/Public_html/specs/X.S0011-002-E_v1.0_091116.pdf">X.S0011-002-E_v1.0_091116.pdf</a>>.
<span class="grey">Yegani, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6245">RFC 6245</a> GRE Key Ext. for MIP4 May 2011</span>
Authors' Addresses
Parviz Yegani
Juniper Networks
1194 North Mathilda Ave.
Sunnyvale, California 94089
USA
Phone: +1 408-759-1973
EMail: pyegani@juniper.net
Kent Leung
Cisco Systems Incorporated
170 West Tasman Drive
San Jose, California 95134
USA
Phone: +1 408 526 5030
EMail: kleung@cisco.com
Avi Lior
Bridgewater Systems Corporation
303 Terry Fox Drive
Ottawa, Ontario K2K 3J1
Canada
Phone: +1 613-591-6655
EMail: avi@bridgewatersystems.com
Kuntal Chowdhury
Cisco Systems Incorporated
170 West Tasman Drive
San Jose, California 95134
USA
EMail: kchowdhu@cisco.com
Jay Navali
Cisco Systems Incorporated
170 West Tasman Drive
San Jose, California 95134
USA
EMail: jnavali@cisco.com
Yegani, et al. Standards Track [Page 8]
</pre>
|
