< draft-wakikawa-mip6-no-ndp-00.txt		draft-wakikawa-mip6-no-ndp-01.txt >
	MIP6 Working Group R. Wakikawa		MIP6 Working Group R. Wakikawa
	Internet-Draft Keio University		Internet-Draft Keio University
	Expires: August 5, 2007 M. Aramoto		Expires: January 10, 2008 M. Aramoto
	Sharp		Sharp
	February 2007		July 9, 2007
	Elimination of Proxy NDP from Home Agent Operations		Elimination of Proxy NDP from Home Agent Operations
	draft-wakikawa-mip6-no-ndp-00.txt		draft-wakikawa-mip6-no-ndp-01.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		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		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.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on August 5, 2007.		This Internet-Draft will expire on January 10, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document summarizes operations of home agent without using the		This document summarizes operations of home agent without using the
	proxy NDP. The Proxy NDP is mainly used to intercept packets by a		proxy NDP. The Proxy NDP is mainly used to intercept packets by a
	Home Agent on Mobile IPv6 and NEMO.		Home Agent on Mobile IPv6 and NEMO.
	skipping to change at page 2, line 33 ¶		skipping to change at page 2, line 33 ¶
	5. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 11		5. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 11
	5.1. Duplicate Address Detection . . . . . . . . . . . . . . . 11		5.1. Duplicate Address Detection . . . . . . . . . . . . . . . 11
	5.2. Sending Router Advertisement . . . . . . . . . . . . . . . 11		5.2. Sending Router Advertisement . . . . . . . . . . . . . . . 11
	5.3. Deliverying Packets to the Mobile Node . . . . . . . . . . 12		5.3. Deliverying Packets to the Mobile Node . . . . . . . . . . 12
	5.4. Filtering Packets for Home Addresses . . . . . . . . . . . 12		5.4. Filtering Packets for Home Addresses . . . . . . . . . . . 12
	5.5. Returing Home . . . . . . . . . . . . . . . . . . . . . . 14		5.5. Returing Home . . . . . . . . . . . . . . . . . . . . . . 14
	6. Mobile Node & Correspondent Node Operation . . . . . . . . . . 15		6. Mobile Node & Correspondent Node Operation . . . . . . . . . . 15
	7. Multiple Care-of Address Registration . . . . . . . . . . . . 16		7. Related Information . . . . . . . . . . . . . . . . . . . . . 16
	8. Related Information . . . . . . . . . . . . . . . . . . . . . 19
	9. IANA considerations . . . . . . . . . . . . . . . . . . . . . 20		8. IANA considerations . . . . . . . . . . . . . . . . . . . . . 17
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 21		9. Security Considerations . . . . . . . . . . . . . . . . . . . 18
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21		10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
	11.1. Normative reference . . . . . . . . . . . . . . . . . . . 21		10.1. Normative reference . . . . . . . . . . . . . . . . . . . 18
	11.2. Informative Reference . . . . . . . . . . . . . . . . . . 21		10.2. Informative Reference . . . . . . . . . . . . . . . . . . 18
	Appendix A. Change Log From Previous Version . . . . . . . . . . 22		Appendix A. Change Log From Previous Version . . . . . . . . . . 19
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
	Intellectual Property and Copyright Statements . . . . . . . . . . 23		Intellectual Property and Copyright Statements . . . . . . . . . . 20
	1. Introduction		1. Introduction
	In Mobile IPv6, one of design limitations is the use of Proxy		In Mobile IPv6, one of design limitations is the use of Proxy
	Neighbor Discovery on Home Agent. Mobile IPv6 uses the proxy		Neighbor Discovery on Home Agent. Mobile IPv6 uses the proxy
	Neighbor Discovery Protocol (proxy NDP) to intercept packets meant		Neighbor Discovery Protocol (proxy NDP) to intercept packets meant
	for mobile nodes on a home agent at a home link. When the proxy NDP		for mobile nodes on a home agent at a home link. When the proxy NDP
	is used, a home prefix must be strictly configured at the physical		is used, a home prefix must be strictly configured at the physical
	link which the home prefix is defined in the Internet topology.		link which the home prefix is defined in the Internet topology.
	Moreover, the performance of NDP may effect that of Mobile IPv6 if		Moreover, the performance of NDP may effect that of Mobile IPv6 if
	skipping to change at page 16, line 5 ¶		skipping to change at page 16, line 5 ¶
	5.5. Returing Home		5.5. Returing Home
	For Returning home, no modification is given in this specification.		For Returning home, no modification is given in this specification.
	6. Mobile Node & Correspondent Node Operation		6. Mobile Node & Correspondent Node Operation
	No modification is required. This Specification is transparent to		No modification is required. This Specification is transparent to
	Mobile Nodes and Correspondent Nodes		Mobile Nodes and Correspondent Nodes
	7. Multiple Care-of Address Registration		7. Related Information
	In the Multiple Care-of Address Registration [2], the Mobile Node
	MUST disable either the interface attached to the home link or the
	interfaces attached to the foreign link. This is because the Home
	Agent defends the home address of the Mobile Node by proxy neighbor
	advertisements. So as to avoid the home address duplication at the
	home link, the Mobile Node MUST select whether it returns home or
	not. If a binding is active for the Mobile Node, all packets routed
	to the home link are intercepted by the Home Agent. On the other
	hand, if the Mobile Node returns home, the Home Agent no longer
	intercept packets and cannot tunnel the packets to the Mobile Node's
	interface attached to the foreign link.
	Figure 9 depicts the scenario where Mobile Node activates the
	interface attached to the home link and the foreign link, and
	communicates with all of the interfaces. Since the Home Agent does
	not use Proxy Neighbor Advertisement to intercept packets, the Mobile
	Node can utilize both of interfaces attached to the home link and the
	foreign link simultaneously. The Home Agent can intercept packets by
	IP routing, but not by proxy Neighbor Discovery.
	+----+
	| CN |
	+--+-+
	|
	+----+-----+ +----+
	| Internet |--------------+ HA |
	+----+---+-+ +--+-+
	|Foreign Link |Home Link
	--------+------------ ------+------
	| |
	|CoA1 |
	+--+--+ |
	| MN +--------------------+
	+-----+
	Binding Cache Database:
	Home Agent's binding (No Proxy neighbor advertisement)
	binding [a:b:c:d::EUI a:b:c:d::EUI BID1] (Home BC)
	binding [a:b:c:d::EUI Care-of Address1 BID2]
	Correspondent Node's binding
	binding [a:b:c:d::EUI a:b:c:d::EUI BID1] (Home BC)
	binding [a:b:c:d::EUI Care-of Address1 BID2]
	or
	None
	Figure 9: Utilizing of both an interface attached to the Home Link
	and an interface attached to the Foreign Link
	When the Mobile Node returns home, it de-registers a binding for the
	interface. While the bindings for the interfaces attached to the
	foreign link are still active. Intercepting packets, the Home Agent
	can decide whether it tunnels to the foreign interface or routes to
	the home interface of the Mobile Node. To do so, the Home Agent must
	know that the Mobile Node is back to the home link. However, if the
	binding is deleted according to [7], there is no way for the Home
	Agent to know that the Mobile Node is at the home, too. The Home
	Agent SHOULD invalidate the binding for the interface attached to the
	home link and MAY NOT delete it. It can alternatively mark that the
	Mobile Node is at the home link, too. In this document, as an
	example, the Home Agent inserts the Home Address of the Mobile Node
	in the Care-of Address field of the Mobile Node. The binding is
	named "Home Binding" in this doc. The Home Agent MAY manage this
	home binding as same as the other binding entry in terms of lifetime
	validation, etc. The Mobile Node MAY send multiple binding de-
	registration to keep this home binding active. Alternatively, the
	Home Agent can use infinity lifetime for the lifetime of the home
	binding. When the Mobile Node leaves the Home Link, it can update
	the home binding to the normal binding. Before that, the Home Agent
	believes the Mobile Node is at the home and may route packets for the
	Mobile Node to the Home Link.
	For this operation, the Binding Unique Identifier sub-option is
	modified as described in Figure Figure 10. The new Home flag is
	introduced. When the H flag is set, the Home Agent MUST treat the
	binding as the home binding. After intercepting the packets, the
	Home Agent may tunnel the packets according to the active binding
	cache(s) or route the packets to the home link according to the home
	binding cache. Note that the H flag MUST be used only for the
	binding de-registration. Note that the same mechanism is used for
	the correspondent node.
	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 Unique ID (BID) |Priority/Status|C|R|H|Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
	+ +
	+ Care-of Address (CoA) +
	+ +
	+---------------------------------------------------------------+
	Figure 10: BID Sub-Option
	Home Binding (H) flag
	When this flag is set, a home agent stores a Home Address in the
	Care-of Address field of the binding cache entry. This flag must
	be used only for binding de-registration. This flag is not used
	in the bulk registration mode.
	Reserved
	5 bits Reserved field. Reserved field must be set with all 0.
	8. Related Information
	Related Documents can be found in the Informative Reference section		Related Documents can be found in the Informative Reference section
	9. IANA considerations		8. IANA considerations
	This document does not require any IANA action.		This document does not require any IANA action.
	10. Security Considerations		9. Security Considerations
	No security vulnerability is not introduced in this specification.		No security vulnerability is not introduced in this specification.
	11. References		10. References
	11.1. Normative reference		10.1. Normative reference
	[1] Thubert, P., "NEMO Home Network models",		[1] Thubert, P., "NEMO Home Network models",
	draft-ietf-nemo-home-network-models-06 (work in progress),		draft-ietf-nemo-home-network-models-06 (work in progress),
	February 2006.		February 2006.
	[2] Wakikawa, R., "Multiple Care-of Addresses Registration",		[2] Wakikawa, R., "Multiple Care-of Addresses Registration",
	draft-ietf-monami6-multiplecoa-00 (work in progress), June 2006.		draft-ietf-monami6-multiplecoa-00 (work in progress), June 2006.
	[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997.		Levels", BCP 14, RFC 2119, March 1997.
	skipping to change at page 21, line 40 ¶		skipping to change at page 18, line 40 ¶
	[6] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,		[6] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,
	"Network Mobility (NEMO) Basic Support Protocol", RFC 3963,		"Network Mobility (NEMO) Basic Support Protocol", RFC 3963,
	January 2005.		January 2005.
	[7] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in		[7] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
	IPv6", RFC 3775, June 2004.		IPv6", RFC 3775, June 2004.
	[8] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery		[8] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery
	for IP Version 6 (IPv6)", RFC 2461, December 1998.		for IP Version 6 (IPv6)", RFC 2461, December 1998.
	11.2. Informative Reference		10.2. Informative Reference
	[9] Ng, C., "Analysis of Multihoming in Network Mobility Support",		[9] Ng, C., "Analysis of Multihoming in Network Mobility Support",
	draft-ietf-nemo-multihoming-issues-06 (work in progress),		draft-ietf-nemo-multihoming-issues-06 (work in progress),
	June 2006.		June 2006.
	Appendix A. Change Log From Previous Version		Appendix A. Change Log From Previous Version
	o Initial Documentation		o Initial Documentation
	Authors' Addresses		Authors' Addresses
	skipping to change at page 22, line 24 ¶		skipping to change at page 19, line 24 ¶
	5322 Endo		5322 Endo
	Fujisawa, Kanagawa 252-8520		Fujisawa, Kanagawa 252-8520
	Japan		Japan
	Phone: +81-466-49-1100		Phone: +81-466-49-1100
	Fax: +81-466-49-1395		Fax: +81-466-49-1395
	Email: ryuji@sfc.wide.ad.jp		Email: ryuji@sfc.wide.ad.jp
	URI: http://www.wakikawa.org/		URI: http://www.wakikawa.org/
	Aramoto Masafumi		Aramoto Masafumi
	Sharp Inc.		SHARP Corporation.
	Department of Environmental Information, Keio University.		Advanced Telecommunication Laboratory
	5322 Endo		Corporate Reserach And Development Group
	Fujisawa, Kanagawa 252-8520		Sharp Corporation.
			22-22 Nagaike-cho
			Abeno-ku, Osaka, Osaka 545-0013
	Japan		Japan
	Phone: +81-466-49-1100		Phone: +81-43-299-8532
	Fax: +81-466-49-1395		Fax: +81-43-299-8719
	Email: ryuji@sfc.wide.ad.jp		Email: aramoto.masafumi@sharp.co.jp
	URI: http://www.wakikawa.org/		URI: http://sharp.co.jp/
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
End of changes. 18 change blocks.
	136 lines changed or deleted		29 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/