RE: [registrars] Marina del Rey Registrar Meeting - September 12

["Tim Ruiz" <tim@xxxxxxxxxxx>]

The Registry issue I referred to is regarding the deletion of domains
that have nameservers hosting domains. The problem:

A customer/registrant decides not to renew domain A, or wants to cancel
it. It cannot be removed because it has nameservers hosting domains. The
domains hosted are not sponsored by the registrar of A. The registrar
and the customer are unsuccessful in their attempts to get the
registrants of the hosted domains to reassign nameservers, or remove the
nameservers of domain A. The registrar ends up stuck with another year
of renewal whether or not he can collect it from the registrant of A.

Of course, VeriSign provides somewhat of a work around for this, but it
isn't ideal. The other registries provide no help whatsoever with this.

I realize there is concern for stability, but this should not be
enforced to the point of forcing registrars and/or registrants to pay
for renewals on names they no longer want. I also think too much is left
up to the registrar to resolve. The registry should take a more active
role in solving this issue.

Possible solutions:

If this is left to be completely a registrar problem, then the registrar
should be allowed to request a "forced" delete or cancellation of a
domain name. That would be a specific command that indicates that the
registrar knows they are asking for the domain to be deleted regardless
of the nameserver issue. Of course the registrar may be expected to take
on some liability for this, perhaps representing that efforts have been
made to contact the registrants of the affected domains.

If the registries are willing to be more involved, then perhaps they
could take it upon themselves to agree to cancel these names if the
nameservers in question no longer ping. A separate request to cancel
names of this nature would be submitted, the registry would check them
out, and delete them if appropriate.

Other ideas?

Tim



