rfc3017.txt

RFC 的详细文档！

      |  "tunnelingProtocols"        (opt)|
      |  dialScript                  (opt)|
      |  pricingInformation          (opt)|
      | + - - - - - - - - - - - - +       |
      | | "location"              |  (opt)|
      | + - - - - - - - - - - - - +       |
      | + - - - - - - - - - - - - +       |
      | | "popSetup"              |  (opt)|
      | + - - - - - - - - - - - - +       |
      | + - - - - - - - - - - - - +       |
      | | "popSupport"            |  (opt)|
      | + - - - - - - - - - - - - +       |
      | + - - - - - - - - - - - - +       |
      | | "popProvider"           |  (opt)|
      | + - - - - - - - - - - - - +       |
      +-----------------------------------+






Riegel & Zorn               Standards Track                     [Page 7]

RFC 3017           Roaming Access Phone Book XML DTD       December 2000


   Syntax:

      <!ENTITY % popInformation
           "address,
            media+,
            minBitsPerSecond?,
            maxBitsPerSecond?,
            popProperty*,
            tunnelProto*,
            dialScript?,
            pricingInformation?,
            city?,
            region?,
            country?,
            (setup | setupPtr)?,
            (support | supportPtr)?,
            (provider |providerPtr)?">

      <!ELEMENT pop ( %popInformation; )>
      <!ATTLIST pop
            entryVersion   CDATA   #REQUIRED>

5.2.1.  pop Attribute "entryVersion"

   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.

5.3.  Setup

   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.

   The following information elements are currently defined for the
   Setup element.  Additional information elements may be defined by
   IANA in future.

   Syntax:

      <!ENTITY % setupInformation
           "dnsServerAddress*,
            nntpServerName*,
            smtpServerName*,
            popServerName*,
            imapServerName*,



Riegel & Zorn               Standards Track                     [Page 8]

RFC 3017           Roaming Access Phone Book XML DTD       December 2000


            wwwProxyServerName*,
            ftpProxyServerName*,
            winsockProxyServerName*,
            defaultGatewayAddress?,
            userNamePrefix?,
            userNameSuffix?">

      <!ELEMENT setup ( %setupInformation; )>
      <!ATTLIST setup
            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 Definitions

6.1.  Information elements defined for the POP element

6.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 be



Riegel & 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.25



Riegel & 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.120





Riegel & 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 available



Riegel & 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>