1. OSPF WG - IETF 66 OSPF Protocol Evolution WG Re-Charter Acee Lindem/Cisco Systems

2. OSPF WG - IETF 66 OSPF Extension Chronology  RFC 1247, RFC 1583, RFC 2178, and RFC 2328 – Evolution of base OSPFv2 protocol  Area Hierarchy with full link state topology within an area  5 Basic LSA Types  32 bit aligned fields  RFC 1584 - MOSPF adds Multicast trees and Type 6 LSAs  RFC 1583 Adds NSSAs and Type 7 LSAs  RFC 2370 – Adds Opaque LSAs with flooding scope built into types. Backward compatible introduction of new LSAs

3. OSPF WG - IETF 66 OSPF Extension Chronology  RFC 2740 – OSPFv3  Generalized flooding of unknown LSAs  LSID no longer denotes route prefix  Separation of intra-area topology and prefix information  RFC 3623 – OSPFv2 Graceful Restart – Uses link scoped opaque LSA.  RFC 3630 – OSPFv2 Traffic Engineering Uses area scoped LSAs  OSPFv2 as PE/CE Protocol - RFC Editor Queue  OSPFv2 MTR – Reuses TOS routing metrics  OSPFv3 Authentication using IPSec - RFC Editor Queue

4. OSPF WG - IETF 66 OSPFv2 Evolution - Goals  Full Backward Compatibility  Introduction of REQUIRED functionality with consideration of the large deployed base  Extensions for routing and TE information  Prudence in allowing additional information carried in OSPFv2 - Not a generalized intra- domain flooding mechanism.

5. OSPF WG - IETF 66 OSPFv2 Evolution - New Charter Items  Link Local Signaling as Standards Track  draft-ietf-ospf-lls-01.txt  OSPF Capabilities Advertisement - Advertise node capabilities for options that won’t fit.  draft-ietf-ospf-cap-08.txt  OSPF Multiple Topology Routing/MIB  draft-ietf-ospf-mt-06.txt  draft-rawat-ospf-mt-mib-00.txt  OSPF Additional Route Attributes  draft-mirtorabi-ospf-tag-00.txt  OSPFv2 use of IPSec  Draft in progress

6. OSPF WG - IETF 66 OSPFv3 Evolution - Goals  Backward Compatibility - Inherent in OSPFv3  Introduction of REQUIRED functionality  Extensions for routing and TE information  Evolution to generalized TLV Based Protocol supporting multiple address families/topologies  Equitable granularity of advertisement with TLV  LSA Type extension for new functions  TLV Type extension for existing LSA Information  Target protocol for MANET extensions  Still NOT a generalized flooding mechanism - Need to use prudence in selecting what is advertised.

7. OSPF WG - IETF 66 OSPFv3 Evolution - New Charter Items  Link Local Signaling as Standards Track  draft-ietf-ospf-lls-01.txt  OSPF Capabilities Advertisement - Advertise node capabilities for options that won’t fit.  draft-ietf-ospf-cap-08.txt  OSPFv3 Multiple Topology Routing/Address Family MIB  draft-ietf-ospf-af-alt-03.txt (Multi-Instance - interim solution)  draft-ietf-ospf-mt-ospfv3-01.txt (Supports TLVs - additional attributes)  OSPFv3 MANET Extensions  WG stalled - No agreement  Implementation/Adoption Momentum slowed

8. OSPF WG - IETF 66 OSPF WG Vision – Single IP IGP Enterprise/ISP/Wireless Networks OSPFv3 Base TLV Extensions OSPFv3 MANET Multi-AF/MTRAttributes

9. OSPF WG - IETF 66 Activities Outside OSPF WG  ASON (Automatic Switched Optical Networks) Requirements  OSPF in limited Environments (e.g., L1VPNs)  MANET Developments  Others?

10. OSPF WG - IETF 66 Charter Strawman Description of Working Group: The OSPF Working develops and documents extensions and bug fixes to the OSPF protocols 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:  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.

11. OSPF WG - IETF 66 Charter Strawman (Continued - #1)  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

12. OSPF WG - IETF 66 Charter Strawman (Continued #2)  Done Extend the hitless restart mechanism to OSPFv3 and submit it to the IESG as a Proposed Standard  Done Develop Traffic Engineering extensions for 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  July 2007 Develop OSPF for IPv6 MIB and submit to IESG for consideration as a Proposed Standard.  Mar 2007 Develop an IPSec based authentication for OSPFv2 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

13. OSPF WG - IETF 66 Charter Strawman (Continued #3)  Mar 2007 Develop a multiple instance OSPFv3 Multiple Topology Routing (MTR) specification and submit to IESG for consideration as a Proposed Standard.  Mar 2007 Advance Link Local Signalling (LLS) from experimental status and submit to IESG for consideration as a Proposed Standard.  July 2007 Develop a OSPFv2 Multiple Topology Routing (MTR) MIB specification and submit to IESG for consideration as a Proposed Standard.  July 2007 Develop OSPFv3 protocol enhancements to reduce flooding overhead and adjacencies in a MANET environment for consideration as a Proposed Standard.  Nov 2007 Develop OSPFv2 protocol enhancement for optionally associating additional attributes with routes/link and submit to IESG for consideration as a Proposed Standard.  Mar 2008 Develop a single instance OSPFv3 Multiple Topology Routing (MTR) specification and submit to IESG for consideration as a Proposed Standard