draft-ietf-6man-addr-select-opt-12.txt		draft-ietf-6man-addr-select-opt-13.txt
	6man Working Group A. Matsumoto		6man Working Group A. Matsumoto
	Internet-Draft T. Fujisaki		Internet-Draft T. Fujisaki
	Intended status: Standards Track NTT		Intended status: Standards Track NTT
	Expires: March 25, 2014 T. Chown		Expires: April 12, 2014 T. Chown
	University of Southampton		University of Southampton
	September 21, 2013		October 09, 2013
	Distributing Address Selection Policy using DHCPv6		Distributing Address Selection Policy using DHCPv6
	draft-ietf-6man-addr-select-opt-12.txt		draft-ietf-6man-addr-select-opt-13.txt
	Abstract		Abstract
	RFC 6724 defines default address selection mechanisms for IPv6 that		RFC 6724 defines default address selection mechanisms for IPv6 that
	allow nodes to select an appropriate address when faced with multiple		allow nodes to select an appropriate address when faced with multiple
	source and/or destination addresses to choose between. RFC 6724		source and/or destination addresses to choose between. RFC 6724
	allows for the future definition of methods to administratively		allows for the future definition of methods to administratively
	configure the address selection policy information. This document		configure the address selection policy information. This document
	defines a new DHCPv6 option for such configuration, allowing a site		defines a new DHCPv6 option for such configuration, allowing a site
	administrator to distribute address selection policy overriding the		administrator to distribute address selection policy overriding the
	skipping to change at page 1, line 40		skipping to change at page 1, line 40
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on March 25, 2014.		This Internet-Draft will expire on April 12, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 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		publication of this document. Please review these documents
	skipping to change at page 6, line 25		skipping to change at page 6, line 25
	(b) preserve the existing flags and active policy table, whether		(b) preserve the existing flags and active policy table, whether
	this be the default policy table, or user configured policy.		this be the default policy table, or user configured policy.
	Choice (a) SHOULD be the default, i.e. that the policy table is not		Choice (a) SHOULD be the default, i.e. that the policy table is not
	explictly configured by the user.		explictly configured by the user.
	3.2. Handling stale distributed flags and policy table		3.2. Handling stale distributed flags and policy table
	When the information from the DHCP server goes stale, the flags and		When the information from the DHCP server goes stale, the flags and
	the policy table received from the DHCP server SHOULD be deprecated.		the policy table received from the DHCP server SHOULD be deprecated.
			The local configuration SHOULD be restored when the DHCP-supplied
			configuration has been deprecated. In order to implement this, a
			host can retain the local configuration even after the flags and the
			policy table is updated by the distributed flags and policy table.
	The received information can be considered stale in several cases,		The received information can be considered stale in several cases,
	e.g., when the interface goes down, the DHCP server does not respond		e.g., when the interface goes down, the DHCP server does not respond
	for a certain amount of time, and the Information Refresh Time is		for a certain amount of time, or the Information Refresh Time has
	expired.		expired.
	3.3. Handling multiple interfaces		3.3. Handling multiple interfaces
	The policy table, and other parameters specified in this document,		The policy table, and other parameters specified in this document,
	are node-global information by their nature. One reason being that		are node-global information by their nature. One reason being that
	the outbound interface is usually chosen after destination address		the outbound interface is usually chosen after destination address
	selection. So a host cannot make use of multiple address selection		selection. So a host cannot make use of multiple address selection
	policies even if they are stored per interface.		policies even if they are stored per interface.
End of changes. 6 change blocks.
	5 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/