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

> > > In 4.1, state it is "unweighted" round-robin.
> >
> >I would suggest changing to:
> >
> >"The unicast class frames MUST be configured to transmit in 
> a round-robin
> >fashion to all of the destination port as specified in RFC2889."
> >
> >The traffic pattern is clearly specified in RFC2889, which is an
> >"unweighted" round-robin traffic pattern.

The intent is *not* to reference the methodology as defined in RFC2889, but
rather to reference the existing traffic pattern terminology definition from
RFC2285 of fully meshed:

"3.3.3 Fully meshed traffic

   Definition:

      Frames offered to a designated number of interfaces of a DUT/SUT
      such that each one of the interfaces under test receives frames
      addressed to all of the other interfaces under test."

By adding Scott's suggestion of "unweighted", we make good use of the
existing definition w/out infering any additional methodological
particulars.

Debby Stopp
_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg