rfc3017.txt

最新的RFC

6.1.14.  POP Provider

   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.

   Syntax:
      <!-- Reference for provider information for this POP -->
      <!ELEMENT providerPtr EMPTY>
      <!ATTLIST providerPtr
            providerID IDREFS  #IMPLIED>

6.2.  Information elements defined for the Setup element

6.2.1.  DNS Server Address

   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).






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


   Syntax:
      <!-- Domain Name Server IP address -->
      <!ELEMENT dnsServerAddress (#PCDATA)>
      <!ATTLIST dnsServerAddress
              value NOTATION (IPADR) #IMPLIED>

6.2.2.  NNTP Server Name

   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.

   Syntax:
      <!-- Name of an NNTP server -->
      <!ELEMENT nntpServerName (#PCDATA)>
      <!ATTLIST nntpServerName
              value NOTATION (FQDN) #IMPLIED>

6.2.3.  SMTP Server Name

   The smtpServerName element contains the FQDN of the Simple Mail
   Transfer Protocol (SMTP) server which should be used when connected
   to this POP.

   Syntax:
      <!-- Name of an SMTP mail server -->
      <!ELEMENT smtpServerName (#PCDATA)>
      <!ATTLIST smtpServerName
              value NOTATION (FQDN) #IMPLIED>

6.2.4.  POP3 Server Name

   The popServerName element contains the FQDN of the Post Office
   Protocol (POP) server which should be used when connected to this
   POP.

   Syntax:
      <!-- Name of an POP3 mail server -->
      <!ELEMENT popServerName (#PCDATA)>
      <!ATTLIST popServerName
              value NOTATION (FQDN) #IMPLIED>

6.2.5.  IMAP Server Name

   The imapServerName element contains the FQDN of the Internet Mail
   Access Protocol (IMAP) server which should be used when connected to
   this POP.




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


   Syntax:
      <!-- Name of an IMAP4 server -->
      <!ELEMENT imapServerName (#PCDATA)>
      <!ATTLIST imapServerName
              value NOTATION (FQDN) #IMPLIED>

6.2.6.  WWW Proxy

   The wwwProxyServerName element contains the FQDN of the World Wide
   Web (WWW) proxy server which should be used when connected to this
   POP.

   Syntax:
      <!-- Name of an WWW Proxy -->
      <!ELEMENT wwwProxyServerName (#PCDATA)>
      <!ATTLIST wwwProxyServerName
              value NOTATION (FQDN) #IMPLIED>

6.2.7.  FTP Proxy

   The ftpProxyServerName element contains the FQDN of the File Transfer
   Protocol (FTP) proxy server which should be used when connected to
   this POP.

   Syntax:
      <!-- Name of an FTP Proxy -->
      <!ELEMENT ftpProxyServerName (#PCDATA)>
      <!ATTLIST ftpProxyServerName
              value NOTATION (FQDN) #IMPLIED>

6.2.8.  Winsock Proxy

   The winsockProxyServerName element contains the FQDN of the Windows
   Socket (Winsock) proxy server which should be used when connected to
   this POP.

   Syntax:
      <!-- Name of an Winsock Proxy -->
      <!ELEMENT winsockProxyServerName (#PCDATA)>
      <!ATTLIST winsockProxyServerName
              value NOTATION (FQDN) #IMPLIED>

6.2.9.  Default Gateway Address

   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).



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


   Syntax:
      <!-- Default Gateway IP address (in dotted decimal notation) -->
      <!ELEMENT defaultGatewayAddress (#PCDATA)>
      <!ATTLIST defaultGatewayAddress
              value NOTATION (IPADR) #IMPLIED>

6.2.10.  User Name Suffix

   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 "[e-mail]".  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.

   Syntax:
      <!-- User Name suffix -->
      <!ELEMENT userNameSuffix (#PCDATA)>

6.2.11.  User Name Prefix

   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.

   Syntax:
      <!-- User Name prefix -->
      <!ELEMENT userNamePrefix (#PCDATA)>

6.3.  Information elements defined for the support element

6.3.1.  Support Telephone Number

   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., "[phone]".

   Syntax:
      <!-- The number to be dialed to contact customer support
           for this POP or provider -->
      <!ELEMENT supportTelephoneNumber (#PCDATA)>




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


6.3.2.  Support Email Address

   The supportMailtoURL element contains a URL for the provider's
   customer support email address, e.g., mailto:[e-mail].  This
   URL could be used to contact customer support personnel regarding
   non-urgent issues.

   Syntax:
      <!-- A Uniform Resource Locator for the provider's customer
           support email address -->
      <!ELEMENT supportMailtoURL (#PCDATA)>

6.4.  Information elements defined for the provider element

6.4.1.  Provider Name

   The providerName element is a string containing the name of the
   provider (e.g., "BIGNET Corporation").

   Syntax:
      <!-- The name of the provider -->
      <!ELEMENT providerName (#PCDATA)>

6.4.2.  Provider Icon

   The providerIcon attribute contains a BASE64 encoded JPEG or GIF
   image which may be used for 'branding' phone book entries or
   displayed when dialing.

   Syntax:
      <!-- An icon in BASE64 encoded JPEG or GIF format -->
      <!ELEMENT providerIcon (#PCDATA)>
      <!ATTLIST providerIcon
              value NOTATION (B64JPG | B64GIF) #IMPLIED>

6.4.3.  Provider's World Wide Web URL

   The wwwURL element contains a Uniform Resource Locator (URL) for the
   provider's Web site, for example, http://www.uu.net.

   Syntax:
      <!-- A Uniform Resource Locator for the provider's home page -->
      <!ELEMENT wwwURL (#PCDATA)>








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


6.4.4.  Provider's Main Email Address

   The generalMailtoURL element contains a URL for the provider's main
   email address, for example, mailto:[e-mail].  This URL could be
   used for general correspondence, complaints, etc.

   Syntax:
      <!-- A Uniform Resource Locator for the provider's
                  email address -->
      <!ELEMENT generalMailtoURL (#PCDATA)>

6.4.5.  Billing Inquiry Email Address

   The billingMailtoURL element contains a URL for the provider's
   billing support email address, for example, mailto:[e-mail].
   This URL could be used to for correspondence regarding billing and
   payment issues.

   Syntax:
      <!-- A Uniform Resource Locator for the email
                  address to be used for billing inquiries -->
      <!ELEMENT billingMailtoURL (#PCDATA)>

6.4.6.  Further elements

   The remainder of the information elements of the provider element are
   described in principle in [3].

7.  Complete XML DTD for the roaming phone book

   <?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. -->

   <!ENTITY % addressFamily "(E164|X121)" >

   <!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" >

   <!ENTITY % modemProtocols "(V21|V22|V29|V32|V32B|V34|V34B|V90)" >

   <!ENTITY % isdnProtocols "(V110L|V110H|V120L|V120H|X75|HDLC)">

   <!ENTITY % atmProtocols "(RFC2364)">




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


   <!ENTITY % frProtocols "(RFC1973)">

   <!ENTITY % x25Protocols "(RFC1598)">

   <!ENTITY % popProperties "(MPPP|MOBIP|MCRX|MCTX)" >

   <!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)?">

   <!ENTITY % setupInformation
        "dnsServerAddress*,
         nntpServerName*,
         smtpServerName*,
         popServerName*,
         imapServerName*,
         wwwProxyServerName*,
         ftpProxyServerName*,
         winsockProxyServerName*,
         defaultGatewayAddress?,
         userNamePrefix?,
         userNameSuffix?">

   <!ENTITY % supportInformation
        "(supportTelephoneNumber|supportMailtoURL)+">

   <!ENTITY % providerInformation
        "providerName?,
         providerIcon?,
         wwwURL?,
         generalMailtoURL?,
         billingMailtoURL?,
         businessCategory?,



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


         x121Address?,
         registeredAddress?,
         destinationIndicator?,
         preferredDeliveryMethod?,
         telexNumber?,
         teletexTerminalIdentifier?,
         telephoneNumber?,
         internationalISDNNumber?,
         facsimileTelephoneNumber?,
         street?,
         postOfficeBox?,
         postalCode?,
         postalAddress?,
         physicalDeliveryOfficeName?,
         description?,
         supportPtr*">

   <!-- ++++++++++++++ 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 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 setup ( %setupInformation; )>
   <!ATTLIST setup
         id      ID      #REQUIRED>

   <!ELEMENT support ( %supportInformation; )>



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


   <!ATTLIST support
         id          ID         #REQUIRED
         language    NMTOKENS   #IMPLIED >

   <!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 >

   <!ELEMENT media %mediaTypes; >

   <!ELEMENT viaMODEM EMPTY>
   <!ATTLIST viaMODEM
           type %modemProtocols; #IMPLIED >

   <!ELEMENT viaISDN EMPTY>
   <!ATTLIST viaISDN
           type %isdnProtocols; #IMPLIED >

   <!ELEMENT viaATM EMPTY>
   <!ATTLIST viaATM
           type %atmProtocols; #IMPLIED >

   <!ELEMENT viaFR EMPTY>
   <!ATTLIST viaFR
           type %frProtocols; #IMPLIED >

   <!ELEMENT viaX25 EMPTY>
   <!ATTLIST viaX25
           type %x25Protocols; #IMPLIED >

   <!ELEMENT minBitsPerSecond (#PCDATA)>