<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [gnso-irtpc] Chat transcript IRTP Part C F2F meeting
- To: "Paul Diaz" <pdiaz@xxxxxxx>, "IRTPC Working Group" <gnso-irtpc@xxxxxxxxx>
- Subject: RE: [gnso-irtpc] Chat transcript IRTP Part C F2F meeting
- From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
- Date: Thu, 15 Mar 2012 12:32:11 -0700
<html><body><span style="font-family:Arial; color:#000000;
font-size:10pt;"><div>Paul:<br><br>Thank you for clarifying. Rob, does this
address your question / concern?<br><br>J.</div><div><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid
blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black;
font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [gnso-irtpc] Chat transcript IRTP Part C F2F meeting<br>
From: Paul Diaz <<a href="mailto:pdiaz@xxxxxxx">pdiaz@xxxxxxx</a>><br>
Date: Thu, March 15, 2012 2:11 pm<br>
To: IRTPC Working Group <<a
href="mailto:gnso-irtpc@xxxxxxxxx">gnso-irtpc@xxxxxxxxx</a>><br>
Cc: Marika Konings <<a
href="mailto:marika.konings@xxxxxxxxx">marika.konings@xxxxxxxxx</a>><br>
<br>
<br>
In response to the following from Wednesday's IRTP-C WG meeting:<br>
<br>
Rob Golding (othello): to clarify my point/question - it _appears_ that
registries are applying their own rules/practices to the "change of registrant"
processes, but locking the domains for "a period" from inter-registrar-transfer
after certain updates - PIR/ORG appear to lock the domain for 60 days after
changes to contacts for example, we need clarification from the registries what
they do (if anything) and (a) publish that so everyone knows and (b) potetially
have it changed inline with the final report/recommendations<br>
<br>
Rob Golding (othello):such actions increase our support load in terms of
clients wanting to transfer in/out, especially in line with WDRP emails, they
login, update, and then find they cant move the domain if they want to<br>
<br>
PIR wants to clarify that we do not/not automatically lock a domain name for
60-days following a change in the registrant's contact information. While it's
possible for the Registrar of Record to submit an EPP command to lock the
domain in such a situation, the .ORG Registry Operator does not do this as a
matter of procedure. PIR does prevent names that were transferred under the
IRTP from bouncing to another registrar within 60 days. This is a pro-consumer
policy, of course, and can be overridden (in conjunction with Registrar
cooperation) once the Registrant demonstrates their registration rights and
desire to move the domain name to another registrar.<br>
<br>
Regards,<br>
<br>
Paul Diaz<br>
Public Interest Registry<br>
<br>
<br>
From: Marika Konings <<a
href="mailto:marika.konings@xxxxxxxxx">marika.konings@xxxxxxxxx</a>><<a
href="mailto:marika.konings@xxxxxxxxx">mailto:marika.konings@xxxxxxxxx</a>>><br>
Date: Thu, 15 Mar 2012 08:29:32 -0700<br>
To: "<a href="mailto:gnso-irtpc@xxxxxxxxx">gnso-irtpc@xxxxxxxxx</a><<a
href="mailto:gnso-irtpc@xxxxxxxxx">mailto:gnso-irtpc@xxxxxxxxx</a>>" <<a
href="mailto:gnso-irtpc@xxxxxxxxx">gnso-irtpc@xxxxxxxxx</a>><<a
href="mailto:gnso-irtpc@xxxxxxxxx">mailto:gnso-irtpc@xxxxxxxxx</a>>><br>
Subject: [gnso-irtpc] Chat transcript IRTP Part C F2F meeting<br>
<br>
For your information, please find below the chat transcript of yesterday's IRTP
Part C F2F meeting.<br>
<br>
With best regards,<br>
<br>
Marika<br>
<br>
On 14/03/12 10:01, "Marika Konings" <<a
href="mailto:marika.konings@xxxxxxxxx">marika.konings@xxxxxxxxx</a>><<a
href="mailto:marika.konings@xxxxxxxxx">mailto:marika.konings@xxxxxxxxx</a>>>
wrote:<br>
<br>
Marika Konings:Good morning everyone. The IRTP Part C Working Group meeting
will get started shortly.<br>
Rob Golding (othello):morning Marika - are you enjoying 'Rica ?<br>
Marika Konings:Yes, very much so<br>
Rob Golding (othello):I'd be sad to have stayed in london - if only it wasn't
gloriously sunny and ~20degrees here today :)<br>
Marika Konings:Wow, that sounds nice!<br>
Rob Golding (othello):not dialed in yet<br>
Rob Golding (othello):calling in a sec<br>
Rob Golding (othello):(load room at the mo here)<br>
Rob Golding (othello):loud even<br>
Michele Neylon:morning<br>
Michele Neylon:Ah Ms Salter<br>
Kelly Salter:Morning Mr Neylon<br>
Erick Irairte:Good Morning :)<br>
Michele Neylon:Kelly - so you going to start playing with us now? :)<br>
Kelly Salter:I thought i'd should listen in... prepare myself for Prague
:)<br>
Michele Neylon::)<br>
Rob Golding (othello):dont start playing with Michele - he's like a rubiks
cube, once you tsrta you'll never put him down ;)<br>
Rob Golding (othello):start - damn wireless keyboard<br>
Michele Neylon:Rob - lol<br>
Sam:I agree with Rob<br>
Sam:ICANN should be trying to standardise the transfer criteria<br>
Sam:accredited registrars should be following the same transfer rules<br>
Rob Golding (othello):@sam - standards are good :)<br>
Sam:Certainly makes integration between different registrars easier. With the
new TLDs coming it seems like the perfect time to rethink this process and
ensuring that everybody is clear in terms of locking, auth codes and other
transfer prohibitations<br>
Rob Golding (othello):to clarify my point/question - it _appears_ that
registries are applying their own rules/practices to the "change of registrant"
processes, but locking the domains for "a period" from inter-registrar-transfer
after certain updates - PIR/ORG appear to lock the domain for 60 days after
changes to contacts for example, we need clarification from the registries what
they do (if anything) and (a) publish that so everyone knows and (b) potetially
have it changed inline with the final report/recommendations<br>
Rob Golding (othello):such actions increase our support load in terms of
clients wanting to transfer in/out, especially in line with WDRP emails, they
login, update, and then find they cant move the domain if they want to<br>
Rob Golding (othello):current registered name holder, replacemnet registered
name holder<br>
Michele Neylon:ooh I like that<br>
Rob Golding (othello):itra-reg "transfers" - where possible / available -
it's easy to move from one enom reseller to another, it's ngh-on-impossible to
move from one logicbox s/ware user to another without a inter-reg transfer, as
teh software doenst allow it (in most circumstances), and with others, even
moving to an alternative "account" to change payment details is treated as a
transfer<br>
Rob Golding (othello):It's certainly a "benefit" to usrs of certain systems,
but not available at all of them<br>
Rob Golding (othello):dropping off the call, sticking around on adobe,
turning speakers back up :)<br>
Marika Konings:Any remote questions / comments are of course also welcome!<br>
Rob Golding (othello):@mikey - the £1+vat fee only applies where you are
updating the owenrship (change of control). there is also a £10+vat charge if
you get *nominet* to transfer the domain between registrar (but registrars can
do that immediately and without charge to them or the registrant) - call a TAG
Release - which _optionally_ the receiving registrar can hold for manual
accept/reject (handshaking) or always reject or always accept<br>
Rob Golding (othello):@mikey - *only* Nominet can do the change of control
(ownership) as they dont allow registrars to update the regsitrant name fields
on the domain - part of the nominet-registrant legal agreemnet entered on
registering a .uk<br>
Rob Golding (othello):@Mikey - 5 day IRTP prescribe limit is 5 days from
acknowledgement by the registry, afetr acknowledgement by the losing registrar,
each of which can add a few days - my experience is 2 days min (as say verisign
only send out the notices to the gaining registrar @ 5am everyday) and 9 days
(longest) with an average of 5-6 days<br>
Barbara Knight - RySG:James, Will there be call in details for the meeting
with the ccNSO?<br>
Michele Neylon:I think they have remote stuff<br>
Michele Neylon:so you can foloow it<br>
Michele Neylon:but let's see what Marika says<br>
Mikey O'Connor -- ISP type guy:<a
href="http://costarica43.icann.org/node/29629">http://costarica43.icann.org/node/29629</a><br>
Michele Neylon:<a
href="http://icann.adobeconnect.com/sjo43-bouganvillea">http://icann.adobeconnect.com/sjo43-bouganvillea</a><br>
Barbara Knight - RySG:thanks gentlemen :-)<br>
Marika Konings:Yes, there should be audiocast, but there is no phone
bridge<br>
Michele Neylon:ah ha<br>
Marika Konings:there is also an Adobe Connect room, so feel free to post any
comments / questions there and I'll try to raise those during the meeting, if
possible.<br>
Barbara Knight - RySG:thanks Marika<br>
Marika Konings:thanks all!<br>
<br>
<br>
<br>
</div>
</blockquote></span></body></html>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|