RE: [bmwg] Comments on draft-ietf-bmwg-mcastm-12.txt

["Hickman, Brooks" <[e-mail]>]

Based on the comments from the last call, the following changes are being
incorporated in the -12 I-D. 

Section 4.1 Mixed Class Throughput:

FROM:

 o	The DUT/SUT MUST learn the appropriate unicast addresses; and"

TO:

 o  The DUT/SUT MUST learn the appropriate unicast and multicast
addresses; and"

FROM:

"Mixed class throughput measurement is defined in RFC2432 [Du98]. A
search algorithm MUST be utilized to determine the Mixed Class Throughput."

TO:

"Mixed class throughput measurement is defined in RFC2432 [Du98]. A
search algorithm MUST be utilized to determine the Mixed Class Throughput.  
The ratio of unicast to multicast frames MUST remain the same when
varying the intended load."


Section 5.2. Min/Max Multicast Latency: 

"The following results MUST be reflected in the test report:

   o	The Max/Min value
   o	The set of all latencies with respective time units related to the
      tested ingress and each tested egress DUT/SUT interface."

TO:

The following results MUST be reflected in the test report:
   o	The Max/Min value

The following results SHOULD be reflected in the test report:
   o	The set of all latencies with respective time units related to the
      tested ingress and each tested egress DUT/SUT interface."


Section 6.1 Group Join Delay 

Modified text for Join Delay test to include ref of state 0/1 discussed at
the start of the procedure.
While there was a suggestion to break the test out into two separate tests,
it was felt that doing so would cause more confusion. There is only one
definition for the group join delay specified in the terminology RFC2432.
The test is making the same measurement, only the context(i.e. - State of
the MFDB in the DUT/SUT) in which that measurement is made is different
between the two methods.

WAS:

Method A:

Method A assumes that the Multicast Forwarding Database <MFDB> of 
the DUT/SUT does not contain or has not learned the specified multicast
group address.  

Method A assumes that the Multicast Forwarding Database <MFDB> of the
DUT/SUT does not contain or has not learned the specified multicast group
address; specifically, the MFDB MUST be in State 0. 


WAS:

Method B:

Method B assumes that the MFDB of the DUT/SUT does contain the specified
multicast group address.

IS:

Method B assumes that the MFDB of the DUT/SUT does contain the specified
multicast group address; specifically, the MFDB MUST be in State 1.

Section 8.2 Forwarding Burdened Group Join Delay 

WAS:

"Similar to Section 6.1, the following configuration parameters MUST be
reflected in the test report:

o	Frame size(s) 
o	Number of tested egress interfaces on the DUT/SUT 
o	IGMP version
o	Offered load to ingress interface
o	Total number of multicast groups
o	Offered load to burdening ports
o	Total number of burdening ports"

IS:

"Similar to Section 6.1, the following configuration parameters MUST be
reflected in the test report:

o	Frame size(s) 
o	Number of tested egress interfaces on the DUT/SUT 
o	IGMP version
o	Offered load to ingress interface
o	Total number of multicast groups
o	Offered load to burdening ports
o	Total number of burdening ports
o	Method used to measure the join delay metric"


_______________________________________________
bmwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/bmwg