Re: [Roll] [roll] #128: Trickle multicast could be considered in other applications?

On Mon, Jul 29, 2013 at 9:41 AM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

>
> Kerry Lynn <kerlyn@ieee.org> wrote:
>     > My original comment was not to suggest that we should delay the
> draft while we
>     > think up new uses for MPL.  Rather, by considering *any* other
> application it
>     > may
>     > help us decide whether the current proposal is sufficiently
> specified.
>
>     > One alternative use of MPL is to enable multicast updates in small
> mutli-subnet
>     > topologies like homenet.  MPL would probably be less complex than
> deploying
>     > PIM-xM on small routers and, unlike IGMP/MLD Proxying [RFC 4605], it
> would
>     > not require hand-configured trees.  I have a dnssdext proposal in
> mind that
>     > could
>     > use MPL to advantage over hetergeneous links.
>
> So, if sdnsext wants to use MPL, then it needs an applicability statement
> to
> make it clear where the boundaries of the scope-3 is.
>
> I'm not arguing that scope-3 is required for MPL beyond LLNs.  In fact,
reactive
forwarding seems to rely only on link local multicast scope.  (FYI, the
provisional
name is dnssdext.)  If there's a need to limit the extent of MPL updates in
the
general case, couldn't this be done with Hop Count?

For homenet deployments of sdnsext, I think that homenet already has a need
> to determine site boundary.
> For eduprise deployments, it might be enough to say that automatic
> detection
> is impossible, and so routers should default to marking interfaces as not
> being scope-3, but should include a mechanism to include the interface into
> that scope (and which scope-3 domain if the router has more than two
> interfaces).
>
> Having said this, do you think we are done with ticket #128?
>
> Well, I thought that ticket #128<http://trac.tools.ietf.org/wg/roll/trac/ticket/128>had a dependency on the proactive forwarding
tickets (#129 <http://trac.tools.ietf.org/wg/roll/trac/ticket/129>,
#130<http://trac.tools.ietf.org/wg/roll/trac/ticket/130>)
but I think you bring up the point that it also depends on
#132 <http://trac.tools.ietf.org/wg/roll/trac/ticket/132>.  I defer to the
group to decide which is the cart and which is the horse.

-K-

 --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>