Protocol Action: 'The OSPF Opaque LSA Option' to Proposed Standard

The IESG <> Fri, 09 May 2008 20:02 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id 7D18F3A68DF; Fri, 9 May 2008 13:02:14 -0700 (PDT)
Received: by (Postfix, from userid 30) id 02A743A68D5; Fri, 9 May 2008 13:02:07 -0700 (PDT)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'The OSPF Opaque LSA Option' to Proposed Standard
Message-Id: <>
Date: Fri, 09 May 2008 13:02:07 -0700
Cc: ospf mailing list <>, ospf chair <>, Internet Architecture Board <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The IESG has approved the following document:

- 'The OSPF Opaque LSA Option '
   <draft-ietf-ospf-rfc2370bis-05.txt> as a Proposed Standard

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

The IESG contact persons are David Ward and Ross Callon.

A URL of this Internet-Draft is:

Technical Summary

   This document defines enhancements to the OSPF protocol to support a
   new class of link-state advertisements (LSA) called Opaque LSAs.
   Opaque LSAs provide a generalized mechanism to allow for the future
   extensibility of OSPF. Opaque LSAs consist of a standard LSA header
   followed by application-specific information.  The information field
   may be used directly by OSPF or by other applications.  Standard OSPF
   link-state database flooding mechanisms are used to distribute Opaque
   LSAs to all or some limited portion of the OSPF topology.

   This document replaces RFC 2370 and adds to it a mechanism to enable
   an OSPF router to validate AS-scope opaque LSAs originated outside of
   the router's OSPF area.

Working Group Summary

   No dissent reported (see PROTO writeup by Acee Linden). This 
   document provides clarifications to RFC2370, with the one 
   technical change (see immediate paragraph above) having been
   discussed in the WG. 

Document Quality

   2370 is widely implemented and deployed and in use. 


   Acee Lindem is document shepherd. Dave Ward is responsible
   AD. IANA issues are unchanged from 2370.

IETF-Announce mailing list