1. Optical Network Interoperability
Vishnu Shukla Thomas Afferton
Member of OIF Board of Directors Member of OIF Board of Directors
Principal Member of Technical Staff Senior Systems Engineer
Verizon Northrop Grumman TASC
FCC, Washington, D.C.
September 24, 2004
Optical Network Interoperability, Shukla/Afferton,

2. Optical Network Interoperability Outline
Part I
Need for optical network interoperability
Current Optical Transport Network (OTN)
Architecture
Issues with current OTN
Emerging optical network technologies
Next-Generation Optical Transport Network (NG-OTN)
Architecture model & interfaces
Transport
Adaptation
Signaling & Control
Management
Examples of new services
Optical Network Interoperability, Shukla/Afferton,

3. Optical Network Interoperability Outline (cont.)
Part II
OIF Overview
Organization
Contribution to OTN interoperability
Network layer
Physical layer
Interoperability Demonstration at Supercomm 2004
Summary
Glossary
Optical Network Interoperability, Shukla/Afferton,

4. OTN Interoperability The Need
Emerging applications require high bandwidth and dynamic interconnection with multiple applications on the network
Intelligent optical network is critical to dynamic bandwidth services
Standardized interworking between various network interfaces and interoperability among vendors are crucial to provision end-to-end services and establish cost effective OTN evolution path
ILEC, IXC boundaries disappearing
Current network is based on multiple technologies and protocols, standard and propriety, making multi-vendor and inter-carrier interworking difficult

5. OTN Interoperability Expected benefits
Carriers can provision end-to-end dynamic bandwidth services
Innovative emerging network technologies can be deployed at faster pace than with a single vendor solutions
Cost effective selection of network elements, platforms and multi-vendor solutions
Reduced operations overheads-simplified provisioning of new services
Larger base of viable platform suppliers
Capital cost control through competitive procurement
Greater depth of technologies and platforms available
Lower operations cost through simplification of network management
Optical Network Interoperability, Shukla/Afferton,

6. OTN Interoperability Expected benefits
More affordable services for our customers
Earlier introduction of next-generation networks, technologies and services
Optical access and core networks
FTTH, MSPP, ROADM, WXC, DWDM, etc.
Dynamic end-to-end bandwidth provisioning, managed bandwidth services, . . .
Optical Network Interoperability, Shukla/Afferton,

7. OTN Interoperability Current optical transport
OTN Transport Plane
NEs\ Networks
OTN Access Network
Metro Network
Regional Core
Network Type
Collector Ring
IOF Ring
Long Haul Ring
NEs Type
SONET add/drop mux (ADM)
ADM
Interconnecting NEs
Broadband digital cross-connect (B-DCS)
B-DCS
Access
Ring B -
DCS
Router
Interoffice
Collector
ADM W

8. OTN Interoperability Issues with current optical transport
Designed for voice traffic, needs to evolve to efficiently support data services
Relatively static structure that does not easily address dynamic services or leverage new technologies
Slow for provisioning of switched connection
Connections setup via a network management system

9. OTN Interoperability Emerging optical technologies: NG-SONET
NG-ADM or Multi-services Provisioning Platform (MSPP)
Integrated grooming and multiplexing functionality for different services (e.g., SONET/TDM, Ethernet, Storage Area Network protocols, IP).
GFP (Generic Framing Procedure)
Updates SONET protocol to provide mapping for virtually any kind of service into SONET. Only required at service ingress and egress points.
VCAT (Virtual Concatenation)
Provides efficient matching of SONET payload bandwidth to service requirements. Only required at service ingress and egress points.
LCAS (Link Capacity Adjustment Scheme)
Technique to dynamically adjust bandwidth provided for the service.
Fiber Channel – transfer rates from 100 to 200 Mbytes/sec (1.06Gbps to 2.125Gbps respectively).
Fiber Channel is Storage Area Network (SAN) protocol.
EoS (Ethernet over SONET) - Generally assumed to imply GFP for mapping Ethernet into SONET but it doesn’t have to be. GFP is an evolution of mappings of different protocols into SONET (HDLC, PPP, etc).
VCAT
Optical Network Interoperability, Shukla/Afferton,

