< draft-ietf-ospf-ospfv3-graceful-restart-07.txt		draft-ietf-ospf-ospfv3-graceful-restart-08.txt >
	Network Working Group P. Pillay-Esnault		Network Working Group P. Pillay-Esnault
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track A. Lindem		Intended status: Standards Track A. Lindem
	Expires: April 22, 2008 Redback Networks		Expires: October 30, 2008 Redback Networks
	October 20, 2007		April 28, 2008
	OSPFv3 Graceful Restart		OSPFv3 Graceful Restart
	draft-ietf-ospf-ospfv3-graceful-restart-07.txt		draft-ietf-ospf-ospfv3-graceful-restart-08.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of 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
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	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 April 22, 2008.		This Internet-Draft will expire on October 30, 2008.
	Copyright Notice
	Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document describes the OSPFv3 graceful restart. The OSPFv3		This document describes the OSPFv3 graceful restart. The OSPFv3
	graceful restart is identical to OSPFv2 except for the differences		graceful restart is identical to OSPFv2 except for the differences
	described in this document. These differences include the format of		described in this document. These differences include the format of
	the grace Link State Advertisements (LSA) and other considerations.		the grace Link State Advertisements (LSA) and other considerations.
	Table of Contents		Table of Contents
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	2.2. Grace LSA Format . . . . . . . . . . . . . . . . . . . . . 4		2.2. Grace LSA Format . . . . . . . . . . . . . . . . . . . . . 4
	3. Additional Considerations for OSPFv3 Graceful Restart . . . . . 5		3. Additional Considerations for OSPFv3 Graceful Restart . . . . . 5
	3.1. Preservation of LSA ID to Prefix Correspondence . . . . . . 5		3.1. Preservation of LSA ID to Prefix Correspondence . . . . . . 5
	3.2. Preservation of Interface IDs for Link-LSAs,		3.2. Preservation of Interface IDs for Link-LSAs,
	Network-LSAs, and Router-LSAs . . . . . . . . . . . . . . . 5		Network-LSAs, and Router-LSAs . . . . . . . . . . . . . . . 5
	4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6		4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6		7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 6		7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
	7.2. Informative References . . . . . . . . . . . . . . . . . . 6		7.2. Informative References . . . . . . . . . . . . . . . . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
	Intellectual Property and Copyright Statements . . . . . . . . . . 8		Intellectual Property and Copyright Statements . . . . . . . . . . 8
	1. Introduction		1. Introduction
	Graceful OSPF restart [GRACE] describes a mechanism to restart the		Graceful OSPF restart [GRACE] describes a mechanism to restart the
	control plane of an OSPFv2 [OSPFv2] router which still has its		control plane of an OSPFv2 [OSPFv2] router which still has its
	forwarding plane intact with a minimum of disruption to the network.		forwarding plane intact with a minimum of disruption to the network.
	In general, the methods described in [GRACE] work for OSPFv3 [OSPFv3]		In general, the methods described in [GRACE] work for OSPFv3 [OSPFv3]
	skipping to change at page 6, line 8 ¶		skipping to change at page 6, line 8 ¶
	interface ID, as described in section 3.1.2 of [OSPFv3], MUST be		interface ID, as described in section 3.1.2 of [OSPFv3], MUST be
	preserved by the restarting router across restarts.		preserved by the restarting router across restarts.
	Many implementations currently use the interface's MIB-II IfIndex		Many implementations currently use the interface's MIB-II IfIndex
	[MIB-INTF] for Interface ID. The persistence of Interface ID across		[MIB-INTF] for Interface ID. The persistence of Interface ID across
	reboots is described in section 3.1.5 of [MIB-PERS].		reboots is described in section 3.1.5 of [MIB-PERS].
	4. Security Considerations		4. Security Considerations
	[OSPFv3-AUTH] relies on manual key distribution which precludes the		[OSPFv3-AUTH] relies on manual key distribution which precludes the
	use of replay protection utilizing sequence numbers. Hence, this		use of replay protection utilizing sequence numbers. The replay of
			an OSPF Link-Update containing a grace-LSA would allow an attacker to
			deceive neighboring routers into believing that a router that has
			been taken out of service (either intentionally or via a malicious
			action by the same attacker) is still active and is in the process of
			graceful restart. However, this attack is much more difficult than
			the obvious replay of standard OSPFv3 hello packets to accomplish the
			same thing by keeping the adjacency up. Since hello packets are sent
			more predictably and knowledge of the key is not required, the risk
			added by OSPFv3 graceful restart is insignificant. Hence, this
	document does not raise any new security concerns other than those		document does not raise any new security concerns other than those
	covered in [OSPFv3], [OSPFv3-AUTH], and [GRACE].		covered in [OSPFv3], [OSPFv3-AUTH], and [GRACE].
	5. IANA Considerations		5. IANA Considerations
	A new LSA function code will be required for the OSPFv3 grace-LSA.		A new LSA function code will be required for the OSPFv3 grace-LSA.
	Assignment of 0x000b has been suggested herein. Grace-LSA TLVs and		Assignment of 0x000b has been suggested herein in the "OSPFv3 LSA
	sub-TLVs will share the same IANA registry as the TLVs and sub-TLVs		Function Codes" sub-registry of the "Open Shortest Path First v3
	used by the OSPFv2 grace-LSA.		(OSPFv3) Parameters" registry. OSPFv3 grace-LSA TLVs and sub-TLVs
			use the "OSPFv2 Grace LSA Top Level TLV" IANA sub-registry of the
			"Open Shortest Path First v2 (OSPFv2) Parameters" registry.
	6. Acknowledgments		6. Acknowledgments
	Many thanks to Kireeti Kompella, Les Ginsberg, and David Ward with		Many thanks to Kireeti Kompella, Les Ginsberg, and David Ward with
	whom much of this was discussed. The authors also wish to thank		whom much of this was discussed. The authors also wish to thank
	Kunihiro Ishiguro and Vivek Dubey for their comments.		Kunihiro Ishiguro and Vivek Dubey for their comments.
	This document was produced using Marshall Rose's xml2rfc tool.		This document was produced using Marshall Rose's xml2rfc tool.
	7. References		7. References
	skipping to change at page 8, line 7 ¶		skipping to change at page 8, line 7 ¶
	Acee Lindem		Acee Lindem
	Redback Networks		Redback Networks
	102 Carric Bend Court		102 Carric Bend Court
	Cary, NC 27519		Cary, NC 27519
	USA		USA
	Email: acee@redback.com		Email: acee@redback.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	skipping to change at page 8, line 44 ¶		skipping to change at line 328 ¶
	attempt made to obtain a general license or permission for the use of		attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Acknowledgment
	Funding for the RFC Editor function is provided by the IETF
	Administrative Support Activity (IASA).
End of changes. 8 change blocks.
	14 lines changed or deleted		21 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/