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"
发送时间:2015-03-12 08:07
主题:[DNSOP] DNS Terminology: Glue
收件人:"Paul Hoffman"
抄送:"IETF DNSOP WG"
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 ___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop