File: rfc3017.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (1845 lines) | stat: -rw-r--r-- 77,916 bytes
parent folder | download | duplicates (2)
<pre>Network Working Group                                          M. Riegel
Request for Comments: 3017                                    Siemens AG
Category: Standards Track                                        G. Zorn
                                                           Cisco Systems
                                                           December 2000


                 <span class="h1">XML DTD for Roaming Access Phone Book</span>

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.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

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 [<a href="#ref-5" title="&quot;Extensible Markup Language (XML) 1.0&quot;">5</a>] (Extensible Markup Language) syntax
   leading to a concise XML DTD (Document Type Declaration) for the
   phone book.

Table of Contents

   <a href="#section-1">1</a>.  Introduction .............................................  <a href="#page-3">3</a>
   <a href="#section-2">2</a>.  Rationale for XML Usage ..................................  <a href="#page-4">4</a>
   <a href="#section-3">3</a>.  Specification of Requirements ............................  <a href="#page-5">5</a>
   <a href="#section-4">4</a>.  Value type notations for 'stronger' typing ...............  <a href="#page-5">5</a>
   <a href="#section-5">5</a>.  Container Element Definitions ............................  <a href="#page-5">5</a>
     <a href="#section-5.1">5.1</a>.  PhoneBook ............................................  <a href="#page-5">5</a>
      <a href="#section-5.1.1">5.1.1</a>.  phoneBook Attribute "name" ........................  <a href="#page-6">6</a>
      <a href="#section-5.1.2">5.1.2</a>.  phoneBook Attribute "version" .....................  <a href="#page-6">6</a>
     <a href="#section-5.2">5.2</a>.  POP ..................................................  <a href="#page-7">7</a>
      <a href="#section-5.2.1">5.2.1</a>.  pop Attribute "entryVersion" ......................  <a href="#page-8">8</a>
     <a href="#section-5.3">5.3</a>.  Setup ................................................  <a href="#page-8">8</a>
     <a href="#section-5.4">5.4</a>.  Support ..............................................  <a href="#page-9">9</a>
     <a href="#section-5.5">5.5</a>.  Provider .............................................  <a href="#page-9">9</a>



<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   <a href="#section-6">6</a>.  Information Element Definitions .......................... <a href="#page-10">10</a>
     <a href="#section-6.1">6.1</a>.  Information elements defined for the POP element ..... <a href="#page-10">10</a>
      <a href="#section-6.1.1">6.1.1</a>.  Address ........................................... <a href="#page-10">10</a>
       <a href="#section-6.1.1.1">6.1.1.1</a>.  address Attribute "family" ..................... <a href="#page-10">10</a>
       <a href="#section-6.1.1.2">6.1.1.2</a>.  address Attribute "countryCode" ................ <a href="#page-11">11</a>
       <a href="#section-6.1.1.3">6.1.1.3</a>.  address Attribute "areaCode" ................... <a href="#page-11">11</a>
      <a href="#section-6.1.2">6.1.2</a>.  Media ............................................. <a href="#page-11">11</a>
       <a href="#section-6.1.2.1">6.1.2.1</a>.  Modem Protocols ................................ <a href="#page-12">12</a>
       <a href="#section-6.1.2.2">6.1.2.2</a>.  ISDN Protocols ................................. <a href="#page-12">12</a>
       <a href="#section-6.1.2.3">6.1.2.3</a>.  ATM Protocols .................................. <a href="#page-13">13</a>
       <a href="#section-6.1.2.4">6.1.2.4</a>.  Frame Relay Protocols .......................... <a href="#page-13">13</a>
       <a href="#section-6.1.2.5">6.1.2.5</a>.  X.25 Protocols ................................. <a href="#page-13">13</a>
      <a href="#section-6.1.3">6.1.3</a>.  Minimum Data Rate ................................. <a href="#page-14">14</a>
      <a href="#section-6.1.4">6.1.4</a>.  Maximum Data Rate ................................. <a href="#page-14">14</a>
      <a href="#section-6.1.5">6.1.5</a>.  POP Properties .................................... <a href="#page-14">14</a>
      <a href="#section-6.1.6">6.1.6</a>.  Tunneling Protocols ............................... <a href="#page-15">15</a>
      <a href="#section-6.1.7">6.1.7</a>.  Dialing Script .................................... <a href="#page-15">15</a>
      <a href="#section-6.1.8">6.1.8</a>.  Pricing Information ............................... <a href="#page-16">16</a>
      <a href="#section-6.1.9">6.1.9</a>.  City .............................................. <a href="#page-16">16</a>
      <a href="#section-6.1.10">6.1.10</a>.  Region ........................................... <a href="#page-16">16</a>
      <a href="#section-6.1.11">6.1.11</a>.  Country .......................................... <a href="#page-16">16</a>
      <a href="#section-6.1.12">6.1.12</a>.  POP Setup ........................................ <a href="#page-17">17</a>
      <a href="#section-6.1.13">6.1.13</a>.  POP Support ...................................... <a href="#page-17">17</a>
      <a href="#section-6.1.14">6.1.14</a>.  POP Provider ..................................... <a href="#page-17">17</a>
     <a href="#section-6.2">6.2</a>.  Information elements defined for the Setup element ... <a href="#page-17">17</a>
      <a href="#section-6.2.1">6.2.1</a>.  DNS Server Address ................................ <a href="#page-17">17</a>
      <a href="#section-6.2.2">6.2.2</a>.  NNTP Server Name .................................. <a href="#page-18">18</a>
      <a href="#section-6.2.3">6.2.3</a>.  SMTP Server Name .................................. <a href="#page-18">18</a>
      <a href="#section-6.2.4">6.2.4</a>.  POP3 Server Name .................................. <a href="#page-18">18</a>
      <a href="#section-6.2.5">6.2.5</a>.  IMAP Server Name .................................. <a href="#page-18">18</a>
      <a href="#section-6.2.6">6.2.6</a>.  WWW Proxy ......................................... <a href="#page-19">19</a>
      <a href="#section-6.2.7">6.2.7</a>.  FTP Proxy ......................................... <a href="#page-19">19</a>
      <a href="#section-6.2.8">6.2.8</a>.  Winsock Proxy ..................................... <a href="#page-19">19</a>
      <a href="#section-6.2.9">6.2.9</a>.  Default Gateway Address ........................... <a href="#page-19">19</a>
      <a href="#section-6.2.10">6.2.10</a>.  User Name Suffix ................................. <a href="#page-20">20</a>
      <a href="#section-6.2.11">6.2.11</a>.  User Name Prefix ................................. <a href="#page-20">20</a>
     <a href="#section-6.3">6.3</a>.  Information elements defined for the support element.. <a href="#page-20">20</a>
      <a href="#section-6.3.1">6.3.1</a>.  Support Telephone Number .......................... <a href="#page-20">20</a>
      <a href="#section-6.3.2">6.3.2</a>.  Support Email Address ............................. <a href="#page-21">21</a>
     6.4.  Information elements defined for the provider element. 21
      <a href="#section-6.4.1">6.4.1</a>.  Provider Name ..................................... <a href="#page-21">21</a>
      <a href="#section-6.4.2">6.4.2</a>.  Provider Icon ..................................... <a href="#page-21">21</a>
      <a href="#section-6.4.3">6.4.3</a>.  Provider's World Wide Web URL ..................... <a href="#page-21">21</a>
      <a href="#section-6.4.4">6.4.4</a>.  Provider's Main Email Address ..................... <a href="#page-22">22</a>
      <a href="#section-6.4.5">6.4.5</a>.  Billing Inquiry Email Address ..................... <a href="#page-22">22</a>
      <a href="#section-6.4.6">6.4.6</a>.  Further elements .................................. <a href="#page-22">22</a>
   <a href="#section-7">7</a>.  Complete XML DTD for the roaming phone book .............. <a href="#page-22">22</a>
   <a href="#section-8">8</a>.  Security Considerations .................................. <a href="#page-28">28</a>



