draft-sajassi-bess-evpn-igmp-mldproxy-01.txt
A. Sajassi (Cisco), Keyur Patel (Cisco), Samir
Thoria (Cisco), Derek Yeung (Cisco), J. Drake
(Juniper), W. Lin (Juniper)
IETF 97, November 2016
Seoul
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
1
Update
 In the last IETF, we discussed the IGMP Proxy issue
relate to All-Active Multi-homed Ethernet Segments
 In here we’ll discuss the consensual solution
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
2
Multi-homing Issue
 How to handle IGMP/MLD proxy when the CE is
multi-homed with All-Active redundancy
• How to synchronize IGMP Join states among PEs
in the redundancy group
• How to synchronize “last member query” among
PEs in the redundancy group
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
3
Multi-Homing Issue – Join Sync
Join
CE2
PE1
PE2
MPLS/IP
Network
PE4
Join
PE3
• If PE2 is the DF for VLAN-x for which IGMP joins are received, then how
does PE2 signal to other remote PEs (e.g., PE4) that it has a interest for
that C-mcast group and thus should be the receiver for that traffic given
that it is the DF but didn’t receive the Join
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
4
Multi-Homing Issue – Last Member
Query
PE1
Join
CE1
PE2
Leave
CE10
LMQ
MPLS/IP
Network
PE4
PE3
• If the last member of a C-mcast group leaves the group, then the PE that
receives that “leave” message, would initiate last member query to make
sure there is no more interested member for that group, before removing
itself from the receiver list
• However, if PE3 sends LMQ, PE1 may receive it, how do we synchronize
this
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
5
Proposed Solution
 Synchronize IGMP Join and Leave messages
among multi-homing PEs for a given ES in order to
properly advertise SMET route for that <EVI, BD>
 Advertise (or withdraw) SMET route (for IGMP
Proxy) from DF PE ONLY for a given <EVI, BD>
 Define two new EVPN routes:
• One for synchronizing IGMP Join messages
• Another for synchronizing IGMP Leave msgs
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
6
Proposed Solution
Synchronizing IGMP Joins
 If a PE (DF or non DF) receives an IGMP Join on
one of its ES’s for a given <EVI, BD> then, it
creates a local IGMP Join state (if doesn’t have
one) and advertise an IGMP Join Synch message to
other multi-homing PEs for that ES
 When a PE receives it (DF or non DF), it instantiate
an IGMP join state for that (x, G) on that <ES, EVI,
BD>, if it doesn’t have a state
• IGMP Join state is the union of local IGMP join
state and receive IGMP join synch route
 If the PE is the DF and hasn’t advertise an SMET
route for that (x, G), then it advertises the route
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
7
Proposed Solution
Synchronizing IGMP Joins – Cont.
 When a PE (DF or non DF) deletes its local IGMP
join (x, G) state for a <ES, EVI, BD>, then it
withdraws its IGMP Join Synch route
 When a PE receives a withdraw for IGMP Join
Synch route, it remove that route for that PE and if
it has no IGMP Join local state and no IGMP Join
Synch rout from any other PE, then it deletes its
IGMP join state for that <ES, EVI, BD>
 If the DF has no IGMP Join (x, G) state for that <EVI,
BD> on any of its ES’s, then it withdraws SMET
route for that (x, G) on that <EVI, BD>.
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
8
IGMP Join Synch Route
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
9
Proposed Solution
Synchronizing IGMP Leave
 When a PE (DF or non DF) receives a local IGMP Leave
message, it initiates Leave procedure regardless if it
has an IGMP join state or not
 It starts a Max. Response Time timer and initiates Last
Member Query procedure
 It advertises an IGMP Leave Synch route for that (x, G)
on that <ES, EVI, BD>.
 When the Max. Response Time timer expires, the PE
that has advertised this route, withdraws it.
 When a PE (DF or non-DF) receives the IGMP Leave
Synch route, it starts its own Max. Response Time timer
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
10
Proposed Solution
Synchronizing IGMP Leave – Cont.
 If one of the multi-homing PEs receives a local Join
before the timer expires, then it advertises an
IGMP Join sync route for that (x, G) on that <ES,
EVI, BD>
• If it doesn’t have an IGMP state, it creates one
and if it is a DF and hasn’t sent out an SMET
route, it sends one
 If one of the multi-homing PEs receives an IGMP
join synch route, then creates an state if it doesn’t
have one. If it is the DF and hasn’t sent out an
SMET route, the it sends one
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
11
Proposed Solution
Synchronizing IGMP Leave – Cont.
 When the Max. Resp. Time timer expires, the PE
that has advertised the IGMP Leave Synch route,
withdraws it
 Any other multi-homing PE for that ES, that has
started Max Resp. Time timer and has not received
a local IGMP join or a remote IGMP synch route, it
deletes its IGMP Join (x, G) state for that <ES, EVI,
BD>
 If the DF PE has no longer IGMP Join (x, G) state for
that <EVI, BD>, it withdraws its SMET route for that
(x, G) on that <EVI, BD>

Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
12
IGMP Leave Synch Route
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
13
Multicast Flags Extended
Community
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
14
EVI-RT Extended Community
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
15
Next Step
 Request for WG Call
Copyright © 2004 Juniper Networks, Inc.
Proprietary and Confidential
www.juniper.net
16