1. MPLS P2MP OAM <draft-swallow-mpls-mcast-cv-00.txt>
IETF-67

2. Requirements
Most P2MP-TE applications will require heavy-weight OAM solutions
Television feeds
Stock ticker
Repair times on the order of human response time highly desirable
Many applications will use egress repair

3. Egress Repair Failover requirement is 50 ms L2 P2MP TE LSP SW
Multicast
Server
P2MP TE LSP
Failover requirement is 50 ms

4. Requirements Scaling properties Auto-configuration of tools
Operators require low-impact on network.
Must deal with many endpoints (1000s)
Auto-configuration of tools
Simple initial configuration
Add/prunes need to automatically trigger OAM configuration

5. Multicast Connectivity Verification
Two basic phases of operation
Configuration distributed from Head-end
LSP Ping
Heartbeat (probes) from Head-end
Multicast BFD
Similar operation for mLDP and P2MP-TE
P2MP-TE head-end knows all the leaves,
usually mLDP head-end does not

6. Multicast Configuration Announcement
Periodically send messages with mcast OAM configuration
Extended MPLS Echo Request Message
Sent to a 127/8 address
Listen for replies from leaves
Can poll for missing leaves using LSP Ping scoping
Configuration message contains a lifetime
Configuration must be refreshed within this time
Need a separate slide containing details of how to change timer intervals.
For example: This message should precede timer changes once originally distributed.

7. LSP Ping Echo Request FEC Stack Discriminator
Period for jittering replies
Refresh interval
Alarm action?
Status for Admin Down

8. Multicast CV Egress Configuration
simply configure that OAM sessions should be accepted for any mLDP and/or P2MP RSVP-TE
Wait for LSP Ping Echo Request message
Validate as normal
Bind discriminator to FEC/Root
Set up actions
Responses jittered over a reply interval in LSP Echo Request message
Optionally could listen for 6 “fast” CV messages and divide by 5 to get the CV message interval dynamically.
Subsequent re-configuration messages can be quickly compared to last one via bit compare, which facilitates LC implementation.

9. Multicast CV Setup
Multicast CV Configuration
MPLS Echo Reply

10. Heart-Beat Root continually probes leaves with BFD
Message is multicasted through normal data plane traffic replication
In one mode, Leaves do not reply to these messages
Use where repair is made at the leaf
E.g. UPSR
BFD packet carries discriminator & status octet (e.g. FDI, Admin Down)
Configuration phase described later.

11. Probing with BFD
Multicast BFD

12. Root Notification Options
No notification
Indicated by 0xFFFF FFFF in Required Min RX Interval
Used when tail will take all actions
Unreliable notification
Root periodically sets poll bit
All leaves respond; responses jittered over value of Required Min RX Interval
Reliable notification
On missed response to poll; unicast polls are sent out of band of the P2MP stream

13. Agenda Multicast LSP Ping Proxy LSP Ping
P2MP-TE
Multicast LDP (mLDP)
Multicast Connectivity Verification
Description of problem space
Session Setup / Management
BFD Probes
Conclusions

14. Conclusions
Multicast LSP OAM can be accomplished by extending the existing MPLS OAM toolset
A complete and comprehensive solution is on its way
Multicast LSP Ping
Proxy LSP Ping
MPLS Multicast BFD
Addresses P2MP-TE & Multicast LDP
Flexible & Scalable

15. Next Steps
Is this a good idea?
Working group draft?