Network Working Group M. Riegel
Request for Comments: 3017 Siemens AG
Category: Standards Track G. Zorn
Cisco Systems
December 2000
Network Working Group M. Riegel
Request for Comments: 3017 Siemens AG
Category: Standards Track G. Zorn
Cisco Systems
December 2000
XML DTD for Roaming Access Phone Book
用于漫游访问电话簿的XML DTD
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 (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
This document defines the syntax as well as the semantics of the information to be included in the phone book for roaming applications. It comprises the information necessary to select the most appropriate ISP and to configure the host to get access to the network of the provider. The specification consists of a small set of required information elements and a variety of possible extensions. All data is specified in XML [5] (Extensible Markup Language) syntax leading to a concise XML DTD (Document Type Declaration) for the phone book.
本文档定义了漫游应用程序通讯录中包含的信息的语法和语义。它包括选择最合适的ISP和配置主机以访问提供商网络所需的信息。该规范由一小部分必需的信息元素和各种可能的扩展组成。所有数据都以XML[5]（可扩展标记语言）语法指定，从而为电话簿生成简明的XML DTD（文档类型声明）。
Table of Contents
目录
1. Introduction ............................................. 3
2. Rationale for XML Usage .................................. 4
3. Specification of Requirements ............................ 5
4. Value type notations for 'stronger' typing ............... 5
5. Container Element Definitions ............................ 5
5.1. PhoneBook ............................................ 5
5.1.1. phoneBook Attribute "name" ........................ 6
5.1.2. phoneBook Attribute "version" ..................... 6
5.2. POP .................................................. 7
5.2.1. pop Attribute "entryVersion" ...................... 8
5.3. Setup ................................................ 8
5.4. Support .............................................. 9
5.5. Provider ............................................. 9
1. Introduction ............................................. 3
2. Rationale for XML Usage .................................. 4
3. Specification of Requirements ............................ 5
4. Value type notations for 'stronger' typing ............... 5
5. Container Element Definitions ............................ 5
5.1. PhoneBook ............................................ 5
5.1.1. phoneBook Attribute "name" ........................ 6
5.1.2. phoneBook Attribute "version" ..................... 6
5.2. POP .................................................. 7
5.2.1. pop Attribute "entryVersion" ...................... 8
5.3. Setup ................................................ 8
5.4. Support .............................................. 9
5.5. Provider ............................................. 9
6. Information Element Definitions .......................... 10
6.1. Information elements defined for the POP element ..... 10
6.1.1. Address ........................................... 10
6.1.1.1. address Attribute "family" ..................... 10
6.1.1.2. address Attribute "countryCode" ................ 11
6.1.1.3. address Attribute "areaCode" ................... 11
6.1.2. Media ............................................. 11
6.1.2.1. Modem Protocols ................................ 12
6.1.2.2. ISDN Protocols ................................. 12
6.1.2.3. ATM Protocols .................................. 13
6.1.2.4. Frame Relay Protocols .......................... 13
6.1.2.5. X.25 Protocols ................................. 13
6.1.3. Minimum Data Rate ................................. 14
6.1.4. Maximum Data Rate ................................. 14
6.1.5. POP Properties .................................... 14
6.1.6. Tunneling Protocols ............................... 15
6.1.7. Dialing Script .................................... 15
6.1.8. Pricing Information ............................... 16
6.1.9. City .............................................. 16
6.1.10. Region ........................................... 16
6.1.11. Country .......................................... 16
6.1.12. POP Setup ........................................ 17
6.1.13. POP Support ...................................... 17
6.1.14. POP Provider ..................................... 17
6.2. Information elements defined for the Setup element ... 17
6.2.1. DNS Server Address ................................ 17
6.2.2. NNTP Server Name .................................. 18
6.2.3. SMTP Server Name .................................. 18
6.2.4. POP3 Server Name .................................. 18
6.2.5. IMAP Server Name .................................. 18
6.2.6. WWW Proxy ......................................... 19
6.2.7. FTP Proxy ......................................... 19
6.2.8. Winsock Proxy ..................................... 19
6.2.9. Default Gateway Address ........................... 19
6.2.10. User Name Suffix ................................. 20
6.2.11. User Name Prefix ................................. 20
6.3. Information elements defined for the support element.. 20
6.3.1. Support Telephone Number .......................... 20
6.3.2. Support Email Address ............................. 21
6.4. Information elements defined for the provider element. 21
6.4.1. Provider Name ..................................... 21
6.4.2. Provider Icon ..................................... 21
6.4.3. Provider's World Wide Web URL ..................... 21
6.4.4. Provider's Main Email Address ..................... 22
6.4.5. Billing Inquiry Email Address ..................... 22
6.4.6. Further elements .................................. 22
7. Complete XML DTD for the roaming phone book .............. 22
8. Security Considerations .................................. 28
6. Information Element Definitions .......................... 10
6.1. Information elements defined for the POP element ..... 10
6.1.1. Address ........................................... 10
6.1.1.1. address Attribute "family" ..................... 10
6.1.1.2. address Attribute "countryCode" ................ 11
6.1.1.3. address Attribute "areaCode" ................... 11
6.1.2. Media ............................................. 11
6.1.2.1. Modem Protocols ................................ 12
6.1.2.2. ISDN Protocols ................................. 12
6.1.2.3. ATM Protocols .................................. 13
6.1.2.4. Frame Relay Protocols .......................... 13
6.1.2.5. X.25 Protocols ................................. 13
6.1.3. Minimum Data Rate ................................. 14
6.1.4. Maximum Data Rate ................................. 14
6.1.5. POP Properties .................................... 14
6.1.6. Tunneling Protocols ............................... 15
6.1.7. Dialing Script .................................... 15
6.1.8. Pricing Information ............................... 16
6.1.9. City .............................................. 16
6.1.10. Region ........................................... 16
6.1.11. Country .......................................... 16
6.1.12. POP Setup ........................................ 17
6.1.13. POP Support ...................................... 17
6.1.14. POP Provider ..................................... 17
6.2. Information elements defined for the Setup element ... 17
6.2.1. DNS Server Address ................................ 17
6.2.2. NNTP Server Name .................................. 18
6.2.3. SMTP Server Name .................................. 18
6.2.4. POP3 Server Name .................................. 18
6.2.5. IMAP Server Name .................................. 18
6.2.6. WWW Proxy ......................................... 19
6.2.7. FTP Proxy ......................................... 19
6.2.8. Winsock Proxy ..................................... 19
6.2.9. Default Gateway Address ........................... 19
6.2.10. User Name Suffix ................................. 20
6.2.11. User Name Prefix ................................. 20
6.3. Information elements defined for the support element.. 20
6.3.1. Support Telephone Number .......................... 20
6.3.2. Support Email Address ............................. 21
6.4. Information elements defined for the provider element. 21
6.4.1. Provider Name ..................................... 21
6.4.2. Provider Icon ..................................... 21
6.4.3. Provider's World Wide Web URL ..................... 21
6.4.4. Provider's Main Email Address ..................... 22
6.4.5. Billing Inquiry Email Address ..................... 22
6.4.6. Further elements .................................. 22
7. Complete XML DTD for the roaming phone book .............. 22
8. Security Considerations .................................. 28
9. IANA Considerations ...................................... 28
9.1. Registration of new attribute values ................. 29
9.2. Registration of new information elements ............. 29
10. References .............................................. 30
11. Appendix: Examples ...................................... 31
11.1. The most simple example ............................. 31
11.2. A more comprehensive example ........................ 31
12. Acknowledgments ......................................... 31
13. Authors' Addresses ...................................... 32
14. Full Copyright Statement ................................ 33
9. IANA Considerations ...................................... 28
9.1. Registration of new attribute values ................. 29
9.2. Registration of new information elements ............. 29
10. References .............................................. 30
11. Appendix: Examples ...................................... 31
11.1. The most simple example ............................. 31
11.2. A more comprehensive example ........................ 31
12. Acknowledgments ......................................... 31
13. Authors' Addresses ...................................... 32
14. Full Copyright Statement ................................ 33
Roaming applications depend on the delivery of information about provided services and the procedures to get connected to the network from the roaming consortium to the individual users as well as from the operators of the network access servers, normally the members of the roaming consortium, and the roaming consortium.
漫游应用程序取决于漫游联合体向个人用户以及网络接入服务器运营商（通常为漫游联合体成员）和漫游联合体提供的有关所提供服务的信息和连接到网络的程序。
"phone book"
+------+ +--+
| | | ++
| ISP1 | -- | | --+
| | +---+ \ "phone book"
+------+ \ +------+
+------+ +--+ \_ | | +--+ +------+
| | | ++ | | | ++ | |
| ISP2 | -- | | -->>--- | | --- | | ->> | USER |
| | +---+ _ | | +---+ | |
+------+ / | | +------+
+------+ +--+ / +------+
| | | ++ / Roaming
| ISP# | -- | | --+ Consortium
| | +---+
+------+
"phone book"
+------+ +--+
| | | ++
| ISP1 | -- | | --+
| | +---+ \ "phone book"
+------+ \ +------+
+------+ +--+ \_ | | +--+ +------+
| | | ++ | | | ++ | |
| ISP2 | -- | | -->>--- | | --- | | ->> | USER |
| | +---+ _ | | +---+ | |
+------+ / | | +------+
+------+ +--+ / +------+
| | | ++ / Roaming
| ISP# | -- | | --+ Consortium
| | +---+
+------+
The roaming consortium assembles from the individual contributions of the providers belonging to the consortium a unified version of the phone book for usage by the customers. Probably different groups of users get different versions of a phone book adapted to their particular needs. Even users might generate different subsets especially suited to particular applications from the information received from the roaming consortium, e.g., retrieving only entries for a particular country or extracting all access points providing wireless connectivity.
漫游联盟从属于该联盟的提供商的个人贡献中收集统一版本的电话簿供客户使用。可能不同的用户群体会得到不同版本的电话簿，以适应他们的特殊需求。甚至用户也可能根据从漫游联盟收到的信息生成特别适合于特定应用的不同子集，例如，仅检索特定国家的条目或提取提供无线连接的所有接入点。
Therefore it is desirable to define a highly portable and well formed structure of the phone book to enable easy generation and postprocessing. Goals of this document include:
因此，需要定义电话簿的高度可移植且格式良好的结构，以便于生成和后处理。本文件的目标包括：
- Creating a flexible, extensible and robust framework upon which to build a standard phone book; - Promoting a standard phone book format, to enhance interoperability between ISPs and roaming consortia as well as to enable automatic extraction of configuration data by a wide variety of devices; - Defining a compact structure containing the essential information for the roaming user, to allow for storage and easy update even on small devices.
- 创建一个灵活、可扩展和健壮的框架，在此基础上构建标准电话簿；-推广标准电话簿格式，增强ISP和漫游联盟之间的互操作性，并使各种设备能够自动提取配置数据；-定义一个包含漫游用户基本信息的紧凑结构，以便即使在小型设备上也能进行存储和轻松更新。
It is not intended by this document to create a plethoric solution, with phone book elements to fit every condition on earth, neither to define any kind of phone book update or transfer protocol.
本文件无意创建一个具有电话簿元素以适应地球上各种条件的通用解决方案，也无意定义任何类型的电话簿更新或传输协议。
XML is rapidly becoming a standard format for data exchange between different applications also taking into account the transfer and access of data over the web. XML is used as syntax for expressing the structure and content of a roaming phone book to enable widespread usage and access to many different kind of media (e.g., paper, CDROM, www) using a widespread selection of access devices. Furthermore XML enables:
XML正在迅速成为不同应用程序之间数据交换的标准格式，同时也考虑到了通过web传输和访问数据。XML被用作表示漫游电话簿的结构和内容的语法，以便使用广泛选择的访问设备广泛使用和访问多种不同类型的媒体（例如纸张、CDROM、www）。此外，XML还支持：
- Extensibility - Flexibility - Integration with directories
- 可扩展性-灵活性-与目录集成
Extensibility is important because phone books are living documents; as such, it is unlikely that all the semantic requirements of arbitrary Internet service providers (ISPs) would be met by a fixed scheme, no matter how well thought out. Phone book designers must be free to create new attributes in a well-understood fashion to meet changing business needs.
可扩展性很重要，因为电话簿是动态文档；因此，无论考虑得多么周密，固定的方案都不可能满足任意互联网服务提供商（ISP）的所有语义要求。电话簿设计师必须能够自由地以一种易于理解的方式创建新属性，以满足不断变化的业务需求。
Flexibility is required of the attribute definition syntax for many of the same reasons that semantic extensibility is necessary. If we assume that phone book designers may need to define elements of arbitrary type, the syntax chosen must be able to represent these data objects cleanly. Using XML for describing the data content of the phone book fits this bill nicely, since it can be used to unambiguously describe virtually any data type.
属性定义语法需要灵活性，原因与语义可扩展性是必要的。如果我们假设电话簿设计者可能需要定义任意类型的元素，那么所选择的语法必须能够清晰地表示这些数据对象。使用XML描述电话簿的数据内容非常符合这一要求，因为它可以明确地描述几乎任何数据类型。
Integration with directories: although it is unlikely that phone books will be stored in the directory due to performance considerations, the creation of a XML DTD describing phone book content leaves that option open, with relatively little incremental effort required to implement it.
与目录的集成：尽管出于性能考虑，电话簿不太可能存储在目录中，但创建描述电话簿内容的XML DTD会使该选项保持打开状态，而实现该选项所需的增量相对较少。
In this document, the key words "MAY", "MUST, "MUST NOT", "optional", "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as described in [1].
在本文件中，关键词“可能”、“必须”、“不得”、“可选”、“建议”、“应该”和“不应该”的解释如[1]所述。
XML DTDs do not currently have capabilities for 'strong typing' of the content of elements. The only type definition foreseen in the base specification is "#PCDATA", 'parsable character data'. This might be sufficient and is used throughout this document to define elements containing information mainly aimed for interpretation by human beings.
XML DTD目前不具备对元素内容进行“强类型化”的功能。基本规范中预见的唯一类型定义是“#PCDATA”、“可解析字符数据”。这可能就足够了，并在本文档中用于定义包含主要用于人类解释的信息的元素。
To enable a more concise description of the content of particular elements several value type notations are introduced. This allows for a more detailed type description of the content of elements in cases where it seems to be desirable.
为了更简洁地描述特定元素的内容，引入了几个值类型符号。这允许在似乎需要的情况下对元素的内容进行更详细的类型描述。
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<!-- Phone book value type notation declarations -->
<!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Fully_qualified_domain_name">
<!NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type IP_address">
<!NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_jpeg_image">
<!NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_gif_image">
<!-- Phone book value type notation declarations -->
<!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Fully_qualified_domain_name">
<!NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type IP_address">
<!NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_jpeg_image">
<!NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_gif_image">
The phoneBook element is the basic container for phone book entries. It has two attributes, a phone book name and a phone book version number (applying to the phone book as a whole), and always contains one or more pop elements. A phoneBook element may also contain multiple Setup, Support and Provider elements, if they are referenced to by more than one pop element.
phoneBook元素是电话簿条目的基本容器。它有两个属性，一个电话簿名称和一个电话簿版本号（应用于整个电话簿），并且始终包含一个或多个pop元素。如果一个电话簿元素被多个pop元素引用，则该元素还可能包含多个Setup、Support和Provider元素。
Syntax:
<!ELEMENT phoneBook (
pop+,
setup*,
support*,
provider*)>
<!ATTLIST phoneBook
name CDATA #REQUIRED
version CDATA #REQUIRED >
Syntax:
<!ELEMENT phoneBook (
pop+,
setup*,
support*,
provider*)>
<!ATTLIST phoneBook
name CDATA #REQUIRED
version CDATA #REQUIRED >
phoneBook
+-----------------------------------+
| phoneBookName (req)|
| phoneBookVersion (req)|
| +-----------------------+ |
| | pop |+ (req)|
| +-----------------------+| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | setup |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | support |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | provider |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
+-----------------------------------+
phoneBook
+-----------------------------------+
| phoneBookName (req)|
| phoneBookVersion (req)|
| +-----------------------+ |
| | pop |+ (req)|
| +-----------------------+| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | setup |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | support |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | provider |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
+-----------------------------------+
The phoneBook attribute "name" is an arbitrary string assigned as an identifier for a phone book.
电话簿属性“name”是指定为电话簿标识符的任意字符串。
The phoneBookVersion attribute is an integer representing the version of the phone book; it is a monotonically increasing counter which should be incremented each time the phone book is modified. This element can be used by a server to help decide what (if any) actions are required to bring a client's phone book up to date. For example, the client can, at connect time, send an update request to the server
phoneBookVersion属性是一个整数，表示电话簿的版本；它是一个单调递增的计数器，每次修改通讯录时都应递增。服务器可以使用此元素来帮助决定需要采取哪些（如果有的话）操作来更新客户端的电话簿。例如，客户端可以在连接时向服务器发送更新请求
including in the request the version number of its current phone book. If the client's phone book version is not the same as the server's current phone book version, the server can easily take appropriate action, e.g., reply with a URL pointing to a file containing the differences between the client and server phone books.
在请求中包括其当前电话簿的版本号。如果客户端的电话簿版本与服务器当前的电话簿版本不同，服务器可以轻松采取适当的操作，例如，使用指向包含客户端和服务器电话簿之间差异的文件的URL进行回复。
The pop element contains information elements relevant to individual network points of presence (POPs). The required information elements are addrFamily, address, media and entryVersion. The media element represents the media types supported by the POP, while the entryVersion element is a monotonically-increasing integer which should be incremented whenever the object is modified.
pop元素包含与各个网络存在点（pop）相关的信息元素。所需的信息元素包括addr家族、地址、媒体和entryVersion。media元素表示POP支持的媒体类型，而entryVersion元素是一个单调递增的整数，每当修改对象时，它都应该递增。
The following information elements are currently defined for the pop element. Additional information elements may be defined by IANA in future.
当前为pop元素定义了以下信息元素。IANA将来可能会定义其他信息元素。
POP
+-----------------------------------+
| entryVersion (req)|
| +-------------------------+ |
| | address | (req)|
| +-------------------------+ |
| media (req)|
| minBitsPerSecond (opt)|
| maxBitsPerSecond (opt)|
| "popProperties" (opt)|
| "tunnelingProtocols" (opt)|
| dialScript (opt)|
| pricingInformation (opt)|
| + - - - - - - - - - - - - + |
| | "location" | (opt)|
| + - - - - - - - - - - - - + |
| + - - - - - - - - - - - - + |
| | "popSetup" | (opt)|
| + - - - - - - - - - - - - + |
| + - - - - - - - - - - - - + |
| | "popSupport" | (opt)|
| + - - - - - - - - - - - - + |
| + - - - - - - - - - - - - + |
| | "popProvider" | (opt)|
| + - - - - - - - - - - - - + |
+-----------------------------------+
POP
+-----------------------------------+
| entryVersion (req)|
| +-------------------------+ |
| | address | (req)|
| +-------------------------+ |
| media (req)|
| minBitsPerSecond (opt)|
| maxBitsPerSecond (opt)|
| "popProperties" (opt)|
| "tunnelingProtocols" (opt)|
| dialScript (opt)|
| pricingInformation (opt)|
| + - - - - - - - - - - - - + |
| | "location" | (opt)|
| + - - - - - - - - - - - - + |
| + - - - - - - - - - - - - + |
| | "popSetup" | (opt)|
| + - - - - - - - - - - - - + |
| + - - - - - - - - - - - - + |
| | "popSupport" | (opt)|
| + - - - - - - - - - - - - + |
| + - - - - - - - - - - - - + |
| | "popProvider" | (opt)|
| + - - - - - - - - - - - - + |
+-----------------------------------+
Syntax:
语法：
<!ENTITY % popInformation "address, media+, minBitsPerSecond?, maxBitsPerSecond?, popProperty*, tunnelProto*, dialScript?, pricingInformation?, city?, region?, country?, (setup | setupPtr)?, (support | supportPtr)?, (provider |providerPtr)?">
<!实体%popInformation“地址、媒体+、minBitsPerSecond？、maxBitsPerSecond？、popProperty*、tunnelProto*、dialScript？、PricinInformation？、城市？、地区？、国家？、（设置|设置PTR）、（支持|支持PTR）、（提供商|提供商PTR）”>
<!ELEMENT pop ( %popInformation; )>
<!ATTLIST pop
entryVersion CDATA #REQUIRED>
<!ELEMENT pop ( %popInformation; )>
<!ATTLIST pop
entryVersion CDATA #REQUIRED>
The entryVersion attribute is an integer representing the version of the POP object; it is a monotonically increasing counter which should be incremented each time the object is modified. This attribute may be useful in merging and updating phone books.
entryVersion属性是一个整数，表示POP对象的版本；它是一个单调递增的计数器，每次修改对象时都应递增。此属性在合并和更新电话簿时可能很有用。
The Setup element includes information elements which describe services which may change from provider to provider or even from POP to POP. Some of the values contained in these information elements may be available by other means (e.g., DHCP), but others may not.
Setup元素包括描述服务的信息元素，这些服务可能会随着提供商的不同而变化，甚至会随着POP的不同而变化。这些信息元素中包含的一些值可能通过其他方式（例如DHCP）可用，但其他值可能不可用。
The following information elements are currently defined for the Setup element. Additional information elements may be defined by IANA in future.
当前为设置元素定义了以下信息元素。IANA将来可能会定义其他信息元素。
Syntax:
语法：
<!ENTITY % setupInformation "dnsServerAddress*, nntpServerName*, smtpServerName*, popServerName*, imapServerName*,
<!实体%setupInformation“dnsServerAddress*、nntpServerName*、smtpServerName*、popServerName*、imapServerName*，
wwwProxyServerName*, ftpProxyServerName*, winsockProxyServerName*, defaultGatewayAddress?, userNamePrefix?, userNameSuffix?">
wwwProxyServerName*、ftpProxyServerName*、winsockProxyServerName*、defaultGatewayAddress？、userNamePrefix？、userNameSuffix？>
<!ELEMENT setup ( %setupInformation; )>
<!ATTLIST setup
id ID #REQUIRED>
<!ELEMENT setup ( %setupInformation; )>
<!ATTLIST setup
id ID #REQUIRED>
The Support element includes those information elements that are pertinent to the provision of customer support for a POP or provider. Languages spoken by the staff at the support center might be specified by multiple entries for the attribute value language.
支持元素包括与为POP或提供商提供客户支持相关的信息元素。支持中心工作人员使用的语言可能由属性值语言的多个条目指定。
Additional information elements for the Support element may be defined by IANA in future.
IANA将来可能会定义支持要素的其他信息要素。
Syntax:
<!ENTITY % supportInformation
"(supportTelephoneNumber | supportMailtoURL)+">
Syntax:
<!ENTITY % supportInformation
"(supportTelephoneNumber | supportMailtoURL)+">
<!ELEMENT support %supportInformation; >
<!ATTLIST support
id ID #REQUIRED
language NMTOKENS #IMPLIED >
<!ELEMENT support %supportInformation; >
<!ATTLIST support
id ID #REQUIRED
language NMTOKENS #IMPLIED >
The Provider element contains information elements pertaining to the general business operations of a given network service provider. The information elements include such things as telephone number, mailing address, etc., as well as URLs for e-mail and a World Wide Web site. A Provider element may also contain a reference to support information.
Provider元素包含与给定网络服务提供商的一般业务操作相关的信息元素。信息元素包括电话号码、邮寄地址等，以及电子邮件和万维网网站的URL。提供者元素还可以包含对支持信息的引用。
Currently the following information elements are defined for the Provider element. Additional information elements may be defined by IANA in future.
目前，为Provider元素定义了以下信息元素。IANA将来可能会定义其他信息元素。
Syntax: <!ENTITY % providerInformation "providerName?, providerIcon?, wwwURL?,
语法：<！实体%providerInformation“providerName”、providerIcon、wwwURL、？，
generalMailtoURL?, billingMailtoURL?, businessCategory?, x121Address?, registeredAddress?, destinationIndicator?, preferredDeliveryMethod?, telexNumber?, teletexTerminalIdentifier?, telephoneNumber?, internationalISDNNumber?, facsimileTelephoneNumber?, street?, postOfficeBox?, postalCode?, postalAddress?, physicalDeliveryOfficeName?, description?, supportPtr*">
通用邮箱？，计费邮箱？，业务类别？，X121地址？，注册地址？，目的地指示器？，首选送达方式？，电传号码？，电传终端识别器？，电话号码？，国际号码？，传真电话号码？，街道？，邮政信箱？，邮政编码？，邮递地址？，物理送达地址？，描述？，supportPtr*“>
<!ELEMENT provider ( %providerInformation; )>
<!ATTLIST provider
id ID #REQUIRED>
<!ELEMENT provider ( %providerInformation; )>
<!ATTLIST provider
id ID #REQUIRED>
The address element provides the information representing the address of the POP. For POPs offering dial-up network access, the address element will at least contain an IA5 string representing a telephone number, formatted in standard fashion [4] (e.g., "+ 1 234 5678"). More detailed information may be available by optional attribute values.
address元素提供表示POP地址的信息。对于提供拨号网络访问的POP，地址元素将至少包含表示电话号码的IA5字符串，格式为标准方式[4]（例如“+12345678”）。更多详细信息可通过可选属性值获得。
Syntax:
<!-- A network address for this POP -->
<!ELEMENT address (#PCDATA)>
Syntax:
<!-- A network address for this POP -->
<!ELEMENT address (#PCDATA)>
The attribute family of the element address defines the address family to which the element value belongs. For POPs offering dial-up network access, the addrFamily attribute will generally contain a value for a telephone network based address family. Currently the following attribute values are defined. Additional values may be
元素地址的属性族定义元素值所属的地址族。对于提供拨号网络访问的POP，addrFamily属性通常包含基于电话网络的地址族的值。目前定义了以下属性值。附加值可能是
registered by IANA in future.
以后由IANA注册。
Value Description
------ ------------------------------------------
E164 ITU-T E.164 (PSTN, SMDS, Frame Relay, ATM)
X121 ITU-T X.121 (X.25, Frame Relay)
Value Description
------ ------------------------------------------
E164 ITU-T E.164 (PSTN, SMDS, Frame Relay, ATM)
X121 ITU-T X.121 (X.25, Frame Relay)
Syntax:
<!-- Attribute values for address family -->
<!ENTITY % addressFamily "(E164|X121)" >
<!ATTLIST address
family %addressFamily; #REQUIRED >
Syntax:
<!-- Attribute values for address family -->
<!ENTITY % addressFamily "(E164|X121)" >
<!ATTLIST address
family %addressFamily; #REQUIRED >
The countryCode attribute indicates the international dialing prefix for the country in which the POP is located.
countryCode属性表示POP所在国家的国际拨号前缀。
Syntax:
<!-- ITU dialing code for the country in which this POP is located -->
<!ATTLIST address
countryCode CDATA #IMPLIED >
Syntax:
<!-- ITU dialing code for the country in which this POP is located -->
<!ATTLIST address
countryCode CDATA #IMPLIED >
The areaCode attribute contains the area or city code component of the telephone number in the 'address' element (if any) associated with this POP.
areaCode属性包含与此POP关联的“address”（地址）元素（如果有）中电话号码的区号或城市代码部分。
<!-- Area or city code component of the telephone number in the
accessTelephoneNumber element associated with this POP -->
<!ATTLIST address
areaCode CDATA #IMPLIED >
<!-- Area or city code component of the telephone number in the
accessTelephoneNumber element associated with this POP -->
<!ATTLIST address
areaCode CDATA #IMPLIED >
The media element is a container describing the types of media and related protocols supported by this POP. The following media types are currently defined. Additional types may be registered by IANA in future.
媒体元素是一个容器，描述此POP支持的媒体类型和相关协议。当前定义了以下媒体类型。IANA将来可能会注册其他类型。
Value Media Type
-------- -----------
viaMODEM Modem
viaISDN ISDN
viaATM ATM
viaFR Frame Relay
viaX25 X.25
Value Media Type
-------- -----------
viaMODEM Modem
viaISDN ISDN
viaATM ATM
viaFR Frame Relay
viaX25 X.25
Syntax:
<!-- The types of media supported by this POP -->
<!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" >
<!ELEMENT media %mediaTypes; >
Syntax:
<!-- The types of media supported by this POP -->
<!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" >
<!ELEMENT media %mediaTypes; >
The viaMODEM element is an empty element representing by its optional type attribute the modem protocol supported by the access devices that can be reached at address. To define multiple available protocols this element may be included repeatedly. The initially defined modem protocol types are listed in the table below. Additional values may be registered by IANA in future.
viaMODEM元素是一个空元素，通过其可选类型属性表示可在地址处访问的访问设备支持的调制解调器协议。要定义多个可用协议，可以重复包含此元素。下表列出了最初定义的调制解调器协议类型。IANA将来可能会注册其他值。
Value Duplex Speed Protocol
----- ------ ----- -------------
V21 Full 300 ITU-T V.21
V22 Full 1200 ITU-T V.22
V29 Half 9600 ITU-T V.29
V32 Full 9600 ITU-T V.32
V32B Full 14.4k ITU-T V.32bis
V34 Full 28.8k ITU-T V.34
V34B Full 33.6k ITU-T V.34bis
V90 Full 56k ITU-T V.90
Value Duplex Speed Protocol
----- ------ ----- -------------
V21 Full 300 ITU-T V.21
V22 Full 1200 ITU-T V.22
V29 Half 9600 ITU-T V.29
V32 Full 9600 ITU-T V.32
V32B Full 14.4k ITU-T V.32bis
V34 Full 28.8k ITU-T V.34
V34B Full 33.6k ITU-T V.34bis
V90 Full 56k ITU-T V.90
Syntax
<!-- A modem media type element -->
<!ENTITY % modemProtocols "(V21|V22|V29|V32|V32B|V34|V34B|V90)" >
<!ELEMENT viaMODEM EMPTY>
<!ATTLIST viaMODEM
type %modemProtocols; #IMPLIED >
Syntax
<!-- A modem media type element -->
<!ENTITY % modemProtocols "(V21|V22|V29|V32|V32B|V34|V34B|V90)" >
<!ELEMENT viaMODEM EMPTY>
<!ATTLIST viaMODEM
type %modemProtocols; #IMPLIED >
The viaISDN element is an empty element representing by its optional type attribute the ISDN protocol supported by the access devices that can be reached at address. To define multiple available protocols this element may be included repeatedly. The initially defined ISDN protocol types are listed in the table below. Additional values may be registered by IANA in future.
viaISDN元素是一个空元素，通过其可选类型属性表示访问设备支持的ISDN协议，可在地址处访问。要定义多个可用协议，可以重复包含此元素。下表列出了最初定义的ISDN协议类型。IANA将来可能会注册其他值。
Value Speed Meaning
----- ----- -----------
V110L 19.2k ITU-T V.110
V110H 38.4k ITU-T V.110
V120L 56k ITU-T V.120
Value Speed Meaning
----- ----- -----------
V110L 19.2k ITU-T V.110
V110H 38.4k ITU-T V.110
V120L 56k ITU-T V.120
V120H 64k ITU-T V.120 X75 64k ITU-T X.75 HDLC 64k RFC 1618
V120H 64k ITU-T V.120 X75 64k ITU-T X.75 HDLC 64k RFC 1618
Syntax:
<!-- An ISDN media type element -->
<!ENTITY % isdnProtocols "(V110L|V110H|V120L|V120H|X75|HDLC)">
<!ELEMENT viaISDN EMPTY>
<!ATTLIST viaISDN
type %isdnProtocols; #IMPLIED >
Syntax:
<!-- An ISDN media type element -->
<!ENTITY % isdnProtocols "(V110L|V110H|V120L|V120H|X75|HDLC)">
<!ELEMENT viaISDN EMPTY>
<!ATTLIST viaISDN
type %isdnProtocols; #IMPLIED >
The viaATM element is an empty element representing by its optional type attribute a particular protocol supported by the access devices that can be reached at address. To define multiple available protocols this element may be included repeatedly. Currently only one protocol is defined. Additional values may be registered by IANA in future.
viaATM元素是一个空元素，通过其可选类型属性表示访问设备支持的特定协议，可以在地址处访问该协议。要定义多个可用协议，可以重复包含此元素。目前只定义了一个协议。IANA将来可能会注册其他值。
Syntax:
<!-- An ATM media type element -->
<!ENTITY % atmProtocols "(RFC2364)">
<!ELEMENT viaATM EMPTY>
<!ATTLIST viaATM
type %atmProtocols; #IMPLIED >
Syntax:
<!-- An ATM media type element -->
<!ENTITY % atmProtocols "(RFC2364)">
<!ELEMENT viaATM EMPTY>
<!ATTLIST viaATM
type %atmProtocols; #IMPLIED >
The viaFR element is an empty element representing by its optional type attribute the particular protocol supported by the access devices that can be reached at address. To define multiple available protocols this element may be included repeatedly. Currently only one protocol is defined. Additional values may be registered by IANA in future.
viaFR元素是一个空元素，通过其可选类型属性表示访问设备支持的特定协议，可以在地址处访问该协议。要定义多个可用协议，可以重复包含此元素。目前只定义了一个协议。IANA将来可能会注册其他值。
Syntax:
<!-- A Frame Relay media type element -->
<!ENTITY % frProtocols "(RFC1973)">
<!ELEMENT viaFR EMPTY>
<!ATTLIST viaFR
type %frProtocols; #IMPLIED >
Syntax:
<!-- A Frame Relay media type element -->
<!ENTITY % frProtocols "(RFC1973)">
<!ELEMENT viaFR EMPTY>
<!ATTLIST viaFR
type %frProtocols; #IMPLIED >
The viaX25 element is an empty element representing by its optional type attribute the particular protocol supported by the access devices that can be reached at address. To define multiple available
viaX25元素是一个空元素，通过其可选类型属性表示访问设备支持的特定协议，可以在地址处访问该协议。定义多个可用的
protocols this element may be included repeatedly. Currently only one protocol is defined. Additional values may be registered by IANA in future.
该元素可以重复包含。目前只定义了一个协议。IANA将来可能会注册其他值。
Syntax:
<!-- A X.25 media type element -->
<!ENTITY % x25Protocols "(RFC1598)">
<!ELEMENT viaX25 EMPTY>
<!ATTLIST viaX25
type %x25Protocols; #IMPLIED >
Syntax:
<!-- A X.25 media type element -->
<!ENTITY % x25Protocols "(RFC1598)">
<!ELEMENT viaX25 EMPTY>
<!ATTLIST viaX25
type %x25Protocols; #IMPLIED >
The minBitsPerSecond element indicates the minimum data rate (in bits/second) supported by the access devices at the POP.
minBitsPerSecond元素表示POP上访问设备支持的最小数据速率（以位/秒为单位）。
Syntax:
<!-- Minimum data rate supported by this POP in bits/second -->
<!ELEMENT minBitsPerSecond (#PCDATA)>
Syntax:
<!-- Minimum data rate supported by this POP in bits/second -->
<!ELEMENT minBitsPerSecond (#PCDATA)>
The maxBitsPerSecond element indicates the maximum data rate (in bits/second) supported by the access devices at the POP.
maxBitsPerSecond元素表示POP上访问设备支持的最大数据速率（以位/秒为单位）。
Syntax:
<!-- Maximum data rate supported by this POP in bits/second -->
<!ELEMENT maxBitsPerSecond (#PCDATA)>
Syntax:
<!-- Maximum data rate supported by this POP in bits/second -->
<!ELEMENT maxBitsPerSecond (#PCDATA)>
The popProperty element is an empty element representing by its attribute value a particular property of this POP. To define multiple available protocols this element might be included several times. The initially defined properties are listed in the table below. Additional values may be registered by IANA in future.
PoppProperty元素是一个空元素，通过其属性值表示此POP的特定属性。要定义多个可用协议，可能会多次包含此元素。下表列出了最初定义的特性。IANA将来可能会注册其他值。
Value Property
------ ----------------------
MPPP Multilink PPP (RFC 1990)
MOBIP Mobile IP (RFC 2002)
MCRX Multicast Reception
MCTX Multicast Transmission
Value Property
------ ----------------------
MPPP Multilink PPP (RFC 1990)
MOBIP Mobile IP (RFC 2002)
MCRX Multicast Reception
MCTX Multicast Transmission
Syntax:
<!-- A property characterizing this POP -->
<!ENTITY % popProperties "(MPPP|MOBIP|MCRX|MCTX)" >
Syntax:
<!-- A property characterizing this POP -->
<!ENTITY % popProperties "(MPPP|MOBIP|MCRX|MCTX)" >
<!ELEMENT popProperty EMPTY>
<!ATTLIST popProperty
type %popProperties; #REQUIRED>
<!ELEMENT popProperty EMPTY>
<!ATTLIST popProperty
type %popProperties; #REQUIRED>
The tunnelProto element is an empty element representing by its attribute a tunneling protocol supported by this POP. To define multiple available protocols this element might be included several times. The initially defined values are listed in the table below. Additional values may be registered by IANA in future.
tunnelProto元素是一个空元素，通过其属性表示此POP支持的隧道协议。要定义多个可用协议，可能会多次包含此元素。下表列出了最初定义的值。IANA将来可能会注册其他值。
Value Protocol
------ ------------------
L2TP RFC 2661 L2TP
PPTP RFC 2637 PPTP
L2F RFC 2341 L2F
ATMP RFC 2107 ATMP
AHT RFC 2402 IP AH Tunnel Mode
ESPT RFC 2406 IP ESP Tunnel Mode
IPIP RFC 1853 IP-IP
MIP RFC 2004 Minimal IP-IP
GRE RFC 1701 GRE
Value Protocol
------ ------------------
L2TP RFC 2661 L2TP
PPTP RFC 2637 PPTP
L2F RFC 2341 L2F
ATMP RFC 2107 ATMP
AHT RFC 2402 IP AH Tunnel Mode
ESPT RFC 2406 IP ESP Tunnel Mode
IPIP RFC 1853 IP-IP
MIP RFC 2004 Minimal IP-IP
GRE RFC 1701 GRE
Syntax:
<!-- A tunneling protocol supported by this POP -->
<!ENTITY % tunnelingProtocols
"(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" >
<!ELEMENT tunnelProto EMPTY>
<!ATTLIST tunnelProto
type %tunnelingProtocols; #REQUIRED>
Syntax:
<!-- A tunneling protocol supported by this POP -->
<!ENTITY % tunnelingProtocols
"(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" >
<!ELEMENT tunnelProto EMPTY>
<!ATTLIST tunnelProto
type %tunnelingProtocols; #REQUIRED>
The dialScript element contains the dialing script to be used when connecting to this POP. The attribute value type of dialScript defines the type of the script that should be used when connecting to this POP.
dialScript元素包含连接到此POP时要使用的拨号脚本。dialScript的属性值类型定义连接到此POP时应使用的脚本类型。
Syntax:
<!-- The dial script to be used -->
<!ELEMENT dialScript (#PCDATA)>
<!ATTLIST dialScript
type CDATA #IMPLIED >
Syntax:
<!-- The dial script to be used -->
<!ELEMENT dialScript (#PCDATA)>
<!ATTLIST dialScript
type CDATA #IMPLIED >
The pricingInformation element is a free-form string representing pricing information for this POP. It may be anything from a simple string indicating relative expense (e.g., "$$$$" for a very expensive POP) to a paragraph describing time-of-day and other differential pricing variables.
PricinInformation元素是一个自由格式的字符串，表示此POP的定价信息。它可以是任何内容，从指示相对费用的简单字符串（例如，对于非常昂贵的POP为“$$$”），到描述时间和其他差异定价变量的段落。
Syntax:
<!-- Pricing information for this POP -->
<!ELEMENT pricing (#PCDATA)>
Syntax:
<!-- Pricing information for this POP -->
<!ELEMENT pricing (#PCDATA)>
The city element contains the name of the city in which the POP is located (not the city(s) from which it is accessible by a local call).
city元素包含POP所在城市的名称（而不是通过本地呼叫可以访问POP的城市）。
Syntax:
<!-- The name of the city in which this POP is located -->
<!ELEMENT city (#PCDATA)>
Syntax:
<!-- The name of the city in which this POP is located -->
<!ELEMENT city (#PCDATA)>
The region element contains the name of the region in which the POP is located. In the United States, this would be the name of a state or (for Washington, D.C.) administrative district. In other countries, it might be the name of a province, parish or county.
region元素包含POP所在区域的名称。在美国，这将是一个州或（华盛顿特区）行政区的名称。在其他国家，它可能是一个省、教区或县的名称。
Syntax:
<!-- The name of the region in which this POP is located -->
<!ELEMENT region (#PCDATA)>
Syntax:
<!-- The name of the region in which this POP is located -->
<!ELEMENT region (#PCDATA)>
The country element contains the name of the country in which the POP is located. The country name may be abbreviated (e.g., "USA" for the United States of America or "UK" for the United Kingdom) but if abbreviations are used the usage must be consistent within a given phone book.
country元素包含POP所在国家的名称。国家名称可以缩写（例如，美利坚合众国的“USA”或英国的“UK”），但如果使用缩写，则在给定电话簿中的用法必须一致。
Syntax:
<!-- The name of the country in which this POP is located -->
<!ELEMENT country (#PCDATA)>
Syntax:
<!-- The name of the country in which this POP is located -->
<!ELEMENT country (#PCDATA)>
The popSetup element is either a setup element, if setup is specific to this particular POP, or a reference to any of the setup elements given in the outer scope of the phonebook element.
popSetup元素是一个setup元素（如果setup特定于此特定的POP），或者是对phonebook元素外部范围中给定的任何setup元素的引用。
Syntax:
<!-- Reference for setup information for this POP -->
<!ELEMENT setupPtr EMPTY>
<!ATTLIST setupPtr
setupID IDREFS #IMPLIED>
Syntax:
<!-- Reference for setup information for this POP -->
<!ELEMENT setupPtr EMPTY>
<!ATTLIST setupPtr
setupID IDREFS #IMPLIED>
The popSupport element is either a support element, if support is specific to this particular POP, or a reference to any of the support elements given in the outer scope of the phonebook element.
popSupport元素要么是一个support元素（如果support特定于此特定的POP），要么是对phonebook元素外部范围中给定的任何support元素的引用。
Syntax:
<!-- Reference for support information for this POP -->
<!ELEMENT supportPtr EMPTY>
<!ATTLIST supportPtr
supportID IDREFS #IMPLIED>
Syntax:
<!-- Reference for support information for this POP -->
<!ELEMENT supportPtr EMPTY>
<!ATTLIST supportPtr
supportID IDREFS #IMPLIED>
The popProvider element is either a provider element, if provider information is specific to this particular POP, or a reference to any of the provider elements given in the outer scope of the phonebook element.
PoppProvider元素要么是提供者元素（如果提供者信息特定于此特定的POP），要么是对电话簿元素外部范围中给定的任何提供者元素的引用。
Syntax:
<!-- Reference for provider information for this POP -->
<!ELEMENT providerPtr EMPTY>
<!ATTLIST providerPtr
providerID IDREFS #IMPLIED>
Syntax:
<!-- Reference for provider information for this POP -->
<!ELEMENT providerPtr EMPTY>
<!ATTLIST providerPtr
providerID IDREFS #IMPLIED>
The dnsServerAddress element represents the IP address of the Domain Name Service (DNS) server which should be used when connected to this POP. The address is represented in the form of a string in dotted-decimal notation (e.g., 192.168.101.1).
dnsServerAddress元素表示连接到此POP时应使用的域名服务（DNS）服务器的IP地址。地址以带点十进制符号的字符串形式表示（例如192.168.101.1）。
Syntax:
<!-- Domain Name Server IP address -->
<!ELEMENT dnsServerAddress (#PCDATA)>
<!ATTLIST dnsServerAddress
value NOTATION (IPADR) #IMPLIED>
Syntax:
<!-- Domain Name Server IP address -->
<!ELEMENT dnsServerAddress (#PCDATA)>
<!ATTLIST dnsServerAddress
value NOTATION (IPADR) #IMPLIED>
The nntpServerName element contains the fully qualified domain name (FQDN) of the Network News Transfer Protocol (NNTP) server which should be used when connected to this POP.
nntpServerName元素包含网络新闻传输协议（NNTP）服务器的完全限定域名（FQDN），连接到此POP时应使用该域名。
Syntax:
<!-- Name of an NNTP server -->
<!ELEMENT nntpServerName (#PCDATA)>
<!ATTLIST nntpServerName
value NOTATION (FQDN) #IMPLIED>
Syntax:
<!-- Name of an NNTP server -->
<!ELEMENT nntpServerName (#PCDATA)>
<!ATTLIST nntpServerName
value NOTATION (FQDN) #IMPLIED>
The smtpServerName element contains the FQDN of the Simple Mail Transfer Protocol (SMTP) server which should be used when connected to this POP.
smtpServerName元素包含简单邮件传输协议（SMTP）服务器的FQDN，连接到此POP时应使用该服务器。
Syntax:
<!-- Name of an SMTP mail server -->
<!ELEMENT smtpServerName (#PCDATA)>
<!ATTLIST smtpServerName
value NOTATION (FQDN) #IMPLIED>
Syntax:
<!-- Name of an SMTP mail server -->
<!ELEMENT smtpServerName (#PCDATA)>
<!ATTLIST smtpServerName
value NOTATION (FQDN) #IMPLIED>
The popServerName element contains the FQDN of the Post Office Protocol (POP) server which should be used when connected to this POP.
popServerName元素包含邮局协议（POP）服务器的FQDN，连接到此POP时应使用该FQDN。
Syntax:
<!-- Name of an POP3 mail server -->
<!ELEMENT popServerName (#PCDATA)>
<!ATTLIST popServerName
value NOTATION (FQDN) #IMPLIED>
Syntax:
<!-- Name of an POP3 mail server -->
<!ELEMENT popServerName (#PCDATA)>
<!ATTLIST popServerName
value NOTATION (FQDN) #IMPLIED>
The imapServerName element contains the FQDN of the Internet Mail Access Protocol (IMAP) server which should be used when connected to this POP.
imapServerName元素包含Internet邮件访问协议（IMAP）服务器的FQDN，连接到此POP时应使用该服务器。
Syntax:
<!-- Name of an IMAP4 server -->
<!ELEMENT imapServerName (#PCDATA)>
<!ATTLIST imapServerName
value NOTATION (FQDN) #IMPLIED>
Syntax:
<!-- Name of an IMAP4 server -->
<!ELEMENT imapServerName (#PCDATA)>
<!ATTLIST imapServerName
value NOTATION (FQDN) #IMPLIED>
The wwwProxyServerName element contains the FQDN of the World Wide Web (WWW) proxy server which should be used when connected to this POP.
wwwProxyServerName元素包含连接到此POP时应使用的万维网（WWW）代理服务器的FQDN。
Syntax:
<!-- Name of an WWW Proxy -->
<!ELEMENT wwwProxyServerName (#PCDATA)>
<!ATTLIST wwwProxyServerName
value NOTATION (FQDN) #IMPLIED>
Syntax:
<!-- Name of an WWW Proxy -->
<!ELEMENT wwwProxyServerName (#PCDATA)>
<!ATTLIST wwwProxyServerName
value NOTATION (FQDN) #IMPLIED>
The ftpProxyServerName element contains the FQDN of the File Transfer Protocol (FTP) proxy server which should be used when connected to this POP.
ftpProxyServerName元素包含文件传输协议（FTP）代理服务器的FQDN，连接到此POP时应使用该代理服务器。
Syntax:
<!-- Name of an FTP Proxy -->
<!ELEMENT ftpProxyServerName (#PCDATA)>
<!ATTLIST ftpProxyServerName
value NOTATION (FQDN) #IMPLIED>
Syntax:
<!-- Name of an FTP Proxy -->
<!ELEMENT ftpProxyServerName (#PCDATA)>
<!ATTLIST ftpProxyServerName
value NOTATION (FQDN) #IMPLIED>
The winsockProxyServerName element contains the FQDN of the Windows Socket (Winsock) proxy server which should be used when connected to this POP.
winsockProxyServerName元素包含连接到此POP时应使用的Windows套接字（Winsock）代理服务器的FQDN。
Syntax:
<!-- Name of an Winsock Proxy -->
<!ELEMENT winsockProxyServerName (#PCDATA)>
<!ATTLIST winsockProxyServerName
value NOTATION (FQDN) #IMPLIED>
Syntax:
<!-- Name of an Winsock Proxy -->
<!ELEMENT winsockProxyServerName (#PCDATA)>
<!ATTLIST winsockProxyServerName
value NOTATION (FQDN) #IMPLIED>
The defaulttGatewayAddress element represents the address of the default gateway which should be used when connected to this POP. The address is represented in the form of a string in dotted-decimal notation (e.g., 192.168.101.1).
defaulttGatewayAddress元素表示连接到此POP时应使用的默认网关的地址。地址以带点十进制符号的字符串形式表示（例如192.168.101.1）。
Syntax:
<!-- Default Gateway IP address (in dotted decimal notation) -->
<!ELEMENT defaultGatewayAddress (#PCDATA)>
<!ATTLIST defaultGatewayAddress
value NOTATION (IPADR) #IMPLIED>
Syntax:
<!-- Default Gateway IP address (in dotted decimal notation) -->
<!ELEMENT defaultGatewayAddress (#PCDATA)>
<!ATTLIST defaultGatewayAddress
value NOTATION (IPADR) #IMPLIED>
The userNameSuffix element represents a string which should be concatenated to the base username. For example, if the base username is "userA" and the value of this element is "@bigco.com", the resulting augmented username would be "userA@bigco.com". An intelligent dialer may concatenate the string automatically. Note that both the userNameSuffix and the userNamePrefix (below) may be applied to the same base username.
userNameSuffix元素表示应连接到基本用户名的字符串。例如，如果基本用户名是“userA”，而此元素的值是“@bigco.com”，则生成的增强用户名将是”userA@bigco.com". 智能拨号器可以自动连接字符串。请注意，userNameSuffix和userNamePrefix（以下）都可以应用于相同的基本用户名。
Syntax:
<!-- User Name suffix -->
<!ELEMENT userNameSuffix (#PCDATA)>
Syntax:
<!-- User Name suffix -->
<!ELEMENT userNameSuffix (#PCDATA)>
The userNamePrefix element represents a string to which the base username should be concatenated. For example, if the base username is "userB" and the value of this element is "BIGCO/" the resulting augmented username would be "BIGCO/userB". An intelligent dialer may perform the concatenation automatically. Note that both the userNameSuffix (above) and the userNamePrefix may be applied to the same base username.
userNamePrefix元素表示基本用户名应连接到的字符串。例如，如果基本用户名是“userB”，而此元素的值是“BIGCO/”，则生成的扩展用户名将是“BIGCO/userB”。智能拨号器可以自动执行连接。请注意，userNameSuffix（如上）和usernamefix都可以应用于相同的基本用户名。
Syntax:
<!-- User Name prefix -->
<!ELEMENT userNamePrefix (#PCDATA)>
Syntax:
<!-- User Name prefix -->
<!ELEMENT userNamePrefix (#PCDATA)>
The supportTelephoneNumber element contains a number that may be called to reach the support center for a particular provider or POP. This element is basically a string and should contain the entire telephone number in international form, e.g., "+1 425 838 8080".
supportTelephoneNumber元素包含一个号码，可以调用该号码以到达特定提供商或POP的支持中心。此元素基本上是一个字符串，应包含国际形式的整个电话号码，例如“+1 425 838 8080”。
Syntax:
<!-- The number to be dialed to contact customer support
for this POP or provider -->
<!ELEMENT supportTelephoneNumber (#PCDATA)>
Syntax:
<!-- The number to be dialed to contact customer support
for this POP or provider -->
<!ELEMENT supportTelephoneNumber (#PCDATA)>
The supportMailtoURL element contains a URL for the provider's customer support email address, e.g., mailto:support@uu.net. This URL could be used to contact customer support personnel regarding non-urgent issues.
supportMailtoURL元素包含提供商客户支持电子邮件地址的URL，例如mailto：support@uu.net. 此URL可用于就非紧急问题联系客户支持人员。
Syntax:
<!-- A Uniform Resource Locator for the provider's customer
support email address -->
<!ELEMENT supportMailtoURL (#PCDATA)>
Syntax:
<!-- A Uniform Resource Locator for the provider's customer
support email address -->
<!ELEMENT supportMailtoURL (#PCDATA)>
The providerName element is a string containing the name of the provider (e.g., "BIGNET Corporation").
providerName元素是一个包含提供者名称的字符串（例如，“BIGNET Corporation”）。
Syntax:
<!-- The name of the provider -->
<!ELEMENT providerName (#PCDATA)>
Syntax:
<!-- The name of the provider -->
<!ELEMENT providerName (#PCDATA)>
The providerIcon attribute contains a BASE64 encoded JPEG or GIF image which may be used for 'branding' phone book entries or displayed when dialing.
providerIcon属性包含BASE64编码的JPEG或GIF图像，可用于“品牌化”电话簿条目或在拨号时显示。
Syntax:
<!-- An icon in BASE64 encoded JPEG or GIF format -->
<!ELEMENT providerIcon (#PCDATA)>
<!ATTLIST providerIcon
value NOTATION (B64JPG | B64GIF) #IMPLIED>
Syntax:
<!-- An icon in BASE64 encoded JPEG or GIF format -->
<!ELEMENT providerIcon (#PCDATA)>
<!ATTLIST providerIcon
value NOTATION (B64JPG | B64GIF) #IMPLIED>
The wwwURL element contains a Uniform Resource Locator (URL) for the provider's Web site, for example, http://www.uu.net.
wwwURL元素包含提供商网站的统一资源定位器（URL），例如，http://www.uu.net.
Syntax:
<!-- A Uniform Resource Locator for the provider's home page -->
<!ELEMENT wwwURL (#PCDATA)>
Syntax:
<!-- A Uniform Resource Locator for the provider's home page -->
<!ELEMENT wwwURL (#PCDATA)>
The generalMailtoURL element contains a URL for the provider's main email address, for example, mailto:contact@uu.net. This URL could be used for general correspondence, complaints, etc.
GeneralMiltourl元素包含提供者主电子邮件地址的URL，例如mailto:contact@uu.net. 此URL可用于一般通信、投诉等。
Syntax:
<!-- A Uniform Resource Locator for the provider's
email address -->
<!ELEMENT generalMailtoURL (#PCDATA)>
Syntax:
<!-- A Uniform Resource Locator for the provider's
email address -->
<!ELEMENT generalMailtoURL (#PCDATA)>
The billingMailtoURL element contains a URL for the provider's billing support email address, for example, mailto:billing@uu.net. This URL could be used to for correspondence regarding billing and payment issues.
billingMailtoURL元素包含提供商的计费支持电子邮件地址的URL，例如mailto:billing@uu.net. 此URL可用于处理有关账单和付款问题的通信。
Syntax:
<!-- A Uniform Resource Locator for the email
address to be used for billing inquiries -->
<!ELEMENT billingMailtoURL (#PCDATA)>
Syntax:
<!-- A Uniform Resource Locator for the email
address to be used for billing inquiries -->
<!ELEMENT billingMailtoURL (#PCDATA)>
The remainder of the information elements of the provider element are described in principle in [3].
提供者元素的其余信息元素原则上在[3]中描述。
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<!-- Parameter entity declaration -->
<!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<!-- This section will be maintained by IANA and can be direct
referenced by the DTD specification by means of an external
parameter entity. -->
<!-- Parameter entity declaration -->
<!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<!-- This section will be maintained by IANA and can be direct
referenced by the DTD specification by means of an external
parameter entity. -->
<!ENTITY % addressFamily "(E164|X121)" >
<!ENTITY % addressFamily "(E164|X121)" >
<!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" >
<!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" >
<!ENTITY % modemProtocols "(V21|V22|V29|V32|V32B|V34|V34B|V90)" >
<!ENTITY % modemProtocols "(V21|V22|V29|V32|V32B|V34|V34B|V90)" >
<!ENTITY % isdnProtocols "(V110L|V110H|V120L|V120H|X75|HDLC)">
<!ENTITY % isdnProtocols "(V110L|V110H|V120L|V120H|X75|HDLC)">
<!ENTITY % atmProtocols "(RFC2364)">
<!ENTITY % atmProtocols "(RFC2364)">
<!ENTITY % frProtocols "(RFC1973)">
<!ENTITY % frProtocols "(RFC1973)">
<!ENTITY % x25Protocols "(RFC1598)">
<!ENTITY % x25Protocols "(RFC1598)">
<!ENTITY % popProperties "(MPPP|MOBIP|MCRX|MCTX)" >
<!ENTITY % popProperties "(MPPP|MOBIP|MCRX|MCTX)" >
<!ENTITY % tunnelingProtocols
"(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" >
<!ENTITY % tunnelingProtocols
"(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" >
<!ENTITY % popInformation "address, media+, minBitsPerSecond?, maxBitsPerSecond?, popProperty*, tunnelProto*, dialScript?, pricingInformation?, city?, region?, country?, (setup|setupPtr)?, (support|supportPtr)?, (provider|providerPtr)?">
<!实体%popInformation“地址、媒体+、minBitsPerSecond？、maxBitsPerSecond？、popProperty*、tunnelProto*、dialScript？、PricinInformation？、城市？、地区？、国家？、（设置|设置PTR）、（支持|支持PTR）、（提供商|提供商PTR）”>
<!ENTITY % setupInformation "dnsServerAddress*, nntpServerName*, smtpServerName*, popServerName*, imapServerName*, wwwProxyServerName*, ftpProxyServerName*, winsockProxyServerName*, defaultGatewayAddress?, userNamePrefix?, userNameSuffix?">
<!实体%setupInformation“dnsServerAddress*、nntpServerName*、smtpServerName*、popServerName*、imapServerName*、wwwProxyServerName*、ftpProxyServerName*、winsockProxyServerName*、defaultGatewayAddress？、userNamePrefix？、userNameSuffix？”>
<!ENTITY % supportInformation
"(supportTelephoneNumber|supportMailtoURL)+">
<!ENTITY % supportInformation
"(supportTelephoneNumber|supportMailtoURL)+">
<!ENTITY % providerInformation "providerName?, providerIcon?, wwwURL?, generalMailtoURL?, billingMailtoURL?, businessCategory?,
<!实体%providerInformation“providerName”，providerIcon？，wwwURL？，GeneralMiltourl？，billingMailtoURL？，businessCategory？，
x121Address?, registeredAddress?, destinationIndicator?, preferredDeliveryMethod?, telexNumber?, teletexTerminalIdentifier?, telephoneNumber?, internationalISDNNumber?, facsimileTelephoneNumber?, street?, postOfficeBox?, postalCode?, postalAddress?, physicalDeliveryOfficeName?, description?, supportPtr*">
X121地址？、注册地址？、目的地指示器？、首选送达方式？、电传号码？、电传终端识别器？、电话号码？、国际电话号码？、传真电话号码？、街道？、邮政信箱？、邮政编码？、邮件地址？、物理送达办公名称？、说明？、支持PTR*“>
<!-- ++++++++++++++ End of IANA maintained section ++++++++++ -->
<!-- ++++++++++++++ End of IANA maintained section ++++++++++ -->
<!-- Phone book value type notation declarations -->
<!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Fully_qualified_domain_name">
<!NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type IP_address">
<!NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_jpeg_image">
<!NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_gif_image">
<!-- Phone book value type notation declarations -->
<!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Fully_qualified_domain_name">
<!NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type IP_address">
<!NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_jpeg_image">
<!NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/NOTATION
value Type Base64_encoded_gif_image">
<!-- Phone book element declarations -->
<!ELEMENT phoneBook (
pop+,
setup*,
support*,
provider*) >
<!ATTLIST phoneBook
name CDATA #REQUIRED
version CDATA #REQUIRED >
<!-- Phone book element declarations -->
<!ELEMENT phoneBook (
pop+,
setup*,
support*,
provider*) >
<!ATTLIST phoneBook
name CDATA #REQUIRED
version CDATA #REQUIRED >
<!ELEMENT pop ( %popInformation; )>
<!ATTLIST pop
entryVersion CDATA #REQUIRED>
<!ELEMENT pop ( %popInformation; )>
<!ATTLIST pop
entryVersion CDATA #REQUIRED>
<!ELEMENT setup ( %setupInformation; )>
<!ATTLIST setup
id ID #REQUIRED>
<!ELEMENT setup ( %setupInformation; )>
<!ATTLIST setup
id ID #REQUIRED>
<!ELEMENT support ( %supportInformation; )>
<!ELEMENT support ( %supportInformation; )>
<!ATTLIST support
id ID #REQUIRED
language NMTOKENS #IMPLIED >
<!ATTLIST support
id ID #REQUIRED
language NMTOKENS #IMPLIED >
<!ELEMENT provider ( %providerInformation; )>
<!ATTLIST provider
id ID #REQUIRED>
<!ELEMENT provider ( %providerInformation; )>
<!ATTLIST provider
id ID #REQUIRED>
<!-- Information elements for pop -->
<!ELEMENT address (#PCDATA)>
<!ATTLIST address
family %addressFamily; #REQUIRED
countryCode CDATA #IMPLIED
areaCode CDATA #IMPLIED >
<!-- Information elements for pop -->
<!ELEMENT address (#PCDATA)>
<!ATTLIST address
family %addressFamily; #REQUIRED
countryCode CDATA #IMPLIED
areaCode CDATA #IMPLIED >
<!ELEMENT media %mediaTypes; >
<!ELEMENT media %mediaTypes; >
<!ELEMENT viaMODEM EMPTY>
<!ATTLIST viaMODEM
type %modemProtocols; #IMPLIED >
<!ELEMENT viaMODEM EMPTY>
<!ATTLIST viaMODEM
type %modemProtocols; #IMPLIED >
<!ELEMENT viaISDN EMPTY>
<!ATTLIST viaISDN
type %isdnProtocols; #IMPLIED >
<!ELEMENT viaISDN EMPTY>
<!ATTLIST viaISDN
type %isdnProtocols; #IMPLIED >
<!ELEMENT viaATM EMPTY>
<!ATTLIST viaATM
type %atmProtocols; #IMPLIED >
<!ELEMENT viaATM EMPTY>
<!ATTLIST viaATM
type %atmProtocols; #IMPLIED >
<!ELEMENT viaFR EMPTY>
<!ATTLIST viaFR
type %frProtocols; #IMPLIED >
<!ELEMENT viaFR EMPTY>
<!ATTLIST viaFR
type %frProtocols; #IMPLIED >
<!ELEMENT viaX25 EMPTY>
<!ATTLIST viaX25
type %x25Protocols; #IMPLIED >
<!ELEMENT viaX25 EMPTY>
<!ATTLIST viaX25
type %x25Protocols; #IMPLIED >
<!ELEMENT minBitsPerSecond (#PCDATA)>
<!ELEMENT minBitsPerSecond (#PCDATA)>
<!ELEMENT maxBitsPerSecond (#PCDATA)>
<!ELEMENT maxBitsPerSecond (#PCDATA)>
<!ELEMENT popProperty EMPTY>
<!ATTLIST popProperty
type %popProperties; #REQUIRED >
<!ELEMENT popProperty EMPTY>
<!ATTLIST popProperty
type %popProperties; #REQUIRED >
<!ELEMENT tunnelProto EMPTY>
<!ATTLIST tunnelProto
type %tunnelingProtocols; #REQUIRED >
<!ELEMENT tunnelProto EMPTY>
<!ATTLIST tunnelProto
type %tunnelingProtocols; #REQUIRED >
<!ELEMENT dialScript (#PCDATA)>
<!ATTLIST dialScript
type CDATA #IMPLIED >
<!ELEMENT dialScript (#PCDATA)>
<!ATTLIST dialScript
type CDATA #IMPLIED >
<!ELEMENT pricing (#PCDATA)>
<!ELEMENT pricing (#PCDATA)>
<!ELEMENT city (#PCDATA)>
<!ELEMENT city (#PCDATA)>
<!ELEMENT region (#PCDATA)>
<!ELEMENT region (#PCDATA)>
<!ELEMENT country (#PCDATA)>
<!ELEMENT country (#PCDATA)>
<!ELEMENT setupPtr EMPTY>
<!ATTLIST setupPtr
setupID IDREFS #IMPLIED>
<!ELEMENT setupPtr EMPTY>
<!ATTLIST setupPtr
setupID IDREFS #IMPLIED>
<!ELEMENT supportPtr EMPTY>
<!ATTLIST supportPtr
supportID IDREFS #IMPLIED>
<!ELEMENT supportPtr EMPTY>
<!ATTLIST supportPtr
supportID IDREFS #IMPLIED>
<!ELEMENT providerPtr EMPTY>
<!ATTLIST providerPtr
providerID IDREFS #IMPLIED>
<!ELEMENT providerPtr EMPTY>
<!ATTLIST providerPtr
providerID IDREFS #IMPLIED>
<!-- Information elements for setup -->
<!ELEMENT dnsServerAddress (#PCDATA)>
<!ATTLIST dnsServerAddress
value NOTATION (IPADR) #IMPLIED>
<!-- Information elements for setup -->
<!ELEMENT dnsServerAddress (#PCDATA)>
<!ATTLIST dnsServerAddress
value NOTATION (IPADR) #IMPLIED>
<!ELEMENT nntpServerName (#PCDATA)>
<!ATTLIST nntpServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT nntpServerName (#PCDATA)>
<!ATTLIST nntpServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT smtpServerName (#PCDATA)>
<!ATTLIST smtpServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT smtpServerName (#PCDATA)>
<!ATTLIST smtpServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT popServerName (#PCDATA)>
<!ATTLIST popServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT popServerName (#PCDATA)>
<!ATTLIST popServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT imapServerName (#PCDATA)>
<!ATTLIST imapServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT imapServerName (#PCDATA)>
<!ATTLIST imapServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT wwwProxyServerName (#PCDATA)>
<!ATTLIST wwwProxyServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT wwwProxyServerName (#PCDATA)>
<!ATTLIST wwwProxyServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT ftpProxyServerName (#PCDATA)>
<!ATTLIST ftpProxyServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT ftpProxyServerName (#PCDATA)>
<!ATTLIST ftpProxyServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT winsockProxyServerName (#PCDATA)>
<!ATTLIST winsockProxyServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT winsockProxyServerName (#PCDATA)>
<!ATTLIST winsockProxyServerName
value NOTATION (FQDN) #IMPLIED>
<!ELEMENT defaultGatewayAddress (#PCDATA)>
<!ATTLIST defaultGatewayAddress
value NOTATION (IPADR) #IMPLIED>
<!ELEMENT defaultGatewayAddress (#PCDATA)>
<!ATTLIST defaultGatewayAddress
value NOTATION (IPADR) #IMPLIED>
<!ELEMENT userNameSuffix (#PCDATA)>
<!ELEMENT userNameSuffix (#PCDATA)>
<!ELEMENT userNamePrefix (#PCDATA)>
<!ELEMENT userNamePrefix (#PCDATA)>
<!-- Information elements for support -->
<!ELEMENT supportTelephoneNumber (#PCDATA)>
<!-- Information elements for support -->
<!ELEMENT supportTelephoneNumber (#PCDATA)>
<!ELEMENT supportMailtoURL (#PCDATA)>
<!ELEMENT supportMailtoURL (#PCDATA)>
<!-- Information elements for provider -->
<!ELEMENT providerName (#PCDATA)>
<!-- Information elements for provider -->
<!ELEMENT providerName (#PCDATA)>
<!ELEMENT providerIcon (#PCDATA)>
<!ATTLIST providerIcon
value NOTATION (B64JPG|B64GIF) #IMPLIED>
<!ELEMENT providerIcon (#PCDATA)>
<!ATTLIST providerIcon
value NOTATION (B64JPG|B64GIF) #IMPLIED>
<!ELEMENT wwwURL (#PCDATA)>
<!ELEMENT wwwURL (#PCDATA)>
<!ELEMENT generalMailtoURL (#PCDATA)>
<!ELEMENT generalMailtoURL (#PCDATA)>
<!ELEMENT billingMailtoURL (#PCDATA)>
<!ELEMENT billingMailtoURL (#PCDATA)>
<!-- Further provider elements according to RFC1274 -->
<!-- Further provider elements according to RFC1274 -->
<!ELEMENT businessCategory (#PCDATA)>
<!ELEMENT businessCategory (#PCDATA)>
<!ELEMENT x121Address (#PCDATA)>
<!ELEMENT x121Address (#PCDATA)>
<!ELEMENT registeredAddress (#PCDATA)>
<!ELEMENT registeredAddress (#PCDATA)>
<!ELEMENT destinationIndicator (#PCDATA)>
<!ELEMENT destinationIndicator (#PCDATA)>
<!ELEMENT preferredDeliveryMethod (#PCDATA)>
<!ELEMENT preferredDeliveryMethod (#PCDATA)>
<!ELEMENT telexNumber (#PCDATA)>
<!ELEMENT telexNumber (#PCDATA)>
<!ELEMENT teletexTerminalIdentifier (#PCDATA)>
<!ELEMENT teletexTerminalIdentifier (#PCDATA)>
<!ELEMENT telephoneNumber (#PCDATA)>
<!ELEMENT telephoneNumber (#PCDATA)>
<!ELEMENT internationalISDNNumber (#PCDATA)>
<!ELEMENT internationalISDNNumber (#PCDATA)>
<!ELEMENT facsimileTelephoneNumber (#PCDATA)>
<!ELEMENT facsimileTelephoneNumber (#PCDATA)>
<!ELEMENT street (#PCDATA)>
<!ELEMENT street (#PCDATA)>
<!ELEMENT postOfficeBox (#PCDATA)>
<!ELEMENT postOfficeBox (#PCDATA)>
<!ELEMENT postalCode (#PCDATA)>
<!ELEMENT postalCode (#PCDATA)>
<!ELEMENT postalAddress (#PCDATA)>
<!ELEMENT postalAddress (#PCDATA)>
<!ELEMENT physicalDeliveryOfficeName (#PCDATA)>
<!ELEMENT physicalDeliveryOfficeName (#PCDATA)>
<!ELEMENT description (#PCDATA)>
<!ELEMENT description (#PCDATA)>
<!-- end of dtd -->
<!-- end of dtd -->
The secure distribution and transport of information of a phone book for roaming applications require a reliable authentication of the issuer of the information as well as means to preserve the integrity of the provided information.
用于漫游应用的电话簿信息的安全分发和传输需要信息发布者的可靠身份验证以及维护所提供信息完整性的方法。
No specific elements for security requirements are provided by the phone book XML DTD itself. It is assumed that security of the roaming phone book is provided by means outside of the scope of this specification, such as signing the phone book using pgp.
电话簿XML DTD本身没有提供安全要求的特定元素。假设漫游电话簿的安全性是通过本规范范围之外的方式提供的，例如使用pgp签署电话簿。
This specification provides the possibility to define further attribute values for all information elements owning enumerated attribute lists as well as to extend the main structures 'pop', 'setup', 'support' and 'provider' by additional information elements. Therefore the specification of the roaming phone book can be adopted to future requirements without changing this document. Extensions and refinements to this specification can be achieved by registration of new elements and attributes by IANA.
本规范提供了为拥有枚举属性列表的所有信息元素定义更多属性值的可能性，以及通过附加信息元素扩展主要结构“pop”、“setup”、“support”和“provider”。因此，漫游电话簿的规范可以在不改变本文件的情况下根据未来的要求采用。可通过IANA注册新元素和属性来扩展和完善本规范。
Extending this specification with additional attributes or elements must not change the validity of documents based on an older version of the XML DTD. Therefore all added information elements must be
使用附加属性或元素扩展此规范不得更改基于旧版本XML DTD的文档的有效性。因此，必须删除所有添加的信息元素
optional, prohibiting the mandatory inclusion of newly defined information elements. Adding new values to enumerated attribute lists has no backward compatibility constraints because it does not harm the validity of attributes already defined.
可选，禁止强制包含新定义的信息元素。向枚举属性列表添加新值没有向后兼容性约束，因为它不会损害已定义属性的有效性。
To facilitate the registration of new information elements and attribute values the DTD of the phone book has been separated in two parts, the extensible part containing only parameter entity declarations for ease inclusion of new values, and the fixed part containing the detailed specification of the content and structure of the phone book. By referencing the parameter entity declarations in the fixed part of the specification the whole phone book becomes extensible.
为了便于注册新的信息元素和属性值，电话簿的DTD分为两部分，可扩展部分仅包含参数实体声明，以便于包含新值，固定部分包含电话簿内容和结构的详细说明。通过引用规范固定部分中的参数实体声明，整个电话簿变得可扩展。
The part containing the parameter entity declarations has to be maintained by the IANA. There are two different classes of declarations in this part requiring different policies for registering new values.
包含参数实体声明的部分必须由IANA维护。在本部分中，有两类不同的声明需要不同的策略来注册新值。
The entities 'addressFamily', 'modemProtocols', 'isdnProtocols', 'atmProtocols', 'frProtocols', 'x25Protocols', 'popProperties' and 'tunnelingProtocols' are describing enumerated attribute value lists. Because there is no limitation in the name space of these attribute values and newly defined attribute values can not harm the validity of existing values, new attribute values can be assigned by Specification Required [6].
实体“addressFamily”、“modemProtocols”、“isdnProtocols”、“atmProtocols”、“frProtocols”、“X25 Protocols”、“PoppProperty”和“tunnelingProtocols”描述枚举属性值列表。由于这些属性值的名称空间没有限制，并且新定义的属性值不会损害现有值的有效性，因此可以根据需要的规范指定新的属性值[6]。
The entities 'mediaTypes', 'popInformation', 'setupInformation', ' supportInformation' and 'providerInformation' define the information elements probably included in the media, pop, setup, support and provider elements. Inserting new values into these lists extends the phone book by arbitrarily new information elements. Inappropriate use of the XML content model can destroy the backward compatibility of the DTD. Therefore the assignment of new information elements requires the approval of a Designated Expert [6]. In addition to the insertion of a new value into the list, the detailed definition of the information element has to be appended to the specification part maintained by the IANA.
实体“mediaTypes”、“popInformation”、“setupInformation”、“supportInformation”和“providerInformation”定义了媒体、pop、设置、支持和提供者元素中可能包含的信息元素。在这些列表中插入新值可以通过任意添加新的信息元素来扩展电话簿。不恰当地使用XML内容模型会破坏DTD的向后兼容性。因此，新信息元素的分配需要指定专家的批准[6]。除了在列表中插入新值外，信息元素的详细定义必须附加到IANA维护的规范部分。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, RFC 1700, October 1994.
[2] Reynolds，J.和J.Postel，“分配的数字”，标准2，RFC 1700，1994年10月。
[3] Barker, P. and S. Kille, "The COSINE and Internet X.500 Schema", RFC 1274, November 1991.
[3] Barker，P.和S.Kille，“余弦和互联网X.500模式”，RFC 1274，1991年11月。
[4] ITU Rec. E.123, "Notation for national and international telephone numbers", 1988.
[4] 国际电联建议E.123，“国家和国际电话号码的符号”，1988年。
[5] "Extensible Markup Language (XML) 1.0" W3C Recommendation 10-
February-1998 http://www.w3.org/TR/1998/REC-xml-19980210
[5] "Extensible Markup Language (XML) 1.0" W3C Recommendation 10-
February-1998 http://www.w3.org/TR/1998/REC-xml-19980210
[6] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[6] Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE phoneBook SYSTEM "roamPhoneBook.dtd">
<phoneBook name="minimalExample" version="1">
<pop entryVersion="1">
<address family="E164">+1 234 5678901</address>
<media><viaMODEM/></media>
</pop>
</phoneBook>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE phoneBook SYSTEM "roamPhoneBook.dtd">
<phoneBook name="minimalExample" version="1">
<pop entryVersion="1">
<address family="E164">+1 234 5678901</address>
<media><viaMODEM/></media>
</pop>
</phoneBook>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE phoneBook SYSTEM "roamPhoneBook.dtd">
<phoneBook name="KNF_simple" version="1">
<pop entryVersion="1">
<address family="E164" countryCode="49">+49913130540</address>
<media>
<viaMODEM type="V90"/>
<viaMODEM type="V34B"/>
<viaISDN type="HDLC"/>
</media>
<setup>
<dnsServerAddress>192.168.147.5</dnsServerAddress>
<dnsServerAddress>193.175.24.33</dnsServerAddress>
</setup>
</pop>
<support id="KNF_main" language="EN DE">
<supportMailtoURL>mailto:support@franken.de</supportMailtoURL>
<supportTelephoneNumber>+499123968066</supportTelephoneNumber>
</support>
</phoneBook>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE phoneBook SYSTEM "roamPhoneBook.dtd">
<phoneBook name="KNF_simple" version="1">
<pop entryVersion="1">
<address family="E164" countryCode="49">+49913130540</address>
<media>
<viaMODEM type="V90"/>
<viaMODEM type="V34B"/>
<viaISDN type="HDLC"/>
</media>
<setup>
<dnsServerAddress>192.168.147.5</dnsServerAddress>
<dnsServerAddress>193.175.24.33</dnsServerAddress>
</setup>
</pop>
<support id="KNF_main" language="EN DE">
<supportMailtoURL>mailto:support@franken.de</supportMailtoURL>
<supportTelephoneNumber>+499123968066</supportTelephoneNumber>
</support>
</phoneBook>
Thanks to Pat Calhoun, Bernard Aboba, Jay Farhat, Butch Anton, Quentin Miller, and Ken Crocker for salient input and review.
感谢Pat Calhoun、Bernard Aboba、Jay Farhat、Butch Anton、Quentin Miller和Ken Crocker的杰出意见和评论。
Questions about this memo can be directed to:
有关本备忘录的问题，请联系：
Max Riegel Siemens AG Hofmannstr. 51 Munich, 81359 Germany
Max Riegel西门子公司Hofmannstr。51慕尼黑，81359德国
Phone: +49 89 722 49557
EMail: maximilian.riegel@icn.siemens.de
Phone: +49 89 722 49557
EMail: maximilian.riegel@icn.siemens.de
Glen Zorn Cisco Systems, Inc. 500 108th Avenue N.E., Suite 500 Bellevue, WA 98004 USA
格伦佐恩思科系统有限公司，地址：美国华盛顿州贝尔维尤第108大道500号，邮编：98004
Phone: +1 425 438 8218
EMail: gwz@cisco.com
Phone: +1 425 438 8218
EMail: gwz@cisco.com
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编辑功能的资金目前由互联网协会提供。