<pre>Network Working Group                                        M. Haberler
Request for Comments: 5527                                           IPA
Category: Informational                                         O. Lendl
                                                                 enum.at
                                                              R. Stastny
                                                            Unaffiliated
                                                                May 2009


      <span class="h1">Combined User and Infrastructure ENUM in the e164.arpa Tree</span>

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents in effect on the date of
   publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Abstract

   This memo defines an interim solution for Infrastructure ENUM in
   order to allow a combined User and Infrastructure ENUM implementation
   in e164.arpa as a national choice.  This interim solution will be
   deprecated after implementation of the long-term solution.

















<span class="grey">Haberler, et al.             Informational                      [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
   <a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
   <a href="#section-3">3</a>. Interim Solution ................................................<a href="#page-3">3</a>
   <a href="#section-4">4</a>. The Algorithm ...................................................<a href="#page-4">4</a>
   <a href="#section-5">5</a>. Determining the Position of the Branch ..........................<a href="#page-5">5</a>
   <a href="#section-6">6</a>. Transition to the Long-Term Solution ............................<a href="#page-6">6</a>
   <a href="#section-7">7</a>. Examples ........................................................<a href="#page-7">7</a>
   <a href="#section-8">8</a>. Security Considerations .........................................<a href="#page-8">8</a>
   <a href="#section-9">9</a>. Acknowledgments .................................................<a href="#page-9">9</a>
   <a href="#section-10">10</a>. References .....................................................<a href="#page-9">9</a>
      <a href="#section-10.1">10.1</a>. Normative References ......................................<a href="#page-9">9</a>
      <a href="#section-10.2">10.2</a>. Informative References ....................................<a href="#page-9">9</a>

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

   ENUM (E.164 Number Mapping, [<a href="./rfc3761" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">RFC3761</a>]) is a system that transforms
   E.164 numbers [<a href="#ref-E164" title="&quot;The International Public Telecommunication Number Plan&quot;">E164</a>] into domain names and then queries the DNS
   (Domain Name Service) [<a href="./rfc1034" title="&quot;Domain names - concepts and facilities&quot;">RFC1034</a>] for NAPTR (Naming Authority Pointer)
   records [<a href="./rfc3401" title="&quot;Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS&quot;">RFC3401</a>] in order to look up which services are available
   for a specific domain name.

   ENUM, as defined in <a href="./rfc3761">RFC 3761</a> (User ENUM), is not well suited for the
   purpose of interconnection by carriers and voice-service providers,
   as can be seen by the use of various private tree arrangements based
   on ENUM mechanisms.

   Infrastructure ENUM is defined as the use of the technology in <a href="./rfc3761">RFC</a>
   <a href="./rfc3761">3761</a> [<a href="./rfc3761" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">RFC3761</a>] by the carrier-of-record (voice service provider)
   [<a href="./rfc5067" title="&quot;Infrastructure ENUM Requirements&quot;">RFC5067</a>] for a specific E.164 number [<a href="#ref-E164" title="&quot;The International Public Telecommunication Number Plan&quot;">E164</a>] in order to publish a
   mapping of this telephone number to one or more Uniform Resource
   Identifiers (URIs) [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>].

   Other voice service providers can query the DNS for this mapping and
   use the resulting URIs as input into their call-routing algorithm.
   These URIs are separate from any URIs that the end-user who registers
   an E.164 number in ENUM may wish to associate with that E.164 number.

   The requirements, terms, and definitions for Infrastructure ENUM are
   defined in [<a href="./rfc5067" title="&quot;Infrastructure ENUM Requirements&quot;">RFC5067</a>].

   Using the same E.164 number to domain mapping techniques for other
   applications under a different, internationally agreed-upon apex
   (instead of e164.arpa) is straightforward on the technical side.
   This process of defining the Dynamic Delegation Discovery System
   (DDDS) [<a href="./rfc3401" title="&quot;Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS&quot;">RFC3401</a>] application for Infrastructure ENUM is defined in
   [<a href="./rfc5526" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM&quot;">RFC5526</a>].  This is the long-term solution.



<span class="grey">Haberler, et al.             Informational                      [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


   This document presents an interim solution for Infrastructure ENUM
   and a mechanism for transitioning to the long-term solution.  The
   interim solution is based on establishing a branch in the e164.arpa
   tree, which resolvers may locate by following the algorithm described
   in <a href="#section-4">Section 4</a>.  The location of the branch is dependent upon country-
   code length, and thus resolvers must determine the position of the
   branch based on the method described in <a href="#section-5">Section 5</a>.  Finally,
   <a href="#section-6">Section 6</a> provides a way that implementations following the
   procedures of Sections <a href="#section-4">4</a> and <a href="#section-5">5</a> may be seamlessly redirected to the
   long-term solution, when it becomes available.

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

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>
   [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Interim Solution</span>

   The agreements to establish the long-term solution may take some
   time.  It was therefore decided to develop an interim solution that
   can be used by individual countries to implement an interoperable
   Infrastructure ENUM tree immediately.  The interim solution will be
   deprecated when the long-term solution [<a href="./rfc5526" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM&quot;">RFC5526</a>] is deployed.  It is
   therefore also required that the interim solution includes a smooth
   migration path to the long-term solution.

   It is also required that existing ENUM clients querying User ENUM as
   defined in <a href="./rfc3761">RFC 3761</a> [<a href="./rfc3761" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">RFC3761</a>] continue to work without any
   modification.

   Because of various reasons (e.g., potentially different delegation
   points, different reliability requirements, and use of DNS
   wildcards), sharing a single domain name between the user itself and
   the respective carrier for a given number is not possible.  Hence, a
   different domain name must be used to store infrastructure ENUM
   information.

   In order to avoid the delays associated with the long-term solution,
   the existing delegations and agreements around e164.arpa need to be
   leveraged.

   The method most easily fulfilling the requirements is to branch off
   the e164.arpa tree into a subdomain at the country-code delegation
   level below e164.arpa and deploy an Infrastructure ENUM subtree
   underneath, without touching User ENUM semantics at all.




<span class="grey">Haberler, et al.             Informational                      [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


   This allows countries using a dedicated country code to introduce the
   interim solution as a national matter to the concerned National
   Regulation Authority (NRA).  The governing body of a shared country
   code and the owner of a global network code can also choose to
   implement this solution within their area of responsibility.

   Under this approach, ITU-T (International Telecommunication Union /
   Telecommunication Standardization Sector), IETF, and IAB involvement
   is only lightweight, e.g., to recommend the proper algorithm defined
   here to enable international interoperability.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  The Algorithm</span>

   <a href="./rfc3761">RFC 3761</a> defines ENUM as a Dynamic Delegation Discovery System (DDDS)
   application according to <a href="./rfc3401">RFC 3401</a> [<a href="./rfc3401" title="&quot;Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS&quot;">RFC3401</a>].  As such, ENUM defines
   the following components of the DDDS algorithm:

   1.  Application Unique String

   2.  First Well-Known Rule

   3.  Expected Output

   4.  Valid Databases

   The "Valid Databases" part contains the transformation of an E.164
   telephone number into a domain name.  <a href="./rfc3761#section-2.4">Section&nbsp;2.4 of RFC 3761</a> uses
   the following 4-step algorithm for this:

   1.  Remove all characters with the exception of the digits.

   2.  Put dots (".") between each digit.

   3.  Reverse the order of the digits.

   4.  Append the string ".e164.arpa" to the end.

   The interim solution for Infrastructure ENUM uses a modified version
   of this algorithm:

   1.  Determine the proper POSITION parameter for this E.164 number
       according to the algorithm in <a href="#section-5">Section 5</a> of this document.

   2.  Build an ordered list of single-digit strings from all digits
       appearing in the telephone number.  All non-digit characters are
       ignored.





<span class="grey">Haberler, et al.             Informational                      [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


   3.  Insert a string consisting of "i" into this list, after POSITION
       strings.  If the list of strings was shorter than POSITION
       elements, then report an error.

   4.  Reverse the order of the list.

   5.  Append the string "e164.arpa" to the end of the list.

   6.  Create a single domain name by joining the list together with
       dots (".") between each string.

   This is the only point where the interim Infrastructure ENUM (I-ENUM)
   solution differs from straight <a href="./rfc3761">RFC 3761</a> ENUM.  All other parts of
   User ENUM, including the enumservices registrations, apply to I-ENUM
   as well.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Determining the Position of the Branch</span>

   In order to allow for the deployment of this interim solution
   independent of IAB/ITU-T/RIPE-NCC negotiations, the branching label
   "i" cannot be inserted in the Tier-0 zone (i.e., the e164.arpa zone
   itself) currently managed by RIPE NCC.  This condition acts as a
   lower bound on the choice of the POSITION parameter.

   For international E.164-numbers for geographic areas (Section 6.2.1
   of [<a href="#ref-E164" title="&quot;The International Public Telecommunication Number Plan&quot;">E164</a>]) and for international E.164-numbers for global services
   (Section 6.2.2 of [<a href="#ref-E164" title="&quot;The International Public Telecommunication Number Plan&quot;">E164</a>]), the most sensible choice for POSITION is
   the number of digits in the country code of the number in question.
   This places the branch directly under the country-code level within
   the e164.arpa ENUM tree.

   For international E.164-number for networks (Section 6.2.3 of
   [<a href="#ref-E164" title="&quot;The International Public Telecommunication Number Plan&quot;">E164</a>]), the appropriate choice for POSITION is the combined length
   of the CC (Country Code) and IC (Identification Code) fields.

   For international E.164-number for groups of countries (Section 6.2.4
   of [<a href="#ref-E164" title="&quot;The International Public Telecommunication Number Plan&quot;">E164</a>]), the value for POSITION is 4.

   The authoritative source for up-to-date country code and network
   Identification Code allocations is published by the ITU-T as a
   complement to the recommendation E.164 [<a href="#ref-E164" title="&quot;The International Public Telecommunication Number Plan&quot;">E164</a>].  The current version
   of this complement is available from the ITU website under "ITU-T /
   Service Publications".

   Please note that country code 1 of the North American Numbering Plan
   (NANP) does not fall under the ITU classification of "groups of
   countries", but is a "shared country code" for a geographic area.
   Thus, the POSITION parameter for the NANP is 1.



<span class="grey">Haberler, et al.             Informational                      [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


   As of 2007, the POSITION value for a specific E.164 number can be
   determined with the following algorithm:

   o  If the number starts with 1 or 7, then POSITION is 1.

   o  If the number is in one of the following 2-digit country codes,
      then POSITION is 2: 20, 27, 30-34, 36, 39, 40, 41, 43-49, 51-58,
      60-66, 81, 82, 84, 86, 90-95, or 98.

   o  If the number starts with 388 or 881, then POSITION is 4.

   o  If the number starts with 878 or 882, then POSITION is 5.

   o  If the number starts with 883 and the next digit is &lt; 5, then
      POSITION is 6.

   o  If the number starts with 883 and the next digit is &gt;= 5, then
      POSITION is 7.

   o  In all other cases, POSITION is 3.

   Given the fact that the ITU-T recently allocated only 3-digit country
   codes, there are no more spare 1- and 2-digit country codes and
   existing 1- and 2-digit country codes are extremely unlikely to be
   recovered, the above list of existing 1- and 2-digit country codes
   can be considered very stable.  The only problem may be for a country
   that has split, as happened recently, for example, to Yugoslavia.

   Regarding network codes, up to 2007, the ITU-T has only allocated 1-
   and 2-digit ICs.  Assignments of 3- and 4-digit ICs started in May
   2007 in the +883 country code.  Any further change in the ITU-T
   policy in this respect will need to be reflected in the above
   algorithm.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Transition to the Long-Term Solution</span>

   The proposed long-term solution for Infrastructure ENUM [<a href="./rfc5526" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM&quot;">RFC5526</a>] is
   the establishment of a new zone apex for that tree.  This apex will
   play the same role as "e164.arpa" does for User ENUM.

   It is unrealistic to assume that all countries and all ENUM clients
   will manage to migrate from the interim solution to the long-term
   solution at a single point in time.  It is thus necessary to plan for
   an incremental transition.

   In order to achieve this, clients using the interim solution need to
   be redirected to the long-term I-ENUM tree for all country codes that
   have already switched to the long-term solution.  This SHOULD be done



<span class="grey">Haberler, et al.             Informational                      [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


   by placing DNAME [<a href="./rfc2672" title="&quot;Non-Terminal DNS Name Redirection&quot;">RFC2672</a>] records at the branch (the "i") label
   pointing to the appropriate domain name in the long-term I-ENUM tree.
   All descendants at that branch label location where the DNAME record
   is inserted MUST be removed, as required by <a href="./rfc2672#section-3">Section&nbsp;3 of RFC 2672</a>.

   Therefore, ALL entities involved in making or answering DNS queries
   for I-ENUM MUST fully support the DNAME record type and its
   semantics.  In particular, entities involved in I-ENUM lookups MUST
   correctly handle responses containing synthesized CNAMEs that may be
   generated as a consequence of DNAME processing by any other element
   in resolution, typically an iterative mode resolving name server.

   These entities MUST also apply adequate measures to detect loops and
   prevent non-terminating resolutions because of improperly configured
   DNAME records or combinations of DNAME and CNAME records.

   Note: Some caching name server implementations are known to handle
   DNAMEs incorrectly.  In the worst case, such bugs could stay
   undetected until a country transitions to the long-term solution.
   Therefore, ensuring full DNAME support from the start (and carefully
   testing that it actually works) is important.

   The domain name for the branch location and its DNAME record SHOULD
   be removed once the transition to the long-term solution is completed
   and all entities involved in I-ENUM have migrated to the new zone
   apex for I-ENUM.

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

   These are two examples of how E.164 numbers translate to
   Infrastructure ENUM domains according to the interim solution.

   +1 21255501234          4.3.2.1.0.5.5.5.2.1.2.i.1.e164.arpa
   +44 2079460123          3.2.1.0.6.4.9.7.0.2.i.4.4.e164.arpa

   Here is the list of the intermediate steps for the second example to
   visualize how the algorithm defined in <a href="#section-4">Section 4</a> operates on "+44
   2079460123":

   1.  "+44 2079460123" is within a 2-digit country code; thus, POSITION
       is 2.

   2.  The list of strings is
       ("4","4","2","0","7","9","4","6","0","1","2","3")

   3.  POSITION is 2; thus, "i" is inserted between the second and the
       third string, yielding:
       ("4","4","i","2","0","7","9","4","6","0","1","2","3")



<span class="grey">Haberler, et al.             Informational                      [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


   4.  Reversing the list gives:
       ("3","2","1","0","6","4","9","7","0","2","i","4","4")

   5.  Appending "e164.arpa" yields:
       ("3","2","1","0","6","4","9","7","0","2","i","4","4","e164.arpa")

   6.  Concatenation with dots yields:
       "3.2.1.0.6.4.9.7.0.2.i.4.4.e164.arpa"

   After the introduction of the long-term Infrastructure ENUM solution,
   using, for example, "ienum.example.net" as the new apex for I-ENUM,
   the administrators of +44 can implement a smooth transition by
   putting the following DNAME record in their zone:

   i.4.4.e164.arpa.    IN DNAME 4.4.ienum.example.net.

   This way, clients using the interim I-ENUM solution end up querying
   the same tree as clients implementing the long-term solution.

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

   Privacy issues have been raised regarding the unwarranted disclosure
   of user information that would result from publishing Infrastructure
   ENUM information in the public DNS.  For instance, such disclosure
   could be used for harvesting numbers in service or obtaining unlisted
   numbers.

   Given that number-range allocation is public information, we believe
   the easiest way to cope with such concerns is to fully unroll
   allocated number ranges in the Infrastructure ENUM subtree, wherever
   such privacy concerns exist.  Whether or not a number is served would
   be exposed by the carrier-of-record when an attempt is made to
   contact the corresponding URI.  We assume this to be an authenticated
   operation, which would not leak information to unauthorized parties.

   Entering all numbers in an allocated number range, whether serviced
   or not, or whether listed or unlisted, will prevent mining attempts
   for such number attributes.

   The result will be that the information in the public DNS will mirror
   number-range allocation information, but no more.  Infrastructure
   ENUM will not tell you more than you can get by just dialing numbers.

   The URI pointing to the destination network of the carrier-of-record
   should also not disclose any privacy information about the identity
   of the end-user.  It is therefore recommended to use either
   anonymized UserIDs or the E.164 number itself in the user part of the
   URI, such as in sip:+441632960084@example.com.



<span class="grey">Haberler, et al.             Informational                      [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


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

   We gratefully acknowledge suggestions and improvements by Jason
   Livingood and Tom Creighton of Comcast, Penn Pfautz of AT&amp;T, Lawrence
   Conroy of Roke Manor Research, Jim Reid, and Alexander Mayrhofer of
   enum.at.

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

<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>.  Normative References</span>

   [<a id="ref-E164">E164</a>]     ITU-T, "The International Public Telecommunication Number
              Plan", Recommendation E.164, February 2005.

   [<a id="ref-RFC1034">RFC1034</a>]  Mockapetris, P., "Domain names - concepts and facilities",
              STD 13, <a href="./rfc1034">RFC 1034</a>, November 1987.

   [<a id="ref-RFC2119">RFC2119</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-RFC2672">RFC2672</a>]  Crawford, M., "Non-Terminal DNS Name Redirection",
              <a href="./rfc2672">RFC 2672</a>, August 1999.

   [<a id="ref-RFC3401">RFC3401</a>]  Mealling, M., "Dynamic Delegation Discovery System (DDDS)
              Part One: The Comprehensive DDDS", <a href="./rfc3401">RFC 3401</a>, October 2002.

   [<a id="ref-RFC3761">RFC3761</a>]  Faltstrom, P. and M. Mealling, "The E.164 to Uniform
              Resource Identifiers (URI) Dynamic Delegation Discovery
              System (DDDS) Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004.

   [<a id="ref-RFC3986">RFC3986</a>]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              <a href="./rfc3986">RFC 3986</a>, January 2005.

<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>.  Informative References</span>

   [<a id="ref-RFC5067">RFC5067</a>]  Lind, S. and P. Pfautz, "Infrastructure ENUM
              Requirements", <a href="./rfc5067">RFC 5067</a>, November 2007.

   [<a id="ref-RFC5526">RFC5526</a>]  Livingood, J., Pfautz, P., and R. Stastny, "The E.164 to
              Uniform Resource Identifiers (URI) Dynamic Delegation
              Discovery System (DDDS) Application for Infrastructure
              ENUM", <a href="./rfc5526">RFC 5526</a>, April 2007.








<span class="grey">Haberler, et al.             Informational                      [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5527">RFC 5527</a>         Combined User and Infrastructure ENUM          May 2009</span>


Authors' Addresses

   Michael Haberler
   Internet Foundation Austria
   Karlsplatz 1/2/9
   Wien  1010
   Austria

   Phone: +43 664 4213465
   EMail: ietf@mah.priv.at
   URI:   <a href="http://www.nic.at/ipa/">http://www.nic.at/ipa/</a>

   Otmar Lendl
   enum.at GmbH
   Karlsplatz 1/2/9
   Wien  A-1010
   Austria

   Phone: +43 1 5056416 33
   EMail: otmar.lendl@enum.at
   URI:   <a href="http://www.enum.at/">http://www.enum.at/</a>


   Richard Stastny
   Unaffiliated
   Anzbachgasse 43
   1140 Vienna
   Austria

   Phone: +43 664 420 4100
   EMail: richardstastny@gmail.com




















Haberler, et al.             Informational                     [Page 10]
</pre>