Re: [DNSOP] DNS Terminology: Glue

"Zheng"<zhengwang09@126.com> Thu, 12 March 2015 13:46 UTC

Return-Path: <zhengwang09@126.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C020D1A016B for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 06:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.011
X-Spam-Level: ****
X-Spam-Status: No, score=4.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_MISSP_FREEMAIL=1.752, FROM_MISSP_XPRIO=0.001, HTML_MESSAGE=0.001, RELAY_IS_220=2.118, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 4WJvVkStc44L for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 06:46:50 -0700 (PDT)
Received: from m15-220.126.com (m15-220.126.com [220.181.15.220]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2A11A0111 for <dnsop@ietf.org>; Thu, 12 Mar 2015 06:46:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=Date:From:Message-ID:Subject:MIME-Version; bh=tCzfN mX32I48PMvizA1n7pZUmFojhA3hiLQnfjUqTa8=; b=dxEboYRXj4oyFRDkCzCX5 Cti6o+a/zsIkHwML6dBkTHjlNog7WVYXnAl1Sb9RuyeLd8pGzM98/D+pP4Eip3SE 9QqWf9NFurY3P3TyZHPVHTsLBVSQVN6RlBEM/+EytearwydOV3jWnuSJm568RhmI leC1tRYFnsm4eAXr+mDj0w=
Received: from zhengwang09$126.com ( [129.6.140.90] ) by ajax-webmail-sdy12 (Coremail) ; Thu, 12 Mar 2015 21:46:28 +0800 (GMT+08:00)
Date: Thu, 12 Mar 2015 09:46:23 -0500
From: Zheng <zhengwang09@126.com>
To: Niall O'Reilly <niall.oreilly@ucd.ie>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <7fb23340.93af6.14c0e3c80ef.Coremail.zhengwang09@126.com>
In-Reply-To: <m2vbi6ju6z.wl-Niall.oReilly@ucd.ie>
References: <m2vbi6ju6z.wl-Niall.oReilly@ucd.ie>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="__=_Part_Boundary_003_011659.001506"
X-Mailer: NetEase Flash Mail 2.4.0.11
X-Priority: 3 (Normal)
X-Originating-IP: [129.6.140.90]
X-CM-TRANSID: 5sqowADHz2O1mAFVIokSAA--.14306W
X-CM-SenderInfo: x2kh0wpzdqwiaz6rjloofrz/1tbiaAS6Y1Q86q2INgACsm
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/UT5TEyNUK4medX0oJ8CO044SS6g>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] DNS Terminology: Glue
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Thu, 12 Mar 2015 13:46:52 -0000

I guess glue in the scope of the zone data may be a proper subset of glue in the scope of "the message". What if zone A has the name server's name "below" the cut fall in the bailiwick of zone B, and both zones are hosted in one authoritative name server?  If that authoritative name server is allowed to place the address (in zone B) of the name server (zone cut in zone A) in a referral response, is that a case of glue in "the message" but not glue in the zone data?



Best regards,
Zheng Wang



发件人:"Niall O'Reilly" <niall.oreilly@ucd.ie>
发送时间:2015-03-12 08:07
主题:[DNSOP] DNS Terminology: Glue
收件人:"Paul Hoffman"<paul.hoffman@vpnc.org>
抄送:"IETF DNSOP WG"<dnsop@ietf.org>

  Hi. 

  In http://www.ietf.org/id/draft-hoffman-dns-terminology-02.txt, 
  "glue" is defined as follows. 

   Glue records -- Resource records which are not part of the 
   authoritative data, and are address resource records for the servers 
   listed in the message.  They contain data that allows access to name 
   servers for subzones.  (Definition from RFC 1034, section 4.2.1) 

  Reference to "the message" seems to be a distraction here.  The 
  cited source defines (and motivates) glue records, in a section 
  which specifies "[t]he data that describes a zone", as follows 

   [...] a zone contains "glue" RRs which are not 
   part of the authoritative data, and are address RRs for the servers. 
   These RRs are only necessary if the name server's name is "below" the 
   cut, and are only used as part of a referral response. 

  I think that placing the definition of glue in the scope of "the 
  message" rather than in that of the zone data is likely to lead to 
  confusion. 

  Best regards, 
  Niall O'Reilly 
   

_______________________________________________ 
DNSOP mailing list 
DNSOP@ietf.org 
https://www.ietf.org/mailman/listinfo/dnsop