ICANN ICANN Email List Archives

[gnso-pednr-dt]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-pednr-dt] Post expiry domain email functionality.

  • To: "Michele Neylon :: Blacknight" <michele@xxxxxxxxxxxxx>
  • Subject: Re: [gnso-pednr-dt] Post expiry domain email functionality.
  • From: Sivasubramanian M <isolatedn@xxxxxxxxx>
  • Date: Wed, 26 May 2010 00:39:02 +0530

Dear Michele,

On Tue, May 25, 2010 at 11:27 PM, Michele Neylon :: Blacknight <
michele@xxxxxxxxxxxxx> wrote:

>
>
> On 25 May 2010, at 14:53, Sivasubramanian M wrote:
>
> > Dear Michelle
> >
> >
> > On Tue, May 25, 2010 at 4:24 PM, Michele Neylon :: Blacknight <
> michele@xxxxxxxxxxxxx> wrote:
> >
> >
> > On 25 May 2010, at 11:31, Sivasubramanian M wrote:
> >
> > > Hello
> > >
> > > I asked some Google Executives if there could be a technical solution
> from an external service provider such as Gmail to the post expiry domain
> email situation. The question was sent by email with a copy to Olivier
> Crepin Leblond of ISOC England / Euralo.
> > >
> > > While he doesn't find the commercial prospects for the external service
> provider convincing, his response points to the fact that technically there
> is a definite way out of the problem.
> >
> >
> > So who is going to pay for it?
> >
> > Definitely not the Registrars. It it takes it will take shape as a
> service for which the Registrants will pay
>
> Siva
>
> Pay who and how?
>
> Bearing in mind that you're talking about registrants who haven't renewed
> their domain names ...
>

There are several models by which an external email service could offer such
a service. Just as there is a free version and business version of a service
such as gmail, a basic level of email service could be offered free to
Registrants by gmail / msn / yahoo (if they are interested in a subscriber
base of 150 million domain Registrants, increasing). The service provider
may offer optional subscription plans for value added services.

If it is icann / an icann supported email server, the Registrant could pay
an additional email surcharge in cases where he renews the domain after an
interruption. Here there is an issue of the Registrants who choose not to
renew the domain names at all. The cost of email service provided to the
Registrants who choose not to renew domain names has to be factored into the
cost of those who do renew their domain names.


>
>
> > or it will be a service offered on a neo-Interent-business model by a
> company such as Google or MSN or it will be an ICANN supported service by a
> third party.
> >
> >
> >
> > >
> > > It is not necessary to abruptly discontinue email service in a post
> expiry situation.
> >
> > Until you can answer the key question about who is going to pay for it
> then it is going to be necessary
> >
> > Just because it's technically "possible" doesn't render it viable and the
> email exchange clearly supports the view that we have all been promoting for
> months. It makes MORE sense for the registrant to simply renew the domain
> name in a timely fashion.
> >
> > I agree that it makes more sense for Registrants to renew their domain
> names in time. But I am concerned about those Registrants (even if they are
> a smaller proportion) whose domain names expire unnoticed.
>
> And so you expect this "magical" email service to "know" where the mail is
> meant to go?
>

The mail need not go anywhere, the mail traffic inwards, directed to the
domain now comes to the external email service provider / icann server. It
stays there, until the Registrant establishes his ownership, either by prior
anticipatory registration with this post expiry email service or if he had
failed to do that, by some other manner of authentication. At this point of
time, whether or not the Registrant has still renewed his domain name or
not, the email log in functionality is facilitated for the Registrant. He
can keep it on the server or download it to his email client.


>
> You also expect people to be able to access it as well I assume?
>
> How?
>

After establishing that he is the Registrant, he will be able to access it
the same way he accesses any other email service

>
>
>
> >
> > Also your suggestion in this email exchange suggests that ICANN would
> somehow want to get involved with an "icann owned or icann-assigned server"
> (sic) is disturbing.
> > Do you even understand what ICANN's role is in all this?
> >
> > What is wrong if I want ICANN to get involved in an ICANN owned or
> icann-assigned server? It is not disproportionately expensive and it is a
> direct service to domain Registrants about whom ICANN is supposed to care !
>
>
> How are you qualified to decide what is expensive and what isn't?
>

We are talking about 150 + million domain names of which half or more domain
names might also be used for email.  To assure a certain level of perpetuity
for 70 or 75 million (and increasing) email enabled domains, the cost of
setting up and maintaining a redundant / fall back email server may not be
proportionately expensive and can be built into ICANN's cost recovery
calculations.

>
> Just to satisfy my own curiousity ...
>
> How many mail users do you currently manage?
>
> How many mail servers do you currently manage?
>
> How many mail servers have you configured?
>

I have configured email accounts within my own domain names using cpanel.
But if you ask me if I am a Technical Authority with expertise in setting up
an email server from scratch, I am not.

But anyone technically qualified may find that I am not altogether wrong.

Thank you.
Sivasubramanian M


>
>
> >
> >
> >
> >
> >
> > >
> > > The email exchange is attached as a PDF for the committee to act upon
> futher.
> >
> > What committee?.
> >
> > Sorry, I meant WG. This PEDNR WG
>
> OK
>
> >
> > Sivasubramanian M
> >
> >
> >
> > Mr Michele Neylon
> > Blacknight Solutions
> > Hosting & Colocation, Brand Protection
> > ICANN Accredited Registrar
> > http://www.blacknight.com/
> > http://blog.blacknight.com/
> > http://mneylon.tel
> > Intl. +353 (0) 59  9183072
> > US: 213-233-1612
> > UK: 0844 484 9361
> > Locall: 1850 929 929
> > Twitter: http://twitter.com/mneylon
> > -------------------------------
> > Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business
> Park,Sleaty
> > Road,Graiguecullen,Carlow,Ireland  Company No.: 370845
> >
> >
> >
>
> Mr Michele Neylon
> Blacknight Solutions
> Hosting & Colocation, Brand Protection
> ICANN Accredited Registrar
> http://www.blacknight.com/
> http://blog.blacknight.com/
> http://mneylon.tel
> Intl. +353 (0) 59  9183072
> US: 213-233-1612
> UK: 0844 484 9361
> Fax. +353 (0) 1 4811 763
> -------------------------------
> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
> Road,Graiguecullen,Carlow,Ireland  Company No.: 370845
>
>
>


<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy