Multicast Extensions to OSPF (mospf) Charter
NOTE: This charter is accurate as of the 37th IETF Meeting in San Jose. It
may now be out-of-date. (Consider this a "snapshot" of the working
group from that meeting.) Up-to-date charters for all active working
groups can be found elsewhere in this Web server.
Routing Area Director(s):
- Joel Halpern <firstname.lastname@example.org>
Mailing List Information
- General Discussion:email@example.com
- To Subscribe: firstname.lastname@example.org
Description of Working Group
This working group will extend the OSPF routing protocol so that it
will be able to efficiently route IP multicast packets. This will
produce a new (multicast) version of the OSPF protocol, which will be
as compatible as possible with the present version (packet formats and
most of the algorithms will hopefully remain unaltered).
Goals and Milestones
- Become familiar with the IGMP protocol as documented in RFC 1112. Survey existing work on multicast routing, in particular, Steve Deering's paper ``Multicast Routing in Internetworks and Extended LANs''. Identify areas where OSPF must be extended to support multicast routing. Identify possible points of contention.
- Review outline of proposed changes to OSPF. Identify any unresolved issues and, if possible, resolve them.
- The group should have a draft specification. Discuss the specification and make any necessary changes. Discuss implementation methods, using as an example, the existing BSD OSPF code, written by Rob Coltun of the University of Maryland.
- Report on implementations of the new multicast OSPF. Fix any problems in the specification that were found by the implementations.
- Submit the MOSPF Specification to the IESG as a Proposed Standard.
- Jun 96
- Update MOSPF to reflect current usage, document interoperability between implementations, and submit to the IESG for consideration as a Draft Standard.
- Dec 96
- Document interoperability between MOSPF and DVMRP, and submit as an Informational RFC.
- Dec 96
- Submit MOSPF to IESG for consideration as a Standard.
No Current Internet-Drafts
Request for Comments