<<<
Chronological Index
>>> <<<
Thread Index
>>>
[gnso-irtpc] Change of Registrant: Our practices
- To: "IRTPC Working Group" <gnso-irtpc@xxxxxxxxx>
- Subject: [gnso-irtpc] Change of Registrant: Our practices
- From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
- Date: Wed, 08 Aug 2012 18:01:07 -0700
<html><body><span style="font-family:Arial; color:#000000;
font-size:10pt;"><div>Team:<br><br>As a follow up to our discussions on
Tuesday's call, here are my notes from visiting with our Domain Services
team:</div><div><br></div><div>(1) Regarding the interplay between
Registrant Name and Registrant Organization</div><div>Our team notes that when
there is data in the "Organization" field, then that entity is considered the
Registrant, while the "Name" fields are used to designate a contact within the
organization. In the event that there is a dispute or confusion between
these two, the person claiming to represent the Organization (with appropriate
documentation, identification,etc.) can over-rule the individual listed in the
"Name' fields.</div><div><br></div><div>(2) Regarding our treatment of
minor updates</div><div>While we try to make our logic as intelligent as
possible, it can be tripped by routine changes, such as changing "James" to
"Jim" or "Incorporated" to "Inc." As a fall back measure, we always
remove any locks that were triggered by changes of this
sort.<br></div><div><br></div><div>(3) Frequency of Routine Changes vs.
Material Changes</div><div>It is difficult to compare, but Routine changes are
frequent enough to mean that we simply remove any associated locks upon
request.</div><div><br></div><div>Hope this
helps.</div><div><br>Thanks--</div><div><br></div><div>J.</div><div><br></div></span></body></html>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|