MPLS%20Generic%20Associated%20Channel%20draft-bocci-pwe3-mpls-ge-ach-00.txt

1
MPLS Generic Associated Channeldraft-bocci-pwe3-m
pls-ge-ach-00.txt

• Matthew Bocci (Alcatel-Lucent) David Ward
  (Cisco) (Eds.)
• Stewart bryant (Cisco), Italo Busi
  (Alcatel-Lucent), Marc Lasserre (Alcatel-Lucent),
  Lieven Levrau (Alcatel-Lucent), Martin Vigoureux
  (Alcatel-Lucent)

2
Motivation

• Need OAM to provide end-to-end and segment fault
  detection, diagnostics, maintenance etc for PWs
  and LSPs
• Existing tools VCCV, BFD, LSP-Ping
• Provide CC and IP-based CV functions
• Requirement to extend toolsets, particularly for
  transport uses of MPLS
• Use common mechanisms for PWs and LSPs

3
New Functional Requirements

• Cover OAM, survivability and other maintenance
  aspects
• draft-vigoureux-mpls-tp-oam-requirements-00.txt
• Fault management CC, CV, Alarm suppression,
  lock, remote defect indicator, etc
• Performance management packet loss, delay, etc
• draft-sprecher-mpls-tp-survive-fwk-00.txt
• Automatic Protection Switching
• draft-gray-mpls-tp-nm-req-00.txt
• Management channel

4
Objectives of the draft

• VCCV already defines a highly extensible
  mechanism to carry OAM protocols over a PW
• PW associated channel
• Extend mechanism to be generally applicable to
  all MPLS LSPs and MPLS sections
• Maintain compatibility with existing PW ACH

5
Generic Associated Channel Header

• Identical to the existing PW ACH of RFC 4385

0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1
2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
-------------------------
------- 0 0 0 1Version
Reserved Channel Type
------------------------
--------
6
What new ACH channel types are required?

• Extended OAM mechanisms
• Alarm Suppression, packet loss measurement, delay
  measurement, etc
• draft-sprecher-mpls-tp-oam-analysis-01.txt
• draft-vigoureux-mpls-tp-oam-requirements-00.txt
• Management Communication Channel (MCC)
• draft-gray-mpls-tp-nm-req-00.txt
• Protection/survivability related info (APS)
• draft-sprecher-mpls-tp-survive-fwk-00.txt
• MPLS-TP related signaling messages (SCC)

7
Vendor Specific Code-point Support

• VCCV does not support vendor-specific types today
• PW associated channel types must be allocated by
  IETF consensus
• However, requirement to support vendor-specific
  code points for protocols running in the ACH
• Protects installed base from potential
  inadvertent overloading of code points
• Each ACH protocol draft must provide a solution
  for supporting vendor-specific types e.g. through
  sub-typing

8
Next Steps

• Confirm full list of new channel types and
  allocate code points
• Feedback on the list?
• Move to working group draft