Re: What is an IGMPv3 Router's initial current state for amulticast group?

Hi:
 
Initial state INCLUDE(A)
messaje TO_EX(B)
Final state EXCLUDE(A*B,B-A)
 
In the case B is "NULL" ( a empty list {} ) in the message, then the final state must be EXCLUDE({}, {}) and it doesn't matter which is the intial state. Both the requested list and the exclude list must be empty lists in the final state.
 
If the above is a litle difficult to understand is because, from my point of view, the requested list is a very bad solution to keep track of include sources when the filter mode is EXCLUDE. 
 
I think it would be a good idea to fix this in IGMPv4
 
Regards
 
Alvaro

________________________________

De: [email protected] en nombre de Suvendu Mozumdar
Enviado el: mié 05/03/2008 7:40
Para: [email protected]
Asunto: [magma] What is an IGMPv3 Router's initial current state for amulticast group?



Hi,
      I have a query regarding the IGMPv3/MLD Router behaviour. In IGMPv3/MLDv2, the action of a router on receiving a report message for a particular Group depends on the router's current state for the group at the time of receiving the report, as defined in section 6.4 of RFC 3376. Now what should be a router's initial current state for a group when it has received the first report for the group, lets say a router comes up afresh and receives the first report message for a group G1 with filter mode TO_EX(NULL). Now it has to consider some initial current state for the group and then based on that it has to take an action for the TO_EX(NULL) report. 

My question is what should be a router's initial current state for a group. I feel it should be INCLUDE(NULL), please advise.

-- 
Suvendu Mozumdar.
QA Architect.
Ixia Technologies Pvt. Ltd
9th Floor, Infinity Tower II
Sector V, Saltlake.
Kolkata 700091.
INDIA.
Mob : +919874081221

_______________________________________________
magma mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/magma