Network Working Group B. Fink
Request for Comments: 2921 ESnet
Category: Informational September 2000
Network Working Group B. Fink
Request for Comments: 2921 ESnet
Category: Informational September 2000
6BONE pTLA and pNLA Formats (pTLA)
6BONE pTLA和pNLA格式（pTLA）
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix, allocated in RFC 2471, "IPv6 Testing Address Allocation", [6BONE-TLA], to create pseudo Top-Level Aggregation Identifiers (pTLA's) and pseudo Next-Level Aggregation Identifiers (pNLA's).
本备忘录定义了6bone如何使用RFC 2471“IPv6测试地址分配”[6bone-TLA]中分配的3FFE:：/16 IPv6地址前缀创建伪顶级聚合标识符（pTLA）和伪下一级聚合标识符（pNLA）。
Acknowledgements
致谢
The address formats here are contributions of various early participants of the 6bone testbed project, and of the IPng and NGtrans IETF working groups.
这里的地址格式是6bone测试床项目的各个早期参与者以及IPng和NGtrans IETF工作组的贡献。
Table of Contents
目录
1. Introduction................................................. 1
2. 6BONE pTLA/pNLA Format....................................... 2
3. Security Considerations...................................... 6
References....................................................... 6
Author's Address................................................. 6
Full Copyright Statement......................................... 7
1. Introduction................................................. 1
2. 6BONE pTLA/pNLA Format....................................... 2
3. Security Considerations...................................... 6
References....................................................... 6
Author's Address................................................. 6
Full Copyright Statement......................................... 7
This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix, allocated in RFC 2471 [6BONE-TLA], to create pseudo Top-Level Aggregation Identifiers (pTLA) and pseudo Next-Level Aggregation Identifiers (pNLA).
此备忘录定义了6bone如何使用RFC 2471[6bone-TLA]中分配的3FFE:：/16 IPv6地址前缀创建伪顶级聚合标识符（pTLA）和伪下一级聚合标识符（pNLA）。
The guiding specifications for IPv6 addressing relating to the 6bone prefix, and the pTLA and pNLA formats, are "IP Version 6 Addressing Architecture" [ADDRARCH], and "An IPv6 Aggregatable Global Unicast Address Format" [AGGR].
与6bone前缀以及pTLA和pNLA格式相关的IPv6寻址指导规范为“IP版本6寻址体系结构”[ADDRARCH]和“IPv6可聚合全局单播地址格式”[AGGR]。
The purpose of creating pseudo TLA and NLA formats for the 6bone is to provide a prototype of the actual TLA and NLA formats as they might be used in production IPv6 networks. To do this economically, using only a minimum of real production IPv6 address space, a single TLA, 3FFE::/16, was reserved by the IANA (Internet Assigned Numbers Authority) for testing on the 6bone. Thus it was necessary to define a pretend-to-be, or pseudo, TLA and NLA structure to use under the 3FFE::/16 prefix.
为6bone创建伪TLA和NLA格式的目的是提供实际TLA和NLA格式的原型，因为它们可能用于生产IPv6网络。为了经济地实现这一点，IANA（Internet Assigned Numbers Authority）仅使用最小的实际生产IPv6地址空间，为在6bone上进行测试保留了一个TLA 3FFE:：/16。因此，有必要在3FFE:：/16前缀下定义一个假装的或伪的TLA和NLA结构。
Given the 48-bit length of the IPv6 Aggregatable Global Unicast Address external routing prefix (that contains the TLA and NLA identifiers), there is enough room to extend the TLA ID to contain a pTLA and shorten the NLA ID to become a pNLA. This document specifies this.
考虑到IPv6可聚合全局单播地址外部路由前缀（包含TLA和NLA标识符）的48位长度，有足够的空间扩展TLA ID以包含pTLA，并缩短NLA ID以成为pNLA。本文件规定了这一点。
In early 1999, it was decided to change the 6bone's pTLA format to allow greater expansion of the testbed network, thus accommodating more than the original 256 pTLA-s. Thus there are now two 6bone pTLA and pNLA formats. This document specifies this.
1999年初，决定更改6bone的pTLA格式，以允许试验台网络的更大扩展，从而容纳超过原来256个pTLA-s的容量。因此，现在有两种6bone pTLA和pNLA格式。本文件规定了这一点。
The original pTLA and pNLA format was intended to accommodate 256 pTLA-s, i.e., backbone networks carrying IPv6 transit traffic.
最初的pTLA和pNLA格式旨在容纳256个pTLA-s，即承载IPv6传输流量的主干网。
The original TLA and NLA ID-s as specified in [AGGR] are as follows:
[AGGR]中规定的原始TLA和NLA ID-s如下：
| 3 | 13 | 32 | 16 | 64 bits |
+---+-----+---------------------+--------+-----------------+
|001| TLA | NLA ID | SLA ID | Interface ID |
+---+-----+---------------------+--------+-----------------+
| 3 | 13 | 32 | 16 | 64 bits |
+---+-----+---------------------+--------+-----------------+
|001| TLA | NLA ID | SLA ID | Interface ID |
+---+-----+---------------------+--------+-----------------+
The TLA value 1FFE was assigned to the 6bone, which when viewed with the 3-bit format prefix in prefix notation form is 3FFE::/16.
TLA值1FFE已分配给6bone，使用前缀表示形式中的3位格式前缀查看时，6bone为3FFE:：/16。
The first 8-bits of the NLA ID space are assigned as the pTLA that defines the top level of aggregation (backbone) for the 6bone. This provides for 256 6bone backbone networks, or pTLA-s, and leaves a 24-bit pNLA ID for each pTLA to assign as needed.
NLA ID空间的前8位被分配为pTLA，该pTLA定义了6bone的顶级聚合（主干）。这提供了256个6bone骨干网络或pTLA-s，并为每个pTLA保留一个24位pNLA ID，以便根据需要进行分配。
| 16 | 8 | 24 | 16 | 64 bits |
+-+---------+-----+-------------+--------+-----------------+
| 0x3FFE |pTLA | pNLA | SLA ID | Interface ID |
+-+---------+-----+-------------+--------+-----------------+
| 16 | 8 | 24 | 16 | 64 bits |
+-+---------+-----+-------------+--------+-----------------+
| 0x3FFE |pTLA | pNLA | SLA ID | Interface ID |
+-+---------+-----+-------------+--------+-----------------+
In prefix notation form the pTLA is 3FFE:nn00::/24, where nn is the pTLA assignment.
在前缀表示形式中，pTLA为3FFE:nn00:：/24，其中nn为pTLA分配。
The remaining NLA ID space can be used by each pTLA for their downward aggregated delegation:
剩余的NLA ID空间可由每个pTLA用于向下聚合的委派：
| n | 24-n bits | 16 | 64 bits |
+-----+--------------------+--------+-----------------+
|pNLA1| Site | SLA ID | Interface ID |
+-----+--------------------+--------+-----------------+
| n | 24-n bits | 16 | 64 bits |
+-----+--------------------+--------+-----------------+
|pNLA1| Site | SLA ID | Interface ID |
+-----+--------------------+--------+-----------------+
| m | 24-n-m | 16 | 64 bits |
+-----+--------------+--------+-----------------+
|pNLA2| Site | SLA ID | Interface ID |
+-----+--------------+--------+-----------------+
| m | 24-n-m | 16 | 64 bits |
+-----+--------------+--------+-----------------+
|pNLA2| Site | SLA ID | Interface ID |
+-----+--------------+--------+-----------------+
| o |24-n-m-o| 16 | 64 bits |
+-----+--------+--------+-----------------+
|pNLA3| Site | SLA ID | Interface ID |
+-----+--------+--------+-----------------+
| o |24-n-m-o| 16 | 64 bits |
+-----+--------+--------+-----------------+
|pNLA3| Site | SLA ID | Interface ID |
+-----+--------+--------+-----------------+
The pNLA delegation works in the same manner as specified in [AGGR]. pTLA's are required to assume registry duties for the pNLA's below them, pNLA1's for those below them, etc.
pNLA授权的工作方式与[AGGR]中规定的相同。pTLA需要为低于他们的pNLA承担注册职责，pNLA1为低于他们的pNLA承担注册职责，等等。
After it became clear that the 6bone would become a useful testbed for transition, in addition to its early role as a testbed for specifications and implementations, the 6bone community decided to expand the size of the pTLA ID.
在明确6bone将成为一个有用的过渡测试平台之后，除了作为规范和实现测试平台的早期角色外，6bone社区决定扩大pTLA ID的规模。
Several important decisions regarding this expansion of the pTLA field are:
关于pTLA油田扩建的几个重要决定如下：
1. to leave the currently allocated 8-bit pTLA-s in use until the space was needed, thus relying on a range value check to indicate the new pTLA format,
1. 将当前分配的8位pTLA-s保留在使用中，直到需要空间为止，从而依靠范围值检查来指示新的pTLA格式，
2. to use a modulo 4-bit sized pTLA ID to make reverse path entry into the DNS easier,
2. 要使用模4位大小的pTLA ID使反向路径更容易进入DNS，
3. given 2. above, to keep the pTLA ID size as small as possible to not restrict pNLA ID size.
3. 给定2。如上所述，保持pTLA ID大小尽可能小，以不限制pNLA ID大小。
Therefore, the first 12-bits of the NLA ID space are assigned as the pTLA that defines the top level of aggegation (backbone) for the 6bone. This would eventually provide for 4096 6bone backbone networks, or pTLA-s, and leaves a 20-bit pNLA ID for each pTLA to assign as needed.
因此，NLA ID空间的前12位被指定为pTLA，该pTLA定义了6bone的顶级聚合（主干）。这将最终提供4096个6bone骨干网络或pTLA-s，并为每个pTLA保留一个20位pNLA ID，以便根据需要进行分配。
| 16 | 12 | 20 | 16 | 64 bits |
+-+---------+-------+-----------+--------+-----------------+
| 0x3FFE | pTLA | pNLA | SLA ID | Interface ID |
+-+---------+-------+-----------+--------+-----------------+
| 16 | 12 | 20 | 16 | 64 bits |
+-+---------+-------+-----------+--------+-----------------+
| 0x3FFE | pTLA | pNLA | SLA ID | Interface ID |
+-+---------+-------+-----------+--------+-----------------+
In prefix notation form the pTLA is 3FFE:nnn0::/28, where nnn is the pTLA assignment. However, as the existing 8-bit pTLA's are being left in use for the present, the nnn value starts at 0x800 for now, thus yielding only 2048 pTLA's in this new format.
在前缀表示形式中，pTLA为3FFE:nnn0:：/28，其中nnn为pTLA分配。然而，由于现有的8位pTLA目前仍在使用中，nnn值目前从0x800开始，因此在这种新格式中仅产生2048个pTLA。
The remaining NLA ID space can be used by each pTLA for their downward aggregated delegation:
剩余的NLA ID空间可由每个pTLA用于向下聚合的委派：
| n | 20-n bits | 16 | 64 bits |
+-----+--------------------+--------+-----------------+
|pNLA1| Site | SLA ID | Interface ID |
+-----+--------------------+--------+-----------------+
| n | 20-n bits | 16 | 64 bits |
+-----+--------------------+--------+-----------------+
|pNLA1| Site | SLA ID | Interface ID |
+-----+--------------------+--------+-----------------+
| m | 20-n-m | 16 | 64 bits |
+-----+--------------+--------+-----------------+
|pNLA2| Site | SLA ID | Interface ID |
+-----+--------------+--------+-----------------+
| m | 20-n-m | 16 | 64 bits |
+-----+--------------+--------+-----------------+
|pNLA2| Site | SLA ID | Interface ID |
+-----+--------------+--------+-----------------+
| o |20-n-m-o| 16 | 64 bits |
+-----+--------+--------+-----------------+
|pNLA3| Site | SLA ID | Interface ID |
+-----+--------+--------+-----------------+
| o |20-n-m-o| 16 | 64 bits |
+-----+--------+--------+-----------------+
|pNLA3| Site | SLA ID | Interface ID |
+-----+--------+--------+-----------------+
As with the original pTLA format, the pNLA delegation works in the same manner as specified in [AGGR]. pTLA's are required to assume registry duties for the pNLA's below them, pNLA1's for those below them, etc.
与原始pTLA格式一样，pNLA委托的工作方式与[AGGR]中规定的相同。pTLA需要为低于他们的pNLA承担注册职责，pNLA1为低于他们的pNLA承担注册职责，等等。
An example usage of the pNLA space is given to demonstrate what is reasonable and possible. It should not be assumed that this implies the pNLA space must be used this way. As the new pTLA and pNLA format is now the default, the example here assumes the 20-bit pNLA format.
给出了pNLA空间的一个使用示例，以说明什么是合理的和可能的。不应假设这意味着必须以这种方式使用pNLA空间。由于新的pTLA和pNLA格式现在是默认格式，因此这里的示例假定为20位pNLA格式。
The following example provides for up to 255 intermediate transit ISP's (called pNLA1 below). The pNLA1 value of zero is meant to indicate that there is no intermediate transit ISP between the backbone pTLA network and the end user site.
以下示例提供了多达255个中间传输ISP（以下称为pNLA1）。pNLA1值为零表示主干pTLA网络和最终用户站点之间没有中间传输ISP。
|<-----20-bit pNLA ID----->|
| |
| 8 | 12 bits | 16 | 64 bits |
+-----+--------------------+--------+-----------------+
|pNLA1| Site ID | SLA ID | Interface ID |
+-----+--------------------+--------+-----------------+
|<-----20-bit pNLA ID----->|
| |
| 8 | 12 bits | 16 | 64 bits |
+-----+--------------------+--------+-----------------+
|pNLA1| Site ID | SLA ID | Interface ID |
+-----+--------------------+--------+-----------------+
Intermediate transit networks (pNLA1's) would assign uniques Site ID's for eachend user site served.
中间交通网络（pNLA1）将为所服务的每个用户站点分配uniques站点ID。
As an example of this, assuming a backbone pTLA of 0x800, no intermediate transit ISP (thus a pNLA1 of 0x00) and a sequential site ID (with start at the right edge numbering) of 0x0001, the routing prefix for the first site would look like:
例如，假设主干pTLA为0x800，没有中间传输ISP（因此pNLA1为0x00）和顺序站点ID（从右边缘开始编号）为0x0001，则第一个站点的路由前缀如下所示：
3FFE:8000:0001/48
6bone _|||| |||| ||||___site
|||| |
b/b site____|||| |
| |
transit________|_|
3FFE:8000:0001/48
6bone _|||| |||| ||||___site
|||| |
b/b site____|||| |
| |
transit________|_|
Another example of this usage, assuming the same backbone pTLA1 of 0x800 and an intermediate transit ISP under it (numbering from the left edge) with an NLA1 of 0x80, and a sequential site ID of 0x0001, the routing prefix for the first site connected would look like:
这种用法的另一个示例是，假设相同的主干pTLA1为0x800，其下有一个中间传输ISP（从左边缘开始编号），NLA1为0x80，顺序站点ID为0x0001，则连接的第一个站点的路由前缀如下所示：
3FFE:0180:0001/48
6bone _|||| |||| ||||___site
||||
b/b site____||||
||
transit_______||
3FFE:0180:0001/48
6bone _|||| |||| ||||___site
||||
b/b site____||||
||
transit_______||
Note 1: the two sites numbered 0x001 in the above examples are really two different sites as their pNLA1 authority above them is different (i.e., in the first case no transit exists thus the site is directly connected to the pTLA backbone ISP, and in the second case the site is directly connected to intermediate transit ISP 0x80).
注1：上述示例中编号为0x001的两个站点实际上是两个不同的站点，因为它们上面的pNLA1权限不同（即，在第一种情况下不存在传输，因此站点直接连接到pTLA主干ISP，在第二种情况下，站点直接连接到中间传输ISP 0x80）。
Note 2: there would be nothing to prevent an pNLA1 transit site from further allocating pNLA's below, but that becomes the policy of the pTLA and pNLA's above them to work out.
注2：不会有任何措施阻止pNLA1过境点进一步分配以下pNLA，但这将成为pTLA和上述pNLA的政策。
Note 3: The 6bone registry, which is a RIPE-style database for documenting IPv6 sites connected to the 6bone, has an "inet6num" object to allow documentation of all IPv6 addresses allocated.
注3:6bone注册表是一个成熟的数据库，用于记录连接到6bone的IPv6站点，它有一个“inet6num”对象，允许记录所有分配的IPv6地址。
IPv6 addressing documents do not have any direct impact on Internet infrastructure security.
IPv6寻址文档对Internet基础设施安全没有任何直接影响。
References
工具书类
[ADDRARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 2373, July 1998.
[ADDRARCH]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 23731998年7月。
[AGGR] Hinden, R., O'Dell, M. and S. Deering, "An IPv6 Aggregatable Global Unicast Address Format", RFC 2374, July 1998.
[AGGR]Hinden，R.，O'Dell，M.和S.Deering，“一种IPv6可聚合全球单播地址格式”，RFC 2374，1998年7月。
[HARDEN] Rockell, R. and R. Fink, "6Bone Backbone Routing Guidelines", RFC 2772, February 2000.
[HARDEN]Rockell，R.和R.Fink，“6Bone主干路由指南”，RFC 27722000年2月。
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[关键词]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[6BONE-TLA] Hinden, R., Fink, R. and J. Postel, "IPv6 Testing Address Allocation", RFC 2471, December 1998.
[6BONE-TLA]Hinden，R.，Fink，R.和J.Postel，“IPv6测试地址分配”，RFC 24711998年12月。
Author's Address
作者地址
Bob Fink, ESnet Lawrence Berkeley National Lab MS 50A-3111 1 Cyclotron Road Berkeley, CA 94720 USA
Bob Fink，ESnet劳伦斯伯克利国家实验室MS 50A-3111美国加利福尼亚州伯克利回旋加速器路1号，邮编94720
Phone: +1 510 486 5692
Fax: +1 510 486 4790
EMail: fink@es.net
Phone: +1 510 486 5692
Fax: +1 510 486 4790
EMail: fink@es.net
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。