Re: [pim] Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

["Reshad Rahman (rrahman)" <[e-mail]>]

Hi Hongji,

It looks like those statistics are needed only for interfaces (not for PWs) , so you could keep them under augment of if:interface, or put those stats under bridge-mrouter-interface and l2vpn-mrouter-interface-ac in the snooping-instance. My preference is for the latter.

Regards,
Reshad.

From: Hongji Zhao <[e-mail]>
Date: Monday, September 17, 2018 at 10:28 PM
To: "Reshad Rahman (rrahman)" <[e-mail]>
Cc: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>, YANG Doctors <[e-mail]>
Subject: RE: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Reshad,

In augment /if:interfaces/if:interface, besides mrouter related data, there are still some statistics related with igmp-mld-snooping.
If take out the whole augmentation of if:interfaces, the statistics will be lost.  What do you think of that?

augment /if:interfaces/if:interface:
    +--rw igmp-mld-snooping
       +--ro statistics
          +--ro received
          |  +--ro query?                  yang:counter64
          |  +--ro membership-report-v1?   yang:counter64
          |  +--ro membership-report-v2?   yang:counter64
          |  +--ro membership-report-v3?   yang:counter64
          |  +--ro leave?                  yang:counter64
          |  +--ro non-member-leave?       yang:counter64
          |  +--ro pim?                    yang:counter64
          +--ro sent
             +--ro query?                  yang:counter64
             +--ro membership-report-v1?   yang:counter64
             +--ro membership-report-v2?   yang:counter64
             +--ro membership-report-v3?   yang:counter64
             +--ro leave?                  yang:counter64
             +--ro non-member-leave?       yang:counter64
             +--ro pim?                    yang:counter64

BR/Hongji
赵宏吉


From: Reshad Rahman (rrahman) <[e-mail]>
Sent: Friday, September 14, 2018 8:48 PM
To: Hongji Zhao <[e-mail]>
Cc: [e-mail]; [e-mail]; YANG Doctors <[e-mail]>
Subject: Re: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Hongji,

Yes I don’t see the purpose of augmenting if:interfaces, I believe all mrouter related data could be in l2vpn-instance or bridge. If this is not the case I’d like to understand why.

I have no further major comments, will do detailed review once this major comment is resolved.

Regards,
Reshad.

From: Hongji Zhao <[e-mail]<mailto:[e-mail]>>
Date: Thursday, September 13, 2018 at 11:47 PM
To: "Reshad Rahman (rrahman)" <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, YANG Doctors <[e-mail]<mailto:[e-mail]>>
Subject: RE: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Reshad,

Do you mean it’s best to take out the whole augmentation of if:interfaces?

And besides it, do you have any other comments about the latest version of igmp snooping model?

Thanks a lot!

BR/Hongji
赵宏吉

From: Reshad Rahman (rrahman) <[e-mail]<mailto:[e-mail]>>
Sent: Friday, September 14, 2018 2:22 AM
To: Hongji Zhao <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; YANG Doctors <[e-mail]<mailto:[e-mail]>>
Subject: Re: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Hongji,

Yes I believe it’s best to take out the augment of if:interfaces and have everything in the l2vpn-instance or bridge. Also, right now I believe  the model is inconsistent because PWs which can be used for mrouter-interface do not have any config outside of l2vpn-instance (but AC interfaces used as mrouter-interface do have mrouter config under if:interface ).

Regards,
Reshad.

From: Hongji Zhao <[e-mail]<mailto:[e-mail]>>
Date: Monday, September 10, 2018 at 10:18 PM
To: "Reshad Rahman (rrahman)" <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, YANG Doctors <[e-mail]<mailto:[e-mail]>>
Subject: RE: Hi Reshad, the issues about igmp snooping model are addressed. Thanks a lot! Re: [yang-doctors] Yangdoctors early review of draft-ietf-pim-igmp-mld-snooping-yang-03

Hi Reshad,

Thanks for your reply.

In IGMP Snooping, the mrouter interface (i.e. Multicast router interface)  is the interface which connects to the multicast router. So there may be more than one mrouter interfaces in a l2vpn-instance or BRIDGE.
As you say,  an interface refers to l2vpn-instance and l2vpn-instance has lists of ACs and PWs for the same mrouter-interface functionality.

Here is how to configure and show Internet Group Management Protocol (IGMP) snooping for IPv4 multicast traffic on the Cisco 7600 series routers.
Gi1/1,Gi2/1,Fa3/48 are all the mrouter interfaces in vlan 1.

Displaying Multicast Router Interfaces
When you enable IGMP snooping, the router automatically learns to which interface the multicast
routers are connected.
To display multicast router interfaces, perform this task:
This example shows how to display the multicast router interfaces in VLAN 1:
Router# show ip igmp snooping mrouter vlan 1
vlan ports
-----+----------------------------------------
1 Gi1/1,Gi2/1,Fa3/48,Router


In the current igmp snooping model, we can configure static-mrouter-interface and static-l2-multicast-group either under the igmp-snooping-instance or under the augment /if:interfaces/if:interface. The purpose is to provide the customer more than one way to configure static-mrouter-interface and static-l2-multicast-group.
Maybe it looks in a mess.
If removing the static-mrouter-interface and static-l2-multicast-group under augment /if:interfaces/if:interface is better, I can remove them.


BR/Hongji
赵宏吉