Optical Control Plane Activities in IETF and OIF

Optical Control Plane Activities in IETF and OIF

L. Ong

9 July 2002

Lyong@ciena.com

L. Ong

9 July 2002

Lyong@ciena.com

2

OutlineOutline

• Intelligent Optical Networking•Goals•Protocols Required

• IETF• Organization, History• Current work and status

• OIF• UNI 1.0 Specification• Future UNI and NNI activities – InterDomain Interface

• Summary•Comparison: Different Focus but Common Goals

• Intelligent Optical Networking•Goals•Protocols Required

• IETF• Organization, History• Current work and status

• OIF• UNI 1.0 Specification• Future UNI and NNI activities – InterDomain Interface

• Summary•Comparison: Different Focus but Common Goals

3

The ProblemsThe Problems

• 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

• 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

One Cause of Limitations:Lack of flexibility and intelligence in hardware and software

Traditional Optical NetworkingTraditional Optical Networking

4

The SolutionThe Solution

NETWORK MGMT PLANENETWORK MGMT PLANE

1. Neighbor Discovery1. Neighbor Discovery2. Routing/Topology Dissemination2. Routing/Topology Dissemination

CONTROL PLANECONTROL PLANE

Intelligent Optical NetworksIntelligent Optical Networks

Automated Processes, Scalability, Robustness, EfficiencyAutomated Processes, Scalability, Robustness, Efficiency

DATA PLANEDATA PLANE

3. Connection Signaling3. Connection Signaling

OUNIOUNIUserUser UserUser

5

Intelligent Optical Network FoundationsIntelligent 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

6

ION-related Standards ActivitiesION-related Standards Activities

Charter: Global Telecom Architecture and StandardsNo. of Members: 189 Member States + 434 Sector Members

Core Participants: • Global Service Providers, PTTs, ILECs• Telecom equipment vendors Goal: International Standards

Charter: Global Telecom Architecture and StandardsNo. of Members: 189 Member States + 434 Sector Members

Core Participants: • Global Service Providers, PTTs, ILECs• Telecom equipment vendors Goal: International Standards

Charter: Evolution of the Internet (IP) ArchitectureMembership: Individuals – community model

Core Participants: • ISPs, Carriers• Router/switch and SW VendorsGoal: Internet Evolution

Charter: Evolution of the Internet (IP) ArchitectureMembership: Individuals – community model

Core Participants: • ISPs, Carriers• Router/switch and SW VendorsGoal: Internet Evolution

Charter: Development of Optical Networking Products and ServicesNo. of Members: 312 Principal Members

Core Participants: • PTTs, ISPs, ILECs, IXCs • Optical Networking VendorsGoal: Optical Network Evolution

Charter: Development of Optical Networking Products and ServicesNo. of Members: 312 Principal Members

Core Participants: • PTTs, ISPs, ILECs, IXCs • Optical Networking VendorsGoal: Optical Network Evolution

IETFIETF

IP Networking StandardsIP Networking Standards

8

IETF Optical StandardsIETF Optical Standards

S ig tran R se rp o o l

T ra nsp o rt A reaB ra d ne r, M a n k in

R o utin g A rea In te rne t, O A M ,S e cu rity, A p ps

m pls ccamp

Sub-IP AreaN e w

IE S G

• 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

9

IETF GMPLS: HistoryIETF 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

10

IP, MPLS and GMPLSIP, 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

11

IETF Standards ProcessIETF Standards Process

• Working Group– Defines protocols

– Approves via email “Last Call”

• Internet Engineering Steering Group (IESG)

– Reviews for correctness and desirability

– Conducts IETF-wide email Last Call

• RFC Editor– Final editing and number assignment

WG DraftWG DraftWG

ApprovalWG

ApprovalIndividual DraftIndividual Draft

IETF Approval

Proposed Std

IETF Approval

Proposed Std

RFCRFC

WG Last CallWG Last Call

IETF Last CallIETF Last Call

RFC editRFC edit

DiscussionDiscussion

ttLastCallLastCall

Proposed StandardProposed Standard

Draft StandardDraft Standard

StandardStandard

12

IETF GMPLS StatusIETF GMPLS Status

• Signaling1. RSVP-TE extensions – starting IETF Last Call

2. CR-LDP extensions – starting IETF Last Call

3. Extensions for SONET/SDH – still resolving comments

• Next step would be Proposed Standard, then RFC

• Link Management• LMP – 2nd WG Last Call

• Routing• OSPF & IS-IS extensions – Currently WG drafts

WG DraftWG DraftWG

ApprovalWG

ApprovalIndividual DraftIndividual Draft

IETF ApprovalProposed StdIETF ApprovalProposed Std

RFCRFC

LMPLMPSignalingSignaling

RoutingRouting

ttLastCallLastCall

Proposed StandardProposed Standard

Draft StandardDraft Standard

StandardStandard

13

IETF GMPLS ImplementationIETF 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

OIFOIF

Optical Network Implementation and deployment

Optical Network Implementation and deployment

15

OIF HistoryOIF 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

16

OIF Standards: OIF UNI 1.0OIF Standards: OIF UNI 1.0

OIF UNIOIF UNI

GMPLSGMPLS

LMPLMPRSVPRSVP LDPLDP

OSPFOSPF ISISISIS

ext ex

t

ext

17

OIF Optical UNI ProgressOIF 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

• 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

18

Current WorkCurrent Work

• UNI 2.0

– Extensions for, e.g., multi-homed access, reachability extensions, enhanced security

– ~19 candidate features

• NNI

– Interface between domains

– InterDomain signaling

– InterDomain routing (new problems)

19

NNI Work: Closer LookNNI Work: Closer Look

Domain Model Domain Model

• Within Domain: homogeneous systems and protocols

• Different Domains: heterogeneous systems and protocols

UNIUNI UNIUNI

UNIUNI

Carrier ADomain X Domain Y

Domain Z

Carrier B

Generic Interdomain Protocol

Generic Interdomain Protocol

Intradomain ProtocolIntradomain Protocol

Interdomain ProtocolInterdomain Protocol

20

Domain ModelDomain Model

– Networks may be organized as multiple domains:

• Administrative/security purposes;

• Scaling purposes;

• Technology/vendor differences…

– InterDomain interface:

• Hides domain characteristics

• Advertises summarized information

• Ideally supports diverse routing

21

Inter-Domain Routing ModelInter-Domain Routing Model

Carrier AOSPF

PNNI

Legacy

SS

SS SS

Inter-Domain protocol

Inter-Domain protocol

Domain SpeakerDomain Speaker

• Allows Differing Domains to Interwork• Legacy (EMS-controlled) Domains Can Also Interwork

• Allows Differing Domains to Interwork• Legacy (EMS-controlled) Domains Can Also Interwork

Reachable addressesBorder links and resource availabilityServices supported (e.g., 1+1, 1:N)

Reachable addressesBorder links and resource availabilityServices supported (e.g., 1+1, 1:N)

22

Future Directions 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

23

IETF vs. ITU vs. OIFIETF 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