Open Shortest Path First IGP (ospf)

This Working Group did not meet

NOTE: This charter is a snapshot of the 52nd IETF Meeting in Salt Lake City, Utah USA. It may now be out-of-date. Last Modified: 05-Dec-01

Chair(s):
John Moy <john.moy@sycamorenet.com>
Routing Area Director(s):
Randy Bush <randy@psg.com>
Bill Fenner <fenner@research.att.com>
Routing Area Advisor:
Bill Fenner <fenner@research.att.com>
Mailing Lists:
General Discussion:ospf@discuss.microsoft.com
To Subscribe: ospf-request@discuss.microsoft.com
Archive: http://discuss.microsoft.com/archives/ospf.html
Description of Working Group:
The OSPF Working develops and documents extensions and bug fixes to the OSPF protocol, as well as documenting OSPF usage scenarios. The specific protocol work items area listed in the Goals and Milestones section below. Additional work items will require rechartering.

Goals and Milestones:
Jun 96   Complete OSPF for IPv6 specification and submit to IESG for consideration as a Proposed Standard.
Jun 96   Document current usage, update OSPFv2 and submit to IESG for consideration as a Standard.
Dec 96   Develop OSPF for IPv6 MIB and submit to IESG for consideration as a Proposed Standard.
Dec 96   Submit Internet-Draft on ISPF extensions of IPv6 to IESG for consideration as a Proposed Standard.
Jun 97   Update OSPF for IPv6 based on implementation experience, and submit to IESG for consideration as a Draft Standard.
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   Obtain performance data for the protocol.
Done   Design the routing protocol, and write its specification.
Done   Make changes to the specification (if necessary) and publish the protocol as a Draft Standard RFC.
Jun 98   Submit OSPF for IPv6 to IESG for consideration as a Standard.
Sep 01   Submit to IESG a document which updates RFC 1793 allowing detection of demand circuit neighbors whose OSPF process has exited.
Sep 01   Submit to IESG a BCP advocating that OSPF LSA refreshes be spread out over time
Sep 01   Submit to IESG a BCP advocating that OSPF Hellos be given preference over other OSPF control traffic.
Oct 01   Update OSPFv2 MIB and submit to IESG as a Standard, replacing RFC 1850
Oct 01   Update MOSPF specification with bug fixes and changes required by RFC 2328. Submit to IESG as Draft Standard
Jan 02   Develop pruning support for MOSPF, allowing it to be used in a transit multicast domain and with IGMPv3. Submit to IESG as Proposed Standard
Jan 02   Develop a hitless restart mechanism for OSPF and submit it to the IESG as a Proposed Standard.
Jan 02   Develop mechanisms to reduce OSPF flooding traffic in highly connected network topologies. Submit to IESG as Proposed Standard.
Internet-Drafts:
Request For Comments:
RFCStatusTitle
RFC1246 Experience with the OSPF Protocol
RFC1245 OSPF Protocol Analysis
RFC1587PSThe OSPF NSSA Option
RFC1586 Guidelines for Running OSPF Over Frame Relay Networks
RFC1765E OSPF Database Overflow
RFC1793PSExtending OSPF to Support Demand Circuits
RFC1850DSOSPF Version 2 Management Information Base
RFC2096PSIP Forwarding Table MIB
RFC2328S OSPF Version 2
RFC2329 OSPF Standardization Report
RFC2370PSThe OSPF Opaque LSA Option
RFC2740PSOSPF for IPv6
RFC2844E OSPF over ATM and Proxy PAR
RFC3137 OSPF Stub Router Advertisement

Current Meeting Report

None received.

Slides

None received.