1 / 38

MPLS Consortium Charter Meeting

MPLS Consortium Charter Meeting. Welcome to UNH Durham, New Hampshire February 7, 2000. Agenda. Welcome and Introductions Overview of the UNH InterOperability Laboratory Establishment of the MPLS Consortium Testing Goals Discussion Charter and Usage Agreement. Agenda (continued).

thiery
Télécharger la présentation

MPLS Consortium Charter Meeting

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. MPLS Consortium Charter Meeting Welcome to UNH Durham, New Hampshire February 7, 2000

  2. Agenda • Welcome and Introductions • Overview of the UNH InterOperability Laboratory • Establishment of the MPLS Consortium • Testing Goals Discussion • Charter and Usage Agreement

  3. Agenda (continued) • Lunch • Election of MPLS Steering Committee • Initial Group Test Planning • Review and Closing Remarks

  4. The Interoperability Problem and the UNH InterOperability Laboratory Scott A. Valcourt Senior Consortium Manager February 7, 2000

  5. Overview • Understanding the Interoperability Problem • Solving the Interoperability Problem • The UNH InterOperability Laboratory

  6. Interoperability Failures • Pushes out market acceptance of new technologies • Increases support cost • Opens windows of opportunity for different solutions • Does not enhance the reputation of a product

  7. The Meaning of Interoperability • Plug and play operation independent of who provided the product • Works in the users environment • Works with the users applications

  8. Foundational Issues • How is interoperability achieved? • How is interoperability demonstrated to the marketplace?

  9. Key #1 The Standard • The standard is the foundation of interoperability. Interoperability problems will exist unless the standard: • Clearly and fully specifies external behavior • Limits options • Addresses market needs • Achieves sufficient developer support and is considered authoritative

  10. Key #2 Technical Testing • New technologies, like new products, have bugs. Test procedures must be available which show that the: • External behavior of the product is consistent with the standard • Product works with other products in different configurations • Product works with common applications

  11. Key #3 Reference Environment • Practical concerns make it necessary to maintain a common center in which interoperability testing can take place • A common site is needed where multiple implementations of the standard are available for testing • Developers must be able to have testing done without exposure of unannounced products or test results

  12. Key #4 An Interoperability Metric • An accepted definition must exist that shows when a product is interoperable • A test report that may be distributed by the owner of the product within the development community • Testing must cover both conformance-like and interoperability items

  13. The Marketing Issues • Cooperation must be achieved between developers • Interoperability intent and achievement must be demonstrated to the public • Testing needs can not significantly delay product introductions • The interoperability metric must be effective to be accepted

  14. The Process • Creating structure to focus industry effort and obtain support • Develop testing tools and technology • Establish reference center • Coordinate demonstrations that show interoperability • Establish a visible interoperability metric

  15. What is the UNH-IOL • Interoperability “facilitation” organization • Part of the University of New Hampshire • Provides technical experience for students in CS and EE • Develops test suites, testing tools, and provides testing services • Helps coordinate interoperability efforts within industry in a cooperative manner • Technical in nature

  16. IOL Experience • Twelve years of helping industry bring “interoperable” technology to market 10BaseT Ethernet Fast Ethernet FDDI Gigabit Ethernet Fibre Channel IP Protocol SNMP Bridge Functions LINUX Token Ring ATM ADSL DOCSIS Wireless (IEEE 802.11) 100VG-AnyLAN HDSL2 MPLS Network Management • Test development experience at physical signaling level up to application level

  17. IOL Acceptance • 150+ corporate memberships world-wide • IOL test reports are trusted by vendors and are often used as basis for quality assurance in OEM deals • Establishment of IOL consortiums accepted as evidence of industry commitment to interoperability within telecom, datacom and other industries

  18. Establishing a MPLS Interoperability Effort • Formation of the MPLS consortium • members agree on charter and fee structure • members elect steering committee • members define scope of testing effort • Consortium develops testing facilities and supports demonstration efforts • Consortium must cover all direct costs of operation

  19. Summary • Addressing the interoperability problem requires: • A good standard, and a good conformance and interoperability test suite • An interoperability reference center and interoperability test procedures • A meaningful interoperability metric • IOL consortiums address interoperability issues in specific technologies

  20. Contact Information Scott A. Valcourt Senior Consortium Manager (603) 862-4489 sav@unh.edu http://www.iol.unh.edu

  21. MPLS Consortium Testing Goals Rob Blais MPLS Consortium Manager February 7, 2000

  22. Consortium Testing Goals • MPLS-Specific Protocols • Routing Protocols • MPLS Services • Interfaces (Layer 2)

  23. MPLS Specific Protocols • RSVP • LDP • CR-LDP

  24. Routing Protocols • OSPF • BGP4 • IS-IS • Others? • Focus on TE extensions

  25. MPLS Services • Class of Service (CoS) • Traffic Engineering • VPNs

  26. Interfaces (Layer 2) • ATM • Packet over SONET (PoS) • Frame-Relay • Gigabit Ethernet • Optical/Lambda/WDM? • Others?

  27. Other Issues • Other things that should be tested

  28. MPLS Consortium Structure Rob Blais MPLS Consortium Manager February 7, 2000

  29. MPLS Consortium Charter • Structure & Terms • Fees

  30. Structure & Terms • Overall • Section 3.1.3

  31. MPLS Consortium Expenses • Labor • Graduate student: $25k/year • Undergraduate student: $12k/year • Full-Time UNH Staff members: $55k/year • General • Overhead: 25%/year • Other expenses: $30k/year • Special equipment needs: ??

  32. Expenses (cont.) • Staffing needs • 3 to 4 Graduate students • 6 to 8 Undergraduate students • Full-time UNH Staff members

  33. Fees • Estimated members: 20 • Estimated expenses: $290,000/year • Membership fee needed: $15,000/year

  34. Steering Committee • Optional • Typically 3 members • 1 member per company • Nominate • Vote

  35. Group Tests • First: March 13 - 17, 2000 • IOL Group Test Facility, Durham, NH • Focus: RSVP • Testing Plans

  36. Group Tests (cont.) • Future tests • LDP/CR-LDP • When?

  37. Contact Information Rob Blais MPLS Consortium Manager (603) 862-4569 rdb@iol.unh.edu http://www.iol.unh.edu

  38. Closing Remarks • Thank you for coming! • Have a Safe Trip Home!

More Related