10. OTN Interoperability Emerging optical technologies: Other Platforms
ROADM (Re-configurable Optical ADM)
Automates wavelength provisioning under software control.
Automates optical power level engineering.
Optical Cross Connects (OXC)
Not really optical -- Optical interfaces on electronic-based cross-connect.
Integrate 3/3 and 3/1 DCS function with OC-n switching.
Among the first elements deployed with control plane capabilities
Wavelength Cross Connects (WXC) or Photonic Switches
All Optical-based cross-connect that provides wavelength switching. Protocol and bit rate independent.

11. NG-OTN Interoperability model
End User
Use Cases
SCN
Domain B
Domain A
MSPP / NGADM IP
TMF 814
NMS
EMS
Router EMS/NMS
NNI
Legacy ADM
CP Proxy
UNI
Interface
Management Layer
Control Layer
Adaptation &
Transport Layer

12. (Embedded Controller)
OTN Interoperability Management, Control, and Transport Hierarchy
Management Plane
CP is positioned between transport and management planes.
NEs are controlled either by CP or by both management plane and CP.
Management plane, including the OSS, configures and supervises the CP.
Management plane has ultimate control over all transport plane and control plane entities.
Control
Plane
(Embedded Controller)
This slide shows the distribution of the support to four types of CP interfaces. These are the I-NNI for intra-domain, E-NNI for inter-doamin CP, the network side of UNI and client side of UNI. Team C supports full peer model and needs only to implement I-NNI interface. Team B shows a uniform support of all four CP interface types. This will provide a rich set of interoperability test scenarios.
Transport Plane
OTN
Optical Network Interoperability, Shukla/Afferton,

13. OTN Interoperability Specific Interfaces
Client: Interfaces from the OTN control plane to the external entities that may connect to the OTN control plane
Transport Plane: Physical interfaces, including SONET, wavelength, . . .
Control and Signaling: Interfaces to support signaling and control of routes in the network
Management and OSS: Interfaces from the control plane to the management plane.

14. OTN Interoperability Interfaces-Client
Efficient and standards-based service adaptation of various client signals into SONET is a critical capability required to make the OTN service-agnostic and to provide interworking between various vendors equipment.
A number of standards that include the Generic Framing Procedure (GFP), Virtual Concatenation (VCAT), and the Link Capacity Adjustment Scheme (LCAS) have been developed to facilitate the mapping of client signals into SONET.
Standardized mapping will be required to facilitate interoperability between end nodes that perform service adaptation.
In addition, clients must have the ability to request bandwidth and connectivity across the OTN through control plane interfaces

15. OTN Interoperability Transport Plane
NG-OTN Transport Plane
NEs\ Networks
NG-OTN Access Network
Metro Network
Regional Core
Network Type
Collector Ring
Mesh or
Ring-DWDM
Mesh
NEs Type
MSPP or NG-ADM
WXC or (R)OADM
WXC
Interconnecting NEs
OXC
None

16. OTN Interoperability OTN control plane
Definition:
A set of architectures and protocols that evolve the static SONET/SDH and DWDM layers of today to a dynamic, self-running optical transport network in the future.
Self-configuration
Auto-discovery/inventory
Dynamic provisioning and service activation
Traffic engineering
QoS support
Self-healing
Auto protection and restoration
To help prepare for the next year CP interoperability test, we conducted a CP survey among the participating vendors, Through the survey, we get a better idea of their CP strategy and implementation roadmap. We have two teams, representing two different approaches in handling inter-domain interfaces. Team B adopts the overlay model for inter-domain interface; an independent E-NNI interface is defined to bridge signaling and routing functions between different domains and technology layers. As a result, Team B’s approach depends on I-NNI and E-NNI standards. Team C chooses the full peer model to interconnect different domains and technology layers; thus only I-NNI is needed. Both teams support UNI-based client interface. Members of Team B are mostly from the original OIF/OFC demo team formed in the last Spring, Currently Team B has 14 members; There are four in Team C.
Here is a breakdown of the members by their platform types.
Examples of Control Plane
PSTN -- SS7
IP -- Datagram (TCP/IP), MPLS
ATM -- UNI, B-ICI, PNNI
Optical Network Interoperability, Shukla/Afferton,

