Network Working Group M. Daniele
Request for Comments: 3419 Consultant
Category: Standards Track J. Schoenwaelder
TU Braunschweig
December 2002
Network Working Group M. Daniele
Request for Comments: 3419 Consultant
Category: Standards Track J. Schoenwaelder
TU Braunschweig
December 2002
Textual Conventions for Transport Addresses
传输地址的文本约定
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This document introduces a Management Information Base (MIB) module that defines textual conventions to represent commonly used transport-layer addressing information. The definitions are compatible with the concept of TAddress/TDomain pairs introduced by the Structure of Management Information version 2 (SMIv2) and support the Internet transport protocols over IPv4 and IPv6.
本文档介绍一个管理信息库（MIB）模块，该模块定义文本约定来表示常用的传输层寻址信息。这些定义与管理信息结构版本2（SMIv2）引入的TadAddress/TdDomain对概念兼容，并支持IPv4和IPv6上的Internet传输协议。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 2
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 Relationship to Other MIBs . . . . . . . . . . . . . . . . . 4
3.1.1 SNMPv2-TC (TAddress, TDomain) . . . . . . . . . . . . . . . 4
3.1.2 SNMPv2-TM . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.3 INET-ADDRESS-MIB (InetAddressType, InetAddress) . . . . . . 5
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . 15
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 15
8. Intellectual Property Notice . . . . . . . . . . . . . . . . 15
Normative References . . . . . . . . . . . . . . . . . . . . 16
Informative References . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 17
Full Copyright Statement . . . . . . . . . . . . . . . . . . 18
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 2
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 Relationship to Other MIBs . . . . . . . . . . . . . . . . . 4
3.1.1 SNMPv2-TC (TAddress, TDomain) . . . . . . . . . . . . . . . 4
3.1.2 SNMPv2-TM . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.3 INET-ADDRESS-MIB (InetAddressType, InetAddress) . . . . . . 5
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . 15
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 15
8. Intellectual Property Notice . . . . . . . . . . . . . . . . 15
Normative References . . . . . . . . . . . . . . . . . . . . 16
Informative References . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 17
Full Copyright Statement . . . . . . . . . . . . . . . . . . 18
Several MIB modules need to represent transport-layer addresses in a generic way. Typical examples are MIBs for application protocols that can operate over several different transports or application management MIBs that need to model generic communication endpoints.
几个MIB模块需要以通用方式表示传输层地址。典型的例子是应用程序协议的MIB，它们可以在多个不同的传输上运行，或者是需要对通用通信端点建模的应用程序管理MIB。
The SMIv2 in STD 58, RFC 2579 [RFC2579] defines the textual conventions TDomain and TAddress to represent generic transport layer endpoints. A generic TAddress value is interpreted in a given transport domain which is identified by a TDomain value. The TDomain is an object identifier which allows MIB authors to extend the set of supported transport domains by providing suitable definitions in standardized or enterprise specific MIB modules.
STD 58、RFC 2579[RFC2579]中的SMIv2定义了文本约定TDomain和TAddress，以表示通用传输层端点。通用TAddress值在给定的传输域中进行解释，该传输域由TDomain值标识。TDomain是一个对象标识符，它允许MIB作者通过在标准化或特定于企业的MIB模块中提供合适的定义来扩展受支持的传输域集。
An initial set of TDomain values and concrete TAddress formats has been standardized in STD 62, RFC 3417 [RFC3417]. These definitions are however mixed up with SNMP semantics. Furthermore, definitions for Internet transport protocols over IPv4 and IPv6 are missing.
STD 62、RFC 3417[RFC3417]标准化了TDomain值和具体TAddress格式的初始设置。但是，这些定义与SNMP语义混淆在一起。此外，缺少IPv4和IPv6上的Internet传输协议的定义。
The purpose of this memo is to introduce a set of well-known textual conventions to represent commonly used transport-layer addressing information which is compatible with the original TDomain and TAddress approach and which includes definitions for additional Internet transport protocols over IPv4 and IPv6. This memo also introduces a new textual convention which enumerates the well-known transport domains since such an enumeration provides in many cases sufficient flexibility and is more efficient compared to object identifiers.
本备忘录的目的是介绍一组众所周知的文本约定，以表示常用的传输层寻址信息，该信息与原始的TDomain和TadAddress方法兼容，并包括IPv4和IPv6上附加Internet传输协议的定义。本备忘录还引入了一种新的文本约定，该约定枚举了众所周知的传输域，因为这种枚举在许多情况下提供了足够的灵活性，并且与对象标识符相比效率更高。
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT" and "MAY" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“应该”、“不应该”和“可能”应按照BCP 14、RFC 2119[RFC2119]中的说明进行解释。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This MIB module contains definitions for commonly used transport layer addressing information. In particular, it provides the following definitions:
此MIB模块包含常用传输层寻址信息的定义。特别是，它提供了以下定义：
1. Textual conventions for generic transport addresses (TransportAddress) and generic transport domains (TransportDomain).
1. 通用传输地址（TransportAddress）和通用传输域（TransportDomain）的文本约定。
2. Object identifier registrations for well-known transport domains.
2. 已知传输域的对象标识符注册。
3. An enumeration of the well-known transport domains, called a transport address type (TransportAddressType).
3. 已知传输域的枚举，称为传输地址类型（TransportAddressType）。
4. A set of textual conventions for the address formats used by well-known transport domains. The DISPLAY-HINTs are aligned with the formats used in URIs [RFC2396], [RFC3291].
4. 著名传输域使用的地址格式的一组文本约定。显示提示与URI[RFC2396]、[RFC3291]中使用的格式一致。
The textual conventions for well-known transport domains support scoped Internet addresses. The scope of an Internet address is a topological span within which the address may be used as a unique identifier for an interface or set of interfaces. A scope zone, or simply a zone, is a concrete connected region of topology of a given scope. Note that a zone is a particular instance of a topological region, whereas a scope is the size of a topological region [SCOPED]. Since Internet addresses on devices that connect multiple zones are not necessarily unique, an additional zone index is needed on these devices to select an interface. The textual conventions TransportAddressIPv4z and TransportAddressIPv6z are provided to support Internet transport addresses that include a zone index. In order to support arbitrary combinations of scoped Internet transport addresses, MIB authors SHOULD use a separate TransportDomain or TransportAddressType objects for each TransportAddress object.
众所周知的传输域的文本约定支持作用域的Internet地址。Internet地址的范围是一个拓扑范围，在此范围内，地址可以用作接口或接口集的唯一标识符。作用域区域，或简称为区域，是给定作用域拓扑的具体连接区域。请注意，分区是拓扑区域的特定实例，而范围是拓扑区域的大小[SCOPED]。由于连接多个区域的设备上的Internet地址不一定是唯一的，因此这些设备上需要额外的区域索引来选择接口。提供文本约定TransportAddressIPv4z和TransportAddressIPv6z以支持包含区域索引的Internet传输地址。为了支持作用域Internet传输地址的任意组合，MIB作者应该为每个TransportAddress对象使用单独的TransportDomain或TransportAddressType对象。
There are two different ways how new transport domains and textual conventions for the address formats used by those new transport domains can be defined.
有两种不同的方式可以定义新的传输域和这些新传输域使用的地址格式的文本约定。
1. The MIB module contained in this memo can be updated and new constants for the TransportDomain and the TransportAddressType enumeration can be assigned.
1. 可以更新此备忘录中包含的MIB模块，并为TransportDomain和TransportAddressType枚举分配新常量。
2. Other MIB modules may define additional transport domains and associated textual conventions. Such an extension can not update the TransportAddressType enumeration.
2. 其他MIB模块可以定义额外的传输域和相关的文本约定。此类扩展无法更新TransportAddressType枚举。
It is therefore a MIB designers choice whether he uses (a) a more compact TransportAddressType object with limited extensibility or (b) a more verbose TransportDomain object which allows arbitrary extensions in other MIB modules.
因此，MIB设计者可以选择使用（a）更紧凑的可扩展性有限的TransportAddressType对象，还是（b）更详细的TransportDomain对象，允许在其他MIB模块中进行任意扩展。
The MIB module contained in this memo does NOT define the transport mappings of any particular protocol. Rather, it defines a set of common identifiers and textual conventions that are intended to be used within various transport mappings documents.
此备忘录中包含的MIB模块未定义任何特定协议的传输映射。相反，它定义了一组公共标识符和文本约定，用于各种传输映射文档中。
This section discusses how the definitions provided by the MIB module contained in this memo relate to definitions in other MIB modules.
本节讨论本备忘录中包含的MIB模块提供的定义与其他MIB模块中的定义之间的关系。
The SNMPv2-TC MIB module [RFC2579] defines the textual conventions TAddress and TDomain to represent generic transport addresses.
SNMPv2 TC MIB模块[RFC2579]定义文本约定TAddress和TDomain以表示通用传输地址。
A TAddress is an octet string with a size between 1 and 255 octets. Experience has shown that there is sometimes a need to represent unknown transport addresses. The MIB module contained in this memo therefore introduces a new textual convention TransportAddress which is an octet string with a size between 0 and 255 octets and otherwise identical semantics. In other words, the sub-type TransportAddress (SIZE (1..255)) is identical with the TAddress defined in the SNMPv2-TC MIB module [RFC2579].
TAddress是一个八位字节字符串，大小介于1到255个八位字节之间。经验表明，有时需要表示未知的传输地址。因此，本备忘录中包含的MIB模块引入了一个新的文本约定TransportAddress，它是一个大小在0到255个八位字节之间的八位字节字符串，语义相同。换句话说，子类型TransportAddress（大小（1..255））与SNMPv2 TC MIB模块[RFC2579]中定义的地址相同。
This MIB module also introduces a new textual convention TransportDomain which is compatible with the TDomain definition so that a complete set of definitions is contained in a single MIB module. New MIB modules SHOULD use the generic TransportDomain, TransportAddressType and TransportAddress definitions defined in this memo. Existing MIB modules may be updated to use the definitions provided in this memo by replacing TDomain with TransportDomain and TAddress with TransportAddress (SIZE (1..255)).
这个MIB模块还引入了一个新的文本约定TransportDomain，它与TDomain定义兼容，因此一个完整的定义集包含在单个MIB模块中。新的MIB模块应使用本备忘录中定义的通用TransportDomain、TransportAddressType和TransportAddress定义。通过用TransportDomain替换TDomain，用TransportAddress（大小（1..255））替换TadAddress，可以更新现有MIB模块，以使用本备忘录中提供的定义。
The transport domain values defined in the SNMPv2-TM MIB module [RFC3417] all contain "snmp" as the prefix in their name and are registered under `snmpDomains' (from RFC 2578 [RFC2578]). They were originally intended to describe SNMP transport domains only - but they were later also used for non-SNMP transport endpoints. These definitions are also incomplete since new transport address domains are needed to support (at least) SNMP over UDP over IPv6.
SNMPv2 TM MIB模块[RFC3417]中定义的传输域值均包含“snmp”作为其名称中的前缀，并在“snmpDomains”下注册（来自RFC 2578[RFC2578]）。它们最初仅用于描述SNMP传输域，但后来也用于非SNMP传输端点。这些定义也不完整，因为需要新的传输地址域来支持（至少）IPv6上UDP上的SNMP。
The transport domain values defined in this memo are independent of the protocol running over the transport-layer and SHOULD be used for all transport endpoints not carrying SNMP traffic. Programs that interpret transport domain values should in addition accept the transport domain values defined in the SNMPv2-TM MIB module in order to provide interoperability with existing implementations that use the SNMP specific transport domain values.
此备忘录中定义的传输域值独立于在传输层上运行的协议，应用于所有不承载SNMP流量的传输端点。此外，解释传输域值的程序还应接受SNMPv2 TM MIB模块中定义的传输域值，以便提供与使用SNMP特定传输域值的现有实现的互操作性。
Transport endpoints which carry SNMP traffic SHOULD continue to use the definitions from the SNMPv2-TM MIB module where applicable. They SHOULD use the transport domain values defined in this memo for SNMP transports not defined in the SNMPv2-TM MIB module, such as SNMP over UDP over IPv6. Programs that interpret transport domain values should in addition accept all the transport domain values defined in this memo in order to provide interoperability in cases where it is not possible or desirable to distinguish the protocols running over a transport endpoint.
携带SNMP通信的传输端点应继续使用SNMPv2 TM MIB模块中的定义（如适用）。对于SNMPv2 TM MIB模块中未定义的SNMP传输，他们应使用此备忘录中定义的传输域值，例如IPv6上UDP上的SNMP。此外，解释传输域值的程序还应接受本备忘录中定义的所有传输域值，以便在无法或不希望区分在传输端点上运行的协议的情况下提供互操作性。
The INET-ADDRESS-MIB MIB module [RFC3291] defines the textual conventions InetAddressType and InetAddress to represent Internet network layer endpoints. Some MIB modules use these textual conventions in conjunction with the InetPortNumber textual convention to represent Internet transport-layer endpoints. This approach is fine as long as a MIB models protocols or applications that are specific to the Internet suite of transport protocols. For protocols or applications that can potentially use other transport protocols, the use of the definitions contained in this memo is more appropriate.
INET-ADDRESS-MIB MIB模块[RFC3291]定义文本约定InetAddressType和InetAddress，以表示Internet网络层端点。一些MIB模块将这些文本约定与InetPortNumber文本约定结合使用，以表示Internet传输层端点。只要MIB为特定于Internet传输协议套件的协议或应用程序建模，这种方法就可以了。对于可能使用其他传输协议的协议或应用程序，使用本备忘录中包含的定义更为合适。
TRANSPORT-ADDRESS-MIB DEFINITIONS ::= BEGIN
TRANSPORT-ADDRESS-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC;
从SNMPv2 TC导入SNMPv2 SMI文本约定中的模块标识、对象标识、mib-2；
transportAddressMIB MODULE-IDENTITY LAST-UPDATED "200211010000Z" ORGANIZATION "IETF Operations and Management Area" CONTACT-INFO "Juergen Schoenwaelder (Editor) TU Braunschweig Bueltenweg 74/75 38106 Braunschweig, Germany
transportAddressMIB模块标识最新更新的“2002110100000Z”组织“IETF运行和管理区域”联系方式“Juergen Schoenwaeld（编辑）TU Braunchweig Bueltenweg 74/75 38106 Braunchweig，Germany
Phone: +49 531 391-3289
EMail: schoenw@ibr.cs.tu-bs.de
Phone: +49 531 391-3289
EMail: schoenw@ibr.cs.tu-bs.de
Send comments to <mibs@ops.ietf.org>." DESCRIPTION "This MIB module provides commonly used transport address definitions.
将评论发送到<mibs@ops.ietf.org>“说明”此MIB模块提供常用的传输地址定义。
Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3419; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2002年）。此版本的MIB模块是RFC 3419的一部分；有关完整的法律通知，请参见RFC本身。”
-- Revision log
--修订日志
REVISION "200211010000Z"
DESCRIPTION
"Initial version, published as RFC 3419."
::= { mib-2 100 }
REVISION "200211010000Z"
DESCRIPTION
"Initial version, published as RFC 3419."
::= { mib-2 100 }
transportDomains OBJECT IDENTIFIER ::= { transportAddressMIB 1 }
transportDomains OBJECT IDENTIFIER ::= { transportAddressMIB 1 }
transportDomainUdpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4 for
global IPv4 addresses."
::= { transportDomains 1 }
transportDomainUdpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4 for
global IPv4 addresses."
::= { transportDomains 1 }
transportDomainUdpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6 for
global IPv6 addresses."
::= { transportDomains 2 }
transportDomainUdpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6 for
global IPv6 addresses."
::= { transportDomains 2 }
transportDomainUdpIpv4z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4z for
scoped IPv4 addresses with a zone index."
::= { transportDomains 3 }
transportDomainUdpIpv4z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4z for
scoped IPv4 addresses with a zone index."
::= { transportDomains 3 }
transportDomainUdpIpv6z OBJECT-IDENTITY STATUS current
TransportDomainUdpiv6z对象标识状态当前
DESCRIPTION
"The UDP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6z for
scoped IPv6 addresses with a zone index."
::= { transportDomains 4 }
DESCRIPTION
"The UDP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6z for
scoped IPv6 addresses with a zone index."
::= { transportDomains 4 }
transportDomainTcpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4 for
global IPv4 addresses."
::= { transportDomains 5 }
transportDomainTcpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4 for
global IPv4 addresses."
::= { transportDomains 5 }
transportDomainTcpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6 for
global IPv6 addresses."
::= { transportDomains 6 }
transportDomainTcpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6 for
global IPv6 addresses."
::= { transportDomains 6 }
transportDomainTcpIpv4z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4z for
scoped IPv4 addresses with a zone index."
::= { transportDomains 7 }
transportDomainTcpIpv4z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4z for
scoped IPv4 addresses with a zone index."
::= { transportDomains 7 }
transportDomainTcpIpv6z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6z for
scoped IPv6 addresses with a zone index."
::= { transportDomains 8 }
transportDomainTcpIpv6z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6z for
scoped IPv6 addresses with a zone index."
::= { transportDomains 8 }
transportDomainSctpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4 for
global IPv4 addresses. This transport domain usually
represents the primary address on multihomed SCTP
endpoints."
::= { transportDomains 9 }
transportDomainSctpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4 for
global IPv4 addresses. This transport domain usually
represents the primary address on multihomed SCTP
endpoints."
::= { transportDomains 9 }
transportDomainSctpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6 for
global IPv6 addresses. This transport domain usually
represents the primary address on multihomed SCTP
endpoints."
::= { transportDomains 10 }
transportDomainSctpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6 for
global IPv6 addresses. This transport domain usually
represents the primary address on multihomed SCTP
endpoints."
::= { transportDomains 10 }
transportDomainSctpIpv4z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4z for
scoped IPv4 addresses with a zone index. This transport
domain usually represents the primary address on
multihomed SCTP endpoints."
::= { transportDomains 11 }
transportDomainSctpIpv4z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv4 transport domain. The corresponding
transport address is of type TransportAddressIPv4z for
scoped IPv4 addresses with a zone index. This transport
domain usually represents the primary address on
multihomed SCTP endpoints."
::= { transportDomains 11 }
transportDomainSctpIpv6z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6z for
scoped IPv6 addresses with a zone index. This transport
domain usually represents the primary address on
multihomed SCTP endpoints."
::= { transportDomains 12 }
transportDomainSctpIpv6z OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv6 transport domain. The corresponding
transport address is of type TransportAddressIPv6z for
scoped IPv6 addresses with a zone index. This transport
domain usually represents the primary address on
multihomed SCTP endpoints."
::= { transportDomains 12 }
transportDomainLocal OBJECT-IDENTITY STATUS current DESCRIPTION "The Posix Local IPC transport domain. The corresponding transport address is of type TransportAddressLocal.
transportDomainLocal对象标识状态当前描述“Posix本地IPC传输域。相应的传输地址类型为TransportAddressLocal。
The Posix Local IPC transport domain incorporates the
well-known UNIX domain sockets."
::= { transportDomains 13 }
The Posix Local IPC transport domain incorporates the
well-known UNIX domain sockets."
::= { transportDomains 13 }
transportDomainUdpDns OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP transport domain using fully qualified domain
names. The corresponding transport address is of type
TransportAddressDns."
::= { transportDomains 14 }
transportDomainUdpDns OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP transport domain using fully qualified domain
names. The corresponding transport address is of type
TransportAddressDns."
::= { transportDomains 14 }
transportDomainTcpDns OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP transport domain using fully qualified domain
names. The corresponding transport address is of type
TransportAddressDns."
::= { transportDomains 15 }
transportDomainTcpDns OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP transport domain using fully qualified domain
names. The corresponding transport address is of type
TransportAddressDns."
::= { transportDomains 15 }
transportDomainSctpDns OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP transport domain using fully qualified domain
names. The corresponding transport address is of type
TransportAddressDns."
::= { transportDomains 16 }
transportDomainSctpDns OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP transport domain using fully qualified domain
names. The corresponding transport address is of type
TransportAddressDns."
::= { transportDomains 16 }
TransportDomain ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a transport domain.
TransportDomain ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a transport domain.
Some possible values, such as transportDomainUdpIpv4, are defined in this module. Other possible values can be defined in other MIB modules." SYNTAX OBJECT IDENTIFIER
此模块中定义了一些可能的值，如transportDomainUdpIpv4。其他可能的值可以在其他MIB模块中定义。”语法对象标识符
--
-- The enumerated values of the textual convention below should
-- be identical to the last sub-identifier of the OID registered
-- for the same domain.
--
--
-- The enumerated values of the textual convention below should
-- be identical to the last sub-identifier of the OID registered
-- for the same domain.
--
TransportAddressType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a transport domain. This is the
enumerated version of the transport domain registrations
in this MIB module. The enumerated values have the
following meaning:
TransportAddressType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a transport domain. This is the
enumerated version of the transport domain registrations
in this MIB module. The enumerated values have the
following meaning:
unknown(0) unknown transport address type udpIpv4(1) transportDomainUdpIpv4 udpIpv6(2) transportDomainUdpIpv6 udpIpv4z(3) transportDomainUdpIpv4z udpIpv6z(4) transportDomainUdpIpv6z tcpIpv4(5) transportDomainTcpIpv4 tcpIpv6(6) transportDomainTcpIpv6 tcpIpv4z(7) transportDomainTcpIpv4z
未知（0）未知传输地址类型udpIpv4（1）传输域udpIpv4 udpIpv6（2）传输域udpIpv6 udpIpv4z（3）传输域udpIpv4z udpIpv6z（4）传输域udpIpv6z tcpIpv4（5）传输域cpipv4 tcpIpv6 tcpIpv6 tcpIpv4z（7）传输域cpipv4z
tcpIpv6z(8) transportDomainTcpIpv6z sctpIpv4(9) transportDomainSctpIpv4 sctpIpv6(10) transportDomainSctpIpv6 sctpIpv4z(11) transportDomainSctpIpv4z sctpIpv6z(12) transportDomainSctpIpv6z local(13) transportDomainLocal udpDns(14) transportDomainUdpDns tcpDns(15) transportDomainTcpDns sctpDns(16) transportDomainSctpDns
tcpIpv6z（8）TransportDomainCpipv6z sctpIpv4（9）transportDomainSctpIpv4 sctpIpv6（10）transportDomainSctpIpv6 sctpIpv4z（11）transportDomainSctpIpv4z sctpIpv6z（12）transportDomainSctpIpv6z本地（13）transportDomainLocal udpDns（14）transportDomainUdpDns tcpDns（15）TransportDomainCPDNS sctpDns（16）transportDomainSctpDns
This textual convention can be used to represent transport domains in situations where a syntax of TransportDomain is unwieldy (for example, when used as an index).
此文本约定可用于在TransportDomain语法难以理解的情况下表示传输域（例如，当用作索引时）。
The usage of this textual convention implies that additional
transport domains can only be supported by updating this MIB
module. This extensibility restriction does not apply for the
TransportDomain textual convention which allows MIB authors
to define additional transport domains independently in
other MIB modules."
SYNTAX INTEGER {
unknown(0),
udpIpv4(1),
udpIpv6(2),
udpIpv4z(3),
udpIpv6z(4),
tcpIpv4(5),
tcpIpv6(6),
tcpIpv4z(7),
tcpIpv6z(8),
sctpIpv4(9),
sctpIpv6(10),
sctpIpv4z(11),
sctpIpv6z(12),
local(13),
udpDns(14),
tcpDns(15),
sctpDns(16)
}
The usage of this textual convention implies that additional
transport domains can only be supported by updating this MIB
module. This extensibility restriction does not apply for the
TransportDomain textual convention which allows MIB authors
to define additional transport domains independently in
other MIB modules."
SYNTAX INTEGER {
unknown(0),
udpIpv4(1),
udpIpv6(2),
udpIpv4z(3),
udpIpv6z(4),
tcpIpv4(5),
tcpIpv6(6),
tcpIpv4z(7),
tcpIpv6z(8),
sctpIpv4(9),
sctpIpv6(10),
sctpIpv4z(11),
sctpIpv6z(12),
local(13),
udpDns(14),
tcpDns(15),
sctpDns(16)
}
TransportAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a generic transport address.
TransportAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a generic transport address.
A TransportAddress value is always interpreted within the context of a TransportAddressType or TransportDomain value. Every usage of the TransportAddress textual convention MUST
TransportAddress值始终在TransportAddressType或TransportDomain值的上下文中进行解释。TransportAddress文本约定的每次使用都必须
specify the TransportAddressType or TransportDomain object which provides the context. Furthermore, MIB authors SHOULD define a separate TransportAddressType or TransportDomain object for each TransportAddress object. It is suggested that the TransportAddressType or TransportDomain is logically registered before the object(s) which use the TransportAddress textual convention if they appear in the same logical row.
指定提供上下文的TransportAddressType或TransportDomain对象。此外，MIB作者应该为每个TransportAddress对象定义一个单独的TransportAddressType或TransportDomain对象。建议TransportAddressType或TransportDomain在逻辑上注册在使用TransportAddress文本约定的对象之前，如果它们出现在同一逻辑行中。
The value of a TransportAddress object must always be consistent with the value of the associated TransportAddressType or TransportDomain object. Attempts to set a TransportAddress object to a value which is inconsistent with the associated TransportAddressType or TransportDomain must fail with an inconsistentValue error.
TransportAddress对象的值必须始终与关联的TransportAddressType或TransportDomain对象的值一致。尝试将TransportAddress对象设置为与关联的TransportAddressType或TransportDomain不一致的值必须失败，并出现不一致值错误。
When this textual convention is used as a syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the OBJECT-TYPE declaration MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers." SYNTAX OCTET STRING (SIZE (0..255))
当此文本约定用作索引对象的语法时，SMIv2，STD 58中指定的128个子标识符的限制可能存在问题。在这种情况下，对象类型声明必须包含一个“SIZE”子句，以限制潜在实例子标识符的数量
TransportAddressIPv4 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv4
address and a port number (as used for example by UDP,
TCP and SCTP):
TransportAddressIPv4 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv4
address and a port number (as used for example by UDP,
TCP and SCTP):
octets contents encoding 1-4 IPv4 address network-byte order 5-6 port number network-byte order
八位字节内容编码1-4 IPv4地址网络字节顺序5-6端口号网络字节顺序
This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair." SYNTAX OCTET STRING (SIZE (6))
此文本约定不应直接用于对象定义，因为它将地址限制为特定格式。但是，如果使用它，它可以单独使用，也可以与TransportAddressType或TransportDomain成对使用
TransportAddressIPv6 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x]0a:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv6
address and a port number (as used for example by UDP,
TransportAddressIPv6 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x]0a:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv6
address and a port number (as used for example by UDP,
TCP and SCTP):
TCP和SCTP）：
octets contents encoding 1-16 IPv6 address network-byte order 17-18 port number network-byte order
八位字节内容编码1-16 IPv6地址网络字节顺序17-18端口号网络字节顺序
This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair." SYNTAX OCTET STRING (SIZE (18))
此文本约定不应直接用于对象定义，因为它将地址限制为特定格式。但是，如果使用它，它可以单独使用，也可以与TransportAddressType或TransportDomain成对使用
TransportAddressIPv4z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d%4d:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv4
address, a zone index and a port number (as used for
example by UDP, TCP and SCTP):
TransportAddressIPv4z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d%4d:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv4
address, a zone index and a port number (as used for
example by UDP, TCP and SCTP):
octets contents encoding 1-4 IPv4 address network-byte order 5-8 zone index network-byte order 9-10 port number network-byte order
八位字节内容编码1-4 IPv4地址网络字节顺序5-8区域索引网络字节顺序9-10端口号网络字节顺序
This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair." SYNTAX OCTET STRING (SIZE (10))
此文本约定不应直接用于对象定义，因为它将地址限制为特定格式。但是，如果使用它，它可以单独使用，也可以与TransportAddressType或TransportDomain成对使用
TransportAddressIPv6z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x%4d]0a:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv6
address, a zone index and a port number (as used for
example by UDP, TCP and SCTP):
TransportAddressIPv6z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x%4d]0a:2d"
STATUS current
DESCRIPTION
"Represents a transport address consisting of an IPv6
address, a zone index and a port number (as used for
example by UDP, TCP and SCTP):
octets contents encoding 1-16 IPv6 address network-byte order 17-20 zone index network-byte order 21-22 port number network-byte order
八位字节内容编码1-16 IPv6地址网络字节顺序17-20区域索引网络字节顺序21-22端口号网络字节顺序
This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format.
此文本约定不应直接用于对象定义，因为它将地址限制为特定格式。
However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair." SYNTAX OCTET STRING (SIZE (22))
但是，如果使用它，它可以单独使用，也可以与TransportAddressType或TransportDomain成对使用
TransportAddressLocal ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1a"
STATUS current
DESCRIPTION
"Represents a POSIX Local IPC transport address:
TransportAddressLocal ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1a"
STATUS current
DESCRIPTION
"Represents a POSIX Local IPC transport address:
octets contents encoding all POSIX Local IPC address string
编码所有POSIX本地IPC地址字符串的八位字节内容
The Posix Local IPC transport domain subsumes UNIX domain sockets.
Posix本地IPC传输域包含UNIX域套接字。
This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair.
此文本约定不应直接用于对象定义，因为它将地址限制为特定格式。但是，如果使用，它可以单独使用，也可以与TransportAddressType或TransportDomain成对使用。
When this textual convention is used as a syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the OBJECT-TYPE declaration MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers." REFERENCE "Protocol Independent Interfaces (IEEE POSIX 1003.1g)" SYNTAX OCTET STRING (SIZE (1..255))
当此文本约定用作索引对象的语法时，SMIv2，STD 58中指定的128个子标识符的限制可能存在问题。在这种情况下，对象类型声明必须包含一个“SIZE”子句，以限制潜在实例子标识符的数量。“REFERENCE”协议独立接口（IEEE POSIX 1003.1g）“语法八位字节字符串（SIZE（1..255））
TransportAddressDns ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1a"
STATUS current
DESCRIPTION
"Represents a DNS domain name followed by a colon ':'
(ASCII character 0x3A) and a port number in ASCII.
The name SHOULD be fully qualified whenever possible.
TransportAddressDns ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1a"
STATUS current
DESCRIPTION
"Represents a DNS domain name followed by a colon ':'
(ASCII character 0x3A) and a port number in ASCII.
The name SHOULD be fully qualified whenever possible.
Values of this textual convention are not directly useable as transport-layer addressing information, and require runtime resolution. As such, applications that write them must be prepared for handling errors if such values are not supported, or cannot be resolved (if resolution occurs at the time of the management operation).
此文本约定的值不能直接用作传输层寻址信息，需要运行时解析。因此，如果这些值不受支持或无法解析（如果在管理操作时发生解析），则编写这些值的应用程序必须准备好处理错误。
The DESCRIPTION clause of TransportAddress objects that may
TransportAddress对象的DESCRIPTION子句，可以
have TransportAddressDns values must fully describe how (and when) such names are to be resolved to IP addresses and vice versa.
have TransportAddressDns值必须完全描述如何（以及何时）将此类名称解析为IP地址，反之亦然。
This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair.
此文本约定不应直接用于对象定义，因为它将地址限制为特定格式。但是，如果使用，它可以单独使用，也可以与TransportAddressType或TransportDomain成对使用。
When this textual convention is used as a syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the OBJECT-TYPE declaration MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers." SYNTAX OCTET STRING (SIZE (1..255))
当此文本约定用作索引对象的语法时，SMIv2，STD 58中指定的128个子标识符的限制可能存在问题。在这种情况下，对象类型声明必须包含一个“SIZE”子句，以限制潜在实例子标识符的数量
END
终止
This section shows some examples how transport addresses are encoded and rendered using some of the transport address definitions.
本节显示了一些示例，说明如何使用一些传输地址定义对传输地址进行编码和呈现。
Description: Unspecified IPv4 address on port 80. Encoding (hex): 000000000050 Display: 0.0.0.0:80
描述：端口80上未指定IPv4地址。编码（十六进制）：0000000000 50显示：0.0.0.0:80
Description: Global IPv4 address on port 80. Encoding (hex): 86A922010050 Display: 134.169.34.1:80
描述：端口80上的全局IPv4地址。编码（十六进制）：86A922010050显示：134.169.34.1:80
Description: Unspecified IPv6 address on port 80.
Encoding (hex): 000000000000000000000000000000000050
Display: [0:0:0:0:0:0:0:0]:80
Description: Unspecified IPv6 address on port 80.
Encoding (hex): 000000000000000000000000000000000050
Display: [0:0:0:0:0:0:0:0]:80
Description: Global IPv6 address on port 80.
Encoding (hex): 108000000000000000080800200C417A0050
Display: [1080:0:0:0:8:800:200C:417A]:80
Description: Global IPv6 address on port 80.
Encoding (hex): 108000000000000000080800200C417A0050
Display: [1080:0:0:0:8:800:200C:417A]:80
Description: Link-local IPv6 address with zone-index 42 on port 80.
Encoding (hex): FE8000000000000000010000000002000000002A0050
Display: [FE80:0:0:0:1:0:0:200%42]:80
Description: Link-local IPv6 address with zone-index 42 on port 80.
Encoding (hex): FE8000000000000000010000000002000000002A0050
Display: [FE80:0:0:0:1:0:0:200%42]:80
Description: Posix Local IPC address (UNIX domain).
Encoding (hex): 2F7661722F6167656E74782F6D6173746572
Display: /var/agentx/master
Description: Posix Local IPC address (UNIX domain).
Encoding (hex): 2F7661722F6167656E74782F6D6173746572
Display: /var/agentx/master
Description: Fully qualified domain name on port 80. Encoding (hex): 7777772E6578616D706C652E6E65743A3830 Display: www.example.net:80
描述：端口80上的完全限定域名。编码（十六进制）：777777 2E6578616D706C652E6E65743A3830显示：www.example.net:80
The MIB module contained in this memo does not define any management objects. Instead, it defines a set of textual conventions which may be used by other MIB modules to define management objects.
此备忘录中包含的MIB模块未定义任何管理对象。相反，它定义了一组文本约定，其他MIB模块可以使用这些文本约定来定义管理对象。
Meaningful security considerations can only be written for MIB modules that define concrete management objects. This document has therefore no impact on the security of the Internet.
只有为定义具体管理对象的MIB模块编写有意义的安全注意事项。因此，本文件对互联网的安全没有影响。
This document was produced by the Operations and Management Area "IPv6MIB" design team. The authors would like to thank Mark Ellison, Brian Haberman, Mike Heard, Glenn Mansfield Keeni, Erik Nordmark, Shawn A. Routhier, Bill Strahm, Dave Thaler and Bert Wijnen for their comments and suggestions.
本文件由运营和管理区域“IPv6MIB”设计团队编制。作者要感谢马克·埃里森、布赖恩·哈伯曼、迈克·赫德、格伦·曼斯菲尔德·基尼、埃里克·诺德马克、肖恩·劳希尔、比尔·斯特拉姆、戴夫·泰勒和伯特·维恩的评论和建议。
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
Normative References
规范性引用文件
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3417] Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3417, December 2002.
[RFC3417]Presohn，R.，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMP）的传输映射”，STD 62，RFC 34172002年12月。
Informative References
资料性引用
[SCOPED] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, A. and B. Zill, "IPv6 Scoped Address Architecture", Work in Progress.
[范围]Deering，S.，Haberman，B.，Jinmei，T.，Nordmark，E.，Onoe，A.和B.Zill，“IPv6范围地址体系结构”，正在进行中。
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RFC2396]Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。
[RFC2732] Hinden, R., Carpenter, B. and L. Masinter, "Format for Literal IPv6 Addresses in URL's", RFC 2732, August 1998.
[RFC2732]Hinden，R.，Carpenter，B.和L.Masinter，“URL中文字IPv6地址的格式”，RFC 2732，1998年8月。
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 3291, December 2001.
[RFC3291]Daniele，M.，Haberman，B.，Routhier，S.和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 3291，2001年12月。
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
Authors' Addresses
作者地址
Mike Daniele Consultant 19 Pinewood Rd Hudson, NH 03051 USA
美国新罕布什尔州哈德逊松林路19号迈克·达涅利咨询公司，邮编：03051
Phone: +1 603 883-6365
EMail: md@world.std.com
Phone: +1 603 883-6365
EMail: md@world.std.com
Juergen Schoenwaelder TU Braunschweig Bueltenweg 74/75 38106 Braunschweig Germany
德国布埃尔滕韦格布伦瑞克大学74/75 38106
Phone: +49 531 391-3289
EMail: schoenw@ibr.cs.tu-bs.de
Phone: +49 531 391-3289
EMail: schoenw@ibr.cs.tu-bs.de
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
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编辑功能的资金目前由互联网协会提供。