1 / 9

OSPF Charter Update

OSPF Charter Update. Abhay Roy/Cisco Systems Acee Lindem/Redback Networks. Completed Work on Current Charter. Extend the hitless restart mechanism to OSPFv3 and submit it to the IESG as a Proposed Standard

jescie-cooper
Download Presentation

OSPF Charter Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OSPF Charter Update Abhay Roy/Cisco Systems Acee Lindem/Redback Networks OSPF WG – IETF 69 - Chicago

  2. Completed Work on Current Charter • Extend the hitless restart mechanism to OSPFv3 and submit it to the IESG as a Proposed Standard • Submit to IESG a BCP advocating that OSPF Hellos be given preference over other OSPF control traffic. (RFC 4222) • Update OSPFv2 MIB and submit to IESG as a Standard, replacing RFC 1850 (RFC 4750) • Specify IPSEC usage with OSPFv3 and submit to IESG for consideration as a Proposed Standard (RFC 4552) OSPF WG – IETF 69 - Chicago

  3. Uncompleted Work on Current Charter • Develop OSPF for IPv6 MIB and submit to IESG for consideration as a Proposed Standard - New Target: March 2008 • Develop Traffic Engineering extensions for OSPFv3 and submit it to the IESG as a Proposed Standard. New Target: March 2008 OSPF WG – IETF 69 - Chicago

  4. Completed Worked Not on Charter • Extend Demand Circuits (RFC 1795) to detect inactive neighbors and submit to IESG as a proposed standard - RFC 3883 • Develop OSPFv2 MTR (Multi-Topology Routing) Extensions and submit to IESG as a proposed standard - RFC 4915 • Document OSPF IANA Considerations for OSPFv2 and OSPFv3 - RFC 4940 • Develop OSPFv2/OSPFv3 extensions to advertise optional capabilities and submit to the IESG as a proposed standard - RFC 4970 OSPF WG – IETF 69 - Chicago

  5. Almost Complete - Not on Charter • Update OSPFv3 (RFC 2740) with Corrections and Clarifications and submit to IESG as a proposed standard • Develop OSPF Multi-Area Adjacency extensions and submit to IESG as a proposed standard • Update OSPF Opaque Option (RFC 2370) and submit to the IESG as a proposed standard. OSPF WG – IETF 69 - Chicago

  6. WG Actively Working On - Not on Charter • OSPFv3 MTR (Multi-Topology-Routing) and multiple address family extensions and submit to the IESG as a proposed standard - Target: March 2009 • Develop OSPFv2/OSPFv3 extensions for link local signalling and submit to the IESG as a proposed standard - Target: March 2008 • Develop multiple OSPF/MANET extension alternatives and submit to the IESG as experimental drafts - Target: July 2008 • Develop OSPFv2 MIB extensions for MTR (Multiple Topology Routing) and submit to the IESG as a proposed standard - Target: March 2008 OSPF WG – IETF 69 - Chicago

  7. WG Actively Working On - Not on Charter - Continued • Develop stronger OSPFv2 authentication and submit to the IESG as a proposed standard - Target: July 2008 OSPF WG – IETF 69 - Chicago

  8. Criteria for Chartered Future Work • Strong industry or IETF requirement to fill OR • OSPF WG “Rough Consensus” to add standards track WG document • Proposals are welcome and we will be adding items as appropriate OSPF WG – IETF 69 - Chicago

  9. Potential Future Work • Advertisement of route attributes in OSPFv2 • OSPFv3 IPsec Auto-keying Work • Future OSPF MANET Work • OSPF Graceful Restart Extensions OSPF WG – IETF 69 - Chicago

More Related