The document summarizes standards and technologies for intelligent optical networks. It discusses the evolution from single-layer networks to a two-layer architecture with separate transport and service layers. The transport layer uses MPLS and GMPLS protocols for optical routing, signaling, and link management. Standards groups are working on optical UNI signaling between the service and transport layers. Both overlay and peer control plane models are considered for inter-layer coupling.

1. Service Intelligence for Optical Networks Top 50 Companies to Watch

2. Control & Signaling in The Next Generation Intelligent Optical Network Examining the Progress Being Made by Standards Groups K. Arvind, Ph.D. Consulting & Founding Engineer [email_address]

3. Plan of the Presentation “ Make no little plans; they have no magic to stir men's blood ”, D. H. Burnham IP/ O Internetworking Evolution IP/ O Internetworking Standards Why, Who, What IP/ O Control Plane Standards IP/ O UNI Standards Conclusion

4. IP/Optical Internetworking Evolution Evolution of carrier network architecture Today Tomorrow

5. Current Generation “Technology is like fish. The longer it stays in the market, the less desirable it becomes”, Andrew Heller, IBM SONET 1980s IP Tsunami 1990s Multi-layer Architecture SONET core DWDM for capacity ATM for intelligence IP for application transport

6. What is wrong? “Every solution breeds new problems”, Murphy’s Law SONET provisioning: static, fixed sizes SONET+DWDM is expensive Fat data pipes: Need SONET multiplexing? ATM: OC-3 (predominant), OC-12 ATM: Complex Rack space at POPs and COs

7. Next Generation Two Layers Transport Layer Bulk Transport Service Layer Service Intelligence Bandwidth => Revenue

8. Transport Layer: Bulk Transport

9. Service Layer: Service Intelligence

10. 2 Layer Architecture: Another View

11. IP/O Internetworking Standards Why? Who? What?

12. IP/ O Standards: Why? Industry: Interoperability vital for success Carriers: Best of breed product selection Vendors: Faster time to market and revenue

13. IP/ O Standards: Who? “The nice thing about standards is that there are so many to choose from”, A.S. Tannenbaum IETF ODSI OIF ITU ANSI T1/X1.5

14. ITU-T Recommendation G.872: Optical Transport Network

15. IP/ O Standards: What? Control Plane Signaling, Routing, Protection, Management Optical Service Layer IETF (MPLS/Traffic Engineering) Optical Transport Layer IETF (MP λS), G.ASON Inter-Layer Control ODSI, OIF, IETF (O-UNI), G.ASON

16. IP/O Standards: What? Optical Service Layer IETF (MPLS/Traffic Engineering) Optical Transport Layer G.ASON, IETF (MP λS) Inter-Layer Interface ODSI, OIF, IETF (O-UNI)

17. G.ASON A utomatically S witched O ptical N etwork: Automated routing and signaling of optical connections Scalable, Intelligent Optical Network Scalability: Distributed architecture Intelligence: Optical routing and signaling algorithms - auto-discovery, constraint-based path selection, support for different levels of restoration End-to-end connectivity: UNI Architectural framework

18. G.ASON Architectural Framework

19. Transport Layer Control “Who controls the past controls the future. Who controls the present controls the past”, George Orwell IP/MPLS-based control plane robust, scalable, well-understood, interoperable, field-tested Paradigm: MP λS Frame-work: IP over Optical Routing Protocols (GMPLS Extensions) Signaling Protocols (GMPLS) Link Management (LMP)

20. MP λ S draft-awduche-mpls-te-optical-02.txt : “Multi-Protocol Lambda Switching: Combining MPLS Traffic Engineering Control with Optical Crossconnects” Isomorphism between layers: Dynamic provisioning and maintenance of virtual pipes Label Switching at both Layers Virtual pipe = Segments (FEC, λ) stitched together at cross-connects (LSR, OXC). Dynamic provisioning: Path selection: Automated selection of pipe segments Topology discovery (routing protocols), Algorithmic constraint-based routing Signaling: Coordinated configuration of cross-connects

