MPLS-TP Control Plane Framework draft-lll-mpls-tp-control-plane-framework-(-1).txt - PowerPoint PPT Presentation

About This Presentation
Title:

MPLS-TP Control Plane Framework draft-lll-mpls-tp-control-plane-framework-(-1).txt

Description:

Recovery (protection & restoration) Lots of other functionality ... Recovery. RFC4427 Terminology. Protection pre-allocated backup resources ... – PowerPoint PPT presentation

Number of Views:155
Avg rating:3.0/5.0
Slides: 9
Provided by: loube8
Learn more at: https://www.ietf.org
Category:

less

Transcript and Presenter's Notes

Title: MPLS-TP Control Plane Framework draft-lll-mpls-tp-control-plane-framework-(-1).txt


1
MPLS-TP Control Plane Framework
draft-lll-mpls-tp-control-plane-framework-(-1).t
xt
  • Editors
  • Loa Andersson ltloa_at_pi.nugt
  • Lou Berger ltlberger_at_labn.netgt
  • Luyuan Fang ltlufang_at_cisco.comgt

2
Draft Objectives
  • Provide context for the MPLS-TP control plane
  • Based on (and somewhat gated by) MPLS-TP drafts
  • Notably requirements, framework and survivability
  • Based on existing IETF control plane
  • Apply GMPLS/MPLS, PW signaling and routing
    wherever possible
  • Draft will not define any protocol extensions
  • Will identify gaps, but will not define solution
  • Will be covered in future drafts as needed
  • Reminder TP does not require a control plane
  • Drives which functions are in OAM and which are
    in Control Plane

3
Draft Highlights
  • PW
  • Base mechanisms
  • Unmodified (LDP, VCCV, PWE3, etc.)
  • Multi-segment
  • Based on in-progress PWE3 work
  • Redundancy is still TBD
  • TE LSPs
  • GMPLS signaling and routing
  • GMPLS-RSVP, GMPLS-ISIS, GMPLS-OSPF
  • P2MP
  • Recovery
  • Have some open issues
  • More on this later

4
Why GMPLS?
  • Already includes support for
  • MPLS labeled data plane
  • Unidirectional P2P and P2MP LSPs
  • Bidirectional LSPs
  • Independent control and data plane topologies
  • Recovery (protection restoration)
  • Lots of other functionality
  • Most common with MPLS, e.g., bundling

5
Recovery
  • RFC4427 Terminology
  • Protection pre-allocated backup resources
  • Restoration allocation after failure
  • RFC4872 End-to-end recovery
  • 11, 11, 1N, Extra traffic
  • Reversion, recovery commands
  • RFC4873 Segment recovery
  • Same as E2E, but for portion of LSP
  • RFC4090 FRR
  • Allowed for by both 4872 and 4873, but
  • May be incompatible with OAM requirements
  • This is not a question for the control plane
    framework

6
Other topics to be covered
  • Part of framework and separate documents
  • Applicability statements in framework,
    extensions in separate drafts
  • OAM, MEP (hierarchy) configuration control
  • Recovery
  • E2E, segment
  • P2P, P2MP
  • CP reference points (E-NNI, I-NNI, UNI)
  • MPLS / GMPLS interop
  • Diffserv object usage in GMPLS (E-LSPs, L-LSPs)
  • Management plane support

7
Which signaling?
  • OAM or CP?

Function MgmtPlane Control Plane OAM
LSP setup / tear down ? ? X
Signaling restoration (not pre-planned) X ? X
Enabling OAM ? ? X
Fault detection (data plane) X X ?
FIS and Coordinated bidirectional switch X X ?
Reversion X X ?
Protection commands (clear, lockout, forced-switch and manual-switch) ? ? TBD
Loopback control ? TBD TBD
AIS X X ?
Alarm free setup/teardown ? ? TBD
-- possible with CP, but not used in MPLS-TP
8
Next steps
  • Publish 1st draft
  • Likely to include writing assignments to
    volunteers
  • Comments?
Write a Comment
User Comments (0)
About PowerShow.com