Hi Ulrich,

I did review the you cited in your earlier e-mail (RFC 5889).   It seems
that RFC suggests that link local addresses not be generated for
interfaces with undetermined link characteristics (which certainly apply
to route over protocols like ROLL RPL and the MANET protocols).

However, in looking 6LoWPAN ND (RFC 6775), isn't assignment of link local
addresses to such a topology exactly what is going on?  If you add ROLL
RPL (RFC 655) to this deployment scenario and specifcally with the
illustrative examples in Annex A, it seems clear that a multi-hop subnet
is exactly what is described.

Next, if someone were to want to support a protocol like mDNS (RFC 6792)
which uses link locals, how could that be supported using RFC 5889?

I think these are important topics as we seemed to have to go to extremes
in our work (ZigBee IP) to deal with ULAs when it would have been great if
link locals were available in the context of a route over protocol like
ROLL RPL.

Don




On 7/24/13 8:32 AM, "Ulrich Herberg" <ulr...@herberg.name> wrote:

>I have pointed out two documents in my earlier email that explain in
>long detail why I believe that multi-hop subnets are a really bad
>idea. The AUTOCONF RFC 5889 presents an architecture for avoiding all
>these problems by using /128 prefixes. In that regards, a subnet wide
>flooding would be fairly uninteresting, as it would not go beyond a
>single router.
>
>Regards
>Ulrich
>
>On Wed, Jul 24, 2013 at 7:58 AM, Michael Richardson
><mcr+i...@sandelman.ca> wrote:
>>
>> I would still like an explanation of why "subnet" is the wrong term.
>>
>> When would scope-3 would be used such that it would not correspond to
>>the set
>> of links on which a "/64" (or other size) is used?
>>
>> --
>> Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
>>
>>
>>
>> _______________________________________________
>> Roll mailing list
>> r...@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>>
>_______________________________________________
>Roll mailing list
>r...@ietf.org
>https://www.ietf.org/mailman/listinfo/roll


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to