Network Working Group                                          G. Huston
Request for Comments: 5398                                 December 2008
Category: Informational
        
Network Working Group                                          G. Huston
Request for Comments: 5398                                 December 2008
Category: Informational
        

Autonomous System (AS) Number Reservation for Documentation Use

自动系统(AS)编号保留供文件使用

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) 2008 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有(c)2008 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.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/ 许可证信息)在本文件发布之日生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。

Abstract

摘要

To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, two blocks of Autonomous System numbers (ASNs) are reserved for use in examples in RFCs, books, documentation, and the like. This document describes the reservation of two blocks of ASNs as reserved numbers for use in documentation.

为了减少将记录的示例与部署的系统关联时发生冲突和混淆的可能性,保留了两个自治系统编号(ASN)块,以便在RFC、书籍、文档等中的示例中使用。本文件描述了两块ASN的保留,作为文件中使用的保留编号。

1. Introduction
1. 介绍

To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, two blocks of Autonomous System numbers (ASNs) are reserved for use in examples in RFCs, books, documentation, and the like. This document describes the reservation of two blocks of ASNs as reserved numbers for use in documentation.

为了减少将记录的示例与部署的系统关联时发生冲突和混淆的可能性,保留了两个自治系统编号(ASN)块,以便在RFC、书籍、文档等中的示例中使用。本文件描述了两块ASN的保留,作为文件中使用的保留编号。

The problems such conflicts may cause have already been encountered with IPv4 addresses where literal use of documented examples in a production environment causes address and routing conflicts with existing services. Since private-use ASNs already have a context of use in deployed networks, these ASNs cannot be used in many example

这些冲突可能导致的问题已经在IPv4地址中遇到,其中在生产环境中使用文档化示例会导致地址和路由与现有服务发生冲突。由于专用ASN已经在部署的网络中具有使用上下文,因此在许多示例中无法使用这些ASN

situations. In making an explicit allocation of a set of AS numbers reserved for documentation use, it is intended that any such operational problems may be avoided in the future.

情况。在明确分配一组保留供文件使用的AS编号时,旨在避免将来出现任何此类操作问题。

Similar considerations have been applied to IPv4 addresses [IANA.IPv4], IPv6 addresses [RFC3849], and domain names [RFC2606], and reservations have been made for similar purposes.

对IPv4地址[IANA.IPv4]、IPv6地址[RFC3849]和域名[RFC2606]也进行了类似的考虑,并为类似目的进行了保留。

2. ASNs for Documentation Use
2. 文件使用ASN

To allow documentation to accurately describe deployment examples, the use of public or private-use AS numbers is inappropriate, and a reserved block of AS numbers is required. This ensures that documentation does not clash with public- or private-use AS numbers in deployed networks, and mitigates the risks to operational integrity of the network through inappropriate use of documentation to perform literal configuration of routing elements on production systems.

为了使文档能够准确地描述部署示例,使用公共或私人AS编号是不合适的,需要保留AS编号块。这确保了文档不会与已部署网络中作为数字的公共或私人用途发生冲突,并通过不适当地使用文档在生产系统上执行路由元素的文字配置来降低网络操作完整性的风险。

To allow for examples relating to the transition to use of 32-bit AS numbers to be correctly described, a reservation of two blocks of AS numbers is proposed in this document. One reserved block of 16 contiguous AS numbers is to lie in the range of numbers that can be expressed as a 16-bit AS number value (i.e., values less than 65536), and a second reserved block of 16 contiguous AS numbers is to lie in the range of numbers that can only be expressed as 32-bit AS numbers (values greater than 65535).

为了正确描述与转换为使用32位AS号有关的示例,本文件建议保留两块AS号。一个16个连续AS数字的保留块位于可表示为16位AS数字值(即,小于65536的值)的数字范围内,另一个16个连续AS数字的保留块位于只能表示为32位AS数字(大于65535的值)的数字范围内。

3. Operational Implications
3. 业务影响

This assignment implies that BGP operational configurations should not peer with neighboring ASes that are numbered from this reserved AS number set.

此分配意味着BGP操作配置不应与从该保留编号集编号的相邻ASE对等。

4. IANA Considerations
4. IANA考虑

IANA has reserved a contiguous block of 16 Autonomous System numbers from the unallocated number range within the "16-bit" number set for documentation purposes, namely 64496 - 64511, and a contiguous block of 16 Autonomous System numbers from the "32-bit" number set for documentation, namely 65536 - 65551. These reservations have been documented in the IANA AS Number Registry [IANA.AS].

IANA已在用于文档编制的“16位”数字集(即64496-64511)内保留了来自未分配数字范围的16个自治系统数字的连续块,以及用于文档编制的“32位”数字集(即65536-65551)的16个自治系统数字的连续块。这些保留已记录在IANA AS编号登记处[IANA.AS]。

5. Security Considerations
5. 安全考虑

AS number reservations do not have any direct impact on Internet infrastructure security.

因为数量保留对互联网基础设施安全没有任何直接影响。

6. Acknowledgements
6. 致谢

The author acknowledges the work of Tomoya Yoshida, Gaurab Upadhaya, and Philip Smith in authoring a policy proposal that was submitted to the APNIC Policy Process in 2008 relating to the reservation of AS numbers for documentation purposes.

作者感谢Tomoya Yoshida、Gaurab Upadhaya和Philip Smith在编写政策提案方面所做的工作,该提案于2008年提交给APNIC政策流程,涉及保留AS编号以供记录之用。

7. Informative References
7. 资料性引用

[IANA.AS] IANA, "Autonomous System (AS) Numbers", Sep 2008, <http://www.iana.org>.

[IANA.AS]IANA,“自主系统(AS)编号”,2008年9月<http://www.iana.org>.

[IANA.IPv4] IANA, "IPv4 Global Unicast Address Assignments", Sep 2008, <http://www.iana.org>.

[IANA.IPv4]IANA,“IPv4全球单播地址分配”,2008年9月<http://www.iana.org>.

[RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", BCP 32, RFC 2606, June 1999.

[RFC2606]Eastlake,D.和A.Panitz,“保留顶级DNS名称”,BCP 32,RFC 26061999年6月。

[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004.

[RFC3849]Huston,G.,Lord,A.,和P.Smith,“为文档保留IPv6地址前缀”,RFC 3849,2004年7月。

Author's Address

作者地址

Geoff Huston

休斯顿

   EMail: gih@apnic.net
        
   EMail: gih@apnic.net