| 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 |
| Nov 2003 | | Develop OSPF for IPv6 MIB and submit to IESG for consideration
as a Proposed Standard. |
| Nov 2003 | | Extend the hitless restart mechanism to OSPFv3 and submit it to
the IESG as a Proposed Standard |
| Nov 2003 | | Develop Traffic Engineering extensions for OSPFv3 and submit it
to the IESG as a Proposed Standard. |
| Nov 2003 | | Submit to IESG a BCP advocating that OSPF Hellos be given
preference over other OSPF control traffic. |
| Nov 2003 | | Update OSPFv2 MIB and submit to IESG as a Standard, replacing
RFC 1850 |
| Nov 2003 | | Specify IPSEC usage with OSPFv3 and submit to IESG for
consideration as a Proposed Standard |
Return to working group directory.