Impact of IPv6 Neighbor Discovery on Cellular M2M Networks
draft-garneij-6man-nd-m2m-issues-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fredrik Garneij , Samita Chakrabarti , Suresh Krishnan | ||
| Last updated | 2015-01-05 (Latest revision 2014-07-04) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The use of IPv6 in 3GPP cellular broadband networks for accessing the Internet and other data services like voice-over-LTE(VoLTE) has increased greatly as a result of EPS network deployments worldwide and new IPv6 capable smartphones and tablets. The upcoming rise of IoT/M2M is anticipated to bring billions of new devices into these networks and the majority of these devices will be using only IPv6. This document discusses the EPS network impact of IoT/M2M IPv6 connectivity specifically targeting the IPv6 Stateless Address Auto Configuration (SLAAC), as specified in [RFC4861] and [RFC4862], which currently is the only supported IPv6 address configuration mechanism in 3GPP standards.
Authors
Fredrik Garneij
Samita Chakrabarti
Suresh Krishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)