Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain

[Michael Richardson <[e-mail]>]

>>>>> "Dario" == Dario Tedeschi <[e-mail]> writes:
    >> In my approach (allow non-link-local in the outer header), I
    >> tried to separate out the identifiers for the application
    >> endpoints and the MPL domain.  That is why I used the outer
    >> header's destination address to identify the MPL domain and the
    >> inner header's destination address to identify the application
    >> endpoints.  With this approach, it actually becomes feasible to
    >> address situations where the devices within an MPL domain
    >> subscribe to arbitrary IPv6 multicast addresses - not just ones
    >> that are based on the unicast prefix.

    Dario> Firstly, yes I agree the inner destination address should
    Dario> determine the application endpoint. What I'm not clear on is
    Dario> why we need an MPL domain to cover more than the LLN or why
    Dario> we need to support multiple MPL domains in one LLN. Tf the
    Dario> latter case is required to allow for different sets of MPL
    Dario> propagation parameters, then I'd imagine that should rather
    Dario> be handled by the HbH option.

So, I think we really need to hear some use cases for having multiple
MPL domains in one LLN.  Please exclude mDNS(ext) in the list.

-- 
Michael Richardson
-on the road-