1. 1 We apologize for not using open source software 1 IP-based Tool Requirements for MPLS Networks Tom Nadeau (tnadeau@cisco.com) George Swallow (swallow@cisco.com) Monique Morrow (Mmorrow@cisco.com)

2. We apologize for not using open source software 2 Motivation Providers have been coming to us with OAM requirements that differed from those that were available. There was a concern that current requirements did not reflect real operational environments. Disparately located requirements for MPLS- related OAM scattered about. Makes it difficult for those writing drafts to find all of the requirements. It is a good idea to put these together in one place.

3. We apologize for not using open source software 3 Motivation (cont) Requirements gathered from a diverse set of MPLS operators and their research departments. Requirements consider both current operational requirements as well as future ones based on real deployments. Providers want evolutionary approaches NOT revolutionary ones. Sensitive to both OPEX and CAPEX. These approaches are suitable for existing MPLS technologies. We do not want to reset current protocols; we want to evolve them.

4. We apologize for not using open source software 4 Recommendations Clarify draft based on comments. Cull out requirements from Dave’s OAM Framework draft. Deliver combined draft by March IETF Meeting. Accept this combined document as an MPLS WG document. Addresses operations and management requirement in charter. Gives direction to future OAM solutions/tools. Keep requirements for MPLS OAM tools and solutions for not only MPLS, but PWE3 and PPVPN MPLS