Internet Engineering Task Force (IETF) J. Abley
Request for Comments: 5855 T. Manderson
BCP: 155 ICANN
Category: Best Current Practice May 2010
ISSN: 2070-1721
Internet Engineering Task Force (IETF) J. Abley
Request for Comments: 5855 T. Manderson
BCP: 155 ICANN
Category: Best Current Practice May 2010
ISSN: 2070-1721
Nameservers for IPv4 and IPv6 Reverse Zones
IPv4和IPv6反向区域的名称服务器
Abstract
摘要
This document specifies a stable naming scheme for the nameservers that serve the zones IN-ADDR.ARPA and IP6.ARPA in the DNS. These zones contain data that facilitate reverse mapping (address to name).
本文档为DNS中为区域IN-ADDR.ARPA和IP6.ARPA提供服务的命名服务器指定了一个稳定的命名方案。这些区域包含便于反向映射（地址到名称）的数据。
Status of This Memo
关于下段备忘
This memo documents an Internet Best Current Practice.
本备忘录记录了互联网最佳实践。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关BCP的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5855.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc5855.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
2. Nameservers for IN-ADDR.ARPA ....................................3
3. Nameservers for IP6.ARPA ........................................3
4. IAB Statement ...................................................4
5. IANA Considerations .............................................4
6. Security Considerations .........................................4
7. References ......................................................4
7.1. Normative References .......................................4
7.2. Informative References .....................................5
Appendix A. Existing NS RRSets ....................................6
Appendix B. Performance Characteristics ...........................7
B.1. Label Compression ..........................................7
B.2. Query Patterns .............................................9
B.2.1. QNAME under IN-ADDR.ARPA ..............................10
B.2.2. QNAME under IP6.ARPA ..................................10
1. Introduction ....................................................2
2. Nameservers for IN-ADDR.ARPA ....................................3
3. Nameservers for IP6.ARPA ........................................3
4. IAB Statement ...................................................4
5. IANA Considerations .............................................4
6. Security Considerations .........................................4
7. References ......................................................4
7.1. Normative References .......................................4
7.2. Informative References .....................................5
Appendix A. Existing NS RRSets ....................................6
Appendix B. Performance Characteristics ...........................7
B.1. Label Compression ..........................................7
B.2. Query Patterns .............................................9
B.2.1. QNAME under IN-ADDR.ARPA ..............................10
B.2.2. QNAME under IP6.ARPA ..................................10
The Domain Name System (DNS) is described in [RFC1034] and [RFC1035]. The DNS currently supports keyed data retrieval using three namespaces -- domain names, IPv4 addresses, and IPv6 addresses. Mapping of IPv4 addresses to names is accomplished using data published in the IN-ADDR.ARPA zone. For IPv6, the IP6.ARPA zone is used (see [RFC3596]). The process of mapping an address to a name is generally known as a "reverse lookup", and the IN-ADDR.ARPA and IP6.ARPA zones are said to support the "reverse DNS".
[RFC1034]和[RFC1035]中描述了域名系统（DNS）。DNS目前支持使用三个名称空间（域名、IPv4地址和IPv6地址）进行密钥数据检索。IPv4地址到名称的映射是使用in-ADDR.ARPA区域中发布的数据完成的。对于IPv6，使用IP6.ARPA区域（请参见[RFC3596]）。将地址映射到名称的过程通常称为“反向查找”，IN-ADDR.ARPA和IP6.ARPA区域据说支持“反向DNS”。
The secure and stable hosting of the IN-ADDR.ARPA and IP6.ARPA zones is critical to the operation of the Internet, since many applications rely upon timely responses to reverse lookups to be able to operate normally.
IN-ADDR.ARPA和IP6.ARPA区域的安全稳定托管对于互联网的运行至关重要，因为许多应用程序依赖于对反向查找的及时响应才能正常运行。
At the time of this writing, the IN-ADDR.ARPA zone is served by a subset of the DNS root servers, and IP6.ARPA by servers operated by APNIC, ARIN, ICANN, LACNIC, and the RIPE NCC (see Appendix A).
在撰写本文时，IN-ADDR.ARPA区域由DNS根服务器的子集提供服务，IP6.ARPA由APNIC、ARIN、ICANN、LACNIC和成熟的NCC运营的服务器提供服务（见附录a）。
This document specifies a dedicated and stable set of nameserver names for each of the IN-ADDR.ARPA and IP6.ARPA zones.
本文档为每个IN-ADDR.ARPA和IP6.ARPA区域指定了一组专用且稳定的名称服务器名称。
The naming scheme specified in this document allows IN-ADDR.ARPA and IP6.ARPA to be delegated to two different sets of nameservers, to facilitate operational separation of the infrastructure used to serve each zone. This separation might help ensure that an operational failure of IN-ADDR.ARPA servers does not impact IPv6 reverse lookups as collateral damage, for example.
本文档中指定的命名方案允许将in-ADDR.ARPA和IP6.ARPA委托给两组不同的名称服务器，以便于对用于服务于每个区域的基础设施进行操作分离。这种分离可能有助于确保IN-ADDR.ARPA服务器的操作故障不会影响IPv6反向查找，例如造成附带损害。
The choice of operators for individual nameservers is beyond the scope of this document and is an IANA function that falls under the scope of Section 4 of the Memorandum of Understanding (MoU) between the IETF and ICANN [RFC2860].
为单个名称服务器选择运营商超出了本文件的范围，属于IETF和ICANN之间谅解备忘录（MoU）第4节[RFC2860]范围内的IANA功能。
This document specifies the following naming scheme for servers that host the IN-ADDR.ARPA zone:
本文档为托管IN-ADDR.ARPA区域的服务器指定以下命名方案：
A.IN-ADDR-SERVERS.ARPA B.IN-ADDR-SERVERS.ARPA C.IN-ADDR-SERVERS.ARPA D.IN-ADDR-SERVERS.ARPA E.IN-ADDR-SERVERS.ARPA F.IN-ADDR-SERVERS.ARPA ...
A.IN-ADDR-SERVERS.ARPA B.IN-ADDR-SERVERS.ARPA C.IN-ADDR-SERVERS.ARPA D.IN-ADDR-SERVERS.ARPA E.IN-ADDR-SERVERS.ARPA F.IN-ADDR-SERVERS.ARPA。。。
The IN-ADDR-SERVERS.ARPA zone has been delegated to the same set of servers as IN-ADDR.ARPA. IPv4 and IPv6 glue records for each of those servers has been added to the ARPA zone.
IN-ADDR-SERVERS.ARPA区域已委托给与IN-ADDR.ARPA相同的一组服务器。每个服务器的IPv4和IPv6粘合记录都已添加到ARPA区域。
The IN-ADDR-SERVERS.ARPA and IN-ADDR.ARPA zones are delegated to the same servers, since they are both dedicated for a single purpose and hence can reasonably share fate.
IN-ADDR-SERVERS.ARPA和IN-ADDR.ARPA区域被委托给相同的服务器，因为它们都专用于一个目的，因此可以合理地共享命运。
All servers in the set are named under the same domain to facilitate label compression. Since glue for all servers exist in the ARPA zone, the use of a single domain does not present a practical single point of failure.
集中的所有服务器都在同一个域下命名，以便于标签压缩。由于所有服务器的粘合都存在于ARPA区域中，因此使用单个域不会出现实际的单点故障。
This document specifies the following nameserver set for the IP6.ARPA zone:
本文档为IP6.ARPA区域指定以下名称服务器集：
A.IP6-SERVERS.ARPA B.IP6-SERVERS.ARPA C.IP6-SERVERS.ARPA D.IP6-SERVERS.ARPA E.IP6-SERVERS.ARPA F.IP6-SERVERS.ARPA ...
A.IP6-SERVERS.ARPA B.IP6-SERVERS.ARPA C.IP6-SERVERS.ARPA D.IP6-SERVERS.ARPA E.IP6-SERVERS.ARPA F.IP6-SERVERS.ARPA。。。
The IP6-SERVERS.ARPA zone has been delegated to the same set of servers as IP6.ARPA. IPv4 and IPv6 glue records for each of those servers has been added to the ARPA zone.
IP6-SERVERS.ARPA区域已委托给与IP6.ARPA相同的一组服务器。每个服务器的IPv4和IPv6粘合记录都已添加到ARPA区域。
In its capacity as the body that provides technical guidance to ICANN for the administration of the ARPA top-level domain as described in [RFC3172], the IAB has reviewed this proposal and supports it as an operational change that is in line with the respective roles of ICANN and the IAB.
IAB作为向ICANN提供[RFC3172]中所述ARPA顶级域管理技术指导的机构，已对本提案进行了审查，并将其作为符合ICANN和IAB各自角色的运营变更予以支持。
With due consideration to the approval of the IAB (see Section 4), the IANA has delegated:
考虑到IAB的批准（见第4节），IANA已授权：
1. IN-ADDR-SERVERS.ARPA to the nameservers listed in Section 2;
1. 将IN-ADDR-SERVERS.ARPA添加到第2节中列出的名称服务器；
2. IP6-SERVERS.ARPA to the nameservers listed in Section 3.
2. IP6-SERVERS.ARPA到第3节中列出的名称服务器。
Additionally, IANA has installed IPv4 and IPv6 glue records for the nameservers concerned in the ARPA zone.
此外，IANA还为ARPA区域中的相关名称服务器安装了IPv4和IPv6粘合记录。
The choice of operators for all nameservers concerned is beyond the scope of this document and is an IANA function that falls under the scope of Section 4 of the MoU between the IETF and ICANN [RFC2860].
所有相关名称服务器的运营商选择超出了本文件的范围，属于IETF和ICANN[RFC2860]之间谅解备忘录第4节范围内的IANA功能。
This document introduces no additional security risks for the Internet.
本文档不会为Internet带来额外的安全风险。
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, November 1987.
[RFC1034]Mockapetris，P.，“域名-概念和设施”，STD 13，RFC 1034，1987年11月。
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[RFC3172] Huston, G., Ed., "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")", BCP 52, RFC 3172, September 2001.
[RFC3172]Huston，G.，Ed.“地址和路由参数区域域（“arpa”）的管理指南和操作要求”，BCP 52，RFC 3172，2001年9月。
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority", RFC 2860, June 2000.
[RFC2860]Carpenter，B.，Baker，F.和M.Roberts，“关于互联网分配号码管理局技术工作的谅解备忘录”，RFC 28602000年6月。
[RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, "DNS Extensions to Support IP Version 6", RFC 3596, October 2003.
[RFC3596]Thomson，S.，Huitema，C.，Ksinant，V.，和M.Souissi，“支持IP版本6的DNS扩展”，RFC 3596，2003年10月。
The NS RRSet for the IN-ADDR.ARPA zone at the time of this writing is as follows:
撰写本文时，IN-ADDR.ARPA区域的NS RRSet如下所示：
IN-ADDR.ARPA. 86400 IN NS A.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS B.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS C.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS D.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS E.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS F.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS G.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS H.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS I.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS K.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS L.ROOT-SERVERS.NET. IN-ADDR.ARPA. 86400 IN NS M.ROOT-SERVERS.NET.
地址：ARPA。NS A.ROOT-SERVERS.NET中的86400。地址：ARPA。NS B.ROOT-SERVERS.NET中的86400。地址：ARPA。NS C.ROOT-SERVERS.NET中的86400。地址：ARPA。NS D.ROOT-SERVERS.NET中的86400。地址：ARPA。NS E.ROOT-SERVERS.NET中的86400。地址：ARPA。NS F.ROOT-SERVERS.NET中的86400。地址：ARPA。NS G.ROOT-SERVERS.NET中的86400。地址：ARPA。NS H.ROOT-SERVERS.NET中的86400。地址：ARPA。NS I.ROOT-SERVERS.NET中的86400。地址：ARPA。NS K.ROOT-SERVERS.NET中的86400。地址：ARPA。NS L.ROOT-SERVERS.NET中的86400。地址：ARPA。NS M.ROOT-SERVERS.NET中的86400。
The NS RRSet for the IP6.ARPA zone at the time of this writing is as follows:
撰写本文时，IP6.ARPA区域的NS RRSet如下所示：
IP6.ARPA. 84600 IN NS NS-SEC.RIPE.NET. IP6.ARPA. 86400 IN NS SEC1.APNIC.NET. IP6.ARPA. 86400 IN NS NS2.LACNIC.NET. IP6.ARPA. 86400 IN NS NS.ICANN.ORG. IP6.ARPA. 86400 IN NS TINNIE.ARIN.NET.
IP6.ARPA。84600英寸NS-SEC.NET。IP6.ARPA。NS SEC1.APNIC.NET中的86400。IP6.ARPA。NS NS2.LACNIC.NET中的86400。IP6.ARPA。86400在NS.ICANN.ORG上。IP6.ARPA。NS TINNIE.ARIN.NET中的86400。
For completeness, the NS RRSet for the ARPA zone at the time of this writing is as follows:
为完整起见，撰写本文时ARPA区域的NS RRSet如下：
ARPA. 86400 IN NS A.ROOT-SERVERS.NET. ARPA. 86400 IN NS B.ROOT-SERVERS.NET. ARPA. 86400 IN NS C.ROOT-SERVERS.NET. ARPA. 86400 IN NS D.ROOT-SERVERS.NET. ARPA. 86400 IN NS E.ROOT-SERVERS.NET. ARPA. 86400 IN NS F.ROOT-SERVERS.NET. ARPA. 86400 IN NS G.ROOT-SERVERS.NET. ARPA. 86400 IN NS H.ROOT-SERVERS.NET. ARPA. 86400 IN NS I.ROOT-SERVERS.NET. ARPA. 86400 IN NS K.ROOT-SERVERS.NET. ARPA. 86400 IN NS L.ROOT-SERVERS.NET. ARPA. 86400 IN NS M.ROOT-SERVERS.NET.
阿帕。NS A.ROOT-SERVERS.NET中的86400。阿帕。NS B.ROOT-SERVERS.NET中的86400。阿帕。NS C.ROOT-SERVERS.NET中的86400。阿帕。NS D.ROOT-SERVERS.NET中的86400。阿帕。NS E.ROOT-SERVERS.NET中的86400。阿帕。NS F.ROOT-SERVERS.NET中的86400。阿帕。NS G.ROOT-SERVERS.NET中的86400。阿帕。NS H.ROOT-SERVERS.NET中的86400。阿帕。NS I.ROOT-SERVERS.NET中的86400。阿帕。NS K.ROOT-SERVERS.NET中的86400。阿帕。NS L.ROOT-SERVERS.NET中的86400。阿帕。NS M.ROOT-SERVERS.NET中的86400。
The choice of names for the respective NS RRSets of the IN-ADDR.ARPA and IP6.ARPA zones have a relatively minor impact on the delegation response sizes from their parent zones, given other anticipated contributors such as DNSSEC. However, it is still considered good practice to use a naming scheme that is reasonably compressible: doing so for frequently queried zones such as these is likely to have at least measurable impact on aggregate DNS traffic in the Internet as a whole, and has potential transport benefits to clients whose queries will not result in secure replies.
考虑到DNSSEC等其他预期贡献者，IN-ADDR.ARPA和IP6.ARPA区域各自的NS RRSET名称的选择对其父区域的委派响应大小的影响相对较小。然而，使用合理可压缩的命名方案仍然被认为是一种良好的做法：对频繁查询的区域（如这些区域）这样做可能会对整个互联网中的DNS总流量产生至少可测量的影响，并对查询不会导致安全回复的客户端具有潜在的传输好处。
The naming schemes described in Sections 2 and 3 are highly compressible. That is, once a single nameserver name has been encoded in a DNS message, subsequent nameservers can be specified with substantially smaller encoding.
第2节和第3节中描述的命名方案是高度可压缩的。也就是说，一旦在DNS消息中对单个名称服务器名称进行了编码，就可以使用更小的编码来指定后续名称服务器。
In the DNS, a complete encoding of an a-label involves a one-byte length field, plus a one-byte-per-character encoding of the a-label itself. A domain name's encoding consists of one or more a-labels, so-encoded, plus a single terminating zero byte. Where a terminating series of a-labels has already been encoded as described above, subsequent terminating references to the same series can be made using a two-byte pointer to that full encoding.
在DNS中，a标签的完整编码包括一个单字节长度字段，再加上a标签本身的每字符一字节编码。域名的编码由一个或多个这样编码的A标签加上一个终止的零字节组成。如果a标签的终止序列已经如上所述进行了编码，则可以使用指向该完整编码的双字节指针对同一序列进行后续终止引用。
The non-compressed representation of the nameserver A.IN-ADDR-SERVERS.ARPA fills (1 + 1) + (15 + 1) + (4 + 1) + 1 = 24 bytes.
名称服务器A.IN-ADDR-SERVERS.ARPA的非压缩表示形式填充（1+1）+（15+1）+（4+1）+1=24字节。
The non-compressed representation of A.IP6-SERVERS.ARPA fills (1 + 1) + (10 + 1) + (4 + 1) + 1 = 19 bytes.
A.IP6-SERVERS.ARPA的非压缩表示形式填充（1+1）+（10+1）+（4+1）+1=19字节。
Subsequent nameservers under either domain are encoded with the initial label, plus two bytes for a pointer to the repeated domain elsewhere in the message, i.e., (1 + 1) + 2 = 4 bytes.
任何域下的后续名称服务器都使用初始标签编码，加上两个字节作为指向消息中其他位置重复域的指针，即（1+1）+2=4字节。
The encoded size of the a-labels in a twelve-record NS RRSet named according to Section 2 for IN-ADDR.ARPA is as follows:
根据第2节in-ADDR.ARPA命名的12条记录RRNS集合中a标签的编码大小如下：
+------------------------+---------------------------------------+
| Nameserver | Encoded Size |
+------------------------+---------------------------------------+
| A.IN-ADDR-SERVERS.ARPA | (1 + 1) + (15 + 1) + (4 + 1) + 1 = 24 |
| | |
| B.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| C.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| D.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| E.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| F.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| G.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| H.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| I.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| J.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| K.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| L.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| Total | 68 bytes |
+------------------------+---------------------------------------+
+------------------------+---------------------------------------+
| Nameserver | Encoded Size |
+------------------------+---------------------------------------+
| A.IN-ADDR-SERVERS.ARPA | (1 + 1) + (15 + 1) + (4 + 1) + 1 = 24 |
| | |
| B.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| C.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| D.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| E.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| F.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| G.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| H.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| I.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| J.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| K.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| L.IN-ADDR-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| Total | 68 bytes |
+------------------------+---------------------------------------+
The encoded size of the a-labels in a six-record NS RRSet named according to Section 3 for IP6.ARPA is, hence, as follows:
因此，根据IP6.ARPA第3节命名的六记录RRNS集合中a标签的编码大小如下：
+--------------------+---------------------------------------+
| Nameserver | Encoded Size |
+--------------------+---------------------------------------+
| A.IP6-SERVERS.ARPA | (1 + 1) + (10 + 1) + (4 + 1) + 1 = 19 |
| | |
| B.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| C.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| D.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| E.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| F.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| Total | 39 bytes |
+--------------------+---------------------------------------+
+--------------------+---------------------------------------+
| Nameserver | Encoded Size |
+--------------------+---------------------------------------+
| A.IP6-SERVERS.ARPA | (1 + 1) + (10 + 1) + (4 + 1) + 1 = 19 |
| | |
| B.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| C.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| D.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| E.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| F.IP6-SERVERS.ARPA | (1 + 1) + 2 = 4 |
| | |
| Total | 39 bytes |
+--------------------+---------------------------------------+
By way of comparison, the encoded size of the labels in the NS RRSet for IP6.ARPA (shown in Appendix A) is as follows:
通过比较，IP6.ARPA的NS RRSet中标签的编码大小（见附录A）如下所示：
+-----------------+--------------------------------------+
| Nameserver | Encoded Size |
+-----------------+--------------------------------------+
| NS-SEC.RIPE.NET | (6 + 1) + (4 + 1) + (3 + 1) + 1 = 17 |
| | |
| SEC1.APNIC.NET | (4 + 1) + (5 + 1) + 2 + 1 = 14 |
| | |
| NS2.LANIC.NET | (3 + 1) + (6 + 1) + 2 + 1 = 14 |
| | |
| NS.ICANN.ORG | (2 + 1) + (5 + 1) + (3 + 1) + 1 = 14 |
| | |
| TINNIE.ARIN.NET | (6 + 1) + (4 + 1) + 2 + 1 = 15 |
| | |
| Total | 74 bytes |
+-----------------+--------------------------------------+
+-----------------+--------------------------------------+
| Nameserver | Encoded Size |
+-----------------+--------------------------------------+
| NS-SEC.RIPE.NET | (6 + 1) + (4 + 1) + (3 + 1) + 1 = 17 |
| | |
| SEC1.APNIC.NET | (4 + 1) + (5 + 1) + 2 + 1 = 14 |
| | |
| NS2.LANIC.NET | (3 + 1) + (6 + 1) + 2 + 1 = 14 |
| | |
| NS.ICANN.ORG | (2 + 1) + (5 + 1) + (3 + 1) + 1 = 14 |
| | |
| TINNIE.ARIN.NET | (6 + 1) + (4 + 1) + 2 + 1 = 15 |
| | |
| Total | 74 bytes |
+-----------------+--------------------------------------+
A brief description of likely query patterns for an empty cache with the existing and new NS RRSets follows.
下面简要介绍了空缓存的可能查询模式以及现有和新的NS RRSET。
Consider the IN-ADDR.ARPA NS RRSet (described in Appendix A) and a QNAME that is delegated beneath the IN-ADDR.ARPA zone:
考虑In ADDR.ARPA NS RRSET（附录A中描述）和在In ADDR.ARPA区域下面委托的QNoT：
1. Query sent to root server that is also authoritative for IN-ADDR.ARPA; response is a referral from the IN-ADDR.ARPA zone.
1. 发送到根服务器的查询，该根服务器也是IN-ADDR.ARPA的权威服务器；响应是来自IN-ADDR.ARPA区域的转介。
In the case where the initial query is sent to the J root server:
在将初始查询发送到J根服务器的情况下：
1. Query sent to J.ROOT-SERVERS.NET (which is not authoritative for the IN-ADDR.ARPA zone); response is a referral to an ARPA server with additional-section glue.
1. 发送到J.ROOT-SERVERS.NET的查询（对于IN-ADDR.ARPA区域而言，该查询不具有权威性）；响应是对带有附加部分的ARPA服务器的引用。
2. Query sent to an ARPA server (all of which are also authoritative in this case for IN-ADDR.ARPA); response is a referral from the IN-ADDR.ARPA zone.
2. 发送到ARPA服务器的查询（在本例中，所有查询对于in-ADDR.ARPA也是权威的）；响应是来自IN-ADDR.ARPA区域的转介。
Consider the same query with the IN-ADDR.ARPA NS RRSet (described in Section 2):
考虑与In ADDR.ARPA NS RRSET相同的查询（在第2节中描述）：
1. Query sent to a root server that is also authoritative for ARPA; response is a referral to an IN-ADDR.ARPA server, with additional-section glue.
1. 发送到根服务器的查询，该根服务器也是ARPA的权威服务器；响应是指向IN-ADDR.ARPA服务器的引用，带有附加的部分。
2. Query sent to an IN-ADDR.ARPA server; response is a referral from the IN-ADDR.ARPA zone.
2. 发送到IN-ADDR.ARPA服务器的查询；响应是来自IN-ADDR.ARPA区域的转介。
In the case where the first query is sent to the J root server:
在第一个查询被发送到J根服务器的情况下：
1. Query sent to J.ROOT-SERVERS.NET (which is not authoritative for ARPA); response is a referral to an ARPA server, with additional-section glue.
1. 发送到J.ROOT-SERVERS.NET的查询（对于ARPA来说，它不是权威的）；响应是对ARPA服务器的引用，带有附加的部分粘合。
2. Query sent to an ARPA server; response is a referral to an IN-ADDR.ARPA server, with additional-section glue.
2. 发送到ARPA服务器的查询；响应是指向IN-ADDR.ARPA服务器的引用，带有附加的部分。
3. Query sent to an IN-ADDR.ARPA server; response is a referral from the IN-ADDR.ARPA zone.
3. 发送到IN-ADDR.ARPA服务器的查询；响应是来自IN-ADDR.ARPA区域的转介。
Consider the IP6.ARPA NS RRSet (described in Appendix A) and a QNAME that is delegated beneath the IP6.ARPA zone:
考虑IP6ARPA NS RRSET（在附录A中描述）和在IP6ARPA区域下面委托的QNATE：
1. Query sent to root server that is also authoritative for ARPA; response is a referral from the ARPA zone to an IP6.ARPA server with no additional-section glue.
1. 发送到根服务器的查询，该根服务器也是ARPA的权威服务器；响应是从ARPA区域到IP6.ARPA服务器的引用，无需额外的分区。
2. A recursive lookup for one of the nameservers specified in the referral must now be performed in order to obtain an address for an IP6.ARPA server. In all cases, three queries are required. Successive recursive lookups may be performed in the event that a server is unresponsive.
2. 现在必须对引用中指定的一个名称服务器执行递归查找，以获取IP6.ARPA服务器的地址。在所有情况下，都需要三个查询。在服务器无响应的情况下，可以执行连续的递归查找。
3. Query sent to IP6.ARPA server; response is a referral from the IP6.ARPA zone.
3. 发送到IP6.ARPA服务器的查询；响应是来自IP6.ARPA区域的转介。
In the case where the first query is sent to the J root server:
在第一个查询被发送到J根服务器的情况下：
1. Query sent to J.ROOT-SERVERS.NET; response is a referral to an ARPA server with additional-section glue.
1. 发送到J.ROOT-SERVERS.NET的查询；响应是对带有附加部分的ARPA服务器的引用。
2. Query sent to an ARPA server; response is a referral from the ARPA zone to an IP6.ARPA server with no additional-section glue.
2. 发送到ARPA服务器的查询；响应是从ARPA区域到IP6.ARPA服务器的引用，无需额外的分区。
3. A recursive lookup for one of the nameservers specified in the referral must now be performed in order to obtain an address for an IP6.ARPA server. In all cases, three queries are required. Successive recursive lookups may be performed in the event that a server is unresponsive.
3. 现在必须对引用中指定的一个名称服务器执行递归查找，以获取IP6.ARPA服务器的地址。在所有情况下，都需要三个查询。在服务器无响应的情况下，可以执行连续的递归查找。
4. Query sent to IP6.ARPA server; response is a referral from the IP6.ARPA zone.
4. 发送到IP6.ARPA服务器的查询；响应是来自IP6.ARPA区域的转介。
Consider the same query with the IP6.ARPA NS RRSet (described in Section 3):
考虑与IP6ARPA NS RRSET相同的查询（在第3节中描述）：
1. Query sent to a root server that is also authoritative for ARPA; response is a referral to an IP6.ARPA server, with additional-section glue.
1. 发送到根服务器的查询，该根服务器也是ARPA的权威服务器；响应是对IP6.ARPA服务器的引用，带有附加的部分。
2. Query sent to an IP6.ARPA server; response is a referral from the IP6.ARPA zone.
2. 发送到IP6.ARPA服务器的查询；响应是来自IP6.ARPA区域的转介。
In the case where the first query is sent to the J root server:
在第一个查询被发送到J根服务器的情况下：
1. Query sent to J.ROOT-SERVERS.NET (which is not authoritative for ARPA); response is a referral to an ARPA server, with additional-section glue.
1. 发送到J.ROOT-SERVERS.NET的查询（对于ARPA来说，它不是权威的）；响应是对ARPA服务器的引用，带有附加的部分粘合。
2. Query sent to an ARPA server; response is a referral to an IP6.ARPA server with additional-section glue.
2. 发送到ARPA服务器的查询；响应是对带有附加部分的IP6.ARPA服务器的引用。
3. Query sent to an IP6.ARPA server; response is a referral from the IP6.ARPA zone.
3. 发送到IP6.ARPA服务器的查询；响应是来自IP6.ARPA区域的转介。
Authors' Addresses
作者地址
Joe Abley ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 USA Phone: +1 310 463 9062 EMail: joe.abley@icann.org
Joe Abley ICANN 4676金钟路330号套房，美国加利福尼亚州玛丽娜·德雷，邮编90292电话：+1310 463 9062电子邮件：Joe。abley@icann.org
Terry Manderson ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 USA Phone: +61 4 1127 5673 EMail: terry.manderson@icann.org
Terry Manderson ICANN 4676金钟路330号套房，美国加利福尼亚州玛丽娜·德雷90292电话：+61 4 1127 5673电子邮件：Terry。manderson@icann.org