Technical Summary
This document describes a mechanism for supporting multiple address
families in OSPFv3 using multiple instances. It maps an address
family (AF) to an OSPFv3 instance using the Instance ID field in the
OSPFv3 packet header. For example, this supports a requirement to
advertise other AFs in OSPFv3 including multicast IPv6, unicast IPv4,
and multicast IPv4. This approach is fairly simple and minimizes
extensions to OSPFv3 for supporting multiple AFs.
Working Group Summary
No controversy reported (see PROTO writeup by Acee Lindem in the
ID tracker).
Document Quality
The document has been well reviewed. Dave Ward, in his capacity
as Routing AD, reviewed it several times. There are several
implementations, at least one of which is commercially
available.
Personnel
Acee Lindem is the Document Shepherd for this document. Ross Callon
is the Responsible Area Director.