Subject: Proposed resolution to LLMNR Issue 41: When Conflict Detection is Required

From: Bernard Aboba <[email-masked]>
Date: Sun, 8 Jun 2003 23:45:27 -0700 (PDT)

The text of Issue 41 is enclosed below.  The proposed fix is:

In Section 4, change:

"By default, a host SHOULD be configured to behave as though all RRs are
UNIQUE.  Uniqueness verification is carried out when the host:

  - starts up or
  - is configured to respond to the LLMNR queries on an interface or
  - is configured to respond to the LLMNR queries using additional
    UNIQUE resource records."

To:

"By default, a host SHOULD be configured to behave as though all RRs are
UNIQUE.  Uniqueness verification is carried out when the host:

 - starts up or is rebooted
- wakes from sleep (if the network interface was inactive during sleep)
- is configured to respond to the LLMNR queries on an interface
- is configured to respond to the LLMNR queries using additional
UNIQUE resource records
- 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)"

------------------------------------------------------------------------
Issue 41: When Conflict Detection is Required
Submitter: Stuart Cheshire
Submitter email address: [email-masked]
Date first submitted: May 25, 2003
Reference:
Document: LLMNR-20
Comment type: T
Priority: S
Section: 4
Rationale/Explanation of issue:

I would have thought it obvious that if a device is powered on without
the cable attached, then performing probes without the cable
connected is unlikely to yield any useful information, and consequently,
when the cable is subsequently connected, any assumption that your
name has been verified unique is completely baseless. However, this is
evidently not obvious. So there is a need to be explicit about when
conflict
detection is done:

* Upon reboot/startup
* Upon wake from sleep (if network interface was inactive during sleep)
* Upon bringing up previously inactive network interface
* Upon Ethernet hardware link-state change that indicates a cable was
attached.
* Upon association with a wireless base station, etc.
* (but NOT periodically as a matter of course)

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