17. OTN Interoperability OTN control plane Background: PSTN Control Plane
Services:
DS0-on-Demand
AIN services
SCP
SCP
SS7 Msg
STP
DS0 over TDM
Architecture
Connection-oriented transport
Separated control and transport planes
Signalling
Dedicated signalling network – SS7 network
SS7 signalling protocols (DS0 Circuit Switch)
PBX
Co Switch
Co Switch
PBX
Routing
Distributed & Static
Client Interface
UNI Overlay – Q.931, D-Channel signalling, or POTS signalling
Voice Traffic Path
Signalling Path
We got a total of Eleven responses. Here we show the distribution of these responses in platform categories.
Optical Network Interoperability, Shukla/Afferton,

18. OTN Interoperability OTN Control Plane – Now & Emerging
SCN SW/Router
IP Router
B-SCP
Signaling Messages
MSPP1
MSPP2
OXC1
OXC2
WXC1
WXC2
SCN
OTN
Clients
Architecture
Connection-oriented broadband transport
Separated control and transport planes
Signalling
Dedicated and/or in-fiber signalling communication networks (SCN)
OTN control plane signalling protocol – GMPLS/RSVP-TE
Broadband Data Path
Routing
Distributed & Dynamic
OTN control plane routing – GMPLS/OSPF-TE
Client Interface
OIF UNI
Signalling Path
We got a total of Eleven responses. Here we show the distribution of these responses in platform categories.
Optical Network Interoperability, Shukla/Afferton,

19. OTN Interoperability ASTN/ASON Architecture Framework
UNI E -
NNI
Domain 1
Domain 2
User 1
User 2
I-NNI
UNI – A demarcation point between users and service provider networks
Un-trusted interface
Signaling only
E-NNI – A demarcation point supporting cross-domain connection provisioning
Intra-carrier/Inter-domain (Trusted) or Inter-carrier (Un-trusted)
Signaling with limited routing info exchanges
I-NNI – Intra-domain node-to-node interface to support control plane functions
Fully trusted
Signaling
Routing
To help prepare for the next year CP interoperability test, we conducted a CP survey among the participating vendors, Through the survey, we get a better idea of their CP strategy and implementation roadmap. We have two teams, representing two different approaches in handling inter-domain interfaces. Team B adopts the overlay model for inter-domain interface; an independent E-NNI interface is defined to bridge signaling and routing functions between different domains and technology layers. As a result, Team B’s approach depends on I-NNI and E-NNI standards. Team C chooses the full peer model to interconnect different domains and technology layers; thus only I-NNI is needed. Both teams support UNI-based client interface. Members of Team B are mostly from the original OIF/OFC demo team formed in the last Spring, Currently Team B has 14 members; There are four in Team C.
Here is a breakdown of the members by their platform types.
Optical Network Interoperability, Shukla/Afferton,

20. OTN Interoperability OTN Control Plane Components
A Signaling Communication Network (I-NNI, E-NNI, UNI)
Separate (Physically or Logically) from transport network
A Layer 3 IP network
Signaling Protocols (I-NNI, E-NNI, UNI)
RSVP-TE, CR-LDP-TE, PNNI (ITU)
Routing Protocols (I-NNI, E-NNI)
OSPF-TE, ISIS-TE
Link Management Protocol (I-NNI, E-NNI, UNI)
LMP, LMP-WDM
We got a total of Eleven responses. Here we show the distribution of these responses in platform categories.
Optical Network Interoperability, Shukla/Afferton,

