Hi Mankamana,
I think more specific description of IGMPv3 for Multicast Join/Leave Synch
process should be better added in this draft
Because IGMPv3 is very complicated, As we know, BLOCK, TO_IN, TO_EX can
make some sources leave or even the group fitermode change.
But the route format definition make me confused about how to express
TO_IN，TO_EX by corresponding type 7 or 8 route.
For example, is there Leave Synch Route(type 8) for the exclude mode
source? If so , how can I understand the route?
Thanks
Yisong
.
From: Mankamana Mishra (mankamis) [mailto:[email protected]]
Sent: Saturday, October 26, 2019 5:08 AM
To: Liuyisong <[email protected]>
Subject: Re: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02
for IGMPv3
Hey,
Wondering if you still have some question about this draft. I would be present
in coming IETF.
From: "Mankamana Mishra (mankamis)"
<[email protected]<mailto:[email protected]>>
Date: Thursday, July 12, 2018 at 7:14 PM
To: Liuyisong <[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Cc: Zhuangshunwan <[email protected]<mailto:[email protected]>>,
"Yangang (Routing Design)" <[email protected]<mailto:[email protected]>>
Subject: Re: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02
for IGMPv3
Hi Yisong
Would you be present in IETF, we could discuss in person and then update the
thread?
Thanks
Mankamana
From: BESS <[email protected]<mailto:[email protected]>> on behalf of
Liuyisong <[email protected]<mailto:[email protected]>>
Date: Thursday, July 12, 2018 at 4:38 AM
To:
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Cc: Zhuangshunwan <[email protected]<mailto:[email protected]>>,
"Yangang (Routing Design)" <[email protected]<mailto:[email protected]>>
Subject: [bess] some questions about draft-ietf-bess-evpn-igmp-mld-proxy-02 for
IGMPv3
Hi folks,
I have some questions about the draft-ietf-bess-evpn-igmp-mld-proxy-02 for
IGMPv3 synchronization
In section 7.2 & 7.3, there are IGMP Join and Leave Synch Route definition as
following:
[cid:[email protected]][cid:[email protected]]
IGMPv3 is very complicated, and it is not very clear to how to construct the
IGMP Join/Leave Synch Route in the draft.
Firstly I think only incremental membership information in the IGMP synch
route, because the route NLRI can only contain one (S,G) or (*,G)
1.for a simple example:
INCLUDE (A) BLOCK (B) INCLUDE (A) Send Q(G,A*B)
We can use include mode, source A*B, group G in IGMP Leave Synch Routes one by
one to notify the other multi-homed PEs.
2.for a more complicated example:
EXCLUDE (X,Y) TO_EX (A) EXCLUDE (A-Y,Y*A) (A-X-Y)=Group Timer
Delete (X-A)
Delete (Y-A)
Send Q(G,A-Y)
Group Timer=GMI
It is more difficult than example 1.There are 5 actions, and should we use both
Join and Leave Synch routes to notify the other multi-homed PEs?
I think we should use:
1） include mode, source A-X-Y, group G in IGMP Join Synch Routes one by one
2） include mode, source X-A, group G in IGMP Join Synch Routes withdraw one by
one
3） exclude mode, source Y-A, group G in IGMP Join Synch Routes withdraw one by
one
4） include mode, source A-Y, group G in IGMP Leave Synch Routes one by one
Is it appropriate for IGMPv3 Synch route construction in the draft?
3.In IGMPv3, only BLOCK, TO_IN, TO_EX can lead to generate last member query.
Is that mean when the PE only receive BLOCK, TO_IN , TO_EX , it should
advertise the leave synch routes to the other multi-homed PEs?
Thanks
Yisong
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess
