Optical Control Plane Activities in IETF and OIF

Optical Control Plane Activities in IETF and OIF L. Ong 9 July 2002 Lyong@ciena. com

Outline • Intelligent Optical Networking • Goals • Protocols Required • IETF • Organization, History • Current work and status • OIF • UNI 1. 0 Specification • Future UNI and NNI activities – Inter. Domain Interface • Summary • Comparison: Different Focus but Common Goals 2

The Problems Traditional Optical Networking • Labor-intensive processes Error-prone, slow and high operations costs • Inflexible protection schemes, fixed-size pipes Limited service levels and poor utilization • Every action flows through the central Network Management system Limited scalability, visibility and manageability One Cause of Limitations: Lack of flexibility and intelligence in hardware and software 3

The Solution Intelligent Optical Networks 2. Routing/Topology Dissemination 1. Neighbor Discovery NETWORK MGMT PLANE User OUNI CONTROL PLANE DATA PLANE 3. Connection Signaling Automated Processes, Scalability, Robustness, Efficiency 4

Intelligent Optical Network Foundations • ION Protocol Functions – Discovery • Neighbor and link identity and characteristics – Routing/Topology Dissemination • Network topology and resource availability – Connection Signaling • Automated provisioning and failure recovery • Concepts endorsed by every standards body – ITU-T, IETF and OIF • Keys to ION/GMPLS/ASON 5

ION-related Standards Activities Charter: Global Telecom Architecture and Standards No. of Members: 189 Member States + 434 Sector Members Core Participants: • Global Service Providers, PTTs, ILECs • Telecom equipment vendors Goal: International Standards Charter: Development of Optical Networking Products and Services Charter: Evolution of the Internet (IP) Architecture No. of Members: 312 Principal Membership: Individuals – community model Core Participants: • PTTs, ISPs, ILECs, IXCs • Optical Networking Vendors Goal: Optical Network Evolution Core Participants: • ISPs, Carriers • Router/switch and SW Vendors Goal: Internet Evolution 6

IETF IP Networking Standards

IETF Optical Standards • IETF’s Traditional Focus – The Internet: IP and IP Services – routing, transport, applications, security & management • Sub-IP Area – Coordinates activities below the IP layer, esp. MPLS/GMPLS – Disbanding soon as work matures 8

IETF GMPLS: History • How did GMPLS start? – Outgrowth of MPLS - IP traffic engineering work – “Generalized” protocols for label-switched path creation • Fiber switching • Wavelength/Waveband switching • Time slot switching (SONET/SDH) • Possible Architectures – Flat network – routers and optical systems fully peered – Hierarchical network – routers are optical clients • Scope – Support of IP networking over optical transport – Non-IP-related use of GMPLS is out-of-scope 9

IP, MPLS and GMPLS 1. IP: Shortest Path takes all packets 2. MPLS: Traffic Engineering allows flows to be mapped to different paths for better utilization 3. GMPLS: MPLS control protocols could also set up connections in a circuit network 10

IETF Standards Process • Working Group – – • Internet Engineering Steering Group (IESG) – – • Proposed Standard Defines protocols Approves via email “Last Call” Draft Standard Reviews for correctness and desirability Conducts IETF-wide email Last Call Standard RFC Editor – Final editing and number assignment Discussion Individual Draft WG Last Call IETF Last Call WG Approval 11 RFC edit IETF Approval Proposed Std RFC t

IETF GMPLS Status • Signaling 1. RSVP-TE extensions – starting IETF Last Call Proposed Standard 2. CR-LDP extensions – starting IETF Last Call 3. Extensions for SONET/SDH – still resolving comments • Next step would be Proposed Standard, then RFC Draft Standard • Link Management • LMP – 2 nd WG Last Call Standard • Routing • OSPF & IS-IS extensions – Currently WG drafts Signaling LMP Routing Individual Draft WG Draft Last Call WG Approval 12 IETF Approval Proposed Std RFC t

IETF GMPLS Implementation • CCAMP WG survey of GMPLS implementation – 21 responses • Most implement RSVP • Subset implement CR-LDP • 13 implement SONET/SDH – Many GMPLS implementations in progress • Future – Complete core GMPLS specifications – Add features, e. g. , restoration/protection – Input from G. ASON, e. g. , call and connection separation 13

OIF Optical Network Implementation and deployment

OIF History • Formed 1998 – (04/98 Cisco and Ciena announcement) • Focus: deployment and interoperability • Results: – Several physical interfaces specified – UNI 1. 0 signaling interface specified (10/01) – Interoperability demonstrations organized • Emphasizes carrier optical networking requirements 15

OIF Standards: OIF UNI 1. 0 GMPLS LMP RSVP OSPF 16 ext ext OIF UNI LDP ISIS

OIF Optical UNI Progress • Work based on IETF GMPLS protocols – Modifications: – UNI = reduced functionality, trust/security – e. g. , ATM or ISDN – No routing required –Service enhancements –TNA address – carrier-provisioned interface address – LMP service discovery added – Signaling service object added – Focus on SONET/SDH environment – Subset of LMP and signaling objects – Use of LMP for neighbor discovery expanded • UNI 1. 0 approved, interoperability events sponsored at Supercomm and other venues 17

Current Work • UNI 2. 0 – Extensions for, e. g. , multi-homed access, reachability extensions, enhanced security – ~19 candidate features • NNI – Interface between domains – Inter. Domain signaling – Inter. Domain routing (new problems) 18

NNI Work: Closer Look Domain X Carrier A Domain Y UNI Intradomain Protocol UNI Carrier B Domain Z Generic Interdomain Protocol • Within Domain: homogeneous systems and protocols • Different Domains: heterogeneous systems and protocols 19 UNI Domain Model

Domain Model – Networks may be organized as multiple domains: • Administrative/security purposes; • Scaling purposes; • Technology/vendor differences… – Inter. Domain interface: • Hides domain characteristics • Advertises summarized information • Ideally supports diverse routing 20

Inter-Domain Routing Model Inter-Domain protocol OSPF S Domain Speaker S Legacy Carrier A S PNNI Reachable addresses Border links and resource availability Services supported (e. g. , 1+1, 1: N) • Allows Differing Domains to Interwork • Legacy (EMS-controlled) Domains Can Also Interwork 21

Future Directions – ITU-T • G. 7715 specification includes interdomain architecture • Functions and requirements defined, protocol to follow – IETF • Similar concepts in IPO Working Group Interdomain Requirements draft • Protocol work still open – OIF NNI • Task Force identifying carrier requirements • Protocol proposals under discussion – Largely based on existing routing protocols 22

IETF vs. ITU vs. OIF • Different focus • ITU focuses on architecture • IETF focuses on building blocks • OIF focuses on applications and interoperability • Common goal: better optical networking • Recognized need for coordination 23