21. OTN Interoperability Interfaces-Management Plane
Management layer interworking will be needed in an NG-OTN multi-vendor network environment enabled with control plane capabilities.
Open standards-based interfaces are a critical factor for enabling management layer interworking.
This will also become important when service adaptation techniques over SONET (e.g., GFP, VCAT, LCAS) are deployed in conjunction with control plane capabilities. There are several points of management plane interworking to consider:
Management plane interworking between the network element and the EMS (NE-EMS interface)
Management plane interworking between the EMS and its northbound NMS/OSS (EMS-NMS interface)
Management plane interworking between multiple OSSs (OSS-OSS)

22. OTN Interoperability-New services A-Z Provisioning via EMS/NMS and Control Plane
Scenario
Carrier NMS/EMS receives a service order for SONET STS-x from an enterprise customer that has three sites in the region. The order specifies points A & Z (e.g., from Site 1 to Site 2), payload rate, transparency, protection class, and other constraints.
The NMS/EMS issues a command to the source node (attached to Site 1), which then triggers the control plane to setup the SONET path to Site 3 according to the requirements specified in the order. Similarly, when the customer terminates the service, NMS/EMS will invoke the control plane to tear down the path.
NG-OTN Technologies
OTN Control Plane (E-NNI, I-NNI)
OTN Mgmt Plane (EMS/NMS SPC support, TMF814) -
Site 1
Site 2
Site 3
Path 1-2
Path 1-3
Path 2-3
SONET A Z

23. OTN Interoperability-New services Dial-Up SONET
Scenario
An enterprise customer with three sites subscribes to a dial-up SONET service with a range of SONET payload rates. The service plan applies to all SONET connections between the sites. Based on business needs, the customer uses UNI signaling to dial-up the service between any two sites, sends information over the SONET path for a unspecified period of time, then hangs up.
NG-SONET – GFP/VC
OTN Control Plane (O-UNI, E-NNI, and I-NNI)
OTN Mgmt Plane (EMS/NMS SC support, TMF814) -
Site 1
Site 2
Site 3
Path 1-2
Path 1-3
Path 2-3
SONET
UNI

24. OTN Interoperability-New services Dial-Up GbE Service
Scenario
An enterprise customer with three sites subscribes to dial-up GbE service with a specified peak rate (P). The service plan applies to all GbE connections between the sites. Based on business needs, the customer uses UNI signaling to dial-up the service between any two sites, sends information at rates <= P for a certain period of time, then hangs up.
NG-OTN Technologies
OTN Control Plane (O-UNI, E-NNI, and I-NNI)
OTN Mgmt Plane (EMS/NMS SC support, TMF814)
Site 2
UNI
Path 1-2
GbE
UNI
Path 2-3
Site 1
GbE -
Path 1-3
Site 3
GbE

25. Part 2 – Optical Internetworking Forum and World Interoperability Event Overview

26. OTN Interoperability- OIF Contributions OIF Overview
Launched in April of 1998 with an objective to foster development of low-cost and scaleable internet using optical technologies
The only industry group bringing together professionals from the data and optical worlds
Open forum: 120+ member companies
International
Carriers
Component and systems vendors
Testing and software companies
OIF Mission To foster the development and deployment of interoperable products and services for data switching and routing using optical networking technologies

27. OTN Interoperability- OIF Contributions OIF Focus
Scaleable Interoperable Optical Internetworking
IP-Over-Switched Optical Network Architecture
Physical layer
Low-cost optical interfaces between networking elements
Standard device level electrical interfaces for low-cost systems
Control layer interoperability between data and optical layers
Dynamic configuration using IP signaling and control mechanisms
Accommodate legacy network under the new physical and control layer mechanisms

28. OTN Interoperability- OIF Contributions Output from OIF
Implementation agreements using
Carrier & user group’s requirements as input
Existing standards and specifications when available
Newly developed solutions when necessary
Interoperability Demonstrations to validate industry acceptance and maturity of implementation agreements
Testing methods to evaluate interoperability that will help in the accelerated development of interoperable products and networks
Input into other standards bodies and other fora

