Skip to main content

OSPFv2 Multi-Instance Extensions
draft-ietf-ospf-multi-instance-09

Approval announcement
Draft of message to be sent after approval:

Announcement

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@tools.ietf.org>
Subject: Protocol Action: 'OSPFv2 Multi-Instance Extensions' to Proposed Standard (draft-ietf-ospf-multi-instance-09.txt)

The IESG has approved the following document:
- 'OSPFv2 Multi-Instance Extensions'
  (draft-ietf-ospf-multi-instance-09.txt) as a Proposed Standard

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

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-ospf-multi-instance/


Ballot Text

Technical Summary

    This draft extends OSPFv2 to support multiple routing domains
    on the same subnet - a capability that already exists in OSPFv3.
    This is different from OSPFv3 where it could be used for
    other purposes such as putting the same interface in multiple areas.
    OSPFv2 supports this capability using a separate subnet or the OSPF
    multi-area adjacency capability.

Working Group Summary

    The only discussion worth noting was the behavior of
    legacy routers receiving OSPF packets with non-Zero instance
    ID. It was concluded that the such packets would be
    misinterpreted as having mismatched authentication type
    and would get dropped. Such errors should get logged and
    should result in the generation of SNMP traps. There was
    concern that this could be an issue if every packet would
    result in SNMP trap generation. However, it was discussed that
    this will not be an issue since most implementations will damp
    the logging of errors and generation of identical SNMP traps.

Document Quality

    There is one known implementation. 

Personnel

   Manav Bhatia is the Document Shepherd.
   Stewart Bryant is the Responsible Area Director.



RFC Editor Note