⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc3017.txt

📁 最新的RFC
💻 TXT
📖 第 1 页 / 共 4 页
字号:
            id      ID      #REQUIRED>5.4.  Support   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.   Additional information elements for the Support element may be   defined by IANA in future.   Syntax:      <!ENTITY % supportInformation           "(supportTelephoneNumber | supportMailtoURL)+">      <!ELEMENT support %supportInformation; >      <!ATTLIST support            id          ID         #REQUIRED            language    NMTOKENS   #IMPLIED >5.5.  Provider   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.   Currently the following information elements are defined for the   Provider element.  Additional information elements may be defined by   IANA in future.   Syntax:      <!ENTITY % providerInformation           "providerName?,            providerIcon?,            wwwURL?,Riegel & Zorn               Standards Track                     [Page 9]RFC 3017           Roaming Access Phone Book XML DTD       December 2000            generalMailtoURL?,            billingMailtoURL?,            businessCategory?,            x121Address?,            registeredAddress?,            destinationIndicator?,            preferredDeliveryMethod?,            telexNumber?,            teletexTerminalIdentifier?,            telephoneNumber?,            internationalISDNNumber?,            facsimileTelephoneNumber?,            street?,            postOfficeBox?,            postalCode?,            postalAddress?,            physicalDeliveryOfficeName?,            description?,            supportPtr*">      <!ELEMENT provider ( %providerInformation; )>      <!ATTLIST provider            id      ID      #REQUIRED>6.  Information Element Definitions6.1.  Information elements defined for the POP element6.1.1.  Address   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.   Syntax:      <!-- A network address for this POP -->      <!ELEMENT address (#PCDATA)>6.1.1.1.  address Attribute "family"   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 beRiegel & Zorn               Standards Track                    [Page 10]RFC 3017           Roaming Access Phone Book XML DTD       December 2000   registered by IANA in future.      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 >6.1.1.2.  address Attribute "countryCode"   The countryCode attribute indicates the international dialing prefix   for the country in which the POP is located.   Syntax:      <!-- ITU dialing code for the country in which this POP is located -->      <!ATTLIST address              countryCode CDATA #IMPLIED >6.1.1.3.  address Attribute "areaCode"   The areaCode attribute contains the area or city code component of   the telephone number in the 'address' element (if any) associated   with this POP.      <!-- Area or city code component of the telephone number in the           accessTelephoneNumber element associated with this POP -->      <!ATTLIST address              areaCode CDATA #IMPLIED >6.1.2.  Media   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.      Value         Media Type      --------      -----------      viaMODEM      Modem      viaISDN       ISDN      viaATM        ATM      viaFR         Frame Relay      viaX25        X.25Riegel & Zorn               Standards Track                    [Page 11]RFC 3017           Roaming Access Phone Book XML DTD       December 2000   Syntax:      <!-- The types of media supported by this POP -->      <!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" >      <!ELEMENT media %mediaTypes; >6.1.2.1.  Modem Protocols   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.      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 >6.1.2.2.  ISDN Protocols   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.      Value  Speed    Meaning      -----  -----    -----------      V110L  19.2k    ITU-T V.110      V110H  38.4k    ITU-T V.110      V120L  56k      ITU-T V.120Riegel & Zorn               Standards Track                    [Page 12]RFC 3017           Roaming Access Phone Book XML DTD       December 2000      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 >6.1.2.3.  ATM Protocols   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.   Syntax:      <!-- An ATM media type element -->      <!ENTITY % atmProtocols "(RFC2364)">      <!ELEMENT viaATM EMPTY>      <!ATTLIST viaATM              type %atmProtocols; #IMPLIED >6.1.2.4.  Frame Relay Protocols   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.   Syntax:      <!-- A Frame Relay media type element -->      <!ENTITY % frProtocols "(RFC1973)">      <!ELEMENT viaFR EMPTY>      <!ATTLIST viaFR              type %frProtocols; #IMPLIED >6.1.2.5.  X.25 Protocols   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 availableRiegel & Zorn               Standards Track                    [Page 13]RFC 3017           Roaming Access Phone Book XML DTD       December 2000   protocols this element may be included repeatedly.  Currently only   one protocol is defined.  Additional values may be registered by IANA   in future.   Syntax:      <!-- A X.25 media type element -->      <!ENTITY % x25Protocols "(RFC1598)">      <!ELEMENT viaX25 EMPTY>      <!ATTLIST viaX25              type %x25Protocols; #IMPLIED >6.1.3.  Minimum Data Rate   The minBitsPerSecond element indicates the minimum data rate (in   bits/second) supported by the access devices at the POP.   Syntax:      <!-- Minimum data rate supported by this POP in bits/second -->      <!ELEMENT minBitsPerSecond (#PCDATA)>6.1.4.  Maximum Data Rate   The maxBitsPerSecond element indicates the maximum data rate (in   bits/second) supported by the access devices at the POP.   Syntax:      <!-- Maximum data rate supported by this POP in bits/second -->      <!ELEMENT maxBitsPerSecond (#PCDATA)>6.1.5.  POP Properties   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.      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)" >Riegel & Zorn               Standards Track                    [Page 14]RFC 3017           Roaming Access Phone Book XML DTD       December 2000      <!ELEMENT popProperty EMPTY>      <!ATTLIST popProperty              type %popProperties; #REQUIRED>6.1.6.  Tunneling Protocols   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.      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>6.1.7.  Dialing Script   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.   Syntax:      <!-- The dial script to be used -->      <!ELEMENT dialScript (#PCDATA)>      <!ATTLIST dialScript              type CDATA #IMPLIED >Riegel & Zorn               Standards Track                    [Page 15]RFC 3017           Roaming Access Phone Book XML DTD       December 20006.1.8.  Pricing Information   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.   Syntax:      <!-- Pricing information for this POP -->      <!ELEMENT pricing (#PCDATA)>6.1.9.  City   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).   Syntax:      <!-- The name of the city in which this POP is located -->      <!ELEMENT city (#PCDATA)>6.1.10.  Region   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.   Syntax:      <!-- The name of the region in which this POP is located -->      <!ELEMENT region (#PCDATA)>6.1.11.  Country   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.   Syntax:      <!-- The name of the country in which this POP is located -->      <!ELEMENT country (#PCDATA)>Riegel & Zorn               Standards Track                    [Page 16]RFC 3017           Roaming Access Phone Book XML DTD       December 20006.1.12.  POP Setup   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.   Syntax:      <!-- Reference for setup information for this POP -->      <!ELEMENT setupPtr EMPTY>      <!ATTLIST setupPtr            setupID   IDREFS  #IMPLIED>6.1.13.  POP Support   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.   Syntax:      <!-- Reference for support information for this POP -->      <!ELEMENT supportPtr EMPTY>      <!ATTLIST supportPtr            supportID IDREFS  #IMPLIED>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -