Re: [gnso-irtpc] questions for the IANA-number question
Hi Simonetta, I think we did (see presentation attached), but as this was at the start of the WG, most might have forgotten about it ;-) However, the section on IANA IDs is relatively short, so I've pasted it below as a reminder. With best regards, Marika >From the IRTP Part C Final Issue Report IANA IDs for registrars c) Whether the process could be streamlined by a requirement that registries use IANA IDs for registrars rather than proprietary IDs. * When a registrar accredits with ICANN, an ID is assigned by ICANN to identify that particular registrar. See http://www.iana.org/assignments/registrar-ids/registrar-ids.xml for the most recent list. However, when a registrar accredits with a particular registry, that registry may also assign a proprietary ID to the registrar, which differs from the IANA ID. * This issue of IANA vs. proprietary ID was raised as part of the Transfer WG discussions in 2005 where it was noted that ‘it would be an improvement for everyone to get rid of the proprietary registrar ids that differ from registry to registry’. The suggestion was to propose that ‘registries shall implement IANA ids in transfers instead’. (see http://forum.icann.org/lists/transfers-wg/msg00003.html) * ICANN has insisted on the consistent use of the IANA ID for all registrars and it has streamlined andimproved communication and other aspects significantly as a result. There have been many problems over the years when registrars change their names or when registries record the names slightly differently in their records. From ICANN’s perspective, using a common, unchanging number assigned by ICANN (through IANA) would prevent such issues. * Further information on the scope or nature that the use of proprietary vs. IANA IDs poses was encouraged as part of the public comment period on the preliminary Issue Report. The gTLD Registries Stakeholder Group (RySG) pointed out that ‘registrar name changes often do make it difficult to ensure that the correct registrar is identified and use of the IANA ID may be helpful in confirming registrar identification’. The RySG also noted that ‘all registries that provide Monthly Registry Operator Reports to ICANN are required to provide both the registrar name and the IANA ID to identify registrar information in the Per Registrar Activity Report file so it is reasonable to think that all registries do maintain this information in their registration systems’. From: "Sedo :: Simonetta Batteiger" <simonetta@xxxxxxxx<mailto:simonetta@xxxxxxxx>> To: Mike O'Connor <mike@xxxxxxxxxx<mailto:mike@xxxxxxxxxx>>, IRTPC Working Group <gnso-irtpc@xxxxxxxxx<mailto:gnso-irtpc@xxxxxxxxx>> Subject: RE: [gnso-irtpc] questions for the IANA-number question Marika/James: I don’t recall us actually reviewing that Issue Report on the IANA item, did we? That might be a good item to put back on the agenda for one of the coming calls… Simonetta From: owner-gnso-irtpc@xxxxxxxxx<mailto:owner-gnso-irtpc@xxxxxxxxx> [mailto:owner-gnso-irtpc@xxxxxxxxx] On Behalf Of Mike O'Connor Sent: Tuesday, April 24, 2012 4:51 PM To: IRTPC Working Group Subject: [gnso-irtpc] questions for the IANA-number question here's that list questions we asked long ago Understand why we're looking at this question -- what problems are we trying to solve * + - Review Issue Report o Some issues were raised a long time ago -- are these questions still valid, given other measures that have been taken in the intervening time * Identify justification, benefits and costs and how we demonstrate them * + - Identify impacts/harms to registrars in addition to registries * Are there material effects that result? * Do those expand to registrants * "Why are we doing this?" * Identify streamlining/scaleability facets of the process * Explore security questions/issues * Look for reasons why not to do this -- include in the instructions for stakeholder feedback * Why aren't they being used, level of effort required to change. - - - - - - - - - phone 651-647-6109 fax 866-280-2356 web http://www.haven2.com handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.) Attachment:
IRTP Part C Issue Report - 8 November 2011.ppt
|