21. IP over Optical Framework draft-many-ip-optical-framework-02.txt: IP over Optical Networks: A Framework UNI + Optical Transport Layer Interconnection Models: Peer and Overlay Intra and inter-optical subnet issues: Addressing, Neighbor discovery, Topology discovery, Restoration models, Signaling issues draft-xu-mpls-ipo-gmpls-arch-00.txt: Generalized MPLS Control Plane Architecture for Automatic Switched Transport Network

22. Optical Routing Protocols draft-ietf-isis-gmpls-extensions-00.txt draft-kompella-ospf-gmpls-extensions-00.txt IS-IS/OSPF GMPLS extensions New sub-TLVs to advertise characteristics specific to optical links. Link TLV (OSPF), Extended IS Reachability TLV (IS-IS) Link Protection Type, Link Descriptor, SRLG sub-TLVs

23. Optical Signaling Protocols draft-ietf-mpls-generalized-signaling-01.txt: Generalized MPLS - Signaling Functional Description. draft-ietf-mpls-generalized-rsvp-te-00.txt draft-ietf-mpls-generalized-cr-ldp-00.txt Generalized label request and label Bi-directional LSP setup: Upstream Label Reduce trail establishment latency: Suggested Label Restrict label choice: Label Set Explicit Label Control: ERO Label subobject Fast notification of failures: Notify message

24. Optical Link Management draft-ietf-mpls-lmp-01.txt Link Management Protocol (LMP) IP encoded: Link layer independent Bundled link: 1 control + n x data channels Control channel diverse from data channels Functions: Control channel management Link connectivity verification Link property correlation Fault isolation

25. Transport Layer Control: Review Paradigm: MP λS  Frame-work: IP over Optical  Routing Protocols  Signaling Protocols  Link Management 

26. IP/O Standards: What? Optical Service Layer IETF (MPLS/Traffic Engineering) Optical Transport Layer IETF (MP λS) Inter-Layer Interface ODSI, OIF, IETF (O-UNI)

27. Inter-Layer Control Inter-Layer Control Coupling Models Optical UNI Signaling Messages Protocols Architecture

28. Control Coupling Models “ People can have the Model T in any color - so long as it's black” - Henry Ford draft-many-optical-framework-02.txt Overlay & Peer Models Overlay Model (Domain Services Model) Uncoupled: ~ IP over ATM Loosely coupled: ~ IP inter-domain routing Peer Model (Unified Service Model) Tightly Coupled: Control planes collapsed into one

29. Collapsed Control Planes

30. Overlay Model Independent routing domains Reachability Information Loosely coupled: BGP, OSPF/ISIS Uncoupled: Address registration protocols Independent signaling/traffic engineering UNI signaling: ODSI, OIF Non-IP service layer: SONET, ATM Separate administrative domains

31. Peer Model Integrated routing domain Complete visibility: One big IP network Unified traffic engineering/signaling UNI signaling not required draft-ietf-mpls-generalized-signaling-00.txt Both layers are IP-based Single administrative domain Data overlay

32. Which Model? “Comparisons are odorous”, III,v,15, Much Ado About Nothing Peer or overlay? Deployment and interoperability time frame Peer  , Overlay  Legacy infrastructure reuse Peer  , Overlay  Non-IP service layer Peer  , Overlay  Power and elegance Peer  , Overlay  Short Term => Overlay, Long Term => Peer

33. Optical UNI Actions Messages and TLVs Signaling Entities Control channels Interactions Protocols Management

34. Optical UNI: Actions Signaling: Set up, Tear down, Modify light paths Light path status enquiry Light path Event Notification “Inter-Domain Routing” Address registration and de-registration Resource Discovery: Service, Neighbor

35. Optical UNI: Messages draft-bala-mpls-optical-uni-signaling-01.txt: Signaling Requirements at the Optical UNI Lightpath Create Request/Response Lightpath Delete Request/Response Lightpath Modify Request/Response Lightpath Status Enquiry/Response Lightpath Notification ODSI/OIF/IETF closely aligned

36. Optical UNI: TLVs draft-bala-mpls-optical-uni-signaling-01.txt Identification-Related Parameters Light path end points: IP address + logical port Contract ID: identifies service contract Light path ID: unique within optical network User Group ID: RFC 2685 VPN ID UNI-C ID: IP address of client device

