MEXT Working Group Hong-Ke Zhang
Internet Draft Zhi-Wei Yan
Expires: April 2009 Hua-Chun Zhou
Si-Dong Zhang
Jian-Feng Guan
Beijing Jiaotong University
October 20, 2008
Extension of Multiple Care-of Addresses Registration for Handover
draft-zhang-mext-mcoa-extension-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 20,2009.
Abstract
The Multiple Care-of Addresses Registration [2] is a useful protocol
which allows a mobile node to get Internet access through multiple
accesses simultaneously, in which case the mobile node would be
configured with multiple active IPv6 care-of addresses. It proposes
extensions to the Mobile IPv6 protocol to register and use multiple
care-of addresses with the Binding Identifier Mobility Option. This
document describes a simple extension to Binding Identifier Mobility
Option to allow mobile node to select the most wanted link for the
ongoing service.
Zhang et al. Expires April 20, 2009 [Page 1]
Internet-Draft McoA Extension October 2008
Conventions used in this document
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 [1].
Table of Contents
1. Introduction................................................2
2. Extended Binding Identifier Mobility Option..................2
3. Security Considerations......................................5
4. References..................................................5
Author's Addresses.............................................5
Intellectual Property Statement.................................5
Full Copyright Statement........................................6
Acknowledgment.................................................6
1. Introduction
The Multiple Care-of Addresses Registration [2] document proposes
extensions to Mobile IPv6 to allow a mobile node to register multiple
care-of addresses for a home address and create multiple binding
cache entries. The BID information stored in the Binding Identifier
Mobility Option is created for each binding the mobile node wants to
create and sent in the binding update. However, The Multiple Care-of
Addresses Registration [2] document mainly focuses on how to
establish and remove the multiple bindings and does not solve the
handover using from one binging to another which is a very actual
problem. The extension to the Binding Identifier Mobility Option
proposed in this document allows mobile node to notify corresponding
entity (Home Agent or Corresponding Node) of the most wanted using
link for the ongoing communication.
2. Extended Binding Identifier Mobility Option
The following (Figure 1) is the definition of the extended format of
Binding Identifier Mobility Option.
Zhang et al. Expires April 20, 2009 [Page 2]
Internet-Draft McoA Extension October 2008
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 = TBD | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Binding ID (BID) | Status |O|H|D| Reserved|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
| Using Binding ID (UBID) | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
+ +
: IPv4 or IPv6 care-of address (CoA) :
+ +
+---------------------------------------------------------------+
Figure 1: Extended BID Mobility Option
Type
Type value for Binding Identifier is TBD
Length
8-bit unsigned integer. Length of the option, in octets, excluding
the Type and Length fields. It MUST be set to either 6, 14, or 22
depending on the care-of address field. When the care-of address is
not carried by this option, the length value MUST be set to 6. If
the IPv4 care-of address is stored in the care-of address field, the
length MUST be 14. Otherwise, the Length value MUST be set to 22 for
IPv6 care-of address.
Binding ID (BID)
The BID which is assigned to the binding indicated by the care-of
address in the Binding Update or the BID mobility option. The BID is a
Zhang et al. Expires April 20, 2009 [Page 3]
Internet-Draft McoA Extension October 2008
16-bit unsigned integer. The value of zero is reserved and MUST NOT be
used.
Status
When the Binding Identifier mobility option is included in a Binding
Acknowledgement, this field overwrites the status field in the Binding
Acknowledgement. If this field is zero, the receiver MUST use the
registration status stored in the Binding Acknowledgement message.
This Status field is also used to carry error information related to
the care-of address test in the Care-of Test message. The status is 8-
bit unsigned integer. The possible status codes are the same as the
status codes of Binding Acknowledgement.
Overwrite (O) flag
When this flag is set, a mobile node requests the recipient to replace
all the bindings to binding entries stored in a Binding Update.
Simultaneous Home and Foreign Binding (H) flag
This flag indicates that the mobile node registers multiple bindings to
the home agent while is attached to the home link. This flag is valid
only for a Binding Update sent to the home agent.
Using BID changing (D) flag
When this flag is set, the mobile node requests the recipient to use
the binding identified by the BID and stop using the binding identified
by the UBID stored in the Using BID space.
Reserved
4 bits Reserved field. The reserved field MUST be zero.
Using Binding ID (UBID)
The Using BID indicates the active binding which is used for the
ongoing communication. The BID is a 16-bit unsigned integer. The value
of zero is reserved and MUST NOT be used.
Care-of Address
This field has the variable length depending on the specified flags.
Either IPv4 or IPv6 care-of address for the corresponding BID can be
stored in this field. This field MUST NOT be used if a Binding
Zhang et al. Expires April 20, 2009 [Page 4]
Internet-Draft McoA Extension October 2008
Identifier mobility option is included in any other message other than
a Binding Update.
3. Security Considerations
This document introduces a new Multiple Care-of Addresses
Registration extension that is used to change the link for the
ongoing communication among the multiple links corresponding to
multiple bindings. The BID Mobility option messages that carry this
extension MUST be authenticated as described in [1], unless other
authentication methods have been agreed upon. Therefore, this
extension does not lessen the security of Multiple Care-of Addresses
Registration protocol.
4. References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] R. Wakikawa et al., "Multiple Care-of Addresses Registration",
working in progress, draft-ietf-monami6-multiplecoa-08.txt,
2008.
Author's Addresses
Hong-Ke Zhang, Zhi-Wei Yan, Hua-Chun Zhou, Si-Dong Zhang, Jian-Feng
Guan
NGI Research Center
Beijing Jiaotong University of China
Phone: +861051685677
Email:hkzhang@bjtu.edu.cn
06120232@bjtu.edu.cn
hchzhou@bjtu.edu.cn
sdzhang@center.njtu.edu.cn
guanjian8632@163.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
Zhang et al. Expires April 20, 2009 [Page 5]
Internet-Draft McoA Extension October 2008
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, The IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Zhang et al. Expires April 20, 2009 [Page 6]