Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard

Russ Allbery <rra@stanford.edu> Fri, 26 August 2005 17:37 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8i8i-0004AO-Aa; Fri, 26 Aug 2005 13:37:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8i8g-000499-4x for ietf@megatron.ietf.org; Fri, 26 Aug 2005 13:37:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03344 for <ietf@ietf.org>; Fri, 26 Aug 2005 13:37:13 -0400 (EDT)
Received: from smtp1.stanford.edu ([171.67.16.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8i9Q-0006Rw-TM for ietf@ietf.org; Fri, 26 Aug 2005 13:38:02 -0400
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.19.147]) by smtp1.Stanford.EDU (8.12.11/8.12.11) with ESMTP id j7QHatDW030563 for <ietf@ietf.org>; Fri, 26 Aug 2005 10:36:55 -0700
Received: by windlord.stanford.edu (Postfix, from userid 1000) id C351BE7BCE; Fri, 26 Aug 2005 10:36:54 -0700 (PDT)
From: Russ Allbery <rra@stanford.edu>
To: ietf@ietf.org
In-Reply-To: <17167.14936.141345.6653@chiark.greenend.org.uk> (Ian Jackson's message of "Fri, 26 Aug 2005 16:50:48 +0100")
Organization: The Eyrie
References: <200508260153.j7Q1rBPj000783@relay4.apple.com> <20050826072055.GA15833@nic.fr> <87ll2pkquy.fsf@windlord.stanford.edu> <430EFCFF.1010203@zurich.ibm.com> <17167.14936.141345.6653@chiark.greenend.org.uk>
Date: Fri, 26 Aug 2005 10:36:54 -0700
Message-ID: <87pss0ioqx.fsf@windlord.stanford.edu>
User-Agent: Gnus/5.110004 (No Gnus v0.4) XEmacs/21.4.17 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Subject: Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Ian Jackson <ijackson@chiark.greenend.org.uk> writes:

> I'm finding this discussion quite disturbing.

You're not the only one, and I'm not even directly affected by this
decision.

> It seems that the proposal is that the IETF should bless LLMNR because
> LLMNR is on the Blessing Track.

> Surely the reasons for the IETF to bless LLMNR as opposed to mDNS
> should be based on technical details and deployment experience ?

Amen.

I recognize that apparently a lot of DNS working group members are
apparently not fond of mDNS for some reason.  That's an important opinion
and should be respected.  However, widespread, existing *successful*
deployment is also a very strong argument and should also be respected.  I
personally tend to give it somewhat more weight than theoretical
arguments, unless the theoretical arguments are *very* strong.

At the very least, I would find it extremely disappointing and contrary to
the needs of the consumers of IETF standards if LLMNR were approved
without attention to interoperability with the existing mDNS deployed base
(which doesn't mean necessarily having interoperability, but it does mean
explaining how existing mDNS installations should deal with LLMNR) and
without a very clear explanation of why the already widely deployed
solution was not standardized instead of standardizing a different
protocol.

Presumably the DNS working group has some incredibly strong arguments that
trump running code or they wouldn't have made the choices that they have.
Let's see them, and furthermore, let's see them *in the document* or at
least in a supporting informational document, since those of us on the
IETF mailing list are certainly not the only people who are going to have
that question.  Implementors are going to have to choose which protocols
to use, and right now they're being given very little useful guidance and
justification by the DNS working group as near as I can tell.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf