< draft-sun-mif-address-policy-dhcp6-00.txt		draft-sun-mif-address-policy-dhcp6-01.txt >
	<Working Group Name> T. Sun		<Working Group Name> T. Sun
	Internet Draft H. Deng		Internet Draft H. Deng
	Intended status: Informational X. Duan		Intended status: Informational X. Duan
	Expires: September 2009 China Mobile		Expires: September 2009 China Mobile
	March 5, 2009		March 10,
			2009
	Address Selection Policy Configuration by DHCPv6 Option		Address Selection Policy Configuration by DHCPv6 Option
	draft-sun-mif-address-policy-dhcp6-00.txt		draft-sun-mif-address-policy-dhcp6-01.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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
	other groups may also distribute working documents as Internet-Drafts.		other groups may also distribute working documents as Internet-Drafts.
	skipping to change at page 1, line 31 ¶		skipping to change at page 1, line 32 ¶
	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 September 5, 2009.		This Internet-Draft will expire on September 10, 2009.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents carefully,		publication of this document. Please review these documents carefully,
	skipping to change at page 2, line 18 ¶		skipping to change at page 2, line 18 ¶
	interface for forwarding. RFC 3484 defines a ''policy table'' for		interface for forwarding. RFC 3484 defines a ''policy table'' for
	default IP address selection. This document extends the DHCPv6 option		default IP address selection. This document extends the DHCPv6 option
	message so that the policy table can be dynamically updated.		message so that the policy table can be dynamically updated.
	Table of Contents		Table of Contents
	1. Introduction................................................2		1. Introduction................................................2
	2. Solutions...................................................4		2. Solutions...................................................4
	2.1. Route Table Updation....................................4		2.1. Route Table Updation....................................4
	2.2. The Option of DHCPv6.......................		2.2. The Option of DHCPv6.......................
	2.3. Some Considerations of the DHCPv6 Option................5		2.3. Some Considerations of the DHCPv6 Option................6
	2.3.1. Conflict of Route Rules............................5		2.3.1. Conflict of Route Rules............................6
	2.3.2. Application Situations.............................6		2.3.2. Application Situations.............................6
	2.3.3. Not Limited to DHCP Servers........................6		2.3.3. Not Limited to DHCP Servers........................6
	3. IANA Considerations.........................................6		3. IANA Considerations.........................................6
	4. Conclusions....................................		4. Conclusions....................................
	5. References..................................................6		5. References..................................................7
	5.1. Normative References....................................6		5.1. Normative References....................................7
	5.2. Informative References..................................7		5.2. Informative References..................................7
	1. Introduction		1. Introduction
	A host such as a laptop or a smart-phone may have multiple interfaces		A host such as a laptop or a smart-phone may have multiple interfaces
	for connections, e.g., a wired Ethernet LAN, a 802.11 LAN, a 3G cell		for connections, e.g., a wired Ethernet LAN, a 802.11 LAN, a 3G cell
	network, one or multiple VPNs or tunnels. In view of more and more		network, one or multiple VPNs or tunnels. In view of more and more
	versatile applications, users may expect a host to utilize several		versatile applications, users may expect a host to utilize several
	interfaces at the same time.		interfaces at the same time.
	skipping to change at page 4, line 5 ¶		skipping to change at page 4, line 5 ¶
	o b1) An application calls sockets to build IP packets.		o b1) An application calls sockets to build IP packets.
	o b2) The socket determines the destination and selects source		o b2) The socket determines the destination and selects source
	address based on the policy table.		address based on the policy table.
	o b3) The socket sends packets to the corresponding interface.		o b3) The socket sends packets to the corresponding interface.
	o b4) The interface will forward the packets to the next hop (the		o b4) The interface will forward the packets to the next hop (the
	corresponding gateway).		corresponding gateway).
	+----+ a1 +---------+ b4 +-------+		+----+ a1 +---------+ b4 +-------+
	|DHCP|<--------- |Interface|--------->|Network|		|DHCP|<--------- |Interface|--------->|Network|
	+----+ --------> +---------+ +-------+		+----+ --------> +---------+ +-------+
	a2 | |		a2 | |
	| |		| |
	b3 | |		b3 | |
	^ | a3		^ | a3
	| ----->----+		| ----->----+
	| |		| |
	+-----------+ b1 +------+ +-----------+		+-----------+ b1 +------+ +-----------+
	|Application|---->|Socket|<------|PolicyTable|		|Application|---->|Socket|<------|PolicyTable|
	skipping to change at page 5, line 8 ¶		skipping to change at page 5, line 8 ¶
	3.2. Address Policy Option		3.2. Address Policy Option
	The DHCPv6 option is extended to contain multiple pieces of default		The DHCPv6 option is extended to contain multiple pieces of default
	address selection policy rules. Each piece of rules contains address,		address selection policy rules. Each piece of rules contains address,
	preference and label which are properties defined in [RFC3484]. The		preference and label which are properties defined in [RFC3484]. The
	ADDRESS_POLICY option is depicted in Figure 2.		ADDRESS_POLICY option is depicted in Figure 2.
	0 1 2 3		0 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		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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| OPTION_ADDRESS_POLICY | option-len |		| OPTION_ADDRESS_POLICY | option-len | IF-Based 1 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	+ Add. Prefix Len 1 | Address Prefix 1 .		+ Add. Prefix Len 1 | Address Prefix 1 .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .
	. .		. .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	+ Preference 1 | Label 1 +		+ Preference 1 | Label 1 +
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	. .		. .
	. .		. .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	+ Add. Prefix Len N | Address Prefix N .		+ IF-Based N | Add. Prefix Len N | Address Prefix N .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .
	. .		. .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	+ Preference N | Label N +		+ Preference N | Label N +
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2 The Address Policy Option.		Figure 2 The Address Policy Option.
	option-code OPTION_ ADDRESS_POLICY (should be defined by IANA).		option-code OPTION_ ADDRESS_POLICY (should be defined by IANA).
	option-len length of the route rule field in octets		option-len length of the route rule field in octets.
	Address Prefix Len Length of a IPv6 destination address prefix, an 8-		IF-Based N A flag used to indicate whether the Nth rule is
	bit unsigned integer ranging from 0 to 128.		''interface Based'' (=1) or ''host based'' (=0).
			Address Prefix Len Length of an IPv6 destination address prefix, an
			8-bit unsigned integer ranging from 0 to 128.
	Address Prefix The address prefix		Address Prefix The address prefix
	Preference A number identifies the priority of one type of IP address.		Preference A number identifies the priority of one type of IP address.
	Label A number that used to mark the correspondence between source		Label A number that used to mark the Nth rule correspondence
	and destination address.		between source and destination address.
			The ''IF-Based'' flag is used to indicate whether the rule applies only
			to the interface that received the DHCP reply message or the rule is
			''host based'' and applies to all the interfaces. This flag is
			introduced for merging route policies that received from multiple
			interfaces.
	3.3. Some Considerations of the DHCPv6 Option		3.3. Some Considerations of the DHCPv6 Option
	3.3.1. Conflict of A Policy Table		3.3.1. Conflict of A Policy Table
	For the situations where the rule in the policy table conflicts with		For the situations where the rule in the policy table conflicts with
	one previous policy table, the latter one will override the previous		one previous policy table, the latter one will override the previous
	rule.		rule.
	3.3.2. Application Situations		3.3.2. Application Situations
	skipping to change at page 7, line 23 ¶		skipping to change at page 7, line 37 ¶
	[I-D. blanchet-mif-problem-statement] Blanchet, M., "Multiple		[I-D. blanchet-mif-problem-statement] Blanchet, M., "Multiple
	Interfaces Problem Statement", draft-blanchet-mif-problem-		Interfaces Problem Statement", draft-blanchet-mif-problem-
	statement-00 (work in progress), December 2008.		statement-00 (work in progress), December 2008.
	[I-D.hui-mif-dhcpv4-routing-00] Hui, M., and Deng, H. ''Extension of		[I-D.hui-mif-dhcpv4-routing-00] Hui, M., and Deng, H. ''Extension of
	DHCPv4 for policy routing of multiple interfaces terminal,''		DHCPv4 for policy routing of multiple interfaces terminal,''
	draft-hui-mif-dhcpv4-routing-00(work in progress), February		draft-hui-mif-dhcpv4-routing-00(work in progress), February
	2009		2009
	[I-D. sun-mif-route-config-dhcp6-00] Sun, T., and Deng, H., ''DHCPv6		[I-D.yang-mif-req] Yang, P., Seite, P., Williams, C., and J. Qin,
	Route Option,'' draft-sun-mif-route-config-dhcp6-00(work in		"Requirements on multiple Interface (MIF) of simple IP",
	progress), March 2009		draft-yang-mif-req-00 (work in progress), March 2009.
			[draft-fujisaki-dhc-addr-select-opt-07] Matsumoto, A., Niinobe, S.,
			Hiromi, R., and Kanayama, K., ''Distributing Address
			Selection Policy using DHCPv6,'' draft-fujisaki-dhc-addr-
			select-opt-07 (work in progress), March 2009.
	Authors' Addresses		Authors' Addresses
	Tao Sun		Tao Sun
	China Moible		China Moible
	53A,Xibianmennei Ave.,		53A,Xibianmennei Ave.,
	Xuanwu District,		Xuanwu District,
	Beijing 100053		Beijing 100053
	China		China
	Email: suntao@chinamobile.com		Email: suntao@chinamobile.com
End of changes. 12 change blocks.
	19 lines changed or deleted		34 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/