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
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
|
<pre>Internet Engineering Task Force (IETF) C. Byrne
Request for Comments: 7278 T-Mobile USA
Category: Informational D. Drown
ISSN: 2070-1721 A. Vizdal
Deutsche Telekom AG
June 2014
<span class="h1">Extending an IPv6 /64 Prefix from a</span>
<span class="h1">Third Generation Partnership Project (3GPP)</span>
<span class="h1">Mobile Interface to a LAN Link</span>
Abstract
This document describes requirements for extending an IPv6 /64 prefix
from a User Equipment Third Generation Partnership Project (3GPP)
radio interface to a LAN link and describes two implementation
examples.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <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/rfc7278">http://www.rfc-editor.org/info/rfc7278</a>.
<span class="grey">Byrne, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
Copyright Notice
Copyright (c) 2014 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-3">3</a>
2. The Challenge of Providing IPv6 Addresses to a LAN Link via a
3GPP UE .........................................................<a href="#page-4">4</a>
3. Requirements for Extending the 3GPP Interface /64 IPv6
Prefix to a LAN Link ............................................<a href="#page-4">4</a>
4. Example Methods for Extending the 3GPP Interface /64
IPv6 Prefix to a LAN Link .......................................<a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. General Behavior for All Example Scenarios .................<a href="#page-5">5</a>
4.2. Example Scenario 1: Global Address Only Assigned to
LAN Link ...................................................<a href="#page-5">5</a>
4.3. Example Scenario 2: A Single Global Address Assigned to a
3GPP Radio and LAN Link ....................................<a href="#page-7">7</a>
<a href="#section-5">5</a>. Security Considerations .........................................<a href="#page-8">8</a>
<a href="#section-6">6</a>. Acknowledgments .................................................<a href="#page-8">8</a>
<a href="#section-7">7</a>. Informative References ..........................................<a href="#page-8">8</a>
<span class="grey">Byrne, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
3GPP mobile cellular networks such as Global System for Mobile
Communications (GSM), Universal Mobile Telecommunications System
(UMTS), and Long Term Evolution (LTE) have architectural support for
IPv6 [<a href="./rfc6459" title=""IPv6 in 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS)"">RFC6459</a>], but only 3GPP Release-10 and onwards of the 3GPP
specification [<a href="#ref-TS.23401" title=""General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"">TS.23401</a>] supports DHCPv6 Prefix Delegation [<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>]
for delegating IPv6 prefixes to a single LAN link.
To facilitate the use of IPv6 in a LAN prior to the deployment of
DHCPv6 Prefix Delegation in 3GPP networks and in User Equipment (UE),
this document describes requirements and provides examples on how the
3GPP UE radio interface assigned global /64 prefix may be extended
from the 3GPP radio interface to a LAN link.
There are two scenarios where this might be done. The first is where
the 3GPP node sets up and manages its own LAN (e.g., an IEEE 802.11
Service Set Identifier (SSID)) and provides single-homed service to
hosts that connect to this LAN. A second scenario is where the 3GPP
node connects to an existing LAN and acts as a router in order to
provide redundant or multi-homed IPv6 service.
This document is intended to address the first scenario; it is not
applicable to the second scenario, because the operational
complexities of the second scenario are not addressed.
This can be achieved by receiving the Router Advertisement (RA)
[<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] announced globally unique /64 IPv6 prefix from the 3GPP
radio interface by the UE and then advertising the same IPv6 prefix
to the LAN link with RA. For all of the cases in the scope of this
document, the UE may be any device that functions as an IPv6 router
between the 3GPP network and a LAN.
This document describes requirements for achieving an IPv6 prefix
extension from a 3GPP radio interface to a LAN link including two
practical implementation examples:
1) The 3GPP UE only has a global-scope address on the LAN link.
2) The 3GPP UE maintains the same consistent 128-bit global-scope
IPv6 anycast address [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] on the 3GPP radio interface and the
LAN link. The LAN link is configured as a /64 and the 3GPP radio
interface is configured as a /128.
<a href="#section-4">Section 4</a> describes the characteristics of each of the two example
approaches.
<span class="grey">Byrne, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Special Language</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">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
Note that this document is not a Standard, and conformance with it is
not required in order to claim conformance with IETF Standards for
IPv6.
This document uses the normative keywords only for precision.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Challenge of Providing IPv6 Addresses to a LAN Link via a</span>
<span class="h2"> 3GPP UE</span>
As described in [<a href="./rfc6459" title=""IPv6 in 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS)"">RFC6459</a>], 3GPP networks assign a /64 global-scope
prefix to each UE using RA. DHCPv6 Prefix Delegation is an optional
part of 3GPP Release-10 and is not covered by any earlier releases.
Neighbor Discovery Proxy (ND Proxy) [<a href="./rfc4389" title=""Neighbor Discovery Proxies (ND Proxy)"">RFC4389</a>] functionality has been
suggested as an option for extending the assigned /64 from the 3GPP
radio interface to the LAN link, but ND Proxy is an Experimental
protocol and has some limitations with loop avoidance.
DHCPv6 is the best way to delegate a prefix to a LAN link. The
methods described in this document SHOULD only be applied when
deploying DHCPv6 Prefix Delegation is not achievable in the 3GPP
network and the UE. The methods described in this document are at
various stages of implementation and deployment planning. The goal
of this memo is to document the available methods that may be used
prior to DHCPv6 deployment.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Requirements for Extending the 3GPP Interface /64 IPv6 Prefix to a</span>
<span class="h2"> LAN Link</span>
R-1: The 3GPP network provided /64 prefix MUST be made available on
the LAN link.
LAN attached devices shall be able to use the 3GPP network
assigned IPv6 prefix (e.g. using IPv6 Stateless Address
Autoconfiguration - SLAAC [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>]).
R-2: The UE MUST defend all of its IPv6 addresses on the LAN link.
In case a LAN attached node will, for example, autoconfigure the
same global IPv6 address as used on the 3GPP interface, the UE
must fail the Duplicate Address Detection (DAD) [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>] process
run by the LAN node.
<span class="grey">Byrne, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
R-3: The LAN link configuration MUST be tightly coupled with the 3GPP
link state.
R-4: The UE MUST decrement the time to live (TTL) when passing
packets between IPv6 links across the UE.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Example Methods for Extending the 3GPP Interface /64 IPv6 Prefix to</span>
<span class="h2"> a LAN Link</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. General Behavior for All Example Scenarios</span>
As [<a href="./rfc6459" title=""IPv6 in 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS)"">RFC6459</a>] describes, the 3GPP-network-assigned /64 is completely
dedicated to the UE and the gateway does not consume any of the /64
addresses. The gateway routes the entire /64 to the UE and does not
perform ND or Neighbor Unreachability Detection (NUD) [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>].
Communication between the UE and the gateway is only done using
link-local addresses and the link is point-to-point. This allows
for the UE to reliably manipulate the /64 from the 3GPP radio
interface without negatively impacting the point-to-point 3GPP radio
link interface. The LAN link RA configuration must be tightly
coupled with the 3GPP link state. If the 3GPP link goes down or
changes the IPv6 prefix, that state should be reflected in the LAN
link IPv6 configuration. Just as in a standard IPv6 router, the
packet TTL will be decremented when passing packets between IPv6
links across the UE. The UE is employing the weak host model
[<a href="./rfc1122" title=""Requirements for Internet Hosts - Communication Layers"">RFC1122</a>]. The RA function on the UE is exclusively run on the LAN
link.
The LAN-link-originated RA message carries a copy of the following
3GPP radio-link-received RA message option fields:
o MTU (if not provided by the 3GPP network, the UE will provide its
3GPP link MTU size)
o Prefix Information
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Example Scenario 1: Global Address Only Assigned to LAN Link</span>
For this case, the UE receives the RA from the 3GPP network but does
not use a global address on the 3GPP interface. The 3GPP-interface-
received RA /64 prefix information is used to configure the Neighbor
Discovery Protocol (NDP) on the LAN. The UE assigns itself an IPv6
address on the LAN link from the 3GPP-interface-received RA. The LAN
link uses RA to announce the prefix to the LAN. The UE LAN link
interface defends its LAN IPv6 address with DAD. The UE shall not
run SLAAC to assign a global address on the 3GPP radio interface
while routing is enabled.
<span class="grey">Byrne, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
This method allows the UE to originate and terminate IPv6
communications as a host while acting as an IPv6 router. The
movement of the IPv6 prefix from the 3GPP radio interface to the LAN
link may result in long-lived data connections being terminated
during the transition from a host-only mode to router-and-host mode.
Connections that are likely to be affected are ones that have been
specifically bound to the 3GPP radio interface. This method is
appropriate if the UE or software on the UE cannot support multiple
interfaces with the same anycast IPv6 address and the UE requires
global connectivity while acting as a router.
Below is the general procedure for this scenario:
1. The user activates router functionality for a LAN on the UE.
2. The UE checks to make sure the 3GPP interface is active and has
an IPv6 address. If the interface does not have an IPv6 address,
an attempt will be made to acquire one; otherwise, the procedure
will terminate.
3. In this example, the UE finds the 3GPP interface is active and
has the IPv6 address 2001:db8:ac10:f002:1234:4567:0:9 assigned.
4. The UE moves the address 2001:db8:ac10:f002:1234:4567:0:9 as a
/64 from the 3GPP interfaces to the LAN link interface, disables
the IPv6 SLAAC feature on the 3GPP radio interface to avoid
address autoconfiguration, and begins announcing the prefix
2001:db8:ac10:f002::/64 via RA to the LAN. For this example, the
LAN has 2001:db8:ac10:f002:1234:4567:0:9/64 and the 3GPP radio
only has a link-local address.
5. The UE directly processes all packets destined to itself at
2001:db8:ac10:f002:1234:4567:0:9.
6. The UE, acting as a router running NDP on the LAN, will route
packets to and from the LAN. IPv6 packets passing between
interfaces will have the TTL decremented.
7. On the LAN link interface, there is no chance of address conflict
since the address is defended using DAD. The 3GPP radio
interface only has a link-local address.
<span class="grey">Byrne, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Example Scenario 2: A Single Global Address Assigned to a</span>
<span class="h3"> 3GPP Radio and LAN Link</span>
In this method, the UE assigns itself one address from the 3GPP-
network RA-announced /64. This one address is configured as anycast
[<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] on both the 3GPP radio link as a /128 and on the LAN link
as a /64. This allows the UE to maintain long-lived data connections
since the 3GPP radio interface address does not change when the
router function is activated. This method may cause complications
for certain software that may not support multiple interfaces with
the same anycast IPv6 address, or are sensitive to prefix length
changes. This method also creates complications for ensuring
uniqueness for Privacy Extensions [<a href="./rfc4941" title=""Privacy Extensions for Stateless Address Autoconfiguration in IPv6"">RFC4941</a>]. When Privacy Extensions
are in use, all temporary addresses will be copied from the 3GPP
radio interface to the LAN link. The preferred and valid lifetimes
will be synchronized, such that the temporary anycast addresses on
both interfaces expire simultaneously.
There might also be more complex scenarios in which the prefix length
is not changed and privacy extensions are supported by having the
subnet span multiple interfaces, as ND Proxy does [<a href="./rfc4389" title=""Neighbor Discovery Proxies (ND Proxy)"">RFC4389</a>]. Further
elaboration is out of scope of the present document.
Below is the general procedure for this scenario:
1. The user activates router functionality for a LAN on the UE.
2. The UE checks to make sure the 3GPP interface is active and has
an IPv6 address. If the interface does not have an IPv6 address,
an attempt will be made to acquire one; otherwise, the procedure
will terminate.
3. In this example, the UE finds the 3GPP interface is active and
has the IPv6 address 2001:db8:ac10:f002:1234:4567:0:9 assigned.
4. The UE moves the address 2001:db8:ac10:f002:1234:4567:0:9 as an
anycast /64 from the 3GPP interface to the LAN interface and
begins announcing the prefix 2001:db8:ac10:f002::/64 via RA to
the LAN. The 3GPP interface maintains the same IPv6 anycast
address with a /128. For this example, the LAN has
2001:db8:ac10:f002:1234:4567:0:9/64 and the 3GPP radio interface
has 2001:db8:ac10:f002:1234:4567:0:9/128.
5. The UE directly processes all packets destined to itself at
2001:db8:ac10:f002:1234:4567:0:9.
<span class="grey">Byrne, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
6. On the LAN interface, there is no chance of address conflict
since the address is defended using DAD. The 3GPP radio
interface only has a /128 and no other systems on the 3GPP radio
point-to-point link may use the global /64.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
Since the UE will be switched from an IPv6 host mode to an IPv6
router-and-host mode, basic IPv6 Customer Premises Equipment (CPE)
security functions [<a href="./rfc6092" title=""Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service"">RFC6092</a>] SHOULD be applied.
Despite the use of temporary IPv6 addresses, the mobile-network-
provided /64 prefix is common to all the LAN-attached devices
potentially concerning privacy. An IPv6 prefix provided by a nomadic
device (e.g., a smartphone) is not a long-lived one due to
re-attaches caused by a device reload, traveling through loosely
covered areas, etc. The network will provide a new IPv6 prefix after
a successful re-attach.
3GPP-mobile-network-capable CPEs (e.g., a router) are likely to keep
the mobile network data connection up for a longer time. Some mobile
networks may be re-setting the mobile network connection regularly
(e.g., every 24 hours), others may not. Privacy-concerned users
shall take appropriate measures to not keep their IPv6 prefixes long
lived.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span>
Many thanks for review and discussion from Dave Thaler, Sylvain
Decremps, Mark Smith, Dmitry Anipko, Masanobu Kawashima, Teemu
Savolainen, Mikael Abrahamsson, Eric Vyncke, Alexandru Petrescu,
Jouni Korhonen, Lorenzo Colitti, Julien Laganier, Owen DeLong, Holger
Metschulat, Yaron Sheffer, and Victor Kuarsingh. Special thanks to
Ann Cerveny for her language review.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Informative References</span>
[<a id="ref-RFC1122">RFC1122</a>] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>, October 1989.
[<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-RFC3633">RFC3633</a>] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", <a href="./rfc3633">RFC 3633</a>,
December 2003.
<span class="grey">Byrne, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006.
[<a id="ref-RFC4389">RFC4389</a>] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery
Proxies (ND Proxy)", <a href="./rfc4389">RFC 4389</a>, April 2006.
[<a id="ref-RFC4861">RFC4861</a>] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>,
September 2007.
[<a id="ref-RFC4862">RFC4862</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, September 2007.
[<a id="ref-RFC4941">RFC4941</a>] Narten, T., Draves, R., and S. Krishnan, "Privacy
Extensions for Stateless Address Autoconfiguration in
IPv6", <a href="./rfc4941">RFC 4941</a>, September 2007.
[<a id="ref-RFC6092">RFC6092</a>] Woodyatt, J., Ed., "Recommended Simple Security
Capabilities in Customer Premises Equipment (CPE) for
Providing Residential IPv6 Internet Service", <a href="./rfc6092">RFC 6092</a>,
January 2011.
[<a id="ref-RFC6459">RFC6459</a>] Korhonen, J., Ed., Soininen, J., Patil, B., Savolainen,
T., Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation
Partnership Project (3GPP) Evolved Packet System (EPS)",
<a href="./rfc6459">RFC 6459</a>, January 2012.
[<a id="ref-TS.23401">TS.23401</a>] 3GPP, "General Packet Radio Service (GPRS) enhancements
for Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access", 3GPP TS 23.401 10.0.0, June 2010.
<span class="grey">Byrne, et al. Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7278">RFC 7278</a> Extending an IPv6 /64 Prefix June 2014</span>
Authors' Addresses
Cameron Byrne
T-Mobile USA
Bellevue, Washington, USA
EMail: Cameron.Byrne@T-Mobile.com
Dan Drown
EMail: Dan@Drown.org
Ales Vizdal
Deutsche Telekom AG
Tomickova 2144/1
Prague, 149 00
Czech Republic
EMail: Ales.Vizdal@T-Mobile.cz
Byrne, et al. Informational [Page 10]
</pre>
|