29. (Packet & Cell Protocols)
OTN Interoperability- OIF Contributions Output from OIF – Implementation Agreements
24 agreements published to date
Applications include:
Control plane interfaces User-to-Network (UNI), Network-to-Network (NNI), Security & Billing
Intra-office Optical interfaces Very Short Reach (VSR) 10Gb/s & 40 Gbps
Tunable Lasers Assembly and Control
Intra-system Electrical interfaces Serializer/Deserializer-Framer interface (SFI), Physical-Link Layer device interfaces(SPI), Fabric-to-Framer interface
UNI
Optical Network B
Optical Network A
Client
NNI
UNI
VSR
SPI
SFI
E/O Tx
SER DES
Framer
Link Layer
(Packet & Cell Protocols)

30. 7 participating carrier labs around the world:
China, Germany, Italy, Japan and USA
15 participating vendors
Successfully demonstrated interoperability of multi-vendor networks among carrier labs across the globe:
Dynamic automatic provisioning of optical circuits
Data-plane interoperability of Ethernet transport over multi networks
Automatic provisioning based on OIF UNI 1.0 release 2 and ENNI Implementation Agreements, both control and data plane
These implementation agreements are based on the ITU-T standards for automatically switched optical networks including:
Requirements and Architecture (G.8080, G.7713, G.7715, G )
Signaling protocols (G )
Ethernet Transport based on ITU-T standards for Ethernet service adaptation, Ethernet over SONET/SDH services testing includes:
Generic Framing Procedure (GFP)
Virtual Concatenation (VCAT)
Link Capacity Adjustment Scheme (LCAS)
June 22-24, 2004

31. OIF World Interoperability Demonstration Notional Topology

32. OIF World Demo – Global Topology
                                    

33. Example #1 of the Connections

34. Example #2 of the Connections

35. Significance of This Achievement
First time ever in the industry to conduct a world wide multi-carrier interoperability testing
Extensive carrier involvement is a key milestone towards industry adoption
Lays groundwork for future inter-carrier interface development
Successful dynamic control plane and data plane integration validates OIF’s Implementation Agreements and ITUs Standards
Demonstrates standardization clearly facilitates multi-vendor interoperability and wide-scale deployment
Remember that the purpose of this presentation isn’t so much a “Look at what we’re doing!” type thing as “What do you think of this and how would you use it?”. Ultimately we need to know if it’s worth our resources, and which particular apps we need to focus on, because we can’t do them all.
Optical Network Interoperability, Shukla/Afferton,

36. OTN Interoperability Summary
Carriers are driving the requirements of the next generation IP optical networks under an unified control plane
Evolutional approach towards the integrated network architecture of an unified control plane has gained wide supports in the service provider and vendor community in the industry
OIF plays an important role in the continued service provider trial and public interoperability events, which are the key steps to ensure successful and deployable next generation network architecture
Large scale, world wide interoperability testing validates the technology maturity
Validated interoperability among industry leading vendors
Allowed service provider to examine performance and network behavior of the next generation network
Demonstrated new network service models and applications
Remember that the purpose of this presentation isn’t so much a “Look at what we’re doing!” type thing as “What do you think of this and how would you use it?”. Ultimately we need to know if it’s worth our resources, and which particular apps we need to focus on, because we can’t do them all.
Optical Network Interoperability, Shukla/Afferton,

37. Thank You

38. OTN Interoperability Glossary

39. Back-up Slides OIF reference material

40. OTN Interoperability- OIF Contributions OIF Directors & Officers
Joe Berthold, Ciena
President
John McDonough, Cisco
VicePresident
Tom Afferton, Northrop Grumman
Treasurer/ Secretary
Marco Carugi, Nortel
Board Member
Tom Palkert, Xilinx
Vishnu Shukla, Verizon
Doug Zuckerman, Telcordia
Technical Committee
Steve Joiner, Bookham Technologies
Chair
MA&E Committee
John D’Ambrosia, Tyco
Chair

