MPLS-TP Control Plane Framework draft-abfb-mpls-tp-control-plane-framework-02.txt

1
MPLS-TP Control Plane Framework
draft-abfb-mpls-tp-control-plane-framework-02.tx
t

• Contributors
• Loa Andersson ltloa_at_pi.nugt
• Lou Berger ltlberger_at_labn.netgt
• Luyuan Fang ltlufang_at_cisco.comgt
• Nabil Bitar ltnabil.n.bitar_at_verizon.comgt
• Attila Takacs ltattila.takacs_at_ericsson.comgt
• Martin Vigoureux ltmartin.vigoureux_at_alcatel-lucen
  t.frgt
• Elisa Bellagamba ltelisa.bellagamba_at_ericsson.comgt

2
Draft Objectives

• Provide a context for the MPLS-TP control plane
• Based on MPLS-TP RFCs and drafts
• Notably requirements, framework and survivability
• Based on existing IETF control plane LSPs and
  PWs
• Apply GMPLS/MPLS, PW control planes wherever
  possible
• Reviews control plane requirements
• Derived from other requirements, but stated in
  the context of control plane
• All requirements must be satisfied
• By the LSP control plane alone for Network Layer
  Adaptation (FW Section 3.4.3)
• By the combination of PW and LSP control planes
  for Pseudowire Adaptation (FW Section 3.4.2)
• Provides a mapping of requirements to existing
  IETF mechanisms
• Identifies gaps
• Does define any protocol extensions
• Extensions to be covered in other drafts as
  needed
• Reminder TP does not require a control plane
• Drives which functions are in OAM and which are
  in Control Plane
• There is some debate as to which functions belong
  in each (not covered in this talk)

3
Changes in Latest Draft Rev

• General edits
• Added references for all listed requirements
• Aligned text with source, as required
• Some requirements removed
• Filled in Section 3 Relationship of PWs and TE
  LSPs
• Rewrote Section 4 TE LSPs
• Reviews existing GMPLS functions as related to TP
• Provides mapping of TP CP Requirements to
  existing mechanisms
• Identifies areas of anticipated extensions
• Minor updates to PW and Security sections

4
Planned Changes

• Issue current draft as -00 WG draft
• Poll completed March 16
• draft-ietf-ccamp-mpls-tp-control-plane-framework
• Immediately submit -01 draft
• Additional author ltEric.Gray_at_Ericsson.comgt
• General edits and consistency fixes
• Minor requirements alignments
• Substantial revision to Section 5 Pseudowires
• Generally aligned with LSP section
• LDP Function and Pseudowires
• PW Control (LDP) and MPLS-TP Requirements Table
• Anticipated MPLS-TP Related Extensions
• Pseudowire OAM and Recovery (Redundancy)
• Final planned major technical change

5
Next Steps

• Immediately
• Issue as -00 WG document
• Issue -01 document with discussed changes
• Issue -02 revision in Mid April
• To address WG comments
• Other general edits
• Update requirements section to align with P2MP
  split in framework documents
• ? Please review and comment!!!

6
Details of Major Changes

• As time permits

7
draft-abfb-02 Section 3

• Section 3 Added Relationship of PWs and TE LSPs
  
• Follows framework and PWE3 reference models
• PW control is independent from LSP signaling
• GMPLS-RSVP for LSPs, LDP for PWs
• RSVP support for PWs is out of scope
• Allows for use of PW control plane without LSP
  control plane and visa-versa
• Results in four cases (no CP, PW CP, LSP CP,
  PWLSP CP)
• In combination, all requirements must be met by
  TP control plane
• By the LSP control plane alone for Network Layer
  Adaptation (FW Section 3.4.3)
• By the combination of PW and LSP control planes
  for Pseudowire Adaptation (FW Section 3.4.2)

8
draft-abfb-02 Section 4

• Section 4 Rewritten TE LSPs
• Reviews existing GMPLS functions as related to TP
• In-Band and Out-Of-Band Control and Management
• Addressing
• Routing
• TE LSPs and Constraint-Based Path Computation
• Signaling
• Unnumbered Links
• Link Bundling
• Hierarchical LSPs
• LSP Recovery
• Control Plane Reference Points (E-NNI, I-NNI,
  UNI)
• OAM, MEP (Hierarchy) Configuration and Control
• Management Plane Support
• Provides mapping of TP CP Requirements to
  existing mechanisms
• GMPLS Architecture, Signaling (GMPLS-RSVP-TE),
  Routing (ISIS and OSPF), Recovery, Hierarchy,

9
draft-abfb-02 Section 4 (cont.)

• Identifies areas of anticipated extensions
• MPLS to MPLS-TP Interworking
• Associated Bidirectional LSPs
• Asymmetric Bandwidth LSPs
• Recovery for P2MP LSPs
• Test Traffic Control and other OAM functions
• CP or OAM?
• Diffserv Object usage in GMPLS

10
draft-ietf-02 Section 5

• Section 5 Pseudowires
• Aligned the structure of this section more
  closely with the structure of section 4
• Now contains the following subsections
• LDP Function and Pseudowires
• PW Control (LDP) and MPLS-TP Requirements Table
• Anticipated MPLS-TP Related Extensions
• Pseudowire OAM and Recovery (Redundancy)
• There is now a requirements table
• similar to that in section 4
• intended to show what drafts/RFCs address (or
  will address) Pseudowire related requirements
  among those listed in section 2
• References PW-LDP, VCCV, GACH, PWE3, Dynamic-PWs
  
• Non PW requirements met by LSP control plane
• Related changes
• Section 2 updated a few requirements to match
  changes in the documents from which they derived
• Section 4 updated a few table entries to refer
  to the new table in section 5
• References added several new references

11
draft-ietf-02 Other Changes

• A review of the requirements in section 2, and
  comparison with requirements sources allowed for
  deprecating/removing a few requirements
• Removed the Network Management Considerations
  section
• The section had no content
• Not clear that this is needed for a framework
  draft
• If anyone would care to propose text for the
  section, it could be re-inserted
• A number of general editing changes