Re: [DNSOP] Mandated order of CNAME records in a CNAME chain?

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 30 September 2016 05:44 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A47512B19F for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 22:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QuN7purayQYb for <dnsop@ietfa.amsl.com>; Thu, 29 Sep 2016 22:44:56 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74A9012B062 for <dnsop@ietf.org>; Thu, 29 Sep 2016 22:44:52 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 1BB02284809; Fri, 30 Sep 2016 05:44:51 +0000 (UTC)
Date: Fri, 30 Sep 2016 05:44:51 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: dnsop@ietf.org
Message-ID: <20160930054450.GU4670@mournblade.imrryr.org>
References: <20160929123532.GD22645@laperouse.bortzmeyer.org> <20160929130333.qsrjntfgmrobj7i2@mycre.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160929130333.qsrjntfgmrobj7i2@mycre.ws>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/BJ2-z0ftpTTizZRSlUraLvaQdik>
Subject: Re: [DNSOP] Mandated order of CNAME records in a CNAME chain?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dnsop@ietf.org
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 05:44:59 -0000

On Thu, Sep 29, 2016 at 09:03:33AM -0400, Robert Edmonds wrote:

> > Very good question but, IMHO, it is thread-stealing (hence changing
> > the subject, and removing thread headers).
> 
> I think there was already a thread on this topic recently on this list
> ("Order of CNAME and A in Authoritative Reply" from August 2015). There
> was some discussion over "adding" versus "appending" and it was pointed
> out that a lot of existing code (e.g., the BSD stub resolver) was
> written using the "add at the end" meaning.

Right you are, and it seems I even participated in that discussion,
though it has entirely faded from memory.  All that said, it seems
to me that no conclusion was arrived at in that 2015 thread.

I'm inclined to conclude (as suggested off-list) that, while it
may be prudent to parse conservatively, and not make ordering
assumptions, in fact less tolerant stub resolvers are sufficiently
common and so one would likely get away with assuming natural
ordering.  So perhaps doing it right is not entirely overkill...

-- 
	Viktor.