< draft-ietf-ospf-ospfv3-autoconfig-04.txt		draft-ietf-ospf-ospfv3-autoconfig-05.txt >
	Network Working Group A. Lindem		Network Working Group A. Lindem
	Internet-Draft J. Arkko		Internet-Draft J. Arkko
	Intended status: Standards Track Ericsson		Intended status: Standards Track Ericsson
	Expires: February 20, 2014 August 19, 2013		Expires: April 23, 2014 October 20, 2013
	OSPFv3 Auto-Configuration		OSPFv3 Auto-Configuration
	draft-ietf-ospf-ospfv3-autoconfig-04.txt		draft-ietf-ospf-ospfv3-autoconfig-05.txt
	Abstract		Abstract
	OSPFv3 is a candidate for deployments in environments where auto-		OSPFv3 is a candidate for deployments in environments where auto-
	configuration is a requirement. One such environment is the IPv6		configuration is a requirement. One such environment is the IPv6
	home network where users expect to simply plug in a router and have		home network where users expect to simply plug in a router and have
	it automatically use OSPFv3 for intra-domain routing. This document		it automatically use OSPFv3 for intra-domain routing. This document
	describes the necessary mechanisms for OSPFv3 to be self-configuring.		describes the necessary mechanisms for OSPFv3 to be self-configuring.
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 February 20, 2014.		This Internet-Draft will expire on April 23, 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 2, line 23 ¶		skipping to change at page 2, line 23 ¶
	not be created outside the IETF Standards Process, except to format		not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other		it for publication as an RFC or to translate it into languages other
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3		1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
	1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3		1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3
	2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . . 5		2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . . 5
	3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 6		3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 7
	3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 6		3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . . 7
	4. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 7		4. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . . 8
	5. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 8		5. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . . 9
	6. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 9		6. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 10
	6.1. Duplicate Router ID Detection for Neighbors . . . . . . . 9		6.1. Duplicate Router ID Detection for Neighbors . . . . . . . 10
	6.2. Duplicate Router ID Detection for OSPFv3 Routers that		6.2. Duplicate Router ID Detection for OSPFv3 Routers that
	are not Neighbors . . . . . . . . . . . . . . . . . . . . 9		are not Neighbors . . . . . . . . . . . . . . . . . . . . 10
	6.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 9		6.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . . 10
	6.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 11		6.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 12
	6.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 11		6.3. Duplicate Router ID Resolution . . . . . . . . . . . . . . 12
	6.4. Change to RFC 2328 Section 13.4, 'Receiving		6.4. Change to RFC 2328 Section 13.4, 'Receiving
	Self-Originated LSA' Processing . . . . . . . . . . . . . 12		Self-Originated LSA' Processing . . . . . . . . . . . . . 13
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 13		7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
	8. Management Considerations . . . . . . . . . . . . . . . . . . 14		8. Management Considerations . . . . . . . . . . . . . . . . . . 15
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16		10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	10.1. Normative References . . . . . . . . . . . . . . . . . . . 16		10.1. Normative References . . . . . . . . . . . . . . . . . . . 17
	10.2. Informative References . . . . . . . . . . . . . . . . . . 16		10.2. Informative References . . . . . . . . . . . . . . . . . . 17
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
	1. Introduction		1. Introduction
	OSPFv3 [OSPFV3] is a candidate for deployments in environments where		OSPFv3 [OSPFV3] is a candidate for deployments in environments where
	auto-configuration is a requirement. Its operation is largely		auto-configuration is a requirement. Its operation is largely
	unchanged from the base OSPFv3 protocol specification [OSPFV3].		unchanged from the base OSPFv3 protocol specification [OSPFV3].
	The following aspects of OSPFv3 auto-configuration are described:		The following aspects of OSPFv3 auto-configuration are described:
	1. Default OSPFv3 Configuration		1. Default OSPFv3 Configuration
	skipping to change at page 5, line 5 ¶		skipping to change at page 4, line 7 ¶
	OSPFv3 Instance ID auto-configuration.		OSPFv3 Instance ID auto-configuration.
	Thanks to Faraz Shamim for review and comments.		Thanks to Faraz Shamim for review and comments.
	Thanks to Mark Smith for the requirement to reduce the adjacency		Thanks to Mark Smith for the requirement to reduce the adjacency
	formation delay in the back-to-back ethernet topologies that are		formation delay in the back-to-back ethernet topologies that are
	prevalent in home networks.		prevalent in home networks.
	The RFC text was produced using Marshall Rose's xml2rfc tool.		The RFC text was produced using Marshall Rose's xml2rfc tool.
			Special thanks go to Markus Stenberg for his implementation of this
			specification.
	2. OSPFv3 Default Configuration		2. OSPFv3 Default Configuration
	For complete auto-configuration, OSPFv3 will need to choose suitable		For complete auto-configuration, OSPFv3 will need to choose suitable
	configuration defaults. These include:		configuration defaults. These include:
	1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in		1. Area 0 Only - All auto-configured OSPFv3 interfaces MUST be in
	area 0.		area 0.
	2. OSPFv3 SHOULD be auto-configured on for IPv6 on all interfaces		2. OSPFv3 SHOULD be auto-configured on for IPv6 on all interfaces
	intended as general IPv6-capable routers. Optionally, an		intended as general IPv6-capable routers. Optionally, an
	interface MAY be excluded if it is clear that running OSPFv3 on		interface MAY be excluded if it is clear that running OSPFv3 on
	the interface is not required. For example, if manual		the interface is not required. For example, if manual
	configuration or another condition indicates that an interface is		configuration or another condition indicates that an interface is
	connected to an Internet Service Provider (ISP) and there is no		connected to an Internet Service Provider (ISP) and there is no
	Border Gateway Protocol (BGP) [BGP] peering, there is typically		Border Gateway Protocol (BGP) [BGP] peering, there is typically
	no need to employ OSPFv3. However, note that in many		no need to employ OSPFv3. In fact, [IPv6-CPE] specifically
	environments it can be useful to test whether an OSPFv3 adjacency		requires that IPv6 Customer Premise Equipment (CPE) routers do
	can be established. In home networking environments, an		not initiate any dynamic routing protocol by default on the
	interface where no OSPFv3 neighbors are found but a DHCP IPv6		router's WAN, i.e., ISP-facing, interface. In home networking
	prefix can be acquired may be considered an ISP-facing interface		environments, an interface where no OSPFv3 neighbors are found
	and running OSPFv3 is unnecessary.		but a DHCP IPv6 prefix can be acquired may be considered an ISP-
			facing interface and running OSPFv3 is unnecessary.
	3. OSPFv3 interfaces will be auto-configured to an interface type		3. OSPFv3 interfaces will be auto-configured to an interface type
	corresponding to their layer-2 capability. For example, Ethernet		corresponding to their layer-2 capability. For example, Ethernet
	interfaces and vanilla Wi-Fi interfaces will be auto-configured		interfaces and vanilla Wi-Fi interfaces will be auto-configured
	as OSPFv3 broadcast networks and Point-to-Point Protocol (PPP)		as OSPFv3 broadcast networks and Point-to-Point Protocol (PPP)
	interfaces will be auto-configured as OSPFv3 Point-to-Point		interfaces will be auto-configured as OSPFv3 Point-to-Point
	interfaces. Most extant OSPFv3 implementations do this already.		interfaces. Most extant OSPFv3 implementations do this already.
	Auto-configured operation over wireless networks requiring a		Auto-configured operation over wireless networks requiring a
	point-to-multipoint (P2MP) topology and dynamic metrics based on		point-to-multipoint (P2MP) topology and dynamic metrics based on
	wireless feedback is not within the scope of this document.		wireless feedback is not within the scope of this document.
	skipping to change at page 17, line 5 ¶		skipping to change at page 17, line 44 ¶
	10.2. Informative References		10.2. Informative References
	[ASYNC-HELLO]		[ASYNC-HELLO]
	Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold		Anand, M., Grover, H., and A. Roy, "Asymmetric OSPF Hold
	Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in		Timer", draft-madhukar-ospf-agr-asymmetric-01.txt (work in
	progress).		progress).
	[BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway		[BGP] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
	Protocol 4 (BGP-4)", RFC 4271, January 2006.		Protocol 4 (BGP-4)", RFC 4271, January 2006.
			[IPv6-CPE]
			Singh, H., Beebee, W., Donley, C., Stark, B., and O.
			Troan, "Basic Requirements for IPv6 Customer Edge
			Routers", RFC 6204, April 2011.
	Authors' Addresses		Authors' Addresses
	Acee Lindem		Acee Lindem
	Ericsson		Ericsson
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	USA		USA
	Email: acee.lindem@ericsson.com		Email: acee.lindem@ericsson.com
End of changes. 9 change blocks.
	27 lines changed or deleted		36 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/