-----Original Message-----
From: owner-registrars@xxxxxxxxxxxxxx
[mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Michael D. Palage
Sent: Tuesday, August 12, 2003 2:37 PM
To: 'Registrars'
Subject: RE: [registrars] Marina del Rey Registrar Meeting - September
12

Tim:

I have heard some off-list discussion regarding potential Interim
Solutions
to Port 43 problems, some of which may be a viable solution to help stem
the
theft of registrar whois data. Hopefully a summary/draft will be
available
to the list so that all registrars could provide some input to this
common
concern.

With regard to your other "issue" what it is?  I think it would be best
to
flesh out the issues prior to the meeting to maximize the productivity
of
the joint meeting.

Mike

> -----Original Message-----
> From: Tim Ruiz [mailto:tim@xxxxxxxxxxx]
> Sent: Tuesday, August 12, 2003 4:20 PM
> To: 'Elana Broitman'; 'Michael D. Palage'; ross@xxxxxxxxxx
> Cc: 'Registrars'; 'Registrars Executive Committee'
> Subject: RE: [registrars] Marina del Rey Registrar Meeting - September
> 12
>
>
> Can a summary of the "Briefing on proposed interim solution to Port
43"
> be posted to the list within the next week or so?
>
> Also, may issues that we want to bring before the Registry
> representatives be presented here on the list prior to the meeting? I
> won't be able to attend but have at least one issue I'd like to raise
> that I have not heard much discussion on before.
>
> Tim
>
>
> -----Original Message-----
> From: owner-registrars@xxxxxxxxxxxxxx
> [mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Elana Broitman
> Sent: Tuesday, August 12, 2003 1:05 PM
> To: Michael D. Palage; ross@xxxxxxxxxx
> Cc: Registrars; Registrars Executive Committee
> Subject: RE: [registrars] Marina del Rey Registrar Meeting - September
> 12
>
> Thank you for the clarification.  Let me resend the meeting
> announcement, clarified!  Also, I've taken off any meetings that are
not
> part of the formal agenda, again for clarification.
>
>
> ANNOUNCEMENT OF MEETING IN MARINA DEL REY - SEPTEMBER 12
>
> While we would encourage everyone to attend the next official ICANN
> meeting in Carthage, Tunisia on October 27-31, 2003, we have heard
from
> many registrars that they are unlikely to attend.
>
>
> In order to support registrar participation and foster dynamic
> discussion of issues, the Constituency has voted to hold an interim
> informal meeting on Friday, September 12th.  No decisions would be
made
> at this interim meeting, so anyone unable to make it should not feel
> disadvantaged. Moreover, we will endeavor to set up telecommunication
> links.
>
>
> Prior to the Constituency meeting - on September 11th, (a) registrars
> and registries (providers) participating in the ICANN Transfers
> Assistance Group and
> (b) the GNSO Council Whois group will try to schedule meetings on
those
> issues.  These are not constituency meetings, but the constituency
will
> be updated on those issues on the 12th.
>
>
> Additionally, some of the registries may offer to hold marketing
> presentations for registrars on the 11th.  We would encourage people
to
> arrive on the 11th, so we will plan a social function as well.
>
>
> The venue will be the Marriott in Marina del Rey.  We are securing
> special rates of $144/night and will provide contact details shortly.
> Please let us know if you are attending by emailing the ExCom (cc'd
> here).
>
>
> The meeting would be conducted in interactive workshop-style sessions
> where appropriate, with guest expert speakers invited for some of the
> topics. We will coordinate with the registry constituency, and hold a
> joint meeting for half of the day, and a separate constituency meeting
> for the other half.
>
>
> The initial proposed agenda is below. Please send us any additional
> agenda item requests by August 15th.  Anyone proposing to speak should
> provide a presentation with a summary of no longer than 1 page
>
> by September 8.
>
>
> SEPTEMBER 11
>
> * Registrar Constituency cocktails and/or dinner,  Time and Place TBD
>
>
> SEPTEMBER 12
>
> 8:30-12:30 Joint Meeting with the Registries
>
> * EPP - update on transition to EPP by all of the registries
>       Briefing by the registries - Registry Representative
>       Issues that may be faced by registrars - Registrar
Representative
>       Next Steps and Question/Debate Session
>
> * Transfers - update on implementation of new policy
>       Short Overview of implementation steps by ICANN
>       Presentation by representative of each constituency to advisory
> group
>       Next Steps and Question/Debate Session
>
> * Whois - update on work of the privacy steering group
>       Briefing on GNSO Council process - Representative of the
steering
> group
>       Briefing by ICANN on GAC role, initiatives and policies
>       Briefing on CRISP
>       Briefing on proposed interim solution to Port 43
>       Next Steps and Question/Debate Session
>
> * New TLDs - update on ICANN process for choosing new TLDs
>       Short Overview of next steps by ICANN
>       Briefing by the registries regarding ISP compatibility
>       Next Steps and Question/Debate Session
>
>
>
> 12:30-2:30 Working Lunch with Registries to address specific topics
>
> * WLS - update on service by VeriSign registry
>
> * IDN - update on service to be offered in com/net/org/info
>
>
> 2:30-5:30 Registrar Constituency Meeting
>
> * Meeting with ICANN staff - Paul Twomey, Dan Halloran, Ellen Sondheim
> (as available)
>
>
> * Fraudulent credit card charge backs - risk sharing with the
registries
>
> * Registrar Constituency budget - review and discussion
>
> * Registrar review of topics covered during joint meeting
>
>
> Regards
>
> Elana Broitman
>
>
> -----Original Message-----
> From: Michael D. Palage [mailto:michael@xxxxxxxxxx]
> Sent: Tuesday, August 12, 2003 3:02 PM
> To: ross@xxxxxxxxxx; Elana Broitman
> Cc: Registrars; Registrars Executive Committee
> Subject: RE: [registrars] Marina del Rey Registrar Meeting - September
> 12
>
>
> Ross,
>
> This is the group that ICANN is setting up to assist in the
> implementation
> of the transfer recommendations. I believe Elana may have
accidentially
> mislabeled it. It should be titled "Transfers Assistance Group".
Please
> refer to Paul's testimony before the Senate where he made reference to
> it. I
> believe I had provided you some documentation on this group while you
> were
> on vacation.
>
> Mike
>
> > -----Original Message-----
> > From: owner-registrars@xxxxxxxxxxxxxx
> > [mailto:owner-registrars@xxxxxxxxxxxxxx]On Behalf Of Ross Wm. Rader
> > Sent: Tuesday, August 12, 2003 2:07 PM
> > To: Elana Broitman
> > Cc: Registrars; Registrars Executive Committee
> > Subject: Re: [registrars] Marina del Rey Registrar Meeting -
September
> > 12
> >
> >
> > > the ICANN advisory group on
> > > transfers
> >
> > I'm assuming that this isn't the task force or an implementation
> > committee, but something else?
> > --
> >
> >
> >                         -rwr
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>