< draft-ietf-ospf-multi-instance-01.txt		draft-ietf-ospf-multi-instance-02.txt >
	Network Working Group A. Lindem		Network Working Group A. Lindem
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Standards Track A. Roy		Intended status: Standards Track A. Roy
	Expires: April 6, 2010 S. Mirtorabi		Expires: October 20, 2010 S. Mirtorabi
	Cisco Systems		Cisco Systems
	October 3, 2009		April 18, 2010
	OSPF Multi-Instance Extensions		OSPF Multi-Instance Extensions
	draft-ietf-ospf-multi-instance-01.txt		draft-ietf-ospf-multi-instance-02.txt
			Abstract
			OSPFv3 includes a mechanism for supporting multiple instances on the
			same link. OSPFv2 could benefit from such a mechanism in order to
			support multiple routing domains on the same subnet. The OSPFv2
			instance ID is reserved for support of separate OSPFv2 protocol
			instances. This is different from OSPFv3 where it could be used for
			other purposes such as putting the same link in multiple areas.
			OSPFv2 supports this capability using a separate subnet or the OSPF
			multi-area adjacency capability.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		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."
	The list of current Internet-Drafts can be accessed at		This Internet-Draft will expire on October 20, 2010.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on April 6, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2010 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 in effect on the date of		Provisions Relating to IETF Documents
	publication of this document (http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info) in effect on the date of
	Please review these documents carefully, as they describe your rights		publication of this document. Please review these documents
	and restrictions with respect to this document.		carefully, as they describe your rights and restrictions with respect
			to this document. Code Components extracted from this document must
	Abstract		include Simplified BSD License text as described in Section 4.e of
			the Trust Legal Provisions and are provided without warranty as
	OSPFv3 includes a mechanism for supporting multiple instances on the		described in the Simplified BSD License.
	same link. OSPFv2 could benefit from such a mechanism in order to
	support multiple routing domains on the same subnet. The OSPFv2
	instance ID is reserved for support of separate OSPFv2 protocol
	instances. This is different from OSPFv3 where it could be used for
	other purposes such as putting the same link in multiple areas.
	OSPFv2 supports this capability using a separate subnet or the OSPF
	multi-area adjacency capability.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3		1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
	2. OSPFv2 Instance Packet Encoding . . . . . . . . . . . . . . . 4		2. OSPFv2 Instance Packet Encoding . . . . . . . . . . . . . . . 4
	3. OSPF Interface Instance ID . . . . . . . . . . . . . . . . . . 6		3. OSPF Interface Instance ID . . . . . . . . . . . . . . . . . . 6
	3.1. Sending and Receiving OSPF packets . . . . . . . . . . . . 6		3.1. Sending and Receiving OSPF packets . . . . . . . . . . . . 6
	4. State Sharing Optimizations between OSPF instances . . . . . . 7		4. State Sharing Optimizations between OSPF instances . . . . . . 7
	5. Backward Compatibility and Deployment Considerations . . . . . 8		5. Backward Compatibility and Deployment Considerations . . . . . 8
End of changes. 8 change blocks.
	30 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/