1 / 18

Steve Joiner, Technical Committee Chair John McDonough, Member OIF Board of Directors

Optical Internetworking Forum. Steve Joiner, Technical Committee Chair John McDonough, Member OIF Board of Directors. www.oiforum.com. What is the OIF?. Why the OIF? Organization of Working Groups Possible Interaction OIF / ITU-T Summary. What is OIF?. Launched in April of 1998

dai
Download Presentation

Steve Joiner, Technical Committee Chair John McDonough, Member OIF Board of Directors

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. Optical Internetworking Forum Steve Joiner, Technical Committee Chair John McDonough, Member OIF Board of Directors www.oiforum.com

  2. What is the OIF? • Why the OIF? • Organization of Working Groups • Possible Interaction OIF / ITU-T • Summary

  3. What is OIF? • Launched in April of 1998 • Open forum: 340+ members including many of the world’s leading carriers and vendors • The only industry group bringing together professionals from the packet and circuit worlds • Addresses key issues in a timely fashion that are not being addressed elsewhere • Mission: To foster the development and deployment of interoperable products and services for data switching and routing using optical networking technologies

  4. Output from OIF • Develop implementation agreements among its members • Standalone documents representing broad agreement among members • OIF implementation agreements assure customers of consistent functionality and interoperability • Provides input into existing standards bodies and influences the development of standards

  5. Technical CommitteeSix Working Groups • Architecture • Services, network requirements and architectures • Carrier • Requirements and applications • Signaling • Protocols for automatic setup of lightpaths • OAM&P (Operations, Administration, Maintenance and Provisioning) • Network management • Interoperability • Interoperability testing • Physical and Link Layer • Equipment and subsystem moduleand optical interfaces

  6. Areas for Standardization • Network Architectures • Including Optical/DWDM technologies • Design for Data services • Physical layer transmission technologies • Higher line rates • Low Cost Short Reach Interfaces • More flexible framing structures • Layer 2 and 3 Transport and Encapsulation • New data centric protocols to transport • Collapsed protocol stacks • Network Management and Control • Simplify and automate management • Fast, flexible & efficient provisioning

  7. OIF and Standards Bodies • OIF submissions perform two functions: • Request standardization of specific OIF recommendations • Provide informational documents to the target standards group • Established Liaisons With: • ANSI T1 • IETF • ATM Forum • IEEE 802.3ae 10 Gigabit Ethernet • Network Processor Forum • ITU-T SG 15

  8. OIF - Optical Internetworking Forum • UNI 1.0 - Optical User to Network Interface • Based upon GMPLS Signaling Protocols • Intra-carrier NNI work underway • Very Short Reach Optics (VSR) 10G and 40G • 12 fiber parallel, 4 fiber parallel, • 850nm serial, 1310nm serial • Internal System and Chip Interfaces • SPI - System Packet Interface • SFI - SERDES Framer Interface

  9. PLL Working Group • Adopted Packet OverSONET/SDH link layer • Interfaces internal to network elements • Benefits to system vendors andtechnology vendors • Interface definitions lead to physicalmodule standardization, thus lower costs • Serializer/Deserializer-FramerInterfaces (SFIs) • System Physical Interfaces (SPIs) • 10G and 40 G • Interfaces between network elements • Very Short Reach Interfaces (VSR) • Parallel optics solutionsfor low cost10 G interfaces Rest of the System Link Layer (Packet and Cell based Protocols) SPI PHY Layer SONET/SDH Framer SFI SERDES E/O Transceiver Transmission Media

  10. PLL Agreements • 10Gb/s VSR Agreements • VSR-1, 12 fiber x 1.25Gb/s 850nm (<300m) • VSR-2, Serial 1310nm (<600m) • VSR-3, 4 fiber x 2.5Gb/s 850nm (<300m) • VSR-4, Serial 850nm (<300m) • Electrical Interface Agreements • SPI-3 OC48 System Packet Interface • SFI-4 OC192 Serdes-Framer Interface • SPI-4 phase 1 OC192 System Packet Interface • SPI-4 phase 2 OC192 System Packet Interface PLL = Physical Link Layer

  11. PLL Work In Progress • VSR 40Gb/s Very Short Reach Optics • SPI-5 40Gb/s System Packet Interface • SFI-5 40Gb/s Serdes-Framer Interface • TFI-5 Framer to Fabric Interface • SFI-4 Phase 2 - OC192 Serdes-Framer Interface with narrower data paths. • Tunable laser – non-optical interface IA

  12. Signaling Working Group • Define Signaling protocols used between optical network elements • Enables clients to establish optical connections • Re-uses work from other standards bodies • UNI 1.0 complete • Now in public domain as implementation agreement. • Future Project • UNI 2.0 started November 2001 • Intra-carrier NNI started November 2001

  13. UNI 1.0 Functions • SONET/SDH Connection Signaling • Establishment • Deletion • Status exchange • Automatic topology discovery • Automatic service discovery • SONET/SDH Transport

  14. UNI 1.0 Protocol Components • Connection Signaling • RSVP or CR-LDP with GMPLS extensions • Additional UNI Objects/TLV’s • Service Discovery & Neighbor Discovery • Link Management Protocol (LMP) • Additional UNI TLV’s • UNI Transport • Out of band - via IP transport (eg Ethernet)may use separate wavelength • In Band - via SONET/SDH DCC

  15. UNI 1.0 and GMPLS Relationship • Generalized Multi-Protocol Label Switching (GMPLS) • MPLS was designed to support forwarding of data based on packet or cell boundaries • Extensions to MPLS to include Time Division (SONET/SDH Add/Drop Multiplexers), wavelength (optical lambdas), and spatial switching • Gives MPLS a way to identify time slots or wavelengths • UNI 1.0 uses GMPLS formats

  16. UNI Interoperability Trials • UNI Interoperability trials - 25 vendors demonstrated UNI interoperability at SUPERCOMM - Atlanta, GA; June, 2001 • 25 Vendors • Agilent • Avici • Alcatel • Ciena • Cinta • Cisco • Coriolis • Corvis • Geyser • Huawei • Metro-Optix • Lucent • Nortel • ONI • Optisphere • Optivera • Redback • Spirent • Sycamore • Tellium • Tenor • Turin • Village • Zaffire

  17. Objective of OIF / ITU-T interaction • The OIF does not want to duplicate other work. • Our membership is substantially different in makeup to the ITU membership • The OIF will debate in its forum the pros/cons of different approaches. • Frequent and close communication will insure that the diversity of objectives and solutions will be heard and lead to the best solutions.

  18. OIF Summary • Brings together professionals from the data and circuit worlds • Addressing key issues important to carriers and vendors • Nine technical documents ratified as Implementation Agreements • Optical module interface standards will allow industry to gain needed economies of scale • Future work: (NNI) Network to Network Interface; richer functionality UNI 2.0; billing for UNI.

More Related