Mobility Capability Negotiation and Protocol Selection
draft-yan-dmm-man-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-10-29
|
|
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 G. Geng
Intended status: Standards Track CNNIC
Expires: May 2, 2018 J. Lee
Sangmyung University
H. Chan
Huawei Technologies
October 29, 2017
Mobility Capability Negotiation and Protocol Selection
draft-yan-dmm-man-02
Abstract
The draft analyzes the issue that multiple mobility management
protocols have been developed according to different requirements.
These different protocols have different functional requirements on
the network element or the host. A scheme is then proposed to
support the negotiation and selection of adopted mobility management
protocol when a host accesses a new network.
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 https://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 May 2, 2018.
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
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Yan, et al. Expires May 2, 2018 [Page 1]
Internet-Draft MCN-PS October 2017
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Possible Cases . . . . . . . . . . . . . . . . . . . . . . . 4
4. Principles and Possible Procedure . . . . . . . . . . . . . . 9
5. Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
A large number of multiple protocols have been developed. In order
to clearly analyze the possible cases, these mobility management
protocols can be categorized as follows:
o Mobile IPv6 (MIPv6) protocol: the mobility management scheme based
on [RFC6275].
o Proxy Mobile IPv6 (PMIPv6) protocol: the mobility management
scheme based on [RFC5213].
o MIPv6 suite protocols: based on MIPv6, there are multiple
extension protocols have been standardized. These protocols can
be classified into two types: protocols for functional extension
and protocols for performance enhancement. The protocols for
functional 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 hosts with multiple access interfaces
and Network Mobility (NEMO) [RFC3963] for mobility of sub-network.
The other type is proposed to enhance performance of the mobility
management, such as Fast Mobile IPv6 (FMIP6) [RFC5268] for fast
handover, Hierarchical Mobile IPv6 (HMIPv6) [RFC5380] for
hierarchical mobility optimization. In the MIPv6 suite protocols,
location update is initiated by the host and the tunnel is also
terminated at the host.
o PMIPv6 suite protocols: in order to reduce the protocol cost and
enhance the handover performance further, the network-based
Show full document text