[gnso-irtpc] Mp3 / IRTP C Use Case Sub team / 05 September 2012

[Nathalie Peregrine <nathalie.peregrine@xxxxxxxxx>]

Dear all,

The next IRTP C meeting is scheduled on the Tuesday 11th September 2012 @ 1400 
UTC.

Please find the MP3 recording of the Inter-Registrar Transfer Policy (IRTP) C 
working group call held on Wednesday 05 September 2012 @ 1300 UTC

http://audio.icann.org/gnso/gnso-irtp-c-20120905-en.mp3

on page:
http://gnso.icann.org/calendar#sep

The transcript will be posted on the same page.

The contents of the AC chat can be found at the bottom of this email.

Attendees:
Michele Neylon - RrSG
Avri Doria - NCSG co-Chair
Hago Dafalla - NCUC
Barbara Knight - RySG
Mike O'Connor - ISPCP
Rob Golding - RrSG
Volker Greimann- RrSG
Jonathan Tenenbaum - RrSG
Angie Graves - CBUC

Expert:
Keith Gaughan

ICANN Staff:
Berry Cobb
Nathalie Peregrine


IRTP C Members:
Alain Berranger
Simonetta Batteiger
James M. Bladel
Chris Chaplow
Phil Corwin
Paul Diaz
Roy Dykes
Avri Doria
Hago Dafalla
Kevin Erdman
Rob Golding
Volker Greimann
Oliver Hope
Zahid Jamil
Bob Mountain
Michele Neylon
Mike O'Connor
Matt Serlin
Jonathan Tenenbaum
Barbara Knight
Rob Villeneuve
Jacob Williams
Angie Graves

Archives: http://forum.icann.org/lists/gnso-irtpc/
Wiki Space: https://community.icann.org/display/gnsoirtppdpwg/Home

** Please let me know if your name has been left off the list **

Kind regards,

Nathalie Peregrine
GNSO Secretariat

Adobe Chat Room Transcript - 05 September 2012


Nathalie  Peregrine:Dial in numbers for the audio: IRELAND                      
      353-1-246-7646           1800-992-368

  Nathalie  Peregrine:password IRTP

  Nathalie  Peregrine:Angie Graves has joined the call

  Volker Greimann:1. Registration Data Directory Services. Until ICANN requires 
a different protocol, Registrar will operate a WHOIS service available via port 
43 in accordance with RFC 3912, and a web-based Directory Service providing 
free public query-based access to at least the elements set forth in Section 
3.3.1.1 through 3.3.1.8 of the Registrar Accreditation Agreement in the format 
set forth in Section 1.4 of this Specification. ICANN reserves the right to 
specify alternative formats and protocols, and upon such specification, the 
Registrar will implement such alternative specification as soon as reasonably 
practicable.

  Volker Greimann:Following the publication by the IETF of a Proposed Standard, 
Draft Standard or Internet Standard and any revisions thereto (as specified in 
RFC 2026) relating to the web-based directory service as specified in the IETF 
Web Extensible Internet Registration Data Service working group, Registrar 
shall implement the directory service specified in any such standard (or any 
revision thereto) no later than 135 days after such implementation is requested 
by ICANN. Registrar shall implement internationalized registration data 
publication guidelines according to the specification published by ICANN 
following the work of the ICANN Internationalized Registration Data Working 
Group  (IRD-WG) and its subsequent efforts, no later than 135 days after it is 
approved by the ICANN Board.

  Michele Neylon:this is from the RAA docs

  avri:current?

  avri:this is proposed so it only comes into effect after all sign?

  Volker Greimann:1.1.          The format of responses shall follow a 
semi-free text format outline below, followed by a blank line and a legal 
disclaimer specifying the rights of Registrar, and of the user querying the 
database.1.2.            Each data object shall be represented as a set of 
key/value pairs, with lines beginning with keys, followed by a colon and a 
space as delimiters, followed by the value.1.3.          For fields where more 
than one value exists, multiple key/value pairs with the same key shall be 
allowed (for example to list multiple name servers). The first key/value pair 
after a blank line should be considered the start of a new record, and should 
be considered as identifying that record, and is used to group data, such as 
hostnames and IP addresses, or a domain name and registrant information, 
together.

  Nathalie  Peregrine:Rob Golding has joined the AC room

  Nathalie  Peregrine:Jonathan Tenenbaum has joined also/

  Rob Golding (Othello/Astutium):they're very definately differnet processes - 
change of registrant is not related to chaneg of registrar

  Volker Greimann:agreed, but they are ofter performed at the same time

  Keith Gaughan:ccTLDs refer to a simultaneous change of registrar and 
registrant as a 'trade'.

  Volker Greimann:btw, what is "the safeguard"

  Volker Greimann:is it something like the verisign domain lock?

  Rob Golding (Othello/Astutium):@volker - a registrar level lock but yes 
similar

  Volker Greimann:ok, we have that, but not as a service to registrants.

  Rob Golding (Othello/Astutium):@keith - and "trades" can often only be done 
direct with the registry - e.g. .uk who charge for registrant name changes

  Keith Gaughan:Yup, I was more mentioning that the terminology is out there 
for updates of both the registrar and registrant.

  Barbara Knight-RySG:in gTLDs, however, registries do not play a role in 
'trades' as they are done at the registrar.

  Rob Golding (Othello/Astutium):@keith a trade doesnt necessarily involve a 
change of registrar though

  Keith Gaughan:True.

  Rob Golding (Othello/Astutium):IME if whois privacy is on, 99% of teh 
rergistrars who offer it auto-junk any emails from 3rd parties, so you cant 
authenticate the transfer with it on anyway.

  Keith Gaughan:Unfortunately, that causes problems with frustrated customers. 
It could be best to flag it when the transfer is initiated.

  Volker Greimann:yes, but some have forwarding mail addresses

  Keith Gaughan:But again, policy around that is inconsistent.

  Rob Golding (Othello/Astutium):I think the "whoi-protect=on" flag to show in 
whois output is dependant on the whois-protect pdp happening, but having a 
"best practice" that people can follow will help

  Keith Gaughan:Agreed.

  Barbara Knight-RySG:I have a hard stop due to another meeting.  Please let me 
know if there will be another meeting before the next IRTP meeting?

  Michele Neylon:Mikey - tightrope

  Rob Golding (Othello/Astutium):I dont think you shoudl be able to turn off 
certain restrictions

  Rob Golding (Othello/Astutium):some gtlds already impose higher level 
restrictions

  Rob Golding (Othello/Astutium):all stop transfers within 30 days of a 
previous transfer (ICANN policy)

  Rob Golding (Othello/Astutium):PIR stop transfers if the email & name have 
changed in last 60 days

  Rob Golding (Othello/Astutium):These 2-stage-auth have to be optional - that 
way the client can pick the registrar security level they're prepared to pay for

  Keith Gaughan:Agreed.

  Volker Greimann:agreed Rob

  Volker Greimann:thats how we do it.