<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   <a href="#section-9">9</a>.  IANA Considerations ...................................... <a href="#page-28">28</a>
     <a href="#section-9.1">9.1</a>.  Registration of new attribute values ................. <a href="#page-29">29</a>
     <a href="#section-9.2">9.2</a>.  Registration of new information elements ............. <a href="#page-29">29</a>
   <a href="#section-10">10</a>.  References .............................................. <a href="#page-30">30</a>
   <a href="#section-11">11</a>.  Appendix: Examples ...................................... <a href="#page-31">31</a>
     <a href="#section-11.1">11.1</a>.  The most simple example ............................. <a href="#page-31">31</a>
     <a href="#section-11.2">11.2</a>.  A more comprehensive example ........................ <a href="#page-31">31</a>
   <a href="#section-12">12</a>.  Acknowledgments ......................................... <a href="#page-31">31</a>
   <a href="#section-13">13</a>.  Authors' Addresses ...................................... <a href="#page-32">32</a>
   <a href="#section-14">14</a>.  Full Copyright Statement ................................ <a href="#page-33">33</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   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 | -- |   | --&gt;&gt;--- |      | --- |   | -&gt;&gt; | 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.






<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   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.

   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.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Rationale for XML Usage</span>

   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:

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

   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.





<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   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.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Specification of Requirements</span>

   In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
   "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as
   described in [<a href="#ref-1" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">1</a>].

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Value type notations for 'stronger' typing</span>

   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.

   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.

      &lt;?xml version="1.0" encoding="UTF-8"?&gt;

      &lt;!-- Phone book value type notation declarations --&gt;
      &lt;!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION
      value Type Fully_qualified_domain_name"&gt;
      &lt;!NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/NOTATION
      value Type IP_address"&gt;
      &lt;!NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/NOTATION
      value Type Base64_encoded_jpeg_image"&gt;
      &lt;!NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/NOTATION
      value Type Base64_encoded_gif_image"&gt;

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Container Element Definitions</span>

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  PhoneBook</span>

   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.



<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   Syntax:
      &lt;!ELEMENT phoneBook (
            pop+,
            setup*,
            support*,
            provider*)&gt;
      &lt;!ATTLIST phoneBook
            name    CDATA   #REQUIRED
            version CDATA   #REQUIRED &gt;

        phoneBook
      +-----------------------------------+
      | phoneBookName                (req)|
      | phoneBookVersion             (req)|
      | +-----------------------+         |
      | | pop                   |+   (req)|
      | +-----------------------+|        |
      |  + - - - - - - - - - - - +        |
      |                                   |
      | + - - - - - - - - - - - +         |
      | | setup                 |+   (opt)|
      | + - - - - - - - - - - - +|        |
      |  + - - - - - - - - - - - +        |
      |                                   |
      | + - - - - - - - - - - - +         |
      | | support               |+   (opt)|
      | + - - - - - - - - - - - +|        |
      |  + - - - - - - - - - - - +        |
      |                                   |
      | + - - - - - - - - - - - +         |
      | | provider              |+   (opt)|
      | + - - - - - - - - - - - +|        |
      |  + - - - - - - - - - - - +        |
      +-----------------------------------+

<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>.  phoneBook Attribute "name"</span>

   The phoneBook attribute "name" is an arbitrary string assigned as an
   identifier for a phone book.

<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>.  phoneBook Attribute "version"</span>

   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



<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   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.

<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  POP</span>

   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.

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

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






<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   Syntax:

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

      &lt;!ELEMENT pop ( %popInformation; )&gt;
      &lt;!ATTLIST pop
            entryVersion   CDATA   #REQUIRED&gt;

<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>.  pop Attribute "entryVersion"</span>

   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.

<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>.  Setup</span>

   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:

      &lt;!ENTITY % setupInformation
           "dnsServerAddress*,
            nntpServerName*,
            smtpServerName*,
            popServerName*,
            imapServerName*,



<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


            wwwProxyServerName*,
            ftpProxyServerName*,
            winsockProxyServerName*,
            defaultGatewayAddress?,
            userNamePrefix?,
            userNameSuffix?"&gt;

      &lt;!ELEMENT setup ( %setupInformation; )&gt;
      &lt;!ATTLIST setup
            id      ID      #REQUIRED&gt;

<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>.  Support</span>

   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:
      &lt;!ENTITY % supportInformation
           "(supportTelephoneNumber | supportMailtoURL)+"&gt;

      &lt;!ELEMENT support %supportInformation; &gt;
      &lt;!ATTLIST support
            id          ID         #REQUIRED
            language    NMTOKENS   #IMPLIED &gt;

<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>.  Provider</span>

   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:
      &lt;!ENTITY % providerInformation
           "providerName?,
            providerIcon?,
            wwwURL?,



<span class="grey">Riegel &amp; Zorn               Standards Track                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


            generalMailtoURL?,
            billingMailtoURL?,
            businessCategory?,
            x121Address?,
            registeredAddress?,
            destinationIndicator?,
            preferredDeliveryMethod?,
            telexNumber?,
            teletexTerminalIdentifier?,
            telephoneNumber?,
            internationalISDNNumber?,
            facsimileTelephoneNumber?,
            street?,
            postOfficeBox?,
            postalCode?,
            postalAddress?,
            physicalDeliveryOfficeName?,
            description?,
            supportPtr*"&gt;

      &lt;!ELEMENT provider ( %providerInformation; )&gt;
      &lt;!ATTLIST provider
            id      ID      #REQUIRED&gt;

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Information Element Definitions</span>

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  Information elements defined for the POP element</span>

<span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>.  Address</span>

   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 [<a href="#ref-4" title="&quot;Notation for national and international telephone numbers&quot;">4</a>] (e.g., "+ 1 234 5678").
   More detailed information may be available by optional attribute
   values.

   Syntax:
      &lt;!-- A network address for this POP --&gt;
      &lt;!ELEMENT address (#PCDATA)&gt;

<span class="h5"><a class="selflink" id="section-6.1.1.1" href="#section-6.1.1.1">6.1.1.1</a>.  address Attribute "family"</span>

   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



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   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:
      &lt;!-- Attribute values for address family --&gt;
      &lt;!ENTITY % addressFamily "(E164|X121)" &gt;
      &lt;!ATTLIST address
              family %addressFamily; #REQUIRED &gt;

<span class="h5"><a class="selflink" id="section-6.1.1.2" href="#section-6.1.1.2">6.1.1.2</a>.  address Attribute "countryCode"</span>

   The countryCode attribute indicates the international dialing prefix
   for the country in which the POP is located.

   Syntax:
      &lt;!-- ITU dialing code for the country in which this POP is located --&gt;
      &lt;!ATTLIST address
              countryCode CDATA #IMPLIED &gt;

<span class="h5"><a class="selflink" id="section-6.1.1.3" href="#section-6.1.1.3">6.1.1.3</a>.  address Attribute "areaCode"</span>

   The areaCode attribute contains the area or city code component of
   the telephone number in the 'address' element (if any) associated
   with this POP.

      &lt;!-- Area or city code component of the telephone number in the
           accessTelephoneNumber element associated with this POP --&gt;
      &lt;!ATTLIST address
              areaCode CDATA #IMPLIED &gt;

<span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>.  Media</span>

   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



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   Syntax:
      &lt;!-- The types of media supported by this POP --&gt;
      &lt;!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" &gt;
      &lt;!ELEMENT media %mediaTypes; &gt;

<span class="h5"><a class="selflink" id="section-6.1.2.1" href="#section-6.1.2.1">6.1.2.1</a>.  Modem Protocols</span>

   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
      &lt;!-- A modem media type element --&gt;
      &lt;!ENTITY % modemProtocols "(V21|V22|V29|V32|V32B|V34|V34B|V90)" &gt;
      &lt;!ELEMENT viaMODEM EMPTY&gt;
      &lt;!ATTLIST viaMODEM
              type %modemProtocols; #IMPLIED &gt;

<span class="h5"><a class="selflink" id="section-6.1.2.2" href="#section-6.1.2.2">6.1.2.2</a>.  ISDN Protocols</span>

   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





<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


      V120H  64k      ITU-T V.120
      X75    64k      ITU-T X.75
      HDLC   64k      <a href="./rfc1618">RFC 1618</a>

   Syntax:
      &lt;!-- An ISDN media type element --&gt;
      &lt;!ENTITY % isdnProtocols "(V110L|V110H|V120L|V120H|X75|HDLC)"&gt;
      &lt;!ELEMENT viaISDN EMPTY&gt;
      &lt;!ATTLIST viaISDN
              type %isdnProtocols; #IMPLIED &gt;

<span class="h5"><a class="selflink" id="section-6.1.2.3" href="#section-6.1.2.3">6.1.2.3</a>.  ATM Protocols</span>

   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:
      &lt;!-- An ATM media type element --&gt;
      &lt;!ENTITY % atmProtocols "(<a href="./rfc2364">RFC2364</a>)"&gt;
      &lt;!ELEMENT viaATM EMPTY&gt;
      &lt;!ATTLIST viaATM
              type %atmProtocols; #IMPLIED &gt;

<span class="h5"><a class="selflink" id="section-6.1.2.4" href="#section-6.1.2.4">6.1.2.4</a>.  Frame Relay Protocols</span>

   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:
      &lt;!-- A Frame Relay media type element --&gt;
      &lt;!ENTITY % frProtocols "(<a href="./rfc1973">RFC1973</a>)"&gt;
      &lt;!ELEMENT viaFR EMPTY&gt;
      &lt;!ATTLIST viaFR
              type %frProtocols; #IMPLIED &gt;

<span class="h5"><a class="selflink" id="section-6.1.2.5" href="#section-6.1.2.5">6.1.2.5</a>.  X.25 Protocols</span>

   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



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   protocols this element may be included repeatedly.  Currently only
   one protocol is defined.  Additional values may be registered by IANA
   in future.

   Syntax:
      &lt;!-- A X.25 media type element --&gt;
      &lt;!ENTITY % x25Protocols "(<a href="./rfc1598">RFC1598</a>)"&gt;
      &lt;!ELEMENT viaX25 EMPTY&gt;
      &lt;!ATTLIST viaX25
              type %x25Protocols; #IMPLIED &gt;

<span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>.  Minimum Data Rate</span>

   The minBitsPerSecond element indicates the minimum data rate (in
   bits/second) supported by the access devices at the POP.

   Syntax:
      &lt;!-- Minimum data rate supported by this POP in bits/second --&gt;
      &lt;!ELEMENT minBitsPerSecond (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.1.4" href="#section-6.1.4">6.1.4</a>.  Maximum Data Rate</span>

   The maxBitsPerSecond element indicates the maximum data rate (in
   bits/second) supported by the access devices at the POP.

   Syntax:
      &lt;!-- Maximum data rate supported by this POP in bits/second --&gt;
      &lt;!ELEMENT maxBitsPerSecond (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.1.5" href="#section-6.1.5">6.1.5</a>.  POP Properties</span>

   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 (<a href="./rfc1990">RFC 1990</a>)
      MOBIP      Mobile IP (<a href="./rfc2002">RFC 2002</a>)
      MCRX       Multicast Reception
      MCTX       Multicast Transmission

   Syntax:
      &lt;!-- A property characterizing this POP --&gt;
      &lt;!ENTITY % popProperties "(MPPP|MOBIP|MCRX|MCTX)" &gt;




<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


      &lt;!ELEMENT popProperty EMPTY&gt;
      &lt;!ATTLIST popProperty
              type %popProperties; #REQUIRED&gt;

<span class="h4"><a class="selflink" id="section-6.1.6" href="#section-6.1.6">6.1.6</a>.  Tunneling Protocols</span>

   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      <a href="./rfc2661">RFC 2661</a>   L2TP
      PPTP      <a href="./rfc2637">RFC 2637</a>   PPTP
      L2F       <a href="./rfc2341">RFC 2341</a>   L2F
      ATMP      <a href="./rfc2107">RFC 2107</a>   ATMP
      AHT       <a href="./rfc2402">RFC 2402</a>   IP AH Tunnel Mode
      ESPT      <a href="./rfc2406">RFC 2406</a>   IP ESP Tunnel Mode
      IPIP      <a href="./rfc1853">RFC 1853</a>   IP-IP
      MIP       <a href="./rfc2004">RFC 2004</a>   Minimal IP-IP
      GRE       <a href="./rfc1701">RFC 1701</a>   GRE

   Syntax:
      &lt;!-- A tunneling protocol supported by this POP --&gt;
      &lt;!ENTITY % tunnelingProtocols
              "(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" &gt;
      &lt;!ELEMENT tunnelProto EMPTY&gt;
      &lt;!ATTLIST tunnelProto
              type %tunnelingProtocols; #REQUIRED&gt;

<span class="h4"><a class="selflink" id="section-6.1.7" href="#section-6.1.7">6.1.7</a>.  Dialing Script</span>

   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:
      &lt;!-- The dial script to be used --&gt;
      &lt;!ELEMENT dialScript (#PCDATA)&gt;
      &lt;!ATTLIST dialScript
              type CDATA #IMPLIED &gt;







<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h4"><a class="selflink" id="section-6.1.8" href="#section-6.1.8">6.1.8</a>.  Pricing Information</span>

   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:
      &lt;!-- Pricing information for this POP --&gt;
      &lt;!ELEMENT pricing (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.1.9" href="#section-6.1.9">6.1.9</a>.  City</span>

   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:
      &lt;!-- The name of the city in which this POP is located --&gt;
      &lt;!ELEMENT city (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.1.10" href="#section-6.1.10">6.1.10</a>.  Region</span>

   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:
      &lt;!-- The name of the region in which this POP is located --&gt;
      &lt;!ELEMENT region (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.1.11" href="#section-6.1.11">6.1.11</a>.  Country</span>

   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:
      &lt;!-- The name of the country in which this POP is located --&gt;
      &lt;!ELEMENT country (#PCDATA)&gt;







<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h4"><a class="selflink" id="section-6.1.12" href="#section-6.1.12">6.1.12</a>.  POP Setup</span>

   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:
      &lt;!-- Reference for setup information for this POP --&gt;
      &lt;!ELEMENT setupPtr EMPTY&gt;
      &lt;!ATTLIST setupPtr
            setupID   IDREFS  #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.1.13" href="#section-6.1.13">6.1.13</a>.  POP Support</span>

   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:
      &lt;!-- Reference for support information for this POP --&gt;
      &lt;!ELEMENT supportPtr EMPTY&gt;
      &lt;!ATTLIST supportPtr
            supportID IDREFS  #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.1.14" href="#section-6.1.14">6.1.14</a>.  POP Provider</span>

   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:
      &lt;!-- Reference for provider information for this POP --&gt;
      &lt;!ELEMENT providerPtr EMPTY&gt;
      &lt;!ATTLIST providerPtr
            providerID IDREFS  #IMPLIED&gt;

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  Information elements defined for the Setup element</span>

<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>.  DNS Server Address</span>

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






<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   Syntax:
      &lt;!-- Domain Name Server IP address --&gt;
      &lt;!ELEMENT dnsServerAddress (#PCDATA)&gt;
      &lt;!ATTLIST dnsServerAddress
              value NOTATION (IPADR) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>.  NNTP Server Name</span>

   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:
      &lt;!-- Name of an NNTP server --&gt;
      &lt;!ELEMENT nntpServerName (#PCDATA)&gt;
      &lt;!ATTLIST nntpServerName
              value NOTATION (FQDN) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>.  SMTP Server Name</span>

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

   Syntax:
      &lt;!-- Name of an SMTP mail server --&gt;
      &lt;!ELEMENT smtpServerName (#PCDATA)&gt;
      &lt;!ATTLIST smtpServerName
              value NOTATION (FQDN) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>.  POP3 Server Name</span>

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

   Syntax:
      &lt;!-- Name of an POP3 mail server --&gt;
      &lt;!ELEMENT popServerName (#PCDATA)&gt;
      &lt;!ATTLIST popServerName
              value NOTATION (FQDN) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.5" href="#section-6.2.5">6.2.5</a>.  IMAP Server Name</span>

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




<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   Syntax:
      &lt;!-- Name of an IMAP4 server --&gt;
      &lt;!ELEMENT imapServerName (#PCDATA)&gt;
      &lt;!ATTLIST imapServerName
              value NOTATION (FQDN) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.6" href="#section-6.2.6">6.2.6</a>.  WWW Proxy</span>

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

   Syntax:
      &lt;!-- Name of an WWW Proxy --&gt;
      &lt;!ELEMENT wwwProxyServerName (#PCDATA)&gt;
      &lt;!ATTLIST wwwProxyServerName
              value NOTATION (FQDN) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.7" href="#section-6.2.7">6.2.7</a>.  FTP Proxy</span>

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

   Syntax:
      &lt;!-- Name of an FTP Proxy --&gt;
      &lt;!ELEMENT ftpProxyServerName (#PCDATA)&gt;
      &lt;!ATTLIST ftpProxyServerName
              value NOTATION (FQDN) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.8" href="#section-6.2.8">6.2.8</a>.  Winsock Proxy</span>

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

   Syntax:
      &lt;!-- Name of an Winsock Proxy --&gt;
      &lt;!ELEMENT winsockProxyServerName (#PCDATA)&gt;
      &lt;!ATTLIST winsockProxyServerName
              value NOTATION (FQDN) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.9" href="#section-6.2.9">6.2.9</a>.  Default Gateway Address</span>

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



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   Syntax:
      &lt;!-- Default Gateway IP address (in dotted decimal notation) --&gt;
      &lt;!ELEMENT defaultGatewayAddress (#PCDATA)&gt;
      &lt;!ATTLIST defaultGatewayAddress
              value NOTATION (IPADR) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.2.10" href="#section-6.2.10">6.2.10</a>.  User Name Suffix</span>

   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.

   Syntax:
      &lt;!-- User Name suffix --&gt;
      &lt;!ELEMENT userNameSuffix (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.2.11" href="#section-6.2.11">6.2.11</a>.  User Name Prefix</span>

   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:
      &lt;!-- User Name prefix --&gt;
      &lt;!ELEMENT userNamePrefix (#PCDATA)&gt;

<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>.  Information elements defined for the support element</span>

<span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>.  Support Telephone Number</span>

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

   Syntax:
      &lt;!-- The number to be dialed to contact customer support
           for this POP or provider --&gt;
      &lt;!ELEMENT supportTelephoneNumber (#PCDATA)&gt;




<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h4"><a class="selflink" id="section-6.3.2" href="#section-6.3.2">6.3.2</a>.  Support Email Address</span>

   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.

   Syntax:
      &lt;!-- A Uniform Resource Locator for the provider's customer
           support email address --&gt;
      &lt;!ELEMENT supportMailtoURL (#PCDATA)&gt;

<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>.  Information elements defined for the provider element</span>

<span class="h4"><a class="selflink" id="section-6.4.1" href="#section-6.4.1">6.4.1</a>.  Provider Name</span>

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

   Syntax:
      &lt;!-- The name of the provider --&gt;
      &lt;!ELEMENT providerName (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.4.2" href="#section-6.4.2">6.4.2</a>.  Provider Icon</span>

   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:
      &lt;!-- An icon in BASE64 encoded JPEG or GIF format --&gt;
      &lt;!ELEMENT providerIcon (#PCDATA)&gt;
      &lt;!ATTLIST providerIcon
              value NOTATION (B64JPG | B64GIF) #IMPLIED&gt;

<span class="h4"><a class="selflink" id="section-6.4.3" href="#section-6.4.3">6.4.3</a>.  Provider's World Wide Web URL</span>

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

   Syntax:
      &lt;!-- A Uniform Resource Locator for the provider's home page --&gt;
      &lt;!ELEMENT wwwURL (#PCDATA)&gt;








<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h4"><a class="selflink" id="section-6.4.4" href="#section-6.4.4">6.4.4</a>.  Provider's Main Email Address</span>

   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.

   Syntax:
      &lt;!-- A Uniform Resource Locator for the provider's
                  email address --&gt;
      &lt;!ELEMENT generalMailtoURL (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.4.5" href="#section-6.4.5">6.4.5</a>.  Billing Inquiry Email Address</span>

   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.

   Syntax:
      &lt;!-- A Uniform Resource Locator for the email
                  address to be used for billing inquiries --&gt;
      &lt;!ELEMENT billingMailtoURL (#PCDATA)&gt;

<span class="h4"><a class="selflink" id="section-6.4.6" href="#section-6.4.6">6.4.6</a>.  Further elements</span>

   The remainder of the information elements of the provider element are
   described in principle in [<a href="#ref-3" title="&quot;The COSINE and Internet X.500 Schema&quot;">3</a>].

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Complete XML DTD for the roaming phone book</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;

   &lt;!-- Parameter entity declaration --&gt;
   &lt;!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --&gt;
   &lt;!-- This section will be maintained by IANA and can be direct
        referenced by the DTD specification by means of an external
        parameter entity. --&gt;

   &lt;!ENTITY % addressFamily "(E164|X121)" &gt;

   &lt;!ENTITY % mediaTypes "(viaMODEM|viaISDN|viaATM|viaFR|viaX25)+" &gt;

   &lt;!ENTITY % modemProtocols "(V21|V22|V29|V32|V32B|V34|V34B|V90)" &gt;

   &lt;!ENTITY % isdnProtocols "(V110L|V110H|V120L|V120H|X75|HDLC)"&gt;

   &lt;!ENTITY % atmProtocols "(<a href="./rfc2364">RFC2364</a>)"&gt;




<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   &lt;!ENTITY % frProtocols "(<a href="./rfc1973">RFC1973</a>)"&gt;

   &lt;!ENTITY % x25Protocols "(<a href="./rfc1598">RFC1598</a>)"&gt;

   &lt;!ENTITY % popProperties "(MPPP|MOBIP|MCRX|MCTX)" &gt;

   &lt;!ENTITY % tunnelingProtocols
        "(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" &gt;

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

   &lt;!ENTITY % setupInformation
        "dnsServerAddress*,
         nntpServerName*,
         smtpServerName*,
         popServerName*,
         imapServerName*,
         wwwProxyServerName*,
         ftpProxyServerName*,
         winsockProxyServerName*,
         defaultGatewayAddress?,
         userNamePrefix?,
         userNameSuffix?"&gt;

   &lt;!ENTITY % supportInformation
        "(supportTelephoneNumber|supportMailtoURL)+"&gt;

   &lt;!ENTITY % providerInformation
        "providerName?,
         providerIcon?,
         wwwURL?,
         generalMailtoURL?,
         billingMailtoURL?,
         businessCategory?,



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


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

   &lt;!-- ++++++++++++++ End of IANA maintained section ++++++++++ --&gt;

   &lt;!-- Phone book value type notation declarations --&gt;
   &lt;!NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/NOTATION
   value Type Fully_qualified_domain_name"&gt;
   &lt;!NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/NOTATION
   value Type IP_address"&gt;
   &lt;!NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/NOTATION
   value Type Base64_encoded_jpeg_image"&gt;
   &lt;!NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/NOTATION
   value Type Base64_encoded_gif_image"&gt;

   &lt;!-- Phone book element declarations --&gt;
   &lt;!ELEMENT phoneBook (
         pop+,
         setup*,
         support*,
         provider*) &gt;
   &lt;!ATTLIST phoneBook
         name    CDATA   #REQUIRED
         version CDATA   #REQUIRED &gt;

   &lt;!ELEMENT pop ( %popInformation; )&gt;
   &lt;!ATTLIST pop
         entryVersion   CDATA   #REQUIRED&gt;

   &lt;!ELEMENT setup ( %setupInformation; )&gt;
   &lt;!ATTLIST setup
         id      ID      #REQUIRED&gt;

   &lt;!ELEMENT support ( %supportInformation; )&gt;



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   &lt;!ATTLIST support
         id          ID         #REQUIRED
         language    NMTOKENS   #IMPLIED &gt;

   &lt;!ELEMENT provider ( %providerInformation; )&gt;
   &lt;!ATTLIST provider
         id      ID      #REQUIRED&gt;

   &lt;!-- Information elements for pop --&gt;
   &lt;!ELEMENT address (#PCDATA)&gt;
   &lt;!ATTLIST address
           family       %addressFamily;  #REQUIRED
           countryCode  CDATA            #IMPLIED
           areaCode     CDATA            #IMPLIED &gt;

   &lt;!ELEMENT media %mediaTypes; &gt;

   &lt;!ELEMENT viaMODEM EMPTY&gt;
   &lt;!ATTLIST viaMODEM
           type %modemProtocols; #IMPLIED &gt;

   &lt;!ELEMENT viaISDN EMPTY&gt;
   &lt;!ATTLIST viaISDN
           type %isdnProtocols; #IMPLIED &gt;

   &lt;!ELEMENT viaATM EMPTY&gt;
   &lt;!ATTLIST viaATM
           type %atmProtocols; #IMPLIED &gt;

   &lt;!ELEMENT viaFR EMPTY&gt;
   &lt;!ATTLIST viaFR
           type %frProtocols; #IMPLIED &gt;

   &lt;!ELEMENT viaX25 EMPTY&gt;
   &lt;!ATTLIST viaX25
           type %x25Protocols; #IMPLIED &gt;

   &lt;!ELEMENT minBitsPerSecond (#PCDATA)&gt;

   &lt;!ELEMENT maxBitsPerSecond (#PCDATA)&gt;

   &lt;!ELEMENT popProperty EMPTY&gt;
   &lt;!ATTLIST popProperty
           type         %popProperties;  #REQUIRED &gt;

   &lt;!ELEMENT tunnelProto EMPTY&gt;
   &lt;!ATTLIST tunnelProto
           type   %tunnelingProtocols;   #REQUIRED &gt;



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   &lt;!ELEMENT dialScript (#PCDATA)&gt;
   &lt;!ATTLIST dialScript
           type CDATA #IMPLIED &gt;

   &lt;!ELEMENT pricing (#PCDATA)&gt;

   &lt;!ELEMENT city (#PCDATA)&gt;

   &lt;!ELEMENT region (#PCDATA)&gt;

   &lt;!ELEMENT country (#PCDATA)&gt;

   &lt;!ELEMENT setupPtr EMPTY&gt;
   &lt;!ATTLIST setupPtr
         setupID   IDREFS  #IMPLIED&gt;

   &lt;!ELEMENT supportPtr EMPTY&gt;
   &lt;!ATTLIST supportPtr
         supportID IDREFS  #IMPLIED&gt;

   &lt;!ELEMENT providerPtr EMPTY&gt;
   &lt;!ATTLIST providerPtr
         providerID IDREFS  #IMPLIED&gt;

   &lt;!-- Information elements for setup --&gt;
   &lt;!ELEMENT dnsServerAddress (#PCDATA)&gt;
   &lt;!ATTLIST dnsServerAddress
           value NOTATION (IPADR) #IMPLIED&gt;

   &lt;!ELEMENT nntpServerName (#PCDATA)&gt;
   &lt;!ATTLIST nntpServerName
           value NOTATION (FQDN) #IMPLIED&gt;

   &lt;!ELEMENT smtpServerName (#PCDATA)&gt;
   &lt;!ATTLIST smtpServerName
           value NOTATION (FQDN) #IMPLIED&gt;

   &lt;!ELEMENT popServerName (#PCDATA)&gt;
   &lt;!ATTLIST popServerName
           value NOTATION (FQDN) #IMPLIED&gt;

   &lt;!ELEMENT imapServerName (#PCDATA)&gt;
   &lt;!ATTLIST imapServerName
           value NOTATION (FQDN) #IMPLIED&gt;

   &lt;!ELEMENT wwwProxyServerName (#PCDATA)&gt;
   &lt;!ATTLIST wwwProxyServerName
           value NOTATION (FQDN) #IMPLIED&gt;



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   &lt;!ELEMENT ftpProxyServerName (#PCDATA)&gt;
   &lt;!ATTLIST ftpProxyServerName
           value NOTATION (FQDN) #IMPLIED&gt;

   &lt;!ELEMENT winsockProxyServerName (#PCDATA)&gt;
   &lt;!ATTLIST winsockProxyServerName
           value NOTATION (FQDN) #IMPLIED&gt;

   &lt;!ELEMENT defaultGatewayAddress (#PCDATA)&gt;
   &lt;!ATTLIST defaultGatewayAddress
           value NOTATION (IPADR) #IMPLIED&gt;

   &lt;!ELEMENT userNameSuffix (#PCDATA)&gt;

   &lt;!ELEMENT userNamePrefix (#PCDATA)&gt;

   &lt;!-- Information elements for support --&gt;
   &lt;!ELEMENT supportTelephoneNumber (#PCDATA)&gt;

   &lt;!ELEMENT supportMailtoURL (#PCDATA)&gt;

   &lt;!-- Information elements for provider --&gt;
   &lt;!ELEMENT providerName (#PCDATA)&gt;

   &lt;!ELEMENT providerIcon (#PCDATA)&gt;
   &lt;!ATTLIST providerIcon
           value NOTATION (B64JPG|B64GIF) #IMPLIED&gt;

   &lt;!ELEMENT wwwURL (#PCDATA)&gt;

   &lt;!ELEMENT generalMailtoURL (#PCDATA)&gt;

   &lt;!ELEMENT billingMailtoURL (#PCDATA)&gt;

   &lt;!-- Further provider elements according to <a href="./rfc1274">RFC1274</a> --&gt;

   &lt;!ELEMENT businessCategory (#PCDATA)&gt;

   &lt;!ELEMENT x121Address (#PCDATA)&gt;

   &lt;!ELEMENT registeredAddress (#PCDATA)&gt;

   &lt;!ELEMENT destinationIndicator (#PCDATA)&gt;

   &lt;!ELEMENT preferredDeliveryMethod (#PCDATA)&gt;

   &lt;!ELEMENT telexNumber (#PCDATA)&gt;




<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   &lt;!ELEMENT teletexTerminalIdentifier (#PCDATA)&gt;

   &lt;!ELEMENT telephoneNumber (#PCDATA)&gt;

   &lt;!ELEMENT internationalISDNNumber (#PCDATA)&gt;

   &lt;!ELEMENT facsimileTelephoneNumber (#PCDATA)&gt;

   &lt;!ELEMENT street (#PCDATA)&gt;

   &lt;!ELEMENT postOfficeBox (#PCDATA)&gt;

   &lt;!ELEMENT postalCode (#PCDATA)&gt;

   &lt;!ELEMENT postalAddress (#PCDATA)&gt;

   &lt;!ELEMENT physicalDeliveryOfficeName (#PCDATA)&gt;

   &lt;!ELEMENT description (#PCDATA)&gt;

   &lt;!-- end of dtd --&gt;

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Security Considerations</span>

   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.

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  IANA Considerations</span>

   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.

   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



<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


   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.

   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.

<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>.  Registration of new attribute values</span>

   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 [<a href="#ref-6" title="">6</a>].

<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>.  Registration of new information elements</span>

   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 [<a href="#ref-6" title="">6</a>].  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.









<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  References</span>

   [<a id="ref-1">1</a>]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-2">2</a>]  Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, <a href="./rfc1700">RFC 1700</a>,
        October 1994.

   [<a id="ref-3">3</a>]  Barker, P. and S. Kille, "The COSINE and Internet X.500 Schema",
        <a href="./rfc1274">RFC 1274</a>, November 1991.

   [<a id="ref-4">4</a>]  ITU Rec. E.123, "Notation for national and international
        telephone numbers", 1988.

   [<a id="ref-5">5</a>]  "Extensible Markup Language (XML) 1.0" W3C Recommendation 10-
        February-1998 <a href="http://www.w3.org/TR/1998/REC-xml-19980210">http://www.w3.org/TR/1998/REC-xml-19980210</a>

   [<a id="ref-6">6</a>]  Narten, T. and  H. Alvestrand, "Guidelines for Writing an IANA
        Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>, October 1998.
































<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>.  Appendix: Examples</span>

<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>.  The most simple example</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;!DOCTYPE phoneBook SYSTEM "roamPhoneBook.dtd"&gt;
   &lt;phoneBook name="minimalExample" version="1"&gt;
      &lt;pop entryVersion="1"&gt;
         &lt;address family="E164"&gt;+1 234 5678901&lt;/address&gt;
         &lt;media&gt;&lt;viaMODEM/&gt;&lt;/media&gt;
      &lt;/pop&gt;
   &lt;/phoneBook&gt;

<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>.  A more comprehensive example</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;!DOCTYPE phoneBook SYSTEM "roamPhoneBook.dtd"&gt;
   &lt;phoneBook name="KNF_simple" version="1"&gt;
      &lt;pop entryVersion="1"&gt;
         &lt;address family="E164" countryCode="49"&gt;+49913130540&lt;/address&gt;
         &lt;media&gt;
            &lt;viaMODEM type="V90"/&gt;
            &lt;viaMODEM type="V34B"/&gt;
            &lt;viaISDN type="HDLC"/&gt;
         &lt;/media&gt;
         &lt;setup&gt;
            &lt;dnsServerAddress&gt;192.168.147.5&lt;/dnsServerAddress&gt;
            &lt;dnsServerAddress&gt;193.175.24.33&lt;/dnsServerAddress&gt;
         &lt;/setup&gt;
      &lt;/pop&gt;
      &lt;support id="KNF_main" language="EN DE"&gt;
         &lt;supportMailtoURL&gt;mailto:support@franken.de&lt;/supportMailtoURL&gt;
         &lt;supportTelephoneNumber&gt;+499123968066&lt;/supportTelephoneNumber&gt;
      &lt;/support&gt;
   &lt;/phoneBook&gt;

<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>.  Acknowledgments</span>

   Thanks to Pat Calhoun, Bernard Aboba, Jay Farhat, Butch Anton,
   Quentin Miller, and Ken Crocker for salient input and review.











<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>.  Authors' Addresses</span>

   Questions about this memo can be directed to:

   Max Riegel
   Siemens AG
   Hofmannstr. 51
   Munich, 81359
   Germany

   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

   Phone:  +1 425 438 8218
   EMail:  gwz@cisco.com





























<span class="grey">Riegel &amp; Zorn               Standards Track                    [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc3017">RFC 3017</a>           Roaming Access Phone Book XML DTD       December 2000</span>


<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>.  Full Copyright Statement</span>

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   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.



















Riegel &amp; Zorn               Standards Track                    [Page 33]
</pre>