37. Optical UNI: TLVs draft-bala-mpls-optical-uni-signaling-01.txt Service-Related Parameters: Directionality: Unidirectional or bidirectional Framing: Signal format (PDH/SONET/SDH etc.) Bandwidth: Service bandwidth Transparency: PLR-C, STE-C, LTE-C Propagation delay: milliseconds Service level: priority, preemption, QoS

38. Optical UNI: TLVs draft-bala-mpls-optical-uni-signaling-01.txt Routing-Related Parameters Diversity: List of the following Light paths with which resources should not be shared Type of diversity: node, link, or SRLG diverse Security-Related Parameters To be specified; reuse security parameters of signaling transport where possible. Policy/Accounting/Authorization-Related Reuse protocol object (e.g., RSVP Policy object) Contract ID

39. Optical UNI: Signaling Entities “Traffic signals in New York are just rough guidelines”, David Letterman Head End Client ( Initiating UNI-C, Trail Head ) IP, ATM, SONET Tail End Client (Terminating UNI-C, Trail Tail) Third Party Client: ODSI Head End OXC ( Initiating UNI-N ) Tail End OXC ( Terminating UNI-N ) Optical Network Controller ( ONC ) Logical or Physical Entity

40. Optical UNI: Signaling Entities

41. Optical UNI: Control Channels In-Band Overhead bytes (e.g., SONET Line DCC) Digital wrapper overhead channel Out-of-Band e.g., Ethernet

42. Optical UNI Control Channels

43. Optical UNI: Interactions Who talks to whom and when? OIF: Traditional UNI ordering Head end router, Head end OXC, Tail end OXC, Tail End Router and back ODSI: Flexible ordering Service layer devices  Optical Network Controller Control Route TLV Service layer coordination prior to UNI request Single point of interaction Third party signaling

44. Optical UNI: Protocols Service Discovery ODSI: PPP extensions (ODSICP) OIF: LMP Extensions Address Registration ODSI: PPP extensions (ODSICP) OIF: LMP Extensions Signaling: OIF/IETF, ODSI

45. OIF UNI Signaling Protocol OIF/IETF: CR-LDP extensions draft-ietf-mpls-ldp-optical-uni-00.txt OIF Contribution 2000.125.3 (UNI 1.0) Reliable transport for TLVs between router and OXC. Create: Label Request, Label Mapping Modify: draft-ietf-mpls-crlsp-modify-01.txt Delete: Label Release, Label Withdraw Notification New LDP messages: Status enquiry, Status response

46. OIF UNI Signaling Protocol OIF/IETF: RSVP-TE extensions draft-yu-mpls-rsvp-oif-uni-ext-00.txt OIF Contribution 2000.125.3 (UNI 1.0) Maps RSVP messages, objects and procedures for O-UNI Create: Path, Resv Modify: LSP setup procedures Delete: PathTear, ResvTear (Reliable) Notification: New Notify message Status: Srefresh Reliability extensions: MSG_ID GMPLS objects

47. ODSI Signaling Protocol http://www.odsi-coalition.com/documents.asp ODSI: UNI is not MPLS Clients may be SONET, ATM devices RSVP/CR-LDP excess baggage? Simple protocol sufficient for TLV transport TCP-based application Signaling request  Build up and Unwinding of distributed transaction.

48. Optical UNI Management ODSI MIB, OIF UNI MIB Simple Monitoring only No support for setting up light paths via SNMP.

49. Status and Future Direction “ If it were done when 'tis done, then 'twere well it were done quickly”, Macbeth Act I ODSI: Interoperability demo completed OIF: Interoperability demo in June 2001 IETF: IPO, CCAMP WG (sub-IP pseudo area) Convergence between standards efforts Long Term Evolution towards Unified Control Future Work Interconnection of optical subnetworks

50. Conclusion "I stand by all the misstatements that I've made.” Dan Quayle Summary: Evolution Why Who What Tremendous interest and momentum Interoperability IP-centric standards