miércoles, 28 de julio de 2010

Como configurar tu correo en un dominio .tel como info@libros.tel

  • 6: Setup name@yourdomain.tel

    A .tel domain does not include email hosting by default, but provides the necessary support for a .tel email address. Please check with your .tel service provider whether a mail hosting service is available, or setup your own mailbox on independent mail servers.

    To have a .tel email address, you need to setup mail servers to host your mailbox, and add MX records pointing to those servers from your .tel domain. You can add MX records from the Settings link in the .tel control panel, or programmatically using the SOAP/AJAX APIs. Again, your .tel provider might offer to do this for you.
    If you do not see the Setup .tel email tab in Settings, please check with your provider if email is supported.

    Below are simple instructions on setting up a free .tel mailbox using Google Mail or Windows Live Mail, or configure Hostgator hosting for .tel domains.

    Google Mail

    1. Sign up for a Google Apps account and add your .tel domain name:
      1. Select the option Administrator: I own or control this domain from the sign up page and enter your .tel domain name.
      2. Enter all your personal information.
      3. Enter the email address you want setup at your .tel domain and finish the sign up process.
    2. Get Google mail server names to setup MX records in your .tel domain.
      1. Skip forced verification of ownership using CNAME records by selecting I will validate later.
      2. Go to your Admin Panel
        Verifying Domain Ownership > Configuring MX Records.
    3. In the control panel, setup .tel to point to Google mail servers, such as
      ASPMX.L.GOOGLE.COM. 10
      ALT1.ASPMX.L.GOOGLE.COM. 20
    4. Wait for Google to validate ownership of your domain. This can take up to 48 hours.

    Windows Live

    1. Add your .tel to Windows Live.
      1. Sign up for a Windows Live account or log in if you are returning user.
      2. Enter the domain you want to add as a Custom Domain.
      3. Accept the Terms and Conditions.
        You will be presented with the MX record for your email service.
    2. Setup .tel to point to Windows Live server.
      1. On the Domain Settings page, get the details of the MX record that you need to set up. This is tied specifically to your domain name rather than being a generic address.
      2. Copy the MX server name into your .tel Settings in the control panel.
      3. Return to the Windows Live process and hit Refresh to validate the changes.
    3. Create member account(s).
      1. In the Member Accounts area, click Add+ to create a new member.
      2. Fill in the form with the requested data (may not work on browsers other than Internet Explorer).
    4. Activate your mail account.
      1. Sign up for the Windows Live Mail system by filling in the form.
      2. Sign in again entering the captcha when prompted.

    Hostgator hosting

    1. Add your .tel to Hostgator.
      1. In your browser, login to your Hostgator Control Panel.
      2. Click the Add-On domains icon
      3. Specify your domain and password and click Add Domain.
    2. Get your MX settings from Hostgator. If you don't know your mail server, perform a DIG command to get those settings for the domain associated with your Hostgator mailbox. For example:

      http://digwebinterface.com/?hostnames=yourname.com&type=MX&ns=resolver&useresolver=69.65.17.101&nameservers=

      You will see something like this copy the values on the right:
      yourname.com. 60 IN MX 20 ns2041.hostgator.com.
      yourname.com. 60 IN MX 10 ns2042.hostgator.com.
    3. In the .tel control panel, setup your .tel to point to Hostgator's MX servers from the DIG result you copied, like "ns2042.hostgator.com." .
    4. maquinaria agrícola caleruega taller mecanico caleruega oficinas bancarias caleruega casas rurales caleruega caleruega golf caleruega noticias web




  • Como configurar un correo en tu dominio .tel por ejemplo info@libros.tel

    Account Settings

    E-mail Settings

    The main advantage of a .tel domain is that you don't need a hosting account to use it. However, if you want to have email accounts for your .tel domain such as user@yourdomain.tel, you will need a hosting account.

     Follow the steps below to set up a mail account for a .tel domain:

     First and foremost, you must have a registered .tel domain. SiteGround customers can order a new .tel domain from their Customer Area > Order Domains.

    • Log in to your .tel domain management section and go to settings -> Setup .tel email.
    • In the Server host name field type the host name(s) of the mail server(s) that will handle your mails. For example, if your account is hosted on the siteground200.com server, type siteground200.com in the field.
    • In the Order field enter a number for the order in which the server(s) will be used. For example, you can type 1 for your first host name and increase the number for any additional host names.
    • Click Save to save your domain's MX records.

    setup .tel email

    • Now you need to create the mail account(s) that you want to use with your .tel domain. To be able to do this, you should first park your .tel domain from your cPanel > Parked domains. Note that due to their specific DNS setup, .tel domains cannot work as parked domains. The only reason you need to park the .tel domain is to be able to create mail accounts for it.
    • The last thing you need to do is to create your mail accounts for the .tel domain from your cPanel -> Email accounts.

    maquinaria agrícola caleruega taller mecanico caleruega oficinas bancarias caleruega casas rurales caleruega caleruega golf caleruega noticias web

    martes, 27 de julio de 2010

    Noticia de tal día como hoy, pero de hace 5 años. Así empezaron los dominio .tel

    Nuevo dominio ".tel": Será destinado a la telefonía a través de Internet.

    La ICANN aprobó el nuevo dominio .tel, el que tendrá la finalidad de ser un nexo entre los diferentes medios de telecomunicaciones, como voz, mensajería, combinaciones de voz y datos.

    27-07-2005 - Por lo que la ICANN designo a la firma Telnic como la responsable de asegurar que las numeraciones y nombres estén restringidos para garantizar la integridad y evitar interferencias en planes de numeración telefónicos nacionales o internacionales que ya estén establecidos o que aparezcan en el futuro.

    La intención de la ICANN es que este nuevo dominio cubra cualquier forma de comunicación entre personas y/o empresas, y por este motivo lo denomina "Internet-Communications".

    La compañía Telnic tiene sus oficinas centrales en Londres y está presidida por Juan Villalonga, ex-presidente de Telefónica.
     

    Si tu negocio aún no tienes un .tel ¿existes?

    Si tienes un negocio, y aún no tienes un .tel, ¿como crees que los demás saben que existes?




    cáncer embarazo alimentacion nutricion libros camino del cid greenpeace anuncios trabajo literatura

    lunes, 26 de julio de 2010

    A pesar de todo, yo sigo creyendo en los .tel

    Putting the final nail to the .TEL .COffin

     

    .CO is 100% Colombian TLD with an international flavor and worldwide reach.

    When the .TEL TLD came out of the ICANN stables it was supposed to be a revolutionary new method of establishing a new identity online.

    Adding to the launch hoopla was the infamous Ben.tel video depicting two hormone-laden Brits fighting for the attention of an uptown blonde – all while riding an intercity train. The one who scribbled "Ben.tel" on the window with his opponent's latte won the girl.

    He might as well have scribbled the .tel domain with feces.

    Once out of the limelight, dot tel was proven to be not only insufficient in providing basic elements expected from a TLD but also extremely weak with regards to search engine visibility.

    In essence, TelNIC – the .tel Registry – brought out a product that was never ready to be used by the unsuspecting public, who rushed to register every serious or silly keyword under the sun, only to see their investment vaporize during the 1st year anniversary;  upon renewal time, .tel domains dropped en masse.

    We can't blame TelNIC for improving on the initial model: they replaced the ugly .tel button with something that looks more appealing but didn't provide space for one's own image. They replaced the masked proxy forwarding and added space for AdSense.

    Errr, that's it pretty much.

    The Achilles tendon of .tel has always been its DNS: locked down to displaying the massive amount of personal data stored in the TelNIC database, there has been no alternate provision in order to host a dot tel in a separate DNS or to park domains for that matter.

    It needs to be noted that TelNIC carries on, undaunted; a few weeks ago they launched the IDN .tel domains – as if we need international users to obtain their own castrated .TEL domains. At least, that led to several new registrations after the anniversary dive in existing .tel numbers.

    And now, .CO is here – at the worst time for .tel, putting the final nail to the dot tel coffin.

    There is no comparison between the two: Dot CO is a letter shy of .com and brings forth a full-fledged TLD that can be parked, developed and most importantly it will rate well with search engines such as Google.

    Sometimes we wonder where is the .TEL blonde these days now that the .CO brunette from Colombia controls the game.

    ¿por qué los dominios .tel aún no optimizan en SEO?

    domingo, 25 de julio de 2010

    Los dominio .tel, no solo son basura, sino autenticos diamantes en bruto, los cuales acabaran valiendo más que los .com

    En respuesta a lo de que los .tel son una basura, debo de reconocer que parece que soy el único que estoy en contra de todo eso. Tanto es así, que he abandonado los 150 dominios que tenía, los he puesto en parking, y he decidido dedicarme exclusivamente a los .tel
    Las estadisticas son malas, de los 300.000 que habían vendidos, se han perdido 50.000 que no se han renovado, google hace unos días les penalizó, Arsys (en España) les despreció no apuntandose a los IDN, en fin todo va medio mal. Sin embargo he decido pensar algo radicalmente diferente a lo que piensa la mayoría, así que:
    1.- Pienso que el ser humano fue creado hace unos 7000 años en el Edem (Eridu) por los Annunakis, lo hicieron por manipulación genética uniendo el cromosoma 2 y 3, y nos crearon para ser sus esclavos.
    2.- Pienso que la pirámide de Keops era una estación de monitorización de datos terrestres (campos magnéticos, temperatura...) los cuales eran enviados al espacio, para ser analizada la habitabilidad de la tierra desde otro planeta lejano. Teoría única de valdeandemagico , con la cual estoy de acuerdo y admiro a este tal valdeandemagico, por tener ideas diferentes.
    3.- Y pienso que los .tel acabarán valiendo mas que los .com, ya que los .com van teniendo cada vez mucha más competencia con dominios que le intentan imitar, y como todos son iguales, pues al final la tarta se va dividiendo en trozos más pequeños. Sin embargo los .tel, son una joya por explotar, pero que no explotará hasta por lo menos el 2014, donde las redes de comunicaciones empiecen a ser IP. Cuando uno trabaja para hacer que la red de comunicaciones STB, la fija, vaya desapareciendo, y que la red de comunicaciones móviles, también vaya desapareciendo, es decir que tienen fecha de caducidad, y sin embargo la NGN (red fija IP) va como una moto, o que la gran inversión económica vaya hacia la red móvil banda ancha (4G, LTE, será todo IP). Pues bien, al final, en unos años todo será IP. Y en dominios, ¿qué se creó para cuando todo sea IP? pues se crearon lo .tel, una red de DNS repartidos por todo el mundo, desde donde se gestionaran los contactos de la gente, y lo gestionará cada cual a su gusto y manera.
    4.- Acabo de probar el OpenAuth de los .tel, y va de maravilla, es decir autenticándome solo una vez, accedo a todos los dominios .tel, sea del operador que sea, también poseen OpenID, he comprobado que poner un enlace patrocinado son 3 segundos, poner lo de adsense 3 segundos, que se puede recibir contenido automáticamente, que se puede hacer para que se pongan comentarios, que se puede actualizar directamente desde Twitter, que está a punto de poderse cambiar el contacto desde un SMS del móvil, que puedes poner 300.000 registros, que es el más barato de todos, pues incluye el alojamiento... Soy el má nuevo en esto, no tengo casi ni idea, pero por ello creo que hay que arriesgar en algo diferente, y solo, solo, solo, hay algo diferente en los .tel, el resto es más de lo mismo.

    Lo dicho, yo no pienso que los .tel sean basura, sino un diamante en bruto a los que aún les queda mucho por pulir, pero son a los únicos que se les puede pulir, y acabaran brillando.
     

    sábado, 24 de julio de 2010

    SEO para los dominio .tel

    SEARCH ENGINE OPTIMIZATION (SEO) AND THE .TEL DOMAIN

    Search engine optimization (SEO) is the process of improving the volume and quality of traffic to a domain or website from search engines via "natural" ("organic" or "algorithmic") search results. As a result, search engines return links to that domain or website higher up the search rankings, thus enabling those searching for relevant resources to discover it more easily.

    Optimizing a domain or website for better search engine ranking primarily involves regular editing of its content to both increase its relevance to specific keyword being used in search queries and to encourage more frequent indexing by search engines. However, the rules for SEO are fluid and constantly change because search engine operator stry to counter 'gaming' – the forcing of results to higher rankings than their perceived value in the specific search conducted.

    Search engine optimization has developed into a huge industry with agencies and specialists analyzing and employing a set of techniques in an attempt to bring together human-readable content and computers that evaluate the relevance of that content. Why is this? Traditional websites lack a standardized structure and also focus on strong visual presentation of content to capture the interest of the viewer/researcher, not necessarily focusing on data. As a result, search engines need to apply complex algorithms to determine whether those websites might be useful for visitors, evaluating a number of variable characteristics. Added to this, the multi-lingual nature of websites, and the differing purposes of Internet searches (someone might be trying to find an address or telephone number of a veterinary surgery, the other a video of kittens playing the piano), and you immediately get a matrix of global possibilities without structure. SEO experts aim to address these unstructured possibilities to try to bring your domain or website to the top of the search results matrix and keep it there. With .tel, SEO skills can be applied more easily and allow your domain and websites to be more productive as a result. All .tel domains are "search engine optimized" insofar as a .tel domain pushes you to publish valuable, structured information in it, which is of great relevance to search engines. Here are a few simple yet unique SEO features that a .tel domain provides over other types of top level domains:

    1. • No HTML coding or webmaster knowledge required

    All .tel edits can be done by the .tel owner and do not require setup of complex meta tags, robot files or other webmaster tools and techniques commonly used on websites. With a .tel, everything you add is published immediately, and seen by search engines as industry-standard, meaningful .tel information. It's as simple as that.

    1. • Machine-readable structured content

    Unlike a traditional website, .tel contains structured information which has standardized labels. For example, a telephone number has the label 'callto:' associated with it, meaning a machine knows how to deal with this type of data record. So the automatic search algorithm needn't to parse the whole text to, for example, identify a string of digits as a phone number. With a solution that is both machine-readable and optimized for presentation to humans is a revolution in SEO.

    1. • Increased relevance and authoritative data source

    Because any contact item has labels to identify its type and location, and any keyword can belong to a category, a simple crawler can instantly identify all the data needed to consider a .tel domain

    Search Engine Optimization and the .tel Domain

    as an authoritative data source. This is far more efficient than meta-tagging information within web pages and highlighting to search engines the manually-created site map.

    1. • Standard source of contact information for directory listings

    .tel domains have a single purpose: contact information. Therefore, search engines will not mistake .tel data for other less relevant information and will integrate .tel data into their local directory page offerings.

    1. • Continuous re-indexing

    Actively used .tel domains will be more appealing to search engines. As contact information in a .tel can be easily changed using profiles from a mobile device, or keywords can be updated through the control panel, a .tel domain can be made dynamic very easily. From the search engine viewpoint, a resource that is frequently updated and used is highly relevant for the search.

    1. • Structured layout for multi-faceted hierarchy of info

    A hierarchy of folders allows you to create an easily navigable and transparent structure to cater to different groups of visitors with various types of queries. Add a section to sell your product, but also another one to explain what it is, link to specs and comparisons, and a phone line for immediate purchase. Each .tel page (sub-domain) is indexed and viewed independently by search engines.

    1. • Localization for geo-based searches

    Because .tel domains allow text and keywords in any language (UTF-8 encoding), you can have a .tel domain or sub-domain catering to your local audience(s). In addition, the Proxy service that presents your .tel on the web using one of the 11 supported languages depending on browser settings, which again increases relevance for local markets and thus for local search engines in those languages. With these assets, a .tel domain owner can create an SEO strategy and develop a .tel domain into a highly-ranked, useful resource which complements traditional websites. Any domain, a .tel or a traditional one, can get to the top of the results table. Here are a few recommendations on how to make this happen:

      1. • Determine the target group for your .tel and the type of query they are going to have: Are they researching a subject?
      2. Are they willing to buy something?
      3. Are they trying to find a resource they visited previously?

    • Populate your .tel with relevant information.

    The more relevant information that is contained within a domain, the better it is for both search engines and people. Adding irrelevant data dilutes the relevance of a resource. Both for visitors and for search engines, getting an exact match for the requested information is the ideal search experience. Based on your findings in item 1, determine important information of different types and add it to your .tel.

    Search Engine Optimization and the .tel Domain 3

    ©2009 Telnic Limited. All rights reserved.

    1. Do not try to cheat, work out a strategy instead.
     
    Trying to cheat the system by matching one particular search algorithm at a particular time won't be a viable long-term marketing strategy. Real SEO is not about exact domain name vs. number of keywords vs. outbound links. Algorithms change, and search engine companies employ human methods to evaluate and improve their search results. Specially trained 'raters' tell the search engine whether the top results are relevant for the query, while monitored number of clicks shows whether actual users follow the links at the top of the search results table.
    1. • Make your .tel interesting for visitors to generate inbound links.
    If visitors like your .tel, they will link to it. Search engines often attribute high value to the amount of inbound linking. Benefit from the dynamic content of .tel to announce special deals, competitions, promo codes and free trials. Visitors will keep coming back and linking to your resource.
    1. • Update and add information often.
    Adding new content such as special offers, new menus, pricing changes, opening times, news or links to other useful resources (whether paid listings or free) can enhance the usefulness of your .tel domain In traditional websites, search engines take the age of the page into account during indexing. Even though a .tel domain is not simply a webpage, search engines use the length of time the data has been static as an indication of its usefulness, so make sure it's also refreshed and renewed in the same way. Again, this can be as simple as changing profiles, or refreshing the keywords.
    1. • Use your .tel and make it your contact hub.
    Sign your blog, forum posts and email with your .tel, add it to your profile on social and professional networks, give it away on cards. Use every free resource you can in order to link to and from your .tel domain in order to create a strong association with relevant resources on the Internet. A .tel domain is the also perfect place to list your websites and provide inbound links to them. The more social your .tel is, the better it will be viewed by search engines. To re-iterate, you have fantastic instruments at your disposal, but you also need to work on your .tel to optimize it for search engines. As .tel domains grow in popularity and become widely adopted, search engines will become more aware of this new extension, and will provide more sophisticated ways of indexing these domains.
  • miércoles, 21 de julio de 2010

    Nos unimos a la propuesta para que Telnic saque a la venta los dominios de 1 y 2 caracteres, dominio .tel

     

    Ahh... One and a Two

    Heyo,

    Ahh... one and a two

    Today is the day that the newly repackaged .CO domain extension offers availability on a first-come first-served basis to the general public. At the time of this writing, in less than 3 hours, for about $25-$30 anyone can register a .CO domain from one of 10 pre-approved ICANN-accredited registrars and their respective resellers. This message is not about their new launch and how the .CO registry – Cointernet.co staged, and continues to stage a brilliant marketing campaign, it's more about taking a page from their strategy and developing a grassroots effort to see if we can assist Telnic to achieve some parallel results, results that may help to increase notoriety and acceptance of the .tel extension worldwide.

    One of the marketing tools that .CO employed was to be pre-authorized by their ICANN charter to sell one and two character domains. I won't go into the obvious pros (there are no cons) of owning and using extremely rare one and two character domains because as we all know, unless you're in the porn biz of course, that shorter is better. Cointernet offered companies and organizations the ability to register one and two character domains where doing so would not only be consistent with their stated business objectives, but to also to create a ton of marketing buzz that would light up the blogospheres, the Twitter'spheres and the YouTube'ospheres of the world.

    Well… it worked. Worked in spades.

    First they held an auction for the single-character domain e.co. It attracted a final bid of US$81,000 and in another stroke of brilliance the proceeds were donated to charity. How's that for getting the 'greens', the tree-huggers and the philanthropically challenged on board? So the benchmark was set. Before a single .CO domain was made available to the general public, .Cointernet established a market value for their single character domains.

    But it didn't stop there.

    Twitter, currently taking over the world 140 characters at a time and the 11th most popular website in the world according to Alexa, (take it with a grain of salt) bought t.co as an URL shortening tool and a vehicle to control certain security aspects of Twitter tweets. Shurly shome smart people doing some smart thinking.

    And now we hear tell…

    That over at Overstock.com, that huge US-based recycling bin (revenue in 2009: $876 gazillion) has just purchased o.co for a whopping $350,000. That, my amigos is what Spinmeisters do best.

    So the point of all of this?

    Is to begin our own little TelMasters campaign to support Telnic so that they too might become authorized to sell one and two character domains. I can't think of a better, more cost effective way to help generate some new buzz and to help pump up the volume (and hopefully the value) on .tel domains.

    Campaign for one and two character .tel domains

    Use the following as a guide, or better yet if you have the time, add your own comments to support this initiative.

    Email to: community@telnic.org

    Gentlemen (and Nadya)

    This is a formal request that Telnic take whatever measures necessary to be able to offer and support one and two character .tel domains, respectively.

    Many other registries offer this option and aside from the obvious market value of the domains to both .tel owners and consumers, Telnic needs to be able to offer these options in order to compete on an equal, level playing field with other registries. Not having the ability to offer one and two character domains severely limits Telnic's competitive place in the market and the overall value as a domain extension.

    Yours truly,
    Mark and Scott
    TelMasters

    Our only other request is that if you can add your support, please do it NOW.
    comparador seguros  comparador seguros aeropuerto hoteles aeropuerto hoteles prestamos teléfonos portátiles móviles joyería

    martes, 20 de julio de 2010

    ¿Han pasado ya 10 años desde la idea de los dominio .tel?



                         Internet-Telephony Directory           April 2000     Telephone Number Mapping (enum)                             D. Peek                                                              R. Walter                                                             D. Ranalli    Internet Draft                                              VMA-TWG    Document: draft-peek-enum-itd-00.txt>                    April 2000    Category: Informational                        Internet-Telephony Directory for                     Mapping E.164 to Internet Addresses   Status of this Memo     This document is an Internet-Draft and is in full conformance with    all provisions of Section 10 of RFC2026 [1].     Internet-Drafts are working documents of the Internet Engineering    Task Force (IETF), its areas, and its working groups. Note that    other groups may also distribute working documents as Internet-    Drafts. Internet-Drafts are draft documents valid for a maximum of    six months and may be updated, replaced, or obsoleted by other    documents at any time. It is inappropriate to use Internet- Drafts    as reference material or to cite them other than as "work in    progress."  The list of current Internet-Drafts can be accessed at    http://www.ietf.org/ietf/1id-abstracts.txt    The list of Internet-Draft Shadow Directories can be accessed at    http://www.ietf.org/shadow.html.  1. Abstract     A holistic directory system is described which translates a standard    E.164 telephone number into the Internet address information    required to support IP-enabled communications applications such as    real-time voice, voice-messaging, fax or unified-messaging. The    proposed system utilizes two logical control tiers to implement the    translation.     The first logical control tier is patterned after a Top Level Domain    (TLD) of the Internet Domain Name System (DNS).  This first-tier    provides a mechanism for locating the appropriate directory within    the second logical tier of the Internet-Telephony directory system    where authoritative Internet address information is stored for a    given E.164 number.  This first-tier is expected to conform to the    regulatory and operational standards defined by the Internet    Corporation for the Assignment of Names and Numbers (ICANN) for the    operation of top-level domains.     The second logical control tier provides a mechanism for accessing    and managing authoritative Internet address information associated    with an E.164 number.  This tier consists of widely distributed DNS    servers controlled by service providers, and corporate network    operators.  Distributed ownership of the second tier directories    allows organizations to control the Internet address information    associated with the E.164 numbers under their day-to-day control.        Peek, Walter, Ranalli     Expires - October 2000                     1 
                         Internet-Telephony Directory           April 2000                             Table of Contents      1.    Abstract                                               1     2.    Conventions used in this document                      3    2.1     Terminology                                          3     3.    Introduction                                           5    3.1     Overview                                             5    3.2     Requirements                                         5     4.    System Description                                     6    4.1     Directory Locator Service (DLS)                      6    4.1.1   The E.164 Domain Name Space                          7    4.1.2   Multiple Application Support                         7    4.1.3   Application Specific E.164 Domain Name Resolution    8    4.2     Authoritative Directory Service (ADS)                9    4.2.1   Resource Record for URI's                            9     5.    E.164 Domain Name Registration                         10    5.1     Background & Scope                                   10    5.2     List Of Actors                                       10    5.3     DLS Registration Process                             11     6.    Application Scenarios                                  11    6.1     SIP appliction                                       11    6.2     VPIM application using LDAP                          12    6.3     VPIM application without LDAP                        12    6.4     Multiple Internet-Telephony service providers        13     7.    Security Considerations                                13    7.1     DLS Security                                         13    7.2     ADS Security                                         13     8.    Prevous Work                                           13     9.    References                                             14     10.   Acknowledgments                                        15     11.   Author's Addresses                                     15     Appendix A.    Conflict Resolution Process                   16     Full Copyright Statement                                     17                Peek, Walter, Ranalli     Expires - October 2000                     2 
                         Internet-Telephony Directory           April 2000  2. Conventions used in this document     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 RFC-2119 [2].  2.1 Terminology     A-record             - Address Record; a standard DNS resource                            record.     ADS                  - Authoritative Directory Service. The second                            logical control tier of the Internet-                            Telephony Directory.     DLS                  - Directory Locator Service.  The first logical                            control tier of the Internet-Telephony                            Directory.     DNS                  - Domain Name System     E.164 Number         - International telephone number as defined                            by the ITU E.164/I.331 [13] standard.                            (e.g. 16033624315)     E.164 Subscriber     - Corporation or individual that has subscribed                            to a PSTN service and been assigned one or                            more associated E.164 numbers.     EMA                  - E-Business Forum (www.ema.org)     ENUM                 - IETF Telephone Number Mapping work group.     ITD                  - Internet-Telephony Directory defined in this                            Document.     ITU                  - International Telecommunications Union.  See                            www.itu.org.     ICANN                - Internet Corporation for the Assignment of                            Names and Numbers (ICANN).     IETF                 - Internet Engineering Task Force(www.ietf.org)     Internet Address     - General term that provides a simple and                            extensible means for identifying an Internet                            resource. Used synonymously with a URI.     LDAP                 - Lightweight Directory Access Protocol;     NAPTR-Record         - Naming Authority PoinTeR; a standard DNS                            resource record.     NS-record            - Name Server record; a standard DNS resource                            record      PSTN Carrier         - Telephone company that assigns E.164 numbers                            to E.164 subscribers. (Corporations or                            individuals)   Peek, Walter, Ranalli     Expires - October 2000                     3 
                         Internet-Telephony Directory           April 2000      Registrant           - E.164 subscriber (corporation or individual)                            that has registered one or more E.164                            numbers in the Internet-Telephony directory.     SIP                  _ Session Initiation Protocol; used in                            establishing a voice over IP call.     TXT-Record           - Text record; a standard DNS resource record.     URI                  - Uniform Resource Identifier                            (i.e. sip:joe@acme.com, ldap://server.com)     VMA                  - International Association for Enhanced Voice                            Services. (www.ivma.ch)     VPIM                 - Voice Profile for Internet Mail     Zone                 - A region of a domain name space that is                            managed by a DNS name server.                                           Peek, Walter, Ranalli     Expires - October 2000                     4 
                         Internet-Telephony Directory           April 2000   3. Introduction  3.1 Overview     This document defines the architecture of an Internet telephony    directory system suitable for global deployment.  It draws upon    information contained in the many previous proposals related to    Internet directory services.  This document attempts to extract the    most useful features of each proposal and meld them into an approach    designed to best meet the needs of the entire Internet-Telephony    industry.     A serious impediment to the development and acceptance of Internet-    Telephony services is the different addressing schemes employed by    the Public Switched Telephone Network (PSTN) and the Internet.  A    global directory service that enables the translation of a PSTN    telephone number (E.164 number) into a corresponding Internet    address eliminates this impediment.  The precise nature and    structure of such a directory has been the object of considerable    speculation, research and discussion.  A number of companies and    technical groups, including the VMA, EMA, IETF and various    organizations within the ITU have made numerous contributions to    this effort.     Telephone numbers follow a well-defined format governed by the E.164    standard of the International Telecommunications Union (ITU).    Therefore, translating a telephone number into an Internet address    is a rather straightforward task.  However, complexities emerge as    the concept is expanded globally and extended to include multiple    Internet-Telephony service providers, each providing different    services tied to the same E.164 number.     Consensus appears to have emerged on at least two key points:       -  The Internet Domain Name System (DNS) is an excellent         technology for the first-tier of the Internet Telephony         Directory.       -  A single-tier system cannot adequately meet the needs of all         Internet-Telephony applications.  Scalability, operational         complexity and information control issues, all mitigate against         a single tier model.     The system proposed herein utilizes the Internet Domain Name System    within a two-tier logical control model to translate an E.164    telephone number into an application specific Internet Address.      Please send comments on this document to the ENUM working group or    directly to peek@evds.com.            Peek, Walter, Ranalli     Expires - October 2000                     5 
                         Internet-Telephony Directory           April 2000     3.2 Requirements     The directory solution:          1. MUST be globally accessible.          2. MUST be highly scalable, responsive, and efficient in its            use of network resources.          3. MUST be flexible enough to support the addressing            requirements of all Internet-Telephony applications. (e.g.            Voice messaging, IP-Telephony, Fax, etc.)          4. Must support multiple Internet-Telephony applications per            E.164 number that may be provided by different application            service providers. (e.g. IP-Centrex from one provider and            Unified-Messaging from another application service provider)   4.  System Description     The system proposed herein utilizes DNS within a two-tier control    model to translate an E.164 telephone number into an application    specific Internet Address.  The first-tier is a "Directory Locator    Service" (DLS) that maps an E.164 telephone number into the IP    address of a second-tier authoritative directory.  The second-tier    is an "Authoritative Directory Service" (ADS) that translates an    E.164 number into an application specific Internet address.  4.1 Directory Locator Service (DLS)     The DLS provides the high-level function of referring a requesting    Internet-Telephony application to the Authoritative Directory    Service (ADS) containing the desired Internet address information    associated with an E.164 number.  The DLS is envisioned as a global    resource for the entire Internet-Telephony industry and as such, is    an ideal candidate for an Internet Domain Name System "Top Level    Domain" (TLD).     Following conventions observed with all existing top-level domains,    (i.e., .com, .net, .org, etc.) the DLS utilizes Name Server (NS)    records and associated A records to delegate authority to    subordinate Name Servers.  This system allows an Internet-Telephony    application or platform to iteratively access a hierarchy of DNS    name servers until the desired resource record information is found    or until the search is exhausted.  This process is commonly referred    to as "resolution".  See RFC1034 [12] for more information.     A Directory Locator Service defined as a DNS top-level domain offers    several advantages:          - A top-level Internet domain is a global resource that           operates under a well-defined regulatory and operational           structure.          - Through the use of standard DNS resolution, a single query is           sufficient to locate the desired Internet address           information.     Peek, Walter, Ranalli     Expires - October 2000                     6 
                         Internet-Telephony Directory           April 2000  4.1.1 The E.164 Domain Name Space     The current practice for IETF ENUM working group documents is to use    "e164.foo" when referring to top-level domains.  This document    proposes the creation of a new top-level domain called "tel" as the    root domain of the E.164 domain name space.  Sub-domains of "tel"    may not be arbitrarily defined; rather they are defined in    accordance with the ITU E.164/I.331 [14] standard. For simplicity of    understanding the context and use of this proposed TLD, the examples    in this document utilize the "tel" top-level domain in place of    "e164.foo".     An E.164 standard [14] telephone number consists of a country code    and a nationally specific part.  For reasons of scalability,    reliability and flexibility, the E.164 domain name space should be    partitioned into a number of zones distributed across multiple name    servers.  The segmentation of an E.164 number into a country code    and a nationally specific part, with the latter further segmented by    area-code/city-code, presents natural boundaries for such    partitioning.  4.1.2 Multiple Application Support     One of the key design requirements of the Internet Telephony    Directory is the ability to support multiple Internet-Telephony    applications using a single E.164 number.  For example, a single    E.164 number will frequently be used for both real-time voice    (SIP/H.323) and voice messaging (VPIM) applications.     This multi-application requirement has been addressed in all    previous ENUM drafts.  The Internet-Telephony Directory system    described in this document further advances this concept by enabling    various application specific Internet addresses tied to a single    E.164 number to be controlled by different service providers.     Consider the following scenario:  A company wants to use Service    Provider-A for an IP-enabled real-time voice service and Service    Provider-B for a unified messaging service.  Both service providers    require control over the Internet address information associated    with their respective services.  As a result, the requirement exists    to distribute control of Internet address information at the    application level.  Further qualifying a name within the E.164    domain name space through the addition of an application specific    prefix or "Service Protocol", fulfills this requirement.     The Service Protocol naming conventions associated with various    Internet-Telephony applications are subject to standardization.  For    example, the list of supported Service Protocol names might include:          sip or h323     (for voice over IP applications)         vpim            (for voice messaging service)         smtp            (for e-mail and unified messaging applications)         fax             (for IP-fax applications)     These example names correspond to several of the service names    discussed in the ENUM workgroup.  This list will increase as new and    different IP-communications services become available.      Peek, Walter, Ranalli     Expires - October 2000                     7 
                         Internet-Telephony Directory           April 2000   4.1.3  Application Specific E.164 Domain Name Resolution     Internet-Telephony applications query the DLS using a DNS query    based on an application specific E.164 domain name.  The following    steps define its formulation:     1.   Start with a complete E.164 telephone number.                  Example: +1-603-362-4315     2.   Remove all characters other than digits.                  Example: 16033624315     3.   Reverse the order of the phone number.                  Example: 51342633061     4.   Insert a "." between each digit and at the end.                  Example: 5.1.3.4.2.6.3.3.0.6.1.     5.   Append, as a suffix, the E.164 top-level domain.                  Example: 5.1.3.4.2.6.3.3.0.6.1.tel.     6.   Append, as a Prefix, a "Service Protocol" name indicative of         the desired service.                  Example: sip.5.1.3.4.2.6.3.3.0.6.1.tel.     When a client DNS resolver queries the DLS, the DLS returns the NS-    and A-records which define the IP address of the next DNS name    server.  Upon receipt of the NS and A records from the DLS, the    client resolver reissues the query to the newly discovered name    server.     The following illustrates a sample zone file fragment containing NS    and A records:      4.3.2.1.5.9.4.1.6.1.4.4.tel.        IN NS  ns1.UKSP.tel.                                         IN NS  ns2.UKSP.tel.     5.1.3.4.2.6.3.3.0.6.1.tel.          IN NS  ns1.CompanyA.tel.                                         IN NS  ns2.CompanyA.tel.      ns1.UKSP.tel.                       IN A   208.146.45.55     ns2.UKSP.tel.                       IN A   208.146.45.56     ns1.CompanyA.tel.                   IN A   208.155.55.55     ns2.CompanyA.tel.                   IN A   208.155.55.56             Peek, Walter, Ranalli     Expires - October 2000                     8 
                         Internet-Telephony Directory           April 2000   4.2 Authoritative Directory Service (ADS)     The ADS provides authoritative Internet address information in    support of one or more Internet-Telephony applications associated    with a subset of E.164 numbers.  The ADS is a delegated DNS name    server [12] that must be properly registered with the top-tier DLS.    Any E.164 Subscriber (corporation or individual that has been    assigned one or more E.164 numbers) may register, deploy and operate    an ADS or delegate the function to a third-party service provider.     The ADS will return one of the following results based on a query    using an application specific E.164 domain name.          1. An end-point address in the form of a URI. For example:             Query:   sip.5.1.3.4.2.6.3.3.0.6.1.tel            Result:  sip:user@company.com             Query:   smtp.5.1.3.4.2.6.3.3.0.6.1.tel            Result:  mailto:user@company.com          2. A referral to a non-DNS service in the form of a URI.  For            example, voice messaging applications requiring spoken name            will utilize a referral to an LDAP directory:             Query:   vpim.5.1.3.4.2.6.3.3.0.6.1.tel            Result:  ldap://ldap.company.com:389/e164=16033624315,dc=tel          3. The NS-records and associated A-records for a delegated ADS            that contains the URI for the requested application.  This            ADS delegation feature enables control over various            Internet-Telephony applications tied to the same E.164            number to be delegated out to different service providers.          4. A negative response.  Indicates that no Internet address            information exists for the specific application queried.   4.2.1  Resource Record for URI's     Currently, no standard DNS resource record exists which specifically    maps a domain name to a complete URI.  However, existing resource    records such as the TXT or NAPTR records may be utilized to achieve    the desired effect until a new resource record with the specific    intent of mapping a domain name to a complete URI is standardized    and deployed.     The Text (TXT) resource record provides a simple yet effective    mechanism for associating an E.164 domain name to a URI.  The Domain    Implementation and Specification RFC 1035[15] defines TXT records as    follows:          "TXT RRs are used to hold descriptive text.  The semantics of         the text depends on the domain where it is found."      In the context of the E.164 domain name space, the TXT record is    semantically defined as mapping an application specific E.164 domain    name to a URI.  Both NAPTR and TXT records could be used to    implement this solution.  Neither is perfect for the task at hand    but TXT records have the advantage of being simple, efficient, and Peek, Walter, Ranalli     Expires - October 2000                     9 
                         Internet-Telephony Directory           April 2000     widely supported.  The following example zone file fragment    demonstrates the utility of TXT resource records.       $ORIGIN 2.6.3.3.0.6.1.tel.       sip.5.1.3.4   IN TXT  sip:dpeek@ServiceProvider2.com      smtp.5.1.3.4  IN TXT  mailto:dpeek@acme.com      vpim.5.1.3.4  IN TXT  ldap://ldap.acme.com/e164=16033624315,dc=tel   5.  E.164 Domain Name Registration  5.1 Background & Scope     The creation and eventual assignment of E.164 numbers to end-user    corporations and individuals (E.164 Subscribers) is a well-defined    process that exists within the PSTN today.  The registration of    E.164 numbers in the Internet-Telephony Directory is complimentary    to this existing process and takes place only after a number has    already been assigned by a PSTN Carrier to an E.164 Subscriber.  5.2 List Of Actors     Following the current practice with all Internet top-level domains,    the registration of E.164 numbers in the DLS will be managed by a    single trusted "Registry".  It is assumed that this exclusive    Registry function will fall under the regulatory control of ICANN.    The actors involved in the registration process are as follows:     ICANN:      -  Internet Corporation for the Assignment of Names and Numbers.      -  Selects and regulates the exclusive DLS Registry.      -  Defines pricing for the top-tier regulated DLS service.     DLS Registry:      -  Entity that deploys and operates the globally distributed DLS         service under contract from ICANN.      -  Entity that builds, deploys and maintains a DLS registration         service for use by all E.164 Registrants.      -  Entity that manages the DLS "Conflict Resolution Process".         (See Appendix A for Conflict Resolution Process proposal)     E.164 Registrant:      -  E.164 Subscriber or designated representative that registers         numbers and an associated ADS in the top-level DLS.      -  Entity that either operates its own ADS or outsources the         function to a third-party provider.  (Corporations may choose         to operate their own ADS while individuals are likely to         outsource the function to a service provider)      -  Entity that agrees to the terms and conditions of the DLS         Registration Agreement as set out by the DLS Registry.            Peek, Walter, Ranalli     Expires - October 2000                    10 
                         Internet-Telephony Directory           April 2000   5.3  DLS Registration Process     1. E.164 Registrant deploys an ADS or contracts with a third-party       provider of ADS services.     2. Registrant "registers" one or more E.164 numbers and associated       ADS via the DLS registration service.     3. Registrant agrees to the terms and conditions of the DLS       Registration Agreement as set forth by the Registry under the       control of ICANN.     4. DLS Registration service (operated by the Registry) checks the       Registrants E.164 numbers against the list of existed registered       numbers to determine if a conflict exists.  If no conflict       exists, the registration is approved.  If a conflict exists, the       DLS Registry works with the two parties that have both claimed to       be the valid E.164 Subscriber for the same number to resolve the       conflict. (See Appendix A for a more detailed description of the       Conflict Resolution Process)     5. Registrant pays the DLS Registry fees and any associated conflict       resolution fees as set forth under the DLS Registration agreement       defined by ICANN.     6. DLS Registry makes Registrant name, address, and contact       information freely available via an on-line Who-is database.       This is a requirement for any top-level domain and an important       support feature for the conflict resolution process.     6.  Application Scenarios  6.1 SIP Application     A SIP application seeking to establish a SIP session formulates an    application specific E.164 domain name and issues a single query to    the DLS for the associated TXT-record through a standard DNS    resolver.        Query:   sip.5.1.3.4.2.6.3.3.0.6.1.tel.     The DLS responds to this query with the NS- and A-records of the    appropriate ADS.  The DNS resolver, after receiving the NS- and A-    records, automatically reissues the identical query to the new name    server (ADS).     Note that the SIP application is only aware of the first query. The    DNS resolver automatically reissues queries through the standard    iterative resolution process [12] until the TXT-record information    is returned.        Result:  sip:user@company.com     The requesting SIP application now has the Internet-Telephony    address information it requires to establish a voice over IP call    using the SIP protocol based simply on a telephone number.   Peek, Walter, Ranalli     Expires - October 2000                    11 
                         Internet-Telephony Directory           April 2000  6.2 VPIM application using LDAP     A VPIM application seeking to send a voicemail message over the    Internet formulates an application specific E.164 domain name and    issues a single query to the DLS for the associated TXT-record    through a standard DNS resolver.        Query:   vpim.5.1.3.4.2.6.3.3.0.6.1.tel.     The DLS responds to this query with the NS- and A-records of the    appropriate ADS.  The DNS resolver, after receiving the NS- and A-    records, automatically reissues the identical query to the new name    server (ADS).     Note that the VPIM application is only aware of the first query. The    DNS resolver automatically reissues queries through the standard    iterative resolution process [12] until the TXT-record information    is returned.        Result:  ldap://ldap.acme.com:389/e164=16033624315,dc=tel     Using the LDAP URI, the VPIM application queries the LDAP directory    to retrieve a VPIM address and "spoken name" via the standard VPIM    schema [4].  Note, the LDAP directory is used in this scenario to    retrieve an audio representation of the destination party's name    that cannot be easily stored in a DNS directory.     6.3 VPIM application without LDAP     LDAP is clearly the technology of choice to manage and store complex    VPIM user information such as spoken-name, audio encoding types, and    other VPIM related address.  However, the installed base of LDAP    servers is limited at present and their increased operational    complexity may inhibit some organizations from deploying enhanced    VPIM services.  For organizations that are not prepared to operate    an LDAP directory, the ADS can be provisioned to return VPIM mailbox    addresses in the form of a mailto URI.  For example:        Query:   vpim.5.1.3.4.2.6.3.3.0.6.1.tel.        Result:  mailto:610002@sprovider.net     By returning a mailto URI the organization forfeits the ability to    supply spoken-name and other enhanced capabilities to querying VPIM    applications.               Peek, Walter, Ranalli     Expires - October 2000                    12 
                         Internet-Telephony Directory           April 2000   6.4  Multiple Internet-Telephony service providers     A company wants to use Service Provider-1 (SP1) for an IP-enabled    real-time voice service and Service Provider-2 (SP2) for a unified    messaging service.  Both service providers require control over the    Internet address information associated with their respective    services.  As a result, the requirement exists to distribute control    of Internet address information at the application level.     To achieve this objective the Company utilizes the inherent    delegation capabilities of the ADS and provisions its application    specific E.164 domain names to reference the appropriate service    provider:     sip.0.0.0.5.2.6.3.3.0.6.1.tel      IN NS ns.SP1.tel    vpim.2.0.0.5.2.6.3.3.0.6.1.tel     IN NS ns.SP2.tel                        ns.SP1.tel     IN A  208.150.79.113                        ns.SP2.tel     IN A  78.21.79.114   7. Security Considerations  7.1 DLS Security     All data stored in the DLS is considered public Internet-Telephony    information and may be retrieved by any requesting Internet-    Telephony application.  7.2 ADS Security     All data stored in the ADS is considered public Internet-Telephony    information that may be retrieved by any requesting Internet-    Telephony application.    8. Previous Work     Many of the concepts outlined in this document are drawn from two    years of direct experience associated with implementing a directory    service in support of the voice messaging industry initiative called    the "Global Voice Mail Service" or GVMS.     The International Association for Enhanced Voice Service (formerly    the Voice Mail Association or VMA) created and began funding the    GVMS initiative in early 1997.  The goal of the GVMS initiative has    been to connect service provider and enterprise voicemail platforms    on a worldwide basis via the Internet.  Key functionality    demonstrated through the GVMS initiative included the ability for    end-users to send voice messages or reply to voice messages over the    Internet without incurring the long distance charges associated with    placing a return telephone call.     Eight leading voicemail vendors participated in creating the GVMS    solution that was demonstrated at VMA conferences in Athens (98),    Helsinki (99) and at Telecom 99 in Geneva.  The vendors include    Comverse, Brite, Glenayre, Lucent, Nortel, Tecnomen, Alcatel, and    UNISYS.  NetNumber.com, Inc. (formerly EVDS) provided the global    directory service supporting the GVMS demonstrations.   Peek, Walter, Ranalli     Expires - October 2000                    13 
                         Internet-Telephony Directory           April 2000  9. References     [1] Bradner, S., "The Internet Standards Process -- Revision 3",         BCP 9, RFC 2026, October 1996.     [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement         Levels", BCP 14,RFC 2119, March 1997     [3] Faltstrom, P., "E.164 and DNS", Work in progress,         <draft-faltstrom-e164-05.txt>,January 2000     [4] Brown, A., "E.164 Resolution", Work in progress,         <draft-brown-e164-01.txt>, October 1999     [5] Brown, A., "Enum Requirements", Work in progress,         <draft-ietf-enum-00.txt>, NOvember 1999     [6] Vaudreuil, G., "Voice Messaging Directory; Address Resolution         Services", Work in progress, <draft-vaudreuil-ars-01.txt>,         December 1999     [7] Vaudreuil, G., "Address Validation Service", Work in progress,         <draft-vaudreuil-avs-00.txt>, December 1999     [8] Vaudreuil, G., "Telephone Number Base Directory Service", Work         in progress, <draft-vaudreuil-e164dir-00.txt>, March 2000     [9] Shockey, R., "The Use of DNS based E.164 Resolution Services by         Internet Fax", Work in progress,         <draft-shockey-e164toifax-00.txt>, December 1999     [10] Berners-Lee, T., "Uniform Resource Identifiers (URI): Generic         Syntax", Standards Track,  RFC 2396, August 1998     [11] Daniel, R., Mealing, M, "Resolution of Uniform Resource         Identifiers using the Domain Name System", Experimental,         RFC 2168, June 1997     [12] Mockapetris, P., "Domain Names - Concepts and Facilities",         STD 13, RFC 1034, November 1987.     [13] ITU-T Rec, "The International Public Telecommunication         Numbering Plan", Recommendation, ITU-T Rec. E.164/I.331 ,         May 1997.                   Peek, Walter, Ranalli     Expires - October 2000                    14 
                         Internet-Telephony Directory           April 2000   10. Acknowledgments     Our special thanks to Dr. Thomas P. Sosnowski for his help in    editing this document. Also thanks to Chuck Santos for providing us    with many technical details.  We would also like to recognize Anne    Brown, Greg Vandreuil, and Patrik Falstrom for their previous work    in this area.  Thanks also to Michael Mealling for providing us with    details on NAPTR records.   11. Author's Addresses     David P. Peek      VMA, Technical Working Group Chairman      13 Village Drive      Atkinson, NH  03811      Phone: 1-603-362-4315      Email: peek@evds.com     Robert Walter      NetNumber.com, VP Development & Operations      Wannilancit Technology Center      650 Suffolk Street, Suite 307      Lowell, MA 01854      rwalter@netnumber.com     Douglas Ranalli      NetNumber.com, President/CEO      Wannilancit Technology Center      650 Suffolk Street, Suite 307      Lowell, MA  01854      dranalli@netnumber.com                              Peek, Walter, Ranalli     Expires - October 2000                    15 
                         Internet-Telephony Directory           April 2000   Appendix A:  Conflict Resolution Process:     Conflict over the registration of numbers in the top-level DLS could    occur for one of three general reasons:       -  Data Entry Error:  E.164 Registrant makes a data entry error         during the DLS registration process and inadvertently registers         a wrong number.       -  Old Data Error:  E.164 Registrant returns day-to-day control         over one or more numbers to the originating PSTN carrier but         fails to update the DLS registration records.  Example:  A         corporation shuts down an office, terminates its phone service         but fails to un-register the numbers in the DLS.       -  Intentional Error:  E.164 Registrant intentionally claims to be         the E.164 Subscriber that has day to day control over a number         when in fact they are not.     Conflict occurs when two Registrants both claim to be the valid    E.164 Subscriber for the same number.  Conflict over ownership of a    name or number in the Internet naming space is not a new problem.    In the domain name space conflict occurs when one entity registers a    name like "McDonalds" in a top-level-domain (mcdonalds.com) and then    another entity claims trademark control over the name "McDonalds".    In the case of the E.164 domain name space, conflict can be easily    resolved because it is clear how the day-to-day control of a number    is defined:       -  PSTN Service Provider Control:  A PSTN Service Provider         (telephone company) that has registered an E.164 number in the         Internet-Telephony directory on behalf of a customer can         certainly validate the identity of the E.164 Subscriber.       -  E.164 Subscriber Control:  A corporation or individual that has         been assigned a number through the normal PSTN provisioning         process is the E.164 Subscriber and is the only valid         Registrant for that number.  Confirmation of such assignment         can be obtained through reviewing PSTN billing records.     Conflict is identified when an entity attempts to register a number    that has already been registered by another E.164 Registrant.  The    burden of maintaining a system for resolving conflict in an orderly    process falls on the DLS Registry.  A process might operate under    the following principles:       -  Cost of resolution should be born by the mistaken party:  It         seems reasonable to expect E.164 Registrants to take         responsibility for their own mistakes.  If the DLS Registry is         required to take action to correct a registration mistake made         by a Registrant then the mistaken party should pay the direct         costs associated with the resolution process.  The terms of         such a process can be outlined in the DLS Registration         Agreement signed by each E.164 Registrant.        Peek, Walter, Ranalli     Expires - October 2000                    16 
                         Internet-Telephony Directory           April 2000        -  Cost of conflict resolution should be zero:  In most cases,         conflict will be the result of a simple human error.         Registrants that make a data entry mistake should be given an         opportunity to correct the mistake at zero cost.  An on-line         system can easily be maintained by the DLS Registry to identify         conflicts, notify the appropriate Registrant, and enable on-         line corrections.  In the event that the entire process can be         managed via an automated on-line process and resolved in a         reasonable period of time then the cost to all parties should         be zero.       -  Billing records can be used to clarify difficult conflicts:  In         the most difficult case where two entities claim control over a         number and the conflict cannot be resolved through an automated         system, billing records can be used to clarify day to day         control over a number.  Extended conflict like this is likely         to be rare, particularly in light of the provision that the         mistaken party is required to pay the direct cost of conflict         resolution under this model.    Full Copyright Statement     "Copyright (C) The Internet Society (date). 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.         Peek, Walter, Ranalli     Expires - October 2000                    17 
    comparador seguros  comparador seguros aeropuerto hoteles aeropuerto hoteles prestamos teléfonos portátiles móviles joyería 

    lunes, 19 de julio de 2010

    La muerte de los .mobi y el nacimiento de los .tel

    I guess it has been about 3 years ago I started working with the mobi domains. For my windshield repair business, it seemed like a natural fit. After all if you're out on the road and you get a chip on your windshield, you could get the information you need on your cell phone.

    I knew though, that there was one weakness to the mobi domain; it was a website that could be set up with a sub-page written for mobile devices. Some examples of an alternative way to create mobile content would be, "m.example.com" or "example.com/mobile".

    As I see it, another problem was a host that would provide the program to meet mobi specs. Besides being limited at best, I was faced with either a good price and limited ability, or a high price. To solve the problem, I found an open source that cost nothing as long as I provided the storage. The storage wasn't an issue as I have 40 gigabyte of storage through my company's website host, not to mention several hundred gigabyte of bandwidth each month. When you consider, that by mobi specs, a page is limited to 20 kilobytes of data, using my existing host for storage wouldn't be an issue.

    As time has progressed, cell phones have gotten better and can handle a lot more data. This I believe has had an effect on mobi, because the restrictive requirements aren't needed for the newer smart phones. As a result earlier this year, dot mobi was sold. Based on what I've read about the reason for the sale and all of the above issues, this showed me that storm clouds were forming.

    Dot tel, another domain, also is a way to provide mobile content at a competitive price. Shortly after the dot tell domains were opened for sale to the public I purchased a dot tel for my windshield repair business and have seen my business grow due to customers using it on their cell phones.

    Since the mobi sale, on several occasions I found a portion of all 3 mobi sites I have, didn't function properly. On every occasion I had to go in and fix code that mysteriously had changed. While I know that the change of ownership of the domain had nothing to do with the code problems, it appears there are more issues.

    Recently I received notice that the open source provider of the mobile program would soon be charging for the service. That in itself wouldn't be a problem, the price being charged is. How ridiculously high? Well consider that the storage and bandwidth is a very small fraction of what I use for a conventional website. Yet the cost to keep my mobi sites up would be nearly 2 ½ times what I pay for my conventional website.

    Okay, the question then becomes what should I do with WipeOutMS.mobi. Moving that material to WipeOutMS.tel was one option. Placing the material on OnCell411.tel another site I own that is dedicated to providing information while out on the road was a second choice. I had placed MS information on the mobi version of that website.

    After thinking it over I decided to merge the information on WipeOutMS.mobi with OnCell411.mobi and put it on OnCell411.tel. Doing this I believe will create more awareness of multiple sclerosis (MS) and help the cause. A second reason is that to get to MS events you need to travel, and this website is designed for travel.

    So what becomes of the old mobi domains? Well I've pointed OnCell411.mobi at OnCell411.tel, so if you use OnCell411.mobi you will end up at the new website. WipeOutMS.mobi is another story, efforts to redirect that domain with the current registrar has failed. A transfer to another registrar is taking place which will give me total control of the domain. I expect that to be completed by the coming weekend. Finally when I tested the new website with ready mobi it scored a 4, which means it will still load on most cell phones.

    OnCell411.tel is still under development so if you have a problem please let me know. My hope is that this project will bring more MS awareness and more support to find a cure to Wipe Out MS-like diseases like polio has been.

    miércoles, 14 de julio de 2010

    75 dias desde que caduca hasta que queda libre el dominio.tel

    Dot Tel Domain Lifecycle - What does expired and dropped actually mean?

    Are you interested in purchasing a dropped or expired domain?

    Have you noticed a domain has not been renewed beyond its expiration date?

    Wondering why you're unable to simply register it?

    Are you about to bid on a tel domain at an expired auction?

    Read on BEFORE bidding for the domain, because any domain auctioned prior to the correct stage can be reclaimed and renewed by the owner! Yes, even if you WIN the auction!!

    Let's use http://regentstreet.tel/ as our example domain:

    Domain Registration
    http://regentstreet.tel/ is registered on May 1st 2009 with registrar ABC for a 1 year period.

    You are not allowed to transfer this to another registrar until July 1st 2009 (60 days after registration).
    A couple of months prior to expiration, most registrars will send out renewal notifications to the owner.

    Domain Expiration
    On May 1st 2010, if the owner has not renewed, http://RegentStreet.tel then it has 'expired'.
    NOTE: this does NOT mean you can now go and register the domain....

    At this point most registrars will HOLD the domain, allowing you to still renew your domain at the regular price.
    NOTE: you are not allowed to transfer the domain away at this stage unless you renew first

    Domain Deletion
    [40 days after Domain Expiration]
    After 40 days (July 9th 2010 in our example), most registrars delete the domain.
    NOTE: if you would like to restore your domain during this period there are usually hefty redemption charges applied.

    After a further 30 days the domain can no longer be restored.
    NOTE: the only way to get the domain is to wait until it is dropped from the registry and released to the available pool.

    Domain Dropped and available for Registration
    [75 days after Domain Expiration]
    After a further 5 days the domain is dropped from the central registry and available to register by anyone.

    Good luck hunting for that dropped domain!

    NOTE: as a .tel domain has yet to go through a full registration -> drop period some of the points here may be inaccurate.

    The dates/points listed above are based on a real example (domain name not mentioned) that occured during an attempt to bid and win a tel domain during a registrar's expired domain auction

    martes, 13 de julio de 2010

    TelMasters Open Authorization (OAuth)




    Heyo,

    We're quite excited about having Telmasters Tools validated and approved by Telnic as a genuine OpenAuth client. We'll be converting all our tools (except Traffic Stats) this week and over the weekend. To prepare for this and to have uninterrupted service, please authorize yourself in advance by visiting https://www.telmasters.com/home/oauth. Once you've done this, you will no longer need to provide your CTH username and password to use our tools.

    From inception:

    Telnic, the .tel registry, incorporated a username and password system to securely access your (CTH) control panel. Using the link supplied by your registrar, you enter your username and password in order to populate and manage your .tel domain. Now if you only have one or two domains to manage, the process of inputting usernames and passwords is not that onerous. In addition, if your registrar was on the ball and enabled you to have many domains in one account, you are able to substantially reduce the amount of time required to access your control panel. However, if you have dozens, hundreds or thousands of domains and are at a registrar that does not have the one-account system, it takes an enormous amount of time to list, maintain and retrieve the username and password for each domain.

    Secure Access:

    Open Authorization, (OAuth) is an open standard that allows users to share their private resources (e.g. photos, videos, contact lists) stored on one site with another site or application without having to issue their username and password.
    OAuth allows users to distribute tokens instead of usernames and passwords to their data hosted by a given service provider. Each token grants access to a specific application for specific resources and for a defined duration (e.g. the next 2 hours).
    Thus OAuth allows a user to grant a third party site access to their information stored with another service provider, without sharing their access permissions or the full extent of their data.

    Tapping into the Tools With Peace of Mind:

    OpenAuth lets us provide you with secure domain management services without revealing your CTH username and password when using our tools and applications. Your OAuth request will be approved upon your successful login at your registrar's Client Authentication page, which provides us with an authenticated 'token' that will be used by our tools. This token is valid for seven days, but gets renewed automatically. However, if you wish to revoke access at any time, do so via your CTH control panel > Settings > Approved Clients > Revoke.

    After authentication, all domains in the account associated with any domain you supply will be accessible via OAuth. Should you have domains at different registrars, or domains in different accounts at the same registrar, you will need to approve access for each registrar/account as OAuth is enabled at the account level.

    We'll keep you posted as soon as further developments become available.

    Cheers,
    TelMasters
    Mark and Scott

    casa rural burgos camino del cid  alicante camino del cid camping alicante camino del cid albergues alicante camino del cid