As per Relevance of the word december, we have this rfc below:
Network Working Group M.
Request for Comments: 3017 Siemens
Category: Standards Track G.
Cisco
December 2000
XML DTD for Roaming Access Phone
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document defines the syntax as well as the semantics of
information to be included in the phone book for
applications. It comprises the information necessary to select
most appropriate ISP and to configure the host to get access to
network of the provider. The specification consists of a small set
required information elements and a variety of possible extensions
All data is specified in XML [5] (Extensible Markup Language)
leading to a concise XML DTD (Document Type Declaration) for
phone book
Table of
1. Introduction ............................................. 3
2. Rationale for XML Usage .................................. 4
3. Specification of Requirements ............................ 5
4. Value type notations for 'stronger' typing ............... 5
5. Container Element Definitions ............................ 5
5.1. PhoneBook ............................................ 5
5.1.1. phoneBook Attribute "name" ........................ 6
5.1.2. phoneBook Attribute "version" ..................... 6
5.2. POP .................................................. 7
5.2.1. pop Attribute "entryVersion" ...................... 8
5.3. Setup ................................................ 8
5.4. Support .............................................. 9
5.5. Provider ............................................. 9
Riegel & Zorn Standards Track [Page 1]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
6. Information Element Definitions .......................... 10
6.1. Information elements defined for the POP element ..... 10
6.1.1. Address ........................................... 10
6.1.1.1. address Attribute "family" ..................... 10
6.1.1.2. address Attribute "countryCode" ................ 11
6.1.1.3. address Attribute "areaCode" ................... 11
6.1.2. Media ............................................. 11
6.1.2.1. Modem Protocols ................................ 12
6.1.2.2. ISDN Protocols ................................. 12
6.1.2.3. ATM Protocols .................................. 13
6.1.2.4. Frame Relay Protocols .......................... 13
6.1.2.5. X.25 Protocols ................................. 13
6.1.3. Minimum Data Rate ................................. 14
6.1.4. Maximum Data Rate ................................. 14
6.1.5. POP Properties .................................... 14
6.1.6. Tunneling Protocols ............................... 15
6.1.7. Dialing Script .................................... 15
6.1.8. Pricing Information ............................... 16
6.1.9. City .............................................. 16
6.1.10. Region ........................................... 16
6.1.11. Country .......................................... 16
6.1.12. POP Setup ........................................ 17
6.1.13. POP Support ...................................... 17
6.1.14. POP Provider ..................................... 17
6.2. Information elements defined for the Setup element ... 17
6.2.1. DNS Server Address ................................ 17
6.2.2. NNTP Server Name .................................. 18
6.2.3. SMTP Server Name .................................. 18
6.2.4. POP3 Server Name .................................. 18
6.2.5. IMAP Server Name .................................. 18
6.2.6. WWW Proxy ......................................... 19
6.2.7. FTP Proxy ......................................... 19
6.2.8. Winsock Proxy ..................................... 19
6.2.9. Default Gateway Address ........................... 19
6.2.10. User Name Suffix ................................. 20
6.2.11. User Name Prefix ................................. 20
6.3. Information elements defined for the support element.. 20
6.3.1. Support Telephone Number .......................... 20
6.3.2. Support Email Address ............................. 21
6.4. Information elements defined for the provider element. 21
6.4.1. Provider Name ..................................... 21
6.4.2. Provider Icon ..................................... 21
6.4.3. Provider's World Wide Web URL ..................... 21
6.4.4. Provider's Main Email Address ..................... 22
6.4.5. Billing Inquiry Email Address ..................... 22
6.4.6. Further elements .................................. 22
7. Complete XML DTD for the roaming phone book .............. 22
8. Security Considerations .................................. 28
Riegel & Zorn Standards Track [Page 2]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
9. IANA Considerations ...................................... 28
9.1. Registration of new attribute values ................. 29
9.2. Registration of new information elements ............. 29
10. References .............................................. 30
11. Appendix: Examples ...................................... 31
11.1. The most simple example ............................. 31
11.2. A more comprehensive example ........................ 31
12. Acknowledgments ......................................... 31
13. Authors' Addresses ...................................... 32
14. Full Copyright Statement ................................ 33
1.
Roaming applications depend on the delivery of information
provided services and the procedures to get connected to the
from the roaming consortium to the individual users as well as
the operators of the network access servers, normally the members
the roaming consortium, and the roaming consortium
"phone book
+------+ +--+
| | | ++
| ISP1 | -- | | --+
| | +---+ \ "phone book
+------+ \ +------+
+------+ +--+ \_ | | +--+ +------+
| | | ++ | | | ++ | |
| ISP2 | -- | | -->>--- | | --- | | ->> | USER |
| | +---+ _ | | +---+ | |
+------+ / | | +------+
+------+ +--+ / +------+
| | | ++ /
| ISP# | -- | | --+
| | +---+
+------+
The roaming consortium assembles from the individual contributions
the providers belonging to the consortium a unified version of
phone book for usage by the customers. Probably different groups
users get different versions of a phone book adapted to
particular needs. Even users might generate different
especially suited to particular applications from the
received from the roaming consortium, e.g., retrieving only
for a particular country or extracting all access points
wireless connectivity
Riegel & Zorn Standards Track [Page 3]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
Therefore it is desirable to define a highly portable and well
structure of the phone book to enable easy generation
postprocessing. Goals of this document include
- Creating a flexible, extensible and robust
upon which to build a standard phone book
- Promoting a standard phone book format, to
interoperability between ISPs and roaming consortia
well as to enable automatic extraction of
data by a wide variety of devices
- Defining a compact structure containing the
information for the roaming user, to allow for
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
define any kind of phone book update or transfer protocol
2. Rationale for XML
XML is rapidly becoming a standard format for data exchange
different applications also taking into account the transfer
access of data over the web. XML is used as syntax for
the structure and content of a roaming phone book to
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
-
-
- Integration with
Extensibility is important because phone books are living documents
as such, it is unlikely that all the semantic requirements
arbitrary Internet service providers (ISPs) would be met by a
scheme, no matter how well thought out. Phone book designers must
free to create new attributes in a well-understood fashion to
changing business needs
Flexibility is required of the attribute definition syntax for
of the same reasons that semantic extensibility is necessary. If
assume that phone book designers may need to define elements
arbitrary type, the syntax chosen must be able to represent
data objects cleanly. Using XML for describing the data content
the phone book fits this bill nicely, since it can be used
unambiguously describe virtually any data type
Riegel & Zorn Standards Track [Page 4]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
Integration with directories: although it is unlikely that
books will be stored in the directory due to
considerations, the creation of a XML DTD describing phone
content leaves that option open, with relatively little
effort required to implement it
3. Specification of
In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
"recommended", "SHOULD", and "SHOULD NOT", are to be interpreted
described in [1].
4. Value type notations for 'stronger'
XML DTDs do not currently have capabilities for 'strong typing'
the content of elements. The only type definition foreseen in
base specification is "#PCDATA", 'parsable character data'.
might be sufficient and is used throughout this document to
elements containing information mainly aimed for interpretation
human beings
To enable a more concise description of the content of
elements several value type notations are introduced. This
for a more detailed type description of the content of elements
cases where it seems to be desirable
encoding="UTF-8"?>
NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/
value Type Fully_qualified_domain_name">
NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/
value Type IP_address">
NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/
value Type Base64_encoded_jpeg_image">
NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/
value Type Base64_encoded_gif_image">
5. Container Element
5.1.
The phoneBook element is the basic container for phone book entries
It has two attributes, a phone book name and a phone book
number (applying to the phone book as a whole), and always
one or more pop elements. A phoneBook element may also
multiple Setup, Support and Provider elements, if they are
to by more than one pop element
Riegel & Zorn Standards Track [Page 5]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
Syntax
pop+,
setup*,
support*,
provider*)>
name CDATA #
version CDATA #REQUIRED >
+-----------------------------------+
| phoneBookName (req)|
| phoneBookVersion (req)|
| +-----------------------+ |
| | pop |+ (req)|
| +-----------------------+| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | setup |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | support |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
| |
| + - - - - - - - - - - - + |
| | provider |+ (opt)|
| + - - - - - - - - - - - +| |
| + - - - - - - - - - - - + |
+-----------------------------------+
5.1.1. phoneBook Attribute "name
The phoneBook attribute "name" is an arbitrary string assigned as
identifier for a phone book
5.1.2. phoneBook Attribute "version
The phoneBookVersion attribute is an integer representing the
of the phone book; it is a monotonically increasing counter
should be incremented each time the phone book is modified.
element can be used by a server to help decide what (if any)
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
Riegel & Zorn Standards Track [Page 6]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
including in the request the version number of its current
book. If the client's phone book version is not the same as
server's current phone book version, the server can easily
appropriate action, e.g., reply with a URL pointing to a
containing the differences between the client and server phone books
5.2.
The pop element contains information elements relevant to
network points of presence (POPs). The required information
are addrFamily, address, media and entryVersion. The media
represents the media types supported by the POP, while
entryVersion element is a monotonically-increasing integer
should be incremented whenever the object is modified
The following information elements are currently defined for the
element. Additional information elements may be defined by IANA
future
+-----------------------------------+
| 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)|
| + - - - - - - - - - - - - + |
+-----------------------------------+
Riegel & Zorn Standards Track [Page 7]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
Syntax
"address
media+,
minBitsPerSecond?,
maxBitsPerSecond?,
popProperty*,
tunnelProto*,
dialScript?,
pricingInformation?,
city?,
region?,
country?,
(setup | setupPtr)?,
(support | supportPtr)?,
(provider |providerPtr)?">
entryVersion CDATA #REQUIRED
5.2.1. pop Attribute "entryVersion
The entryVersion attribute is an integer representing the version
the POP object; it is a monotonically increasing counter which
be incremented each time the object is modified. This attribute
be useful in merging and updating phone books
5.3.
The Setup element includes information elements which
services which may change from provider to provider or even from
to POP. Some of the values contained in these information
may be available by other means (e.g., DHCP), but others may not
The following information elements are currently defined for
Setup element. Additional information elements may be defined
IANA in future
Syntax
"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?">
id ID #REQUIRED
5.4.
The Support element includes those information elements that
pertinent to the provision of customer support for a POP or provider
Languages spoken by the staff at the support center might
specified by multiple entries for the attribute value language
Additional information elements for the Support element may
defined by IANA in future
Syntax
"(supportTelephoneNumber | supportMailtoURL)+">
id ID #
language NMTOKENS #IMPLIED >
5.5.
The Provider element contains information elements pertaining to
general business operations of a given network service provider.
information elements include such things as telephone number,
address, etc., as well as URLs for e-mail and a World Wide Web site
A Provider element may also contain a reference to
information
Currently the following information elements are defined for
Provider element. Additional information elements may be defined
IANA in future
Syntax
"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*">
provider ( %providerInformation; )>
id ID #REQUIRED
6. Information Element
6.1. Information elements defined for the POP
6.1.1.
The address element provides the information representing the
of the POP. For POPs offering dial-up network access, the
element will at least contain an IA5 string representing a
number, formatted in standard fashion [4] (e.g., "+ 1 234 5678").
More detailed information may be available by optional
values
Syntax
6.1.1.1. address Attribute "family
The attribute family of the element address defines the
family to which the element value belongs. For POPs offering dial-
network access, the addrFamily attribute will generally contain
value for a telephone network based address family. Currently
following attribute values are defined. Additional values may
Riegel & Zorn Standards Track [Page 10]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
registered by IANA in future
Value
------ ------------------------------------------
E164 ITU-T E.164 (PSTN, SMDS, Frame Relay, ATM
X121 ITU-T X.121 (X.25, Frame Relay
Syntax
family %addressFamily; #REQUIRED >
6.1.1.2. address Attribute "countryCode
The countryCode attribute indicates the international dialing
for the country in which the POP is located
Syntax
countryCode CDATA #IMPLIED >
6.1.1.3. address Attribute "areaCode
The areaCode attribute contains the area or city code component
the telephone number in the 'address' element (if any)
with this POP
areaCode CDATA #IMPLIED >
6.1.2.
The media element is a container describing the types of media
related protocols supported by this POP. The following media
are currently defined. Additional types may be registered by IANA
future
Value Media
-------- -----------
viaMODEM
viaISDN
viaATM
viaFR Frame
viaX25 X.25
Riegel & Zorn Standards Track [Page 11]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
Syntax
6.1.2.1. Modem
The viaMODEM element is an empty element representing by its
type attribute the modem protocol supported by the access
that can be reached at address. To define multiple
protocols this element may be included repeatedly. The
defined modem protocol types are listed in the table below
Additional values may be registered by IANA in future
Value Duplex Speed
----- ------ ----- -------------
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.32
V34 Full 28.8k ITU-T V.34
V34B Full 33.6k ITU-T V.34
V90 Full 56k ITU-T V.90
type %modemProtocols; #IMPLIED >
6.1.2.2. ISDN
The viaISDN element is an empty element representing by its
type attribute the ISDN protocol supported by the access devices
can be reached at address. To define multiple available
this element may be included repeatedly. The initially defined
protocol types are listed in the table below. Additional values
be registered by IANA in future
Value Speed
----- ----- -----------
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
type %isdnProtocols; #IMPLIED >
6.1.2.3. ATM
The viaATM element is an empty element representing by its
type attribute a particular protocol supported by the access
that can be reached at address. To define multiple
protocols this element may be included repeatedly. Currently
one protocol is defined. Additional values may be registered by
in future
Syntax
type %atmProtocols; #IMPLIED >
6.1.2.4. Frame Relay
The viaFR element is an empty element representing by its
type attribute the particular protocol supported by the
devices that can be reached at address. To define multiple
protocols this element may be included repeatedly. Currently
one protocol is defined. Additional values may be registered by
in future
Syntax
type %frProtocols; #IMPLIED >
6.1.2.5. X.25
The viaX25 element is an empty element representing by its
type attribute the particular protocol supported by the
devices that can be reached at address. To define multiple
Riegel & Zorn Standards Track [Page 13]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
protocols this element may be included repeatedly. Currently
one protocol is defined. Additional values may be registered by
in future
Syntax
type %x25Protocols; #IMPLIED >
6.1.3. Minimum Data
The minBitsPerSecond element indicates the minimum data rate (
bits/second) supported by the access devices at the POP
Syntax
6.1.4. Maximum Data
The maxBitsPerSecond element indicates the maximum data rate (
bits/second) supported by the access devices at the POP
Syntax
6.1.5. POP
The popProperty element is an empty element representing by
attribute value a particular property of this POP. To
multiple available protocols this element might be included
times. The initially defined properties are listed in the
below. Additional values may be registered by IANA in future
Value
------ ----------------------
MPPP Multilink PPP (RFC 1990)
MOBIP Mobile IP (RFC 2002)
MCRX Multicast
MCTX Multicast
Syntax
Riegel & Zorn Standards Track [Page 14]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
type %popProperties; #REQUIRED
6.1.6. Tunneling
The tunnelProto element is an empty element representing by
attribute a tunneling protocol supported by this POP. To
multiple available protocols this element might be included
times. The initially defined values are listed in the table below
Additional values may be registered by IANA in future
Value
------ ------------------
L2TP RFC 2661 L2
PPTP RFC 2637
L2F RFC 2341 L2
ATMP RFC 2107
AHT RFC 2402 IP AH Tunnel
ESPT RFC 2406 IP ESP Tunnel
IPIP RFC 1853 IP-
MIP RFC 2004 Minimal IP-
GRE RFC 1701
Syntax
"(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" >
type %tunnelingProtocols; #REQUIRED
6.1.7. Dialing
The dialScript element contains the dialing script to be used
connecting to this POP. The attribute value type of
defines the type of the script that should be used when connecting
this POP
Syntax
type CDATA #IMPLIED >
Riegel & Zorn Standards Track [Page 15]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
6.1.8. Pricing
The pricingInformation element is a free-form string
pricing information for this POP. It may be anything from a
string indicating relative expense (e.g., "$$$$" for a very
POP) to a paragraph describing time-of-day and other
pricing variables
Syntax
6.1.9.
The city element contains the name of the city in which the POP
located (not the city(s) from which it is accessible by a
call).
Syntax
6.1.10.
The region element contains the name of the region in which the
is located. In the United States, this would be the name of a
or (for Washington, D.C.) administrative district. In
countries, it might be the name of a province, parish or county
Syntax
6.1.11.
The country element contains the name of the country in which the
is located. The country name may be abbreviated (e.g., "USA" for
United States of America or "UK" for the United Kingdom) but
abbreviations are used the usage must be consistent within a
phone book
Syntax
Riegel & Zorn Standards Track [Page 16]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
6.1.12. POP
The popSetup element is either a setup element, if setup is
to this particular POP, or a reference to any of the setup
given in the outer scope of the phonebook element
Syntax
setupID IDREFS #IMPLIED
6.1.13. POP
The popSupport element is either a support element, if support
specific to this particular POP, or a reference to any of the
elements given in the outer scope of the phonebook element
Syntax
supportID IDREFS #IMPLIED
6.1.14. POP
The popProvider element is either a provider element, if
information is specific to this particular POP, or a reference to
of the provider elements given in the outer scope of the
element
Syntax
providerID IDREFS #IMPLIED
6.2. Information elements defined for the Setup
6.2.1. DNS Server
The dnsServerAddress element represents the IP address of the
Name Service (DNS) server which should be used when connected to
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
value NOTATION (IPADR) #IMPLIED
6.2.2. NNTP Server
The nntpServerName element contains the fully qualified domain
(FQDN) of the Network News Transfer Protocol (NNTP) server
should be used when connected to this POP
Syntax
value NOTATION (FQDN) #IMPLIED
6.2.3. SMTP Server
The smtpServerName element contains the FQDN of the Simple
Transfer Protocol (SMTP) server which should be used when
to this POP
Syntax
value NOTATION (FQDN) #IMPLIED
6.2.4. POP3 Server
The popServerName element contains the FQDN of the Post
Protocol (POP) server which should be used when connected to
POP
Syntax
value NOTATION (FQDN) #IMPLIED
6.2.5. IMAP Server
The imapServerName element contains the FQDN of the Internet
Access Protocol (IMAP) server which should be used when connected
this POP
Riegel & Zorn Standards Track [Page 18]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
Syntax
value NOTATION (FQDN) #IMPLIED
6.2.6. WWW
The wwwProxyServerName element contains the FQDN of the World
Web (WWW) proxy server which should be used when connected to
POP
Syntax
value NOTATION (FQDN) #IMPLIED
6.2.7. FTP
The ftpProxyServerName element contains the FQDN of the File
Protocol (FTP) proxy server which should be used when connected
this POP
Syntax
value NOTATION (FQDN) #IMPLIED
6.2.8. Winsock
The winsockProxyServerName element contains the FQDN of the
Socket (Winsock) proxy server which should be used when connected
this POP
Syntax
value NOTATION (FQDN) #IMPLIED
6.2.9. Default Gateway
The defaulttGatewayAddress element represents the address of
default gateway which should be used when connected to this POP.
address is represented in the form of a string in dotted-
notation (e.g., 192.168.101.1).
Riegel & Zorn Standards Track [Page 19]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
Syntax
value NOTATION (IPADR) #IMPLIED
6.2.10. User Name
The userNameSuffix element represents a string which should
concatenated to the base username. For example, if the base
is "userA" and the value of this element is "@bigco.com",
resulting augmented username would be "userA@bigco.com".
intelligent dialer may concatenate the string automatically.
that both the userNameSuffix and the userNamePrefix (below) may
applied to the same base username
Syntax
6.2.11. User Name
The userNamePrefix element represents a string to which the
username should be concatenated. For example, if the base
is "userB" and the value of this element is "BIGCO/" the
augmented username would be "BIGCO/userB". An intelligent dialer
perform the concatenation automatically. Note that both
userNameSuffix (above) and the userNamePrefix may be applied to
same base username
Syntax
6.3. Information elements defined for the support
6.3.1. Support Telephone
The supportTelephoneNumber element contains a number that may
called to reach the support center for a particular provider or POP
This element is basically a string and should contain the
telephone number in international form, e.g., "+1 425 838 8080".
Syntax
Riegel & Zorn Standards Track [Page 20]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
6.3.2. Support Email
The supportMailtoURL element contains a URL for the provider'
customer support email address, e.g., mailto:support@uu.net.
URL could be used to contact customer support personnel
non-urgent issues
Syntax
6.4. Information elements defined for the provider
6.4.1. Provider
The providerName element is a string containing the name of
provider (e.g., "BIGNET Corporation").
Syntax
6.4.2. Provider
The providerIcon attribute contains a BASE64 encoded JPEG or
image which may be used for 'branding' phone book entries
displayed when dialing
Syntax
value NOTATION (B64JPG | B64GIF) #IMPLIED
6.4.3. Provider's World Wide Web
The wwwURL element contains a Uniform Resource Locator (URL) for
provider's Web site, for example, http://www.uu.net
Syntax
Riegel & Zorn Standards Track [Page 21]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
6.4.4. Provider's Main Email
The generalMailtoURL element contains a URL for the provider's
email address, for example, mailto:contact@uu.net. This URL could
used for general correspondence, complaints, etc
Syntax
6.4.5. Billing Inquiry Email
The billingMailtoURL element contains a URL for the provider'
billing support email address, for example, mailto:billing@uu.net
This URL could be used to for correspondence regarding billing
payment issues
Syntax
6.4.6. Further
The remainder of the information elements of the provider element
described in principle in [3].
7. Complete XML DTD for the roaming phone
encoding="UTF-8"?>
Riegel & Zorn Standards Track [Page 22]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
"(L2TP|PPTP|L2F|ATMP|AHT|ESPT|IPIP|MIP|GRE)" >
"address
media+,
minBitsPerSecond?,
maxBitsPerSecond?,
popProperty*,
tunnelProto*,
dialScript?,
pricingInformation?,
city?,
region?,
country?,
(setup|setupPtr)?,
(support|supportPtr)?,
(provider|providerPtr)?">
"dnsServerAddress*,
nntpServerName*,
smtpServerName*,
popServerName*,
imapServerName*,
wwwProxyServerName*,
ftpProxyServerName*,
winsockProxyServerName*,
defaultGatewayAddress?,
userNamePrefix?,
userNameSuffix?">
"(supportTelephoneNumber|supportMailtoURL)+">
"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*">
NOTATION FQDN PUBLIC "-//IETF/roamPhoneBook/
value Type Fully_qualified_domain_name">
NOTATION IPADR PUBLIC "-//IETF/roamPhoneBook/
value Type IP_address">
NOTATION B64JPG PUBLIC "-//IETF/roamPhoneBook/
value Type Base64_encoded_jpeg_image">
NOTATION B64GIF PUBLIC "-//IETF/roamPhoneBook/
value Type Base64_encoded_gif_image">
pop+,
setup*,
support*,
provider*) >
name CDATA #
version CDATA #REQUIRED >
entryVersion CDATA #REQUIRED
id ID #REQUIRED
Riegel & Zorn Standards Track [Page 24]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
id ID #
language NMTOKENS #IMPLIED >
provider ( %providerInformation; )>
id ID #REQUIRED
family %addressFamily; #
countryCode CDATA #
areaCode CDATA #IMPLIED >
type %modemProtocols; #IMPLIED >
type %isdnProtocols; #IMPLIED >
type %atmProtocols; #IMPLIED >
type %frProtocols; #IMPLIED >
type %x25Protocols; #IMPLIED >
type %popProperties; #REQUIRED >
type %tunnelingProtocols; #REQUIRED >
Riegel & Zorn Standards Track [Page 25]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
type CDATA #IMPLIED >
setupID IDREFS #IMPLIED
supportID IDREFS #IMPLIED
providerID IDREFS #IMPLIED
value NOTATION (IPADR) #IMPLIED
value NOTATION (FQDN) #IMPLIED
value NOTATION (FQDN) #IMPLIED
value NOTATION (FQDN) #IMPLIED
value NOTATION (FQDN) #IMPLIED
value NOTATION (FQDN) #IMPLIED
Riegel & Zorn Standards Track [Page 26]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
value NOTATION (FQDN) #IMPLIED
value NOTATION (FQDN) #IMPLIED
value NOTATION (IPADR) #IMPLIED
value NOTATION (B64JPG|B64GIF) #IMPLIED
Riegel & Zorn Standards Track [Page 27]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
description (#PCDATA)>
8. Security
The secure distribution and transport of information of a phone
for roaming applications require a reliable authentication of
issuer of the information as well as means to preserve the
of the provided information
No specific elements for security requirements are provided by
phone book XML DTD itself. It is assumed that security of
roaming phone book is provided by means outside of the scope of
specification, such as signing the phone book using pgp
9. IANA
This specification provides the possibility to define
attribute values for all information elements owning
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
to future requirements without changing this document.
and refinements to this specification can be achieved by
of new elements and attributes by IANA
Extending this specification with additional attributes or
must not change the validity of documents based on an older
of the XML DTD. Therefore all added information elements must
Riegel & Zorn Standards Track [Page 28]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
optional, prohibiting the mandatory inclusion of newly
information elements. Adding new values to enumerated
lists has no backward compatibility constraints because it does
harm the validity of attributes already defined
To facilitate the registration of new information elements
attribute values the DTD of the phone book has been separated in
parts, the extensible part containing only parameter
declarations for ease inclusion of new values, and the fixed
containing the detailed specification of the content and structure
the phone book. By referencing the parameter entity declarations
the fixed part of the specification the whole phone book
extensible
The part containing the parameter entity declarations has to
maintained by the IANA. There are two different classes
declarations in this part requiring different policies
registering new values
9.1. Registration of new attribute
The entities 'addressFamily', 'modemProtocols', 'isdnProtocols',
'atmProtocols', 'frProtocols', 'x25Protocols', 'popProperties'
'tunnelingProtocols' are describing enumerated attribute value lists
Because there is no limitation in the name space of these
values and newly defined attribute values can not harm the
of existing values, new attribute values can be assigned
Specification Required [6].
9.2. Registration of new information
The entities 'mediaTypes', 'popInformation', 'setupInformation', '
supportInformation' and 'providerInformation' define the
elements probably included in the media, pop, setup, support
provider elements. Inserting new values into these lists extends
phone book by arbitrarily new information elements.
use of the XML content model can destroy the backward
of the DTD. Therefore the assignment of new information
requires the approval of a Designated Expert [6]. In addition to
insertion of a new value into the list, the detailed definition
the information element has to be appended to the specification
maintained by the IANA
Riegel & Zorn Standards Track [Page 29]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
10.
[1] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997.
[2] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, RFC 1700,
October 1994.
[3] Barker, P. and S. Kille, "The COSINE and Internet X.500 Schema",
RFC 1274, November 1991.
[4] ITU Rec. E.123, "Notation for national and
telephone numbers", 1988.
[5] "Extensible Markup Language (XML) 1.0" W3C Recommendation 10-
February-1998 http://www.w3.org/TR/1998/REC-xml-19980210
[6] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
Riegel & Zorn Standards Track [Page 30]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
11. Appendix:
11.1. The most simple
encoding="UTF-8"?>
+1 234 5678901
11.2. A more comprehensive
encoding="UTF-8"?>
+49913130540
192.168.147.5
193.175.24.33
language="EN DE">
mailto:support@franken.de
+499123968066
12.
Thanks to Pat Calhoun, Bernard Aboba, Jay Farhat, Butch Anton
Quentin Miller, and Ken Crocker for salient input and review
Riegel & Zorn Standards Track [Page 31]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
13. Authors'
Questions about this memo can be directed to
Max
Siemens
Hofmannstr. 51
Munich, 81359
Phone: +49 89 722 49557
EMail: maximilian.riegel@icn.siemens.
Glen
Cisco Systems, Inc
500 108th Avenue N.E., Suite 500
Bellevue, WA 98004
Phone: +1 425 438 8218
EMail: gwz@cisco.
Riegel & Zorn Standards Track [Page 32]
RFC 3017 Roaming Access Phone Book XML DTD December 2000
14. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Riegel & Zorn Standards Track [Page 33]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
