Re: new issue: [LL36] Combine and rework section 1.7 and 2.11 to be clearer

    Date:        Fri, 05 Dec 2003 15:20:15 -0600
    From:        "John C. Welch" <[email protected]>
    Message-ID:  <BBF652AF.184EC78%[email protected]>

  | So it appears as though the system is simply saying, "okay, we have a
  | 'proper' ip address, use that for all the other zeroconf stuff as well."

That's just fine, this is what we want to happen - but the final part of
your sentence should be "use that for all the other stuff as well",
zeroconf has nothing whatever to do with it.

v4LL addresses are not something magic for zeroconf use - neither restricted
to be used by protocols defined here, nor required to be used by protocols
defined here - they're just a way of getting a limited use address when
nothing else is available.  Once obtained, they operate just like any other
address, given their limitations (totally unroutable).

  | Working routable address is used as the v4LL address as well.

No, a workable routable address cannot possibly be a v4LL address,
by definition, a LL address is not routable.

I suspect that you mean that you use a non-LL address in a secnario where
you migt have been imagining a LL address would be used - that's nothing
special, LL addresses have no magic extra properties (aside from being
able to be created by a node on its own) - once they exist, they do absolutely
nothing that any other address can't do equally as well (they are just
more restricted in with what they can communicate, because they can't be
routed).

It is always possible to use a wider scope address (1918, or global) instead
of a LL address in the v4 world (not so in v6, where some usages require the
use of LL addresses).

kre