[gnso-lockpdp-wg] RE: For immediate review - updated definition of locking

["Schneller, Matt" <Matt.Schneller@xxxxxxxxx>]

Sorry to miss the call this morning without prior notice.

I don't know that I care a lot about the definition either way, but I thought 
we had adopted the former definition to maintain the broadest possible range of 
registrar discretion.  Under the former definition, it's up to the registrar 
(and the registrar's contract terms with their clients) to determine whether or 
not they do anything (or even can do anything) that would impair the domain 
name's resolving.  Since our initial registrar survey indicated that some 
registrars do disable the domain from resolving to a live website, the latter 
definition might override pre-existing registrar contract terms or practice.  
So long as the minimum baseline of lock (no changes of registrar or registrant) 
are met, I don't know that it's of concern to anyone other than the registrar 
and registrant what else that registrar does or doesn't do.

Matt

From: owner-gnso-lockpdp-wg@xxxxxxxxx [mailto:owner-gnso-lockpdp-wg@xxxxxxxxx] 
On Behalf Of Marika Konings
Sent: Thursday, March 14, 2013 7:30 AM
To: Gnso-lockpdp-wg@xxxxxxxxx
Subject: [gnso-lockpdp-wg] For immediate review - updated definition of locking

Dear All,

We had a relatively short call today as only few people were able to join the 
meeting. There was one item of substance that was discussed and we would like 
to receive your feedback on by COB today (Thursday 14 March). As suggested on 
the mailing list, those on the call agreed to modify the current definition of 
'locking' from:

"the term "lock" means preventing any changes of registrar and registrant"

To

"the term "lock" means preventing any changes of registrar and registrant, 
without impairing the resolution of the domain name"

If there are any objections to this change, please make those known to the 
mailing list at the latest by close of business (wherever you are) today.

With best regards,

Marika