OSPFv2 Prefix/Link Attribute Advertisement

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    ospf mailing list <ospf@ietf.org>,
    ospf chair <ospf-chairs@ietf.org>
Subject: Protocol Action: 'OSPFv2 Prefix/Link Attribute Advertisement' to Proposed Standard (draft-ietf-ospf-prefix-link-attr-13.txt)

The IESG has approved the following document:
- 'OSPFv2 Prefix/Link Attribute Advertisement'
  (draft-ietf-ospf-prefix-link-attr-13.txt) as Proposed Standard

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

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah

A URL of this Internet Draft is:

Technical Summary

    OSPFv2 requires functional extension beyond what can readily be done
   with the fixed-format Link State Advertisements (LSAs) as described
   in RFC 2328.This document defines OSPF opaque LSAs based on Type-
   Length-Value (TLV) tuples that can be used to associate additional
   attributes with prefixes or links.

Working Group Summary

     There has been much discusson about the protocol operations
      when the extended prefix TLVs appear multiple times in the OPAQUE 
      LSA and different flooding scope of the extended Prefix LSA.
      As a result of the discussion, the document has been updated with 
      details of receive side handling for all the cases along with 
      recommended behaviours for send side to minimize disruptions 
      in the network.

Document Quality

      This document has been a WG document for a little under one year.
      It is stable, without changes to the technical solution for more
      than three months. 

      Additionally, the document has been successfully implemented by
      interoperability tested by multiple vendors as indicated by the 
      implementation status section. 


      Shraddha Hegde is the Document Shepherd.
      Alia Atlas is the Responsible Area Director.

RFC Editor Note

  Please remove the Section 5 on Implementation Status.