Return-Path: 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 7B386129418 for ; Tue, 4 Apr 2017 22:47:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.235 X-Spam-Level: X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no 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 FsbndEfG_Ymj for ; Tue, 4 Apr 2017 22:47:28 -0700 (PDT) Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:140:644b::225]) by ietfa.amsl.com (Postfix) with ESMTP id 623AC129416 for ; Tue, 4 Apr 2017 22:47:28 -0700 (PDT) Received: from jurassic (unknown [115.118.211.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 9DBE456A0447; Wed, 5 Apr 2017 05:47:26 +0000 (GMT) Date: Wed, 5 Apr 2017 11:17:23 +0530 From: Mukund Sivaraman To: dnsop@ietf.org Message-ID: <20170405054723.GB15831@jurassic> References: <20170405054338.GA15831@jurassic> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="0eh6TmSyL6TZE2Uz" Content-Disposition: inline In-Reply-To: <20170405054338.GA15831@jurassic> User-Agent: Mutt/1.8.0 (2017-02-23) Archived-At: Subject: Re: [DNSOP] RCODE and CNAME chain X-BeenThere: dnsop@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IETF DNSOP WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2017 05:47:29 -0000 --0eh6TmSyL6TZE2Uz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 05, 2017 at 11:13:38AM +0530, Mukund Sivaraman wrote: > It seems to me that it should be NOERROR(1) because RFC 1035 defines s/NOERROR(1)/NOERROR(0)/ > NXDOMAIN as "this code signifies that the domain name referenced in the > query does not exist" which in my interpretation doesn't match the > modified QNAME when following the CNAME change. s/CNAME change/CNAME chain/ Mukund --0eh6TmSyL6TZE2Uz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJY5ITqAAoJEB9EXrAiC5LsXc0P/ii3fWq96X9wlQQcyaFXPusT JIGRQexKSlxoxZ3js6Gqk3G6WwA0mBZxBG/lNZx66b7kwp1RSEGfW4WGt32XZi0a HuMdPi36YKl+cUXKuVK7c73EsdILOkgaf3NvWh5iZfyIro2Ts5+2MHjLxE/jn119 liqmBJjzEdNU8x09cbIDsPa2sGXzOr9yPh2bCfkmQpF/1c0l1h5fUWxBQNdXncCQ NhLHK5rU8KtHYCXnjrcfBsnXafAQqcb8/+T45NE36qkPenpWLKlpamdsGtOFQmwd d3INSiMu2LAAAzw5WAaU4Psj2uLQ4hokUnWprnqSxPYsiPbh5A8EOOztU0IoG50c KSZX34efziH/sCm4C23/Cu/FcugL8HR0VpOqrMn8wDh3PVJPsDEHB8Qmz4inL1F0 yOZ18eoHHtOpiVbSAOgpOuPMuwftuNYhyjkl42EDn2Q16mbDLlZE2g5DCqyxy+Yj H+Z6+sAgNguhdckM3nVFhuNjj825VU97TEBCo6Owq6YOhKQXBLI3BVlbK06pBKtS CLydkb/DIktqPzG5/IRHFyfLy2cSIY4SuWNR1O2OKOtuCU79sqrCQVKeUD8EbiNh nYu+8XMBIXlZrcAonYHVGzaPcEKDv2hfpNhJzpPuhFlRvW8D5ZcIa/t9oBEW+ajO ZlOEmq+jP9423PuBWLA0 =wC7c -----END PGP SIGNATURE----- --0eh6TmSyL6TZE2Uz--