< draft-ietf-ospf-ospfv3-autoconfig-10.txt		draft-ietf-ospf-ospfv3-autoconfig-11.txt >
	Network Working Group A. Lindem		Network Working Group A. Lindem
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track J. Arkko		Intended status: Standards Track J. Arkko
	Expires: July 9, 2015 Ericsson		Expires: July 19, 2015 Ericsson
	January 5, 2015		January 15, 2015
	OSPFv3 Auto-Configuration		OSPFv3 Auto-Configuration
	draft-ietf-ospf-ospfv3-autoconfig-10.txt		draft-ietf-ospf-ospfv3-autoconfig-11.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 35 ¶		skipping to change at page 1, line 35 ¶
	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 July 9, 2015.		This Internet-Draft will expire on July 19, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 16 ¶		skipping to change at page 2, line 16 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3		1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
	1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3		1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3
	2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . 4		2. OSPFv3 Default Configuration . . . . . . . . . . . . . . . . 4
	3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 5		3. OSPFv3 HelloInterval/RouterDeadInterval Flexibility . . . . . 5
	3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . 5		3.1. Wait Timer Reduction . . . . . . . . . . . . . . . . . . 5
	4. OSPFv3 Minimal Authentication Configuration . . . . . . . . . 5		4. OSPFv3 Minimal Authentication Configuration . . . . . . . . . 5
	5. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . 5		5. OSPFv3 Router ID Selection . . . . . . . . . . . . . . . . . 6
	6. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . 6		6. OSPFv3 Adjacency Formation . . . . . . . . . . . . . . . . . 6
	7. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 6		7. OSPFv3 Duplicate Router ID Detection and Resolution . . . . . 6
	7.1. Duplicate Router ID Detection for Neighbors . . . . . . . 6		7.1. Duplicate Router ID Detection for Neighbors . . . . . . . 6
	7.2. Duplicate Router ID Detection for OSPFv3 Routers that are		7.2. Duplicate Router ID Detection for OSPFv3 Routers that are
	not Neighbors . . . . . . . . . . . . . . . . . . . . . . 7		not Neighbors . . . . . . . . . . . . . . . . . . . . . . 7
	7.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . 7		7.2.1. OSPFv3 Router Auto-Configuration LSA . . . . . . . . 7
	7.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 9		7.2.2. Router-Hardware-Fingerprint TLV . . . . . . . . . . . 9
	7.3. Duplicate Router ID Resolution . . . . . . . . . . . . . 9		7.3. Duplicate Router ID Resolution . . . . . . . . . . . . . 9
	7.4. Change to RFC 2328 Section 13.4, 'Receiving Self-		7.4. Change to RFC 2328 Section 13.4, 'Receiving Self-
	Originated LSA' Processing . . . . . . . . . . . . . . . 9		Originated LSA' Processing . . . . . . . . . . . . . . . 9
	skipping to change at page 3, line 46 ¶		skipping to change at page 3, line 46 ¶
	OSPFv3 hardware fingerprint content.		OSPFv3 hardware fingerprint content.
	Thanks to Curtis Villamizar for document review and analysis of		Thanks to Curtis Villamizar for document review and analysis of
	duplicate router-id resolution nuances.		duplicate router-id resolution nuances.
	Thanks to Uma Chunduri for comments during OSPF WG last call.		Thanks to Uma Chunduri for comments during OSPF WG last call.
	Thanks to Martin Vigoureux for Routing Area Directorate review and		Thanks to Martin Vigoureux for Routing Area Directorate review and
	comments.		comments.
			Thanks to Adam Montville for Security Area Directorate review and
			comments.
	Special thanks go to Markus Stenberg for his implementation of this		Special thanks go to Markus Stenberg for his implementation of this
	specification in Bird.		specification in Bird.
	Special thanks also go to David Lamparter for his implementation of		Special thanks also go to David Lamparter for his implementation of
	this specification in Quagga.		this specification in Quagga.
	The RFC text was produced using Marshall Rose's xml2rfc tool.		The RFC text was produced using Marshall Rose's xml2rfc tool.
	2. OSPFv3 Default Configuration		2. OSPFv3 Default Configuration
	skipping to change at page 5, line 47 ¶		skipping to change at page 6, line 7 ¶
	overrides the goal of complete OSPFv3 autoconfiguration. Therefore,		overrides the goal of complete OSPFv3 autoconfiguration. Therefore,
	it is RECOMMENDED that OSPFv3 routers supporting this specification		it is RECOMMENDED that OSPFv3 routers supporting this specification
	minimally offer an option to explicitly configure a single password		minimally offer an option to explicitly configure a single password
	for HMAC-SHA authentication as described in [OSPFV3-AUTH-TRAILER].		for HMAC-SHA authentication as described in [OSPFV3-AUTH-TRAILER].
	When configured, the password will be used on all auto-configured		When configured, the password will be used on all auto-configured
	interfaces with the Security Association Identifier (SA ID) set to 1		interfaces with the Security Association Identifier (SA ID) set to 1
	and HMAC-SHA-256 used as the authentication algorithm.		and HMAC-SHA-256 used as the authentication algorithm.
	5. OSPFv3 Router ID Selection		5. OSPFv3 Router ID Selection
	An OSPFv3 router requires a unique Router ID for correct protocol		An OSPFv3 router requires a unique Router ID within the OSPFv3
	operation. An OSPFv3 router implementing this specification will		routing domain for correct protocol operation. An OSPFv3 router
	select a router-id that has a high probability of uniqueness. A		implementing this specification will select a router-id that has a
	pseudo-random number SHOULD be used for the OSPFv3 Router ID. The		high probability of uniqueness. A pseudo-random number SHOULD be
	generation should be seeded with a variable that is likely to be		used for the OSPFv3 Router ID. The generation SHOULD be seeded with
	unique in the applicable OSPFv3 router deployment. A good choice of		a variable that is likely to be unique in the applicable OSPFv3
	seed would be some portion or hash of the Router-Hardware-Fingerprint		router deployment. A good choice of seed would be some portion or
	as described in Section 7.2.2.		hash of the Router-Hardware-Fingerprint as described in
			Section 7.2.2.
	Since there is a possibility of a Router ID collision, duplicate		Since there is a possibility of a Router ID collision, duplicate
	Router ID detection and resolution are required as described in		Router ID detection and resolution are required as described in
	Section 7 and Section 7.3. OSPFv3 routers SHOULD maintain the last		Section 7 and Section 7.3. OSPFv3 routers SHOULD maintain the last
	successfully chosen Router ID in non-volatile storage to avoid		successfully chosen Router ID in non-volatile storage to avoid
	collisions subsequent to when an autoconfigured OSPFv3 router is		collisions subsequent to when an autoconfigured OSPFv3 router is
	first added to the OSPFv3 routing domain.		first added to the OSPFv3 routing domain.
	6. OSPFv3 Adjacency Formation		6. OSPFv3 Adjacency Formation
	skipping to change at page 10, line 34 ¶		skipping to change at page 10, line 34 ¶
	The goals of security and complete OSPFv3 auto-configuration are		The goals of security and complete OSPFv3 auto-configuration are
	somewhat contradictory. When no explicit security configuration		somewhat contradictory. When no explicit security configuration
	takes place, auto-configuration implies that additional devices		takes place, auto-configuration implies that additional devices
	placed in the network are automatically adopted as a part of the		placed in the network are automatically adopted as a part of the
	network. However, auto-configuration can also be combined with		network. However, auto-configuration can also be combined with
	password configuration (see Section 4) or future extensions for		password configuration (see Section 4) or future extensions for
	automatic pairing between devices. These mechanisms can help provide		automatic pairing between devices. These mechanisms can help provide
	an automatically configured, securely routed network.		an automatically configured, securely routed network.
			In deployments where stronger authentification or encryption is
			required, OSPFv3 IPsec [OSPFV3-IPSEC] or stronger OSPFv3
			Authentication trailer [OSPFV3-AUTH-TRAILER] algorithms MAY be used
			at the expense of additional configuration. The configuration and
			operational description of such deployments is beyond the scope of
			this document.
	9. Management Considerations		9. Management Considerations
	It is RECOMMENDED that OSPFv3 routers supporting this specification		It is RECOMMENDED that OSPFv3 routers supporting this specification
	also allow explicit configuration of OSPFv3 parameters as specified		also allow explicit configuration of OSPFv3 parameters as specified
	in Appendix C of [OSPFV3]. This is in addition to the authentication		in Appendix C of [OSPFV3]. This is in addition to the authentication
	key configuration recommended in Section 4. However, it is		key configuration recommended in Section 4. However, it is
	acknowledged that there may be some deployment scenarios where manual		acknowledged that there may be some deployment scenarios where manual
	authentication key configuration is not required.		authentication key configuration is not required.
	Since there is a small possibility of OSPFv3 Router ID collisions,		Since there is a small possibility of OSPFv3 Router ID collisions,
	skipping to change at page 12, line 28 ¶		skipping to change at page 12, line 31 ¶
	[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)		[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
	Registration Authority", IEEE Tutorial		Registration Authority", IEEE Tutorial
	http://standards.ieee.org/regauth/oui/tutorials/		http://standards.ieee.org/regauth/oui/tutorials/
	EUI64.html, March 1997.		EUI64.html, March 1997.
	[IPv6-CPE]		[IPv6-CPE]
	Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic		Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic
	Requirements for IPv6 Customer Edge Routers", RFC 7084,		Requirements for IPv6 Customer Edge Routers", RFC 7084,
	November 2013.		November 2013.
			[OSPFV3-IPSEC]
			Gupta, M. and S. Melam, "Authentication/Confidentiality
			for OSPFv3", RFC 4552, June 2006.
	Authors' Addresses		Authors' Addresses
	Acee Lindem		Acee Lindem
	Cisco Systems		Cisco Systems
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	USA		USA
	Email: acee@cisco.com		Email: acee@cisco.com
End of changes. 8 change blocks.
	13 lines changed or deleted		28 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/