22
Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net 1 MPLS Inter-domain Traffic Engineering Matt Kolon [email protected] APRICOT 2005 - Kyoto

MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential 21 Conclusion! End-to-end QoS, resource optimization, and recovery

  • Upload
    others

  • View
    6

  • Download
    1

Embed Size (px)

Citation preview

Page 1: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net 1

MPLS Inter-domainTraffic Engineering

Matt [email protected] 2005 - Kyoto

Page 2: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

2Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Agenda

! MPLS TE Review! Problems of Inter-domain TE! Reachability and TE Info Distribution! Signaling! Path Computation! Conclusion

Page 3: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

3Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Review: MPLS Traffic Engineering! Eliminates overlay model of L2/IP Traffic Engineering! TE available from router platforms and administration! Allows intelligent use of available resources! Brings benefits of MPLS to any traffic

• Can carry non-IP traffic• Deterministic performance• Aids in obtaining QoS • Allows use of FRR and protection

! Is widely deployed and understood

Page 4: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

4Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Review: MPLS Traffic Engineering

Engineers unidirectional paths through provider network without using the IGP’s shortest path calculation

Singapore

IGP Shortest Path

Traffic Engineered Path

Taipei

Page 5: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

5Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Standard MPLS TE Mechanisms! Extended IGP

• Builds TED as well as LS database• Uses established extensions to ISIS and OSPF

! Traffic Engineering Database (TED)• Includes link attributes like BW, color, etc.

! Constrained SPF algorithm• Builds ERO according to link attributes

! RSVP for path signaling• Follows ERO with PATH and RESV messages

Page 6: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

6Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Applications for Inter-domain TE! End-to-end inter-domain SLAs! Carrier-of-carrier services (e.g. VPNs)! Extended or virtual POP! Extended or virtual trunk! Inter-provider NNIs! Inter-area intra-domain applications

Page 7: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

7Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Issues for Inter-domain TE! Distributing TE information

• Spreading topology and/or constraint information between domains

! Path computation• Determining a partial or complete path at

ingress and perhaps in other places! Signaling LSPs

• Establishing LSPs using RSVP

Page 8: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

8Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Distributing TE Information! TE information is currently distributed by IGPs! Doesn’t help inter-domain application! Inter-domain TE links

• Require a TE distribution mechanism• This might be TE extensions to BGP• BGP TE info could then be fed to IGP• Processing and information scaling are

concerns

Page 9: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

9Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Signaling Options! Four Distinct Options

• Nesting• Contiguous• Stitched• Hybrid

! Choice may be influenced by path computation techniques (see next section)

! May also depend on application, topology, capabilities of network

Page 10: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

10Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Signaling Options:Nesting! One or more LSPs carried inside another! FA LSP may be pre-provisioned or dynamic! FA LSP controls path of first LSP in red network

Page 11: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

11Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Signaling Options:Contiguous! Single end-to-end LSP! Hop-by-hop signaling used! Requires some knowledge of red network by

blue ingress router

Page 12: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

12Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Signaling Options: LSP Stitching! 2 LSPs stitched to act as one! Stitching may happen at single ASBR, or

through a separate inter-domain LSP, or other tunnel mechanism

Stitches LSPsTogether

Page 13: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

13Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Signaling Options: Hybrid! Hybrid methods may be used

• Combination of two or more signaling options! Choice of downstream method(s) may be:

• Requested by upstream• Restricted by attribute object• Imposed by downstream• Negotiated between domains

Page 14: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

14Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Path Computation! Offline! Ingress! Domain Boundary! Path Computation Element(s)

Page 15: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

15Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Path Computation: Offline! Offline tools or planner! Requires OOB sharing of TE information

ERO

Page 16: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

16Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Path Computation: Ingress! Head-end (ingress) router responsible for ERO! Full, partial, or local-only info may be available

FullERO Here Loose hop here

Page 17: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

17Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Path Computation: Domain Boundary! LSR at each domain boundary adds to ERO! Standard ERO processing rules still apply

ComputesERO 1

ComputesERO 2, appendsTo ERO 1

Page 18: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

18Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Path Computation: PCE! PCE = Path Computation Element(s)! PCEs may have full or partial visibility! Can help preserve confidentiality

EROInformation

Page 19: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

19Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Optimal Inter-domain Paths! Optimal = the path as if no domain boundaries

existed! Optimization and partitioning are always at odds

??

Page 20: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

20Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Other issues! LSP Re-optimization! LSP Setup Failure! LSP Repair! Fast Reroute! Path Diversity! Constraint Definitions! Inter-domain OAM! GMPLS

Page 21: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

21Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net

Conclusion! End-to-end QoS, resource optimization, and recovery

requires TE

! MPLS is the chosen TE method

! End-to-end means Inter-domain in the future! A framework, and later mechanisms, for Inter-domain

MPLS TE are required

• Some mechanisms exist, some will have to be created or enhanced

! Work in this area is ongoing in ccamp, tewg, viz:draft-ietf-ccamp-inter-domain-framework-00.txt

Page 22: MPLS Inter-domain Traffic Engineering · Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential  21 Conclusion! End-to-end QoS, resource optimization, and recovery

Copyright © 2003 Juniper Networks, Inc. Proprietary and Confidential www.juniper.net 22

Thank You

Matt [email protected]