1 / 16

Optical Network Integration via GMPLS

Optical Network Integration via GMPLS. February 15, 2005. GMPLS In a Nutshell. GMPLS = Generalized MPLS Builds on success of MPLS in core IP networks Extends notion of “label” to encompass additional transport technologies TDM time slot, DWDM/CWDM Lambda, Fiber switching

austin
Download Presentation

Optical Network Integration via GMPLS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Optical Network Integration via GMPLS February 15, 2005

  2. GMPLS In a Nutshell • GMPLS = Generalized MPLS • Builds on success of MPLS in core IP networks • Extends notion of “label” to encompass additional transport technologies • TDM time slot, DWDM/CWDM Lambda, Fiber switching • Reuses existing IP network protocols • Topology discovery, TE resource advertisment via OSPF-TE • Path selection, resource reservation via RSVP-TE • Industry-wide acceptance, standards are complete

  3. Reuse of MPLS and IP Control Ingress initiates light path setup Data flow λ5 λ8 λ2 λ2 λ2 GMPLS Controlled Path • Request propagated to egress • Egress responds with lambda • Response propagated upstream to ingress

  4. Setting the Stage • Regional Optical Nets (RONs) arrive • Several up and running, more in the pipeline • Connection-oriented, control plane enabled (GMPLS, UNI/NNI) • DWDM, lambda switching, edge-to-edge lightpaths • User community expectations • Extreme bandwidth, dedicated and on-demand • Inter-regional connections • RONs often interconnected via IP-only networks • Lambdas not yet always available end-to-end • IP-only networks may not be control plane enabled • How can control plane technologies be leveraged to meet user expectations in the current environment?

  5. The Ideal RON1 ION RON2 “OK!” “OK!” “OK!” = Packet Link = Lambda Link = GMPLS LSP “Request 5Gps” “Receiving 5Gps” RON = Regional Optical Network ION = Intercontinental Optical Network

  6. The Reality IP Network RON1 RON2 “OK!” “Uh, well …” How to cross the control plane gap? “Request 5Gps”

  7. Option 1: Best Effort IP Network RON1 RON2 N1 N2 U1 U2 1. GMPLS LSP from U1 to N1 2. GMPLS LSP from N2 to U2 • Each segment provisioned separately • Best-effort in the middle • IP network uninvolved in control

  8. Option 2: Manual Stitching IP Network RON1 RON2 N1 N2 U1 U2 1. GMPLS LSP from U1 to N1 2. MPLS LSP from N1 to N2 3. GMPLS LSP from N2 to U2 • Each segment provisioned separately • Some QoS in the middle • IP network must be MPLS-enabled

  9. Option 3: End-to-End MPLS IP Network RON1 RON2 N1 N2 U1 U2 1. GMPLS LSP from U1 to N1, forms FA 2. GMPLS LSP from N2 to U2, forms FA 3. MPLS LSP from U1 to U2, thru FAs • MPLS is signaled end-to-end • Routers at RONs must support FA-LSPs • IP network must be MPLS-enabled, share signaling with RONs

  10. Option 4: Tunneled GMPLS IP Network RON1 RON2 N1 N2 U1 U2 1. Configured tunnel (GRE, IPIP) + TE link 2. GMPLS LSP from U1 to U2, thru tunnel • GMPLS is signaled end-to-end • Best-effort in the middle • IP network uninvolved in control

  11. Option 5: End-to-End GMPLS IP Network RON1 RON2 N1 N2 U1 U2 1. GMPLS LSP from U1 to U2 • GMPLS is signaled end-to-end • IP network must be GMPLS-enabled, share signaling with RONs • Realizable via UNI/NNI, hierarchy

  12. Summary

  13. Basic Standards • Routing • RFC3630 (OSPF-TE v2) • draft-ietf-ospf-ospfv3-traffic-02.txt (OSPF-TE v3) • draft-ietf-ccamp-gmpls-routing-09.txt (routing architecture) • draft-ietf-ccamp-ospf-gmpls-extensions-12.txt (OSPF-GMPLS) • Signaling • RFC3471 (signaling architecture) • RFC3209 (RSVP-TE) • RFC3473 (RSVP-GMPLS) • OIF-UNI-01.0 (UNI extensions to RSVP) • OIF-UNI-01.0-R2-Common (UNI extensions to RSVP) • E-NNI-01.0 (initial xNNI implementation agreement) • Mature, several interoperable implementations

  14. Inter-domain Drafts • General requirements for inter-domain TE • draft-ietf-tewg-interarea-mpls-te-req-02.txt • draft-ietf-tewg-interas-mpls-te-req-07.txt • Both WG drafts, under discussion in Sub-IP Area, TEWG • Specific approaches to inter-domain GMPLS • draft-ietf-ccamp-inter-domain-framework-00.txt • Covers reachability, TE discovery, PCE, inter-domain signaling • WG draft, actively under discussion • draft-otani-ccamp-interas-GMPLS-TE-01.txt • Covers inter-AS reachability/TE data sharing, without specifying particular protocols • Individual draft, discussed at CCAMP meeting 12/04 • draft-ayyangar-ccamp-inter-domain-rsvp-te-01.txt • Extensions to RSVP-GMPLS for inter-domain signaling • Individual draft, also discussed at CCAMP meeting 12/04

  15. Thank you

  16. Multiple LSP Types Packet TDM Lambda Fiber Lambda TDM Packet GMPLS unifies control across technologies

More Related