Diff: draft-ietf-ospf-ospfv3-autoconfig-11.txt - draft-ietf-ospf-ospfv3-autoconfig-12.txt

	< draft-ietf-ospf-ospfv3-autoconfig-11.txt	draft-ietf-ospf-ospfv3-autoconfig-12.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	Updates: 5340 (if approved) J. Arkko
	Expires: July 19, 2015 Ericsson	Intended status: Standards Track Ericsson
	January 15, 2015	Expires: July 20, 2015 January 16, 2015

	OSPFv3 Auto-Configuration	OSPFv3 Auto-Configuration

	draft-ietf-ospf-ospfv3-autoconfig-11.txt	draft-ietf-ospf-ospfv3-autoconfig-12.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 19, 2015.	This Internet-Draft will expire on July 20, 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 3, line 49 ¶	skipping to change at page 3, line 49 ¶
	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	Thanks to Adam Montville for Security Area Directorate review and
	comments.	comments.


		Thanks to Qin Wu for Operations & Management Area Directorate review
		and comments.

		Thanks to Robert Sparks for General Area (GEN-ART) 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 7, line 30 ¶	skipping to change at page 7, line 33 ¶
	Router ID specified in the LSA header. LSAs received with the local	Router ID specified in the LSA header. LSAs received with the local
	OSPFv3 Router's Router ID in the LSA header are perceived as self-	OSPFv3 Router's Router ID in the LSA header are perceived as self-
	originated (see section 4.6 of [OSPFV3]). In these received Auto-	originated (see section 4.6 of [OSPFV3]). In these received Auto-
	Configuration LSAs, the Router-Hardware-Fingerprint TLV is compared	Configuration LSAs, the Router-Hardware-Fingerprint TLV is compared
	against the OSPFv3 Router's own router hardware fingerprint. If the	against the OSPFv3 Router's own router hardware fingerprint. If the
	fingerprints are not equal, there is a duplicate Router ID conflict	fingerprints are not equal, there is a duplicate Router ID conflict
	and the OSPFv3 router with the numerically smaller router hardware	and the OSPFv3 router with the numerically smaller router hardware
	fingerprint MUST select a new Router ID as described in Section 7.3.	fingerprint MUST select a new Router ID as described in Section 7.3.

	This new LSA is designated for information related to OSPFv3 Auto-	This new LSA is designated for information related to OSPFv3 Auto-

	configuration and, in the future, could be used other auto-	configuration and, in the future, could be used for other auto-
	configuration information, e.g., global IPv6 prefixes. However, this	configuration information, e.g., global IPv6 prefixes. However, this
	is beyond the scope of this document.	is beyond the scope of this document.

	7.2.1. OSPFv3 Router Auto-Configuration LSA	7.2.1. OSPFv3 Router Auto-Configuration LSA

	The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and	The OSPFv3 Auto-Configuration (AC) LSA has a function code of TBD and
	the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit	the S2/S1 bits set to 01 indicating Area Flooding Scope. The U bit
	will be set indicating that the OSPFv3 AC LSA should be flooded even	will be set indicating that the OSPFv3 AC LSA should be flooded even
	if it is not understood. The Link State ID (LSID) value will be a	if it is not understood. The Link State ID (LSID) value will be a
	integer index used to discriminate between multiple AC LSAs	integer index used to discriminate between multiple AC LSAs

	skipping to change at page 10, line 45 ¶	skipping to change at page 10, line 45 ¶
	required, OSPFv3 IPsec [OSPFV3-IPSEC] or stronger OSPFv3	required, OSPFv3 IPsec [OSPFV3-IPSEC] or stronger OSPFv3
	Authentication trailer [OSPFV3-AUTH-TRAILER] algorithms MAY be used	Authentication trailer [OSPFV3-AUTH-TRAILER] algorithms MAY be used
	at the expense of additional configuration. The configuration and	at the expense of additional configuration. The configuration and
	operational description of such deployments is beyond the scope of	operational description of such deployments is beyond the scope of
	this document.	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]. The would allow explicit override of
	key configuration recommended in Section 4. However, it is	autoconfigured parameters in situations where it is required (e.g.,
	acknowledged that there may be some deployment scenarios where manual	if the deployment requires multiple OSPFv3 areas). This is in
	authentication key configuration is not required.	addition to the authentication key configuration recommended in
		Section 4 which supports OSPFv3 authentication with the absolute
		minimum manual configuration.

	Since there is a small possibility of OSPFv3 Router ID collisions,	Since there is a small possibility of OSPFv3 Router ID collisions,
	manual configuration of OSPFv3 Router IDs is RECOMMENDED in OSPFv3	manual configuration of OSPFv3 Router IDs is RECOMMENDED in OSPFv3
	routing domains where route recovergence due to a router ID change is	routing domains where route recovergence due to a router ID change is
	intolerable.	intolerable.

	10. IANA Considerations	10. IANA Considerations

	This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto-	This specification defines an OSPFv3 LSA Type for the OSPFv3 Auto-
	Configuration (AC) LSA, as described in Section 7.2.1. The value TBD	Configuration (AC) LSA, as described in Section 7.2.1. The value TBD

End of changes. 6 change blocks.
	10 lines changed or deleted	18 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/