ICANN/GNSO GNSO Email List Archives

[registrars]


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

RE: [registrars] EPP transfer

  • To: "Elana Broitman" <ebroitman@xxxxxxxxxxxx>, <registrars@xxxxxxxx>
  • Subject: RE: [registrars] EPP transfer
  • From: "Elana Broitman" <ebroitman@xxxxxxxxxxxx>
  • Date: Thu, 17 Jun 2004 14:41:03 -0400
  • Sender: owner-registrars@xxxxxxxxxxxxxx
  • Thread-index: AcQ5OrDXrNXl7WwRTQSSGx0d0u0lfgC1x20ABiGOh6A=
  • Thread-topic: [registrars] EPP transfer

Dear all - the Ex.Com. had a conference call today with the registries
regarding the wish list that the constituency drafted when discussing
the EPP Transition.  Below is a brief overview of their comments.

*	com/net registries should remain thin after transition;
	--	The VeriSign Registry indicated that they have heard
this from a number of registrars. They don't oppose this recommendation,
but would request the registrars communicate it directly to ICANN as
soon as possible. This will be covered further in the plan that VeriSign
will eventually roll out. I will draft a statement for the
constituency's vetting.  
	--	Obviously if a registry operator other than VeriSign
gets the .net contract, we will need to ensure that ICANN is aware of
this wish from the registrars.

*	registries should conduct an OT&E environment prior to
initiating a transition period
	--	The registries plan to do so.  The gTLD registries
(other than com/net) have requested that ICANN allow them to postpone
finalization of their transition until 12/31/04, and registrar
transition until 3/31/05.  The OT&E environment for all of them would be
opened and operating by 12/31/05, to remain open as current and future
registrars transition into the latest EPP standard.

*	registries should sync up their business rules as much as
possible (e.g., whois fields)
	--	Registries asked for more detail regarding such rules.
They also indicated their strong desire to continue to exhibit
differences - particularly for competitive reasons.  We said that we are
not trying to eliminate reasonable business differences, but to the
extent that business rules are the same, they should sync up across the
registries.  Our task is to itemize business rules that we would
recommend syncing.  For example, standardize registry maintenance
notices, invoices, and other operational reports, based on the best
practices of one of the registries.  

*	a 3rd party should validate that the registries have synced the
rules prior to initiating a transition period
	--	The registries were opposed to this as a requirement.

*	transition processes should be the same or as similar as
possible
	--	While they would make no commitment, the registries
indicated their plan to work together to sync up and simplify the
transition process. 

*	RRP-EPP transitions should allow for legacy registrations until
transitions are completed and checked in order not to turn off
registration/renewals
	-- 	This will be covered further in the plan that VeriSign
will eventually roll out, since this only affects com/net. Obviously if
a registry operator other than VeriSign gets the .net contract, we will
need to ensure that ICANN is aware of this wish from the registrars.

*	the transition should be as long as possible, at least through
Q1 2005
	--	 The gTLD registries (other than com/net) have requested
that ICANN allow them to postpone finalization of their transition until
12/31/04, and registrar transition until 3/31/05.

*	com/net transition should allow for an additional year beyond
BONI
	--	The VeriSign Registry indicated that they have heard
this from a number of registrars. They don't oppose this recommendation,
but will not make any commitment at this time beyond including it in
their current planning, which VeriSign will eventually roll out.  

*	the registries should not require auth codes for transfers until
all transition periods are done
	--	This will be covered further in the plan that VeriSign
will eventually roll out, since this only affects com/net. Obviously if
a registry operator other than VeriSign gets the .net contract, we will
need to ensure that ICANN is aware of this wish from the registrars.

*	an implementation committee that includes registrars should be
established
	--	The registries have agreed to form an implementing
registry-registrar working group to collaborate on issues such as
syncing up business rules, EPP transitions, etc.  The registrars need to
identify a small, but representative group of registrars, to such group
- by the end of next week.  I suggest that we do this informally via
email - by starting with volunteers - rather than launching a formal
voting process.

*	there should be a standardization of maintenance notices and
other types of notices and reports
	-- 	covered above

*	registrars should be able to electronically query registries
about their balances
	--  	Registries felt that this was an issue for each registry
individually, rather than one appropriate for the constituency.

*	registries should provide a list of recommended developers for
reference by registrars that need consultants
	-- 	Registries will provide contacts - not recommendations -
as they come across such contacts.

If anyone has further comments/questions, please let us know.

Regards,

Elana Broitman
Register.com
575 Eighth Avenue
New York, NY 10018
Phone (212) 798-9215
> EFax  (800) 886-2716
Fax   (212) 629-9309
ebroitman@xxxxxxxxxxxx 




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