41. OTN Interoperability- OIF Contributions OIF and Standards Bodies
Established Liaisons With:
American National Standards Institute - ANSI T1
International Telecommunications Union - ITU-T – OIF is A5 qualified
Internet Engineering Task Force - IETF
ATM Forum
IEEE 802.3ae 10 Gb Ethernet
Network Processing Forum - NPF
Metro Ethernet Forum – MEF
Rapid I/O
Tele Management Forum – TMF
XFP MSA Group

42. OTN Interoperability- OIF Contributions Technical Committee - Working Groups
Architecture & Signaling
Services, network requirements and architectures
Protocols for automatic setup of lightpaths
Carrier
Requirements and applications
OAM&P (Operations, Administration, Maintenance and Provisioning)
Network management
Interoperability
Interoperability testing
Physical and Link Layer
Equipment and subsystem module interfaces
PLUG (Physical Layer User Group )
Guidelines for components, modules, subsystems and communication links

43. OTN Interoperability- OIF Contributions Implementation Agreements
Electrical Interfaces
OIF-SPI SPI-3 Packet Interface for Physical and Link Layers for OC-48.
OIF-SFI Proposal for a common electrical interface between SONET framer and serializer/deserializer parts for OC-192 interfaces.
OIF-SFI SERDES Framer Interface Level 4 (SFI-4) Phase 2: Implementation Agreement for 10Gb/s Interface for Physical Layer Devices.
OIF-SPI System Physical Interface Level 4 (SPI-4) Phase 1: A System Interface for Interconnection Between Physical and Link Layer, or Peer-to-Peer Entities Operating at an OC-192 Rate (10 Gb/s).
OIF-SPI System Packet Interface Level 4 (SPI-4) Phase 2: OC-192 System Interface for Physical and Link Layer Devices.
OIF-SPI System Packet Interface Level 5 (SPI-5) : OC-768 System Interface for Physical and Link Layer Devices.
OIF-SFI Serdes Framer Interface Level 5 (SFI-5): 40Gb/s Interface for Physical Layer Devices.
OIF-SxI System Interface Level 5 (SxI-5): Common Electrical Characteristics for Gbps Parallel Interfaces.
OIF-TFI TDM Fabric to Framer Interface (TFI5)

44. OTN Interoperability- OIF Contributions Implementation Agreements
Tunable Lasers
OIF-TL Implementation Agreement for Common Software Protocol, Control Syntax, and Physical (Electrical and Mechanical) Interfaces for Tunable Laser Modules.
OIF-TLMSA Multi-Source Agreement for CW Tunable Lasers.
OIF-ITLA-MSA Integratable Tunable Laser Assembly Multi-Source Agreement
Very Short Reach Interface
OIF-VSR Very Short Reach (VSR) OC-192 Interface for Parallel Optics.
VSR4-02 (OC-192 Very Short Reach Interface, 1 fiber 1310nm) Note: VSR4-02 has been included as the 4dB link option in VSR4-05 below
OIF-VSR Very Short Reach (VSR) OC-192 Four Fiber Interface Based on Parallel Optics.
OIF-VSR Serial Shortwave Very Short Reach (VSR) OC-192 Interface for Multimode Fiber.
OIF-VSR Very Short Reach (VSR) OC-192 Interface Using 1310 Wavelength and 4 and 11 dB Link Budgets.
OIF-VSR Very Short Reach Interface Level 5 (VSR-5): SONET/SDH OC-768 Interface for Very Short Reach (VSR) Applications.

45. OTN Interoperability- OIF Contributions Implementation Agreements
UNI – NNI
OIF-UNI User Network Interface (UNI) 1.0 Signaling Specification.
OIF-UNI-01.0-R2 - User Network Interface (UNI) 1.0 Signaling Specification, Release 2: Common Part
OIF-CDR Call Detail Records for OIF UNI 1.0 Billing.
OIF-SEP Security Extension for UNI and NNI
OIF-SMI Security Management Interfaces to Network Elements
OIF-E-NNI-Sig Intra-Carrier E-NNI Signaling Specification