Mobility Capability Negotiation and Protocol Selection
draft-yan-dmm-man-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-06-21
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
DMM Working Group Z. Yan
Internet-Draft CNNIC
Intended status: Standards Track J. Lee
Expires: December 22, 2017 Sangmyung University
H. Chan
Huawei Technologies
June 20, 2017
Mobility Capability Negotiation and Protocol Selection
draft-yan-dmm-man-01
Abstract
Based on IPv6, multiple mobility management protocols have been
developed and generally they can be classified into two types:
network-based and host-based. Different protocols have different
functional requirements on the network element or the terminal and
then a scheme should be used in order to support the negotiation and
selection of adopted mobility management protocol when a terminal
accesses to a new network. In this draft, this issue is considered
and analyzed.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 22, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
Yan, et al. Expires December 22, 2017 [Page 1]
Internet-Draft MCN-PS June 2017
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
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Principles and possible solution . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
Based on Mobile IPv6 (MIPv6) [RFC6275], there are multiple extension
protocols have been standardized. These protocols can be classified
into two categories: protocols for the function extension and
protocols for the performance enhancement. The protocols for the
function extension are proposed to support some specific scenarios or
functions, such as Dual-stack Mobile IPv6 (DSMIPv6) [RFC5555] for
mobility of the dual-stack nodes, Multiple Care-of-address (MCoA)
[RFC5648] for mobile nodes with multiple access interfaces and
Network Mobility (NEMO) [RFC3963] for mobility of sub-network. The
other category is proposed to enhance the performance of the mobility
management, such as Fast Mobile IPv6 (FMIP6) [RFC5268] for fast
handover, Hierarchical Mobile IPv6 (HMIPv6) [RFC5380] for
hierarchical mobility optimization. MIPv6 and these extensions are
classified in the host-based mobility management protocol suite
because the location update is initiated by the terminal and the
tunnel is also terminated at the terminal.
In order to reduce the protocol cost and enhance the handover
performance further, the network-based mobility management protocols
were proposed and Proxy Mobile IPv6 (PMIPv6) [RFC5213] was
standardized as a basis. Based on PMIPv6, a series of its extensions
Show full document text