ICANN ICANN Email List Archives

[gnso-irtpc]


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

[gnso-irtpc] a plea for people to join the "use case" call tomorrow

  • To: IRTPC Working Group <gnso-irtpc@xxxxxxxxx>
  • Subject: [gnso-irtpc] a plea for people to join the "use case" call tomorrow
  • From: "Mike O'Connor" <mike@xxxxxxxxxx>
  • Date: Tue, 4 Sep 2012 10:22:41 -0500

hi all,

as i mentioned right at the end of the call today, we could really use some 
FOA/Auth-Code/registrant-information-transfer expertise on the "use case" call 
tomorrow.

note to Mountain -- i've asked Berry to set up "real" bridge and Adobe-room 
capability for the call, so stand by for a note from him with the particulars, 
rather than using your bridge

the call is scheduled at: 

Wednesday, 05 September 2012 at 1300 UTC.
06:00 PST, 9:00 EST, 10:00 Buenos Aires/Rio de Janeiro, 14:00 London, 15:00 
CET, 16:00 Khartoum (EAT), 18:00 Karachi (PKT)

as i said on the call, the use-cases are relatively simple to describe in a 
thick-WHOIS environment because access to Registrant information is 
straightforward.  but the thin WHOIS process is quite different and we need to 
figure out a way (if there is one) to make the use-cases work for that 
environment as well.  Michele mentioned that there's RAA discussion about 
consistent publication of that data, which might be the ticket.  there's also a 
Thick WHOIS working group that's in the drafting stage but that outcome is down 
the road a bit.

options:

- defer until the RAA and Thick WHOIS WG's work is complete

- collapse change of Registrar and change of Registrant back into a single 
process with an IRT-lock (which can be toggled off/on with high security)

- use some other mechanism to exchange Registrant information

thanks,

mikey

- - - - - - - - -
phone   651-647-6109  
fax             866-280-2356  
web     http://www.haven2.com
handle  OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)



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

Privacy Policy | Terms of Service | Cookies Policy