LLMNR Issue 60: Uniqueness check on linkup

[Bernard Aboba <aboba@internaut.com>]

Issue 60: Uniqueness check on linkup
Submitter name: Ralph Droms
Submitter email address: rdroms@cisco.com
Date first submitted: December 3, 2003
Reference:
Document: LLMNR-27
Comment type: T
Priority: S
Section: 4
Rationale/Explanation of issue:

Section 4, fifth paragraph: I think the host should perform the
uniqueness test when the interface is connected to a link (in addition
to the other events in the bullet list).

[BA] I think this is probably correct, since while the
host was disconnected, another host might have checked
for uniqueness of the name, and not gotten a response.
As a result, once the host connects to the network, it needs
to do a uniquenss check.

In order to avoid an impact on roaming latency, it
probably makes sense for this check to be done
optimistically -- the host does not respond to
LLMNR queries until it verifies uniqueness of the
name, but it should be able to do other things,
such as initiate TCP connections, etc. As a
result, the LLMNR name uniqueness test is not
in the critical path for roaming.

Proposed fix is as follows:

In Section 4, add to the list of events on which uniqueness checking is
triggered:
"- detects that an interface is connected and is usable
(e.g. an IEEE 802 hardware link-state change indicating
that a cable was attached or that an association has occurred
with a wireless base station and that any required authentication
has completed)"


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>