Transcript OIF Overview

Achieving Seamless IP Optical
Network Integration
OIF Interoperability Update
Amy Wang, Avici Systems
Agenda






Traditional optical network architecture
OIF history
OIF technical working groups
OIF protocol implementation agreements and
demonstration milestones
OFC UNI/NNI demo highlight
Conclusion
Traditional Optical Network Architecture



Manual configuration - inefficient usage of the network
resource and slow service turn up time
IP & transport networks managed separately - not cost
effective nor efficient for planning or managing
changes
Lack of open standards/ interoperability – does not
allow carriers to leverage multiple vendors for best of
breed solutions
As a result, it is evident that carriers require
solutions over unified control plane across IP and
optical layer
OIF History


Founded in 1998, OIF is an open forum focused on
accelerating the deployment of next generation
optical interworking networks
OIF provides a venue for equipment manufacturers,
users, carriers and service providers to work
together to
•
•
develop key specifications to ensure the
interoperability of optical networks
resolve deployment issues
OIF Technical Working Groups
Carrier
Working Group
Carrier Requirements
Carrier Requirements
Interoperability
Results and findings
Architecture
Physical Link Layer WG
Signaling
Implementation
Agreements
Interoperability
Results and findings
Implementation
Agreements
Interoperability
OAM&P
Protocol WGs
Interoperability
Results and findings
Protocol Implementation Agreement
and Demonstration Milestones

OIF UNI 1.0
•
•

User Network Interface (UNI) 1.0 Signaling
Specification
An interim UNI 1.0 public demo held at SuperComm
2001 proofed UNI interworking with over 25 vendors
on control plane and data plane
NNI Implementation Agreement for OFC 2003
•
•
Inter domain signaling
Inter domain OSPF/ISIS based routing
OIF UNI/NNI Network Reference Model


UNI (User-Network Interface) - a signaling mechanism
between clients and transport devices
NNI - communication and signaling method among
optical domains in the optical core network (intra carrier,
inter domain)
UNI
NNI
Transport
UNI
NNI
IP routers
domain
Transport
Transport
domain
Transport
NNI
domain
NNI
Optical Core
NNI
UNI
NNI
domain
UNI IP routers
Transport
domain
UNI
NNI
Transport
Transport
domain
IP Connections
domain
UNI
IP routers
optical Connections
UNI/NNI Interoperability Trial Goals



Proof of concept of the OIF (Inter-domain) E-NNI
concept
Validate the UNI/NNI interworking solution
Demonstrate maturity of UNI 1.0 Agreements
OIF UNI/NNI Public Demonstration
at OFC 2003
Core Domain 4
Core Domain 1
Core Domain 3
Core Domain 6
Core Domain 5
Core Domain 2
UNI/NNI Interoperability Trial Assumptions





Interoperability agreement are based on
• User Network Interface (UNI) 1.0 Signaling Specification
(IA, OIF2001.125.7)
• NNI Implementation Agreement Proposal for OFC 2003
(OIF2002.476)
Connections are established dynamically over
• an UNI initiated interface (switched connections) or
• an
EMS/NMS initiated interface (soft permanent
connections)
Explicit routing is provided by the first metro or core node
initiating the network connection.
The test network topologies refer to clients and domains. Each
domain could represent either an individual TNE (Transport
Network Equipment) or a vendor domain containing multiple
TNE devices
Testing was focused on control plane only
Multi vendor Interoperability
Timeline

2002
planning
NNI requirement and demo pre
Fall, 2002
for
NNI Implementation Agreement Proposal
OFC 2003; Interoperability team is formed

Jan 14, 03
Vendors Sign up commitment

March 8~16, 03
Interoperability testing and Pre-staging

March 15, 03

March 25~27, 03

Carrier Observer Day
Public Demonstration at OFC, Atlanta
UNH Closed Door Testing
Interoperability Participating Companies












Alcatel (UNI-C, UNI-N, E-NNI, NMS/EMS)
Avici (UNI-C)
Ciena (UNI-N, E-NNI)
Data Connection (UNI-C, UNI-N, E-NNI, NMS/EMS)
Elematics (UNI-N, E-NNI)
Mahi Networks (UNI-N, E-NNI, NMS/EMS)
NEC (UNI-C, UNI-N, E-NNI)
Motorola/Netplane (UNI-C, UNI-N, E-NNI, NMS/EMS)
Nortel (UNI-N, E-NNI)
Sycamore (UNI-N, E-NNI, NMS/EMS)
Tellabs (UNI-N, E-NNI, NMS/EMS)
Tellium (UNI-N, E-NNI, NMS/EMS)
Test Methodology

Round robin approach - random vendor pairings
/grouping
•
•

create diversity and fairness
maximize partner/interoperability exposure by
exhaustive pairing
Testing Steps
•
•
•
Routing establishment among the network devices
Signaling are tested with UNI initiated and EMS/NMS
initiated connections
Network build out are based on results from daily test
progress
Test Scheduling - Closed Door Event

Extensive test rotations
•
•



Partner definitions defined by technical manager
2~3 hrs per test rotation
Allow vendor to have the opportunity to retest after
fixes are provided
Daily technical meetings to provide feedback and
address interoperability issues in timely manner
Final two days focused on network stability and
robustness specific public demo setup
Interoperability Outcomes (1)



Fixed implementation errors by the demo
participants
Reached team consensus on specification
clarification / consistent implementation
alignment
Documented open issues in the Finding Report
(OIF2003.035) for further discussion by OIF
technical WGs
•
•
Specification clarification
Architectural questions/concerns for both UNI/NNI
Interoperability Outcomes (2)
OFC Demo
Public Demonstration Highlights

OFC 2003
• First time ever in the industry to successfully
demonstrate multi vendor UNI/NNI interoperability;
demonstrated set up and removal of 15 LSPs across multidomain network in real time;
• Participated by 12 vendors with 15 types of product of real
network equipment or simulated nodes
• Network topology with 10 network client devices and over
30 simulated network elements in 12 domains
• Signaling and routing information exchanges was
captured and updated in the real time with display
software to reflect dynamic connection establishment
• Over 15 press interviews and group demo tours
• OIF ribbon cutting ceremony covered at the front page of
the OFC Daily
• 11 UNI - NNI presentations were made at the OIF theater
area
• Positive feedbacks received from carrier spectators and
general OFC audience
OFC Booth – UNI/NNI Demo Area
OFC Booth – Theater Area Presentations
UNI/NNI Signaling Display
NNI Routing Display
Conclusion

What worked Well
•
•
•

Early planning and weekly technical team calls
identifies interop issues ahead of time
Extensive test rotations at UNH closed door
testing
Commitment from all interop participants
Next Steps
• Accelerate OIF protocol development with
discussion on the Interoperability Finding
document (oif2003.035)
• NNI spec
• UNI 1.0 impact
Thank You