Re: [homenet] Configuration must not be carried by the routing protocol

[Henning Rogge <[e-mail]>]

On Thu, Jun 27, 2013 at 12:56 AM, Juliusz Chroboczek
<[e-mail]> wrote:
>> what's a routing protocol?
>> a distributed database.
>
> No, it isn't.
>
> ....
>
>> do we need to invent a separate distributed database for each class
>> of information?
>
> Yes, because different kinds of information have different
> requirements.  There is information that needs to be reliably
> synchronised in a timely manner (the link-state DB), there is
> information that must be distributed in a timely manner but need not
> be synchronised throughout the network (configuration information),
> there is global information that is too large to be distributed except
> on demand (DNS), there is local information that is not distributed
> except on demand (mDNS), and probably many other kinds that I'm missing.

I agree with Juliusz, putting all information transfer in the homenet
(including routing decisions, configuration and DNS?) area into a
single protocol is crazy. We don't gain a lot by this strategy except
a lot of complexity and inflexibility in the implementation.

Henning Rogge

--
We began as wanderers, and we are wanderers still. We have lingered
long enough on the shores of the cosmic ocean. We are ready at last to
set sail for the stars - Carl Sagan