Chromium have made some design decisions which assumes that a MST can only
belong to one MS but that is not the reason for bringing this up. It's part
of the process to have to rewrite code as the spec evolves and from an
implementation view I don't see that one is harder to implement that the
other.
I just saw a major change in described behavior and could not find any
compelling reasons why that was made.
/Tommy
On Wed, Aug 21, 2013 at 9:34 AM, Stefan HÃ¥kansson LK <
stefan.lk.hakansson@ericsson.com> wrote:
>
> But if there are difficulties to implement support for allowing a MST to
> belong to more than one MS, of course that is something we must consider.
>
>