Protocol Action: 'Support of address families in OSPFv3' to Proposed Standard

The IESG <> Wed, 17 February 2010 14:55 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id 65F993A7ECB; Wed, 17 Feb 2010 06:55:16 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Support of address families in OSPFv3' to Proposed Standard
Message-Id: <>
Date: Wed, 17 Feb 2010 06:55:16 -0800 (PST)
Cc: ospf mailing list <>, ospf chair <>, Internet Architecture Board <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 17 Feb 2010 14:55:16 -0000

The IESG has approved the following document:

- 'Support of address families in OSPFv3 '
   <draft-ietf-ospf-af-alt-10.txt> as a Proposed Standard

This document is the product of the Open Shortest Path First IGP Working Group. 

The IESG contact persons are Ross Callon and Adrian Farrel.

A URL of this Internet-Draft is:

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


   Acee Lindem is the Document Shepherd for this document. Ross Callon
   is the Responsible Area Director.