Subject: Proposed resolution to LLMNR Issue 8

From: Bernard Aboba <[email-masked]>
Date: Mon, 17 Mar 2003 09:50:19 -0800 (PST)

Issue 8: Conflict resolution
Submitter: Mika Liljeberg
Submitter email address: [email-masked]
Date first submitted: March 11, 2003
Document: LLMNR-13
Comment type: T
Priority: S
Section: 5
Rationale/Explanation of issue:

Section 5 states:

Every responder that responds to a LLMNR query and/or dynamic update
request AND includes a UNIQUE record in the response:

   1. MUST verify that there is no other host within the scope of the
      LLMNR query propagation that can return a resource record
      for the same name, type and class.
   2. MUST NOT include a UNIQUE resource record in the
      response without having verified its uniqueness.

How does a responder know whether a particular RR that it owns is UNIQUE
or not? Looks like this attribute has to be manually configured for
every RR on every authoritative responder. Is this interpretation
correct?

I suppose an implementation can simply choose to not support cluster
names and just assert that every RR it owns is UNIQUE.

MikaL
[BA] -

I believe that the default assumption is that the RR is UNIQUE
unless it is configured otherwise. Add the following to
Section 4:

"By default, a host SHOULD be configured to behave as though
all RRs are UNIQUE."

--
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/>