Re: [dnsext] RFC 6604 Clarification

Jiankang Yao <yaojk@cnnic.cn> Tue, 31 March 2015 14:26 UTC

Return-Path: <yaojk@cnnic.cn>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65EA91ACD81 for <dnsext@ietfa.amsl.com>; Tue, 31 Mar 2015 07:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.238
X-Spam-Level: ***
X-Spam-Status: No, score=3.238 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MIME_CHARSET_FARAWAY=2.45, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Whj_G3SzSy6w for <dnsext@ietfa.amsl.com>; Tue, 31 Mar 2015 07:26:26 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 05B8A1ACD7E for <dnsext@ietf.org>; Tue, 31 Mar 2015 07:26:25 -0700 (PDT)
Received: from [192.168.1.110] (unknown [125.33.4.118]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0ApMISPrhpVrcYkAA--.5716S2; Tue, 31 Mar 2015 22:26:24 +0800 (CST)
References: <af1796c3bda84e99844715264afc67a5@HKXPR30MB021.064d.mgd.msft.net> <551A4B2B.9070406@nlnetlabs.nl>
Mime-Version: 1.0 (1.0)
In-Reply-To: <551A4B2B.9070406@nlnetlabs.nl>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD8E7EA6-7B27-4442-8FCD-F54533DEB530@cnnic.cn>
X-Mailer: iPhone Mail (11D201)
From: Jiankang Yao <yaojk@cnnic.cn>
Date: Tue, 31 Mar 2015 22:37:32 +0800
To: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
X-CM-TRANSID: AQAAf0ApMISPrhpVrcYkAA--.5716S2
X-Coremail-Antispam: 1UD129KBjvJXoW7Gw48tFWxKr1ftr4xAw4rGrg_yoW8Jr4kpF ZxG3ZFyFWDJr1Iyw1vqrW2gF40yr93Cr9xCF95t3yIvw1v9rn5Zr40qa1S9rW7urW8Jay0 yrW5X397uFy5JFJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUk2b7Iv0xC_Zr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr1j6F4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwV C2z280aVCY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC 0VAKzVAqx4xG6I80ewAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr 1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JMxkIecxEwVAFwVW5XwCF04k2 0xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r1j6r18MI 8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr41l IxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIx AIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2 z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxU4VWlDUUUU
X-CM-SenderInfo: x1dryyw6fq0xffof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsext/3tioolTBkEoc7wFwow2pnEui9m4>
Cc: "dnsext@ietf.org" <dnsext@ietf.org>
Subject: Re: [dnsext] RFC 6604 Clarification
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 14:26:28 -0000




> 在 2015年3月31日,15:22,"W.C.A. Wijngaards" <wouter@nlnetlabs.nl> 写道:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Hi Kumar,
> 
> I cannot answer on the RFC part, but I want to answer on what will
> make the resolver continue the lookup.
> 
>> On 30/03/15 11:04, Kumar Ashutosh wrote:
>> Hi
>> 
>> As per RFC 6604, section 3
>> 
>> When an xNAME chain is followed, all but the last query cycle
>> 
>> necessarily had no error.  The RCODE in the ultimate DNS response
>> 
>> MUST BE set based on the final query cycle leading to that
>> 
>> response.  If the xNAME chain was terminated by an error, it will
>> 
>> be that error code.  If the xNAME chain terminated without error,
>> 
>> it will be zero.
>> 
>> 
>> 
>> This is a little vague on two accounts:
>> 
>> 1.What would be the error code if the server decides to curtail
>> the CNAME chain after a certain length (say 20). Is it still
>> success or do we indicate in some other way.
> 
> The curtailed CNAME chain is best sent with RCODE NOERROR(0).
> 
>> 




Based on the current text below"
>>   If the xNAME chain terminated without error, it will be zero.
>> "

"Curtail the cname chain" can be regarded as a kind of "terminated without error".
So I agree that it is zero (no error).

Jiankang Yao