| Done | | Gather operational experience with the OSPF protocol and submit
the document as an Informational RFC. |
| Done | | Develop multiple implementations, and test against each other. |
| Done | | Design the routing protocol, and write its specification. |
| Done | | Obtain performance data for the protocol. |
| Done | | Make changes to the specification (if necessary) and publish
the protocol as a Draft Standard RFC. |
| Done | | Submit OSPF for IPv6 to IESG for consideration as a Standard. |
| Done | | Update the OSPF NSSA option specified in RFC 1587 and submit to
IESG for consideration as a Proposed Standard |
| Done | | Develop Traffic Engineering extensions for OSPFv2 and submit it
to the IESG as a Proposed Standard |
| Done | | Submit to IESG a document which updates RFC 1793 allowing
detection of demand circuit neighbors whose OSPF process has
exited. |
| Done | | Submit to IESG a BCP advocating that OSPF LSA refreshes be
spread out over time |
| Done | | Develop a hitless restart mechanism for OSPF and submit it to
the IESG as a Proposed Standard. |
| Done | | Document Alternative ABR implementations and submit ti IESG as
an Informational RFC |
| Done | | Extend the hitless restart mechanism to OSPFv3 and submit it to
the IESG as a Proposed Standard |
| Done | | Submit to IESG a BCP advocating that OSPF Hellos be given
preference over other OSPF control traffic. |
| Done | | Update OSPFv2 MIB and submit to IESG as a Standard, replacing
RFC 1850 |
| Done | | Specify IPSEC usage with OSPFv3 and submit to IESG for
consideration as a Proposed Standard |
| Done | | Extend OSPF Demand Circuits to detect inactive neighbors and
submit to IESG for consideration as a Proposed Standard |
| Done | | Provide mechanisms to prevent looping in RFC 2547 OSPF networks
and submit to IESG for consideration as a Proposed Standard |
| Done | | Develop OSPFv2 Multiple Topology Routing (MTR) specification
and submit to IESG for consideration as a Proposed Standard |
| Done | | Develop OSPF Capabilities Advertisement specification and
submit to IESG for consideration as a Proposed Standard |
| Done | | Document IANA Considerations for OSPFv2 and OSPFv3 for
consideration as a BCP |
| Mar 2008 | | Develop OSPF for IPv6 MIB and submit to IESG for consideration
as a Proposed Standard |
| Mar 2008 | | Reissue RFC 2370 with corrections and clarifications and submit
to IESG for consideration as a Proposed Standard |
| Mar 2008 | | Reissue RFC 2740 with corrections and clarifications and submit
to IESG for consideration as a Proposed Standard |
| Mar 2008 | | Develop mechanisms for support of multi-area adjacencies on a
single link and submit to IESG for consideration as a Proposed
Standard |
| Mar 2008 | | Advance Link Local Signaling (LLS) from experimental status and
submit to IESG for consideration as a Proposed Standard |
| Jul 2008 | | Develop Traffic Engineering extensions for OSPFv3 and submit it
to the IESG as a Proposed Standard |
| Jul 2008 | | Develop multiple instance OSPFv3 protocol mechanisms to support
multiple address families and topologies |
| Jul 2008 | | Develop multiple OSPFv3 protocol alternatives to reduce
flooding overhead and adjacencies in a MANET environment and
submit to the IESG as experimental RFCs |
| Jul 2008 | | Develop a OSPFv2 Multiple Topology Routing (MTR) MIB
specification and submit to IESG for consideration as a
Proposed Standard |
| Nov 2008 | | Develop stronger authentication mechanisms for OSPFv2 and
submit to IESG as a Proposed Standard |
| Mar 2009 | | Develop a single instance OSPFv3 Multiple Topology Routing
(MTR) specification and submit to IESG for consideration as a
Proposed Standard |
Return to working group directory.