Registrar IDs for new gTLDs
Hi there. After seeing Francisco Arias's presentation during ICANN Singapore, I had a doubt that one person also asked during the session: if the agreement only specifies 9999 as Registrar ID, can we divide the registrations depending on its billable nature between 9998 and 9999 without breaking the agreement ? Agreement text says: "02 iana-id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in http://www.iana.org/assignments/registrar-ids " Any thoughts on that ? Any ICANN clarifications on this ? Tks, Rubens NIC.br
Maybe that post from 2013 helps? At least, ICANN clarified you can use the 9997 ID for the ICANN required monitoring registrar: http://mm.icann.org/pipermail/gtld-tech/2013-November/000174.html However, it doesn't say anything about the 9998 ID... Alex
-----Ursprüngliche Nachricht----- Von: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Rubens Kuhl Gesendet: Donnerstag, 03. April 2014 20:05 An: gtld-tech@icann.org Betreff: [gtld-tech] Registrar IDs for new gTLDs
Hi there.
After seeing Francisco Arias's presentation during ICANN Singapore, I had a doubt that one person also asked during the session: if the agreement only specifies 9999 as Registrar ID, can we divide the registrations depending on its billable nature between 9998 and 9999 without breaking the agreement ? Agreement text says: "02 iana-id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in http://www.iana.org/assignments/registrar-ids "
Any thoughts on that ? Any ICANN clarifications on this ?
Tks, Rubens NIC.br
It seems the 9998 ID is newer than that, proposed by one back-end registry in order to ease up differentiating non-billable names like NIC, WWW, WHOIS from other registry-owned names. Rubens Em 03/04/2014, à(s) 16:07:000, Alexander Mayrhofer <alexander.mayrhofer@nic.at> escreveu:
Maybe that post from 2013 helps? At least, ICANN clarified you can use the 9997 ID for the ICANN required monitoring registrar:
http://mm.icann.org/pipermail/gtld-tech/2013-November/000174.html
However, it doesn't say anything about the 9998 ID...
Alex
-----Ursprüngliche Nachricht----- Von: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Rubens Kuhl Gesendet: Donnerstag, 03. April 2014 20:05 An: gtld-tech@icann.org Betreff: [gtld-tech] Registrar IDs for new gTLDs
Hi there.
After seeing Francisco Arias's presentation during ICANN Singapore, I had a doubt that one person also asked during the session: if the agreement only specifies 9999 as Registrar ID, can we divide the registrations depending on its billable nature between 9998 and 9999 without breaking the agreement ? Agreement text says: "02 iana-id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in http://www.iana.org/assignments/registrar-ids "
Any thoughts on that ? Any ICANN clarifications on this ?
Tks, Rubens NIC.br
http://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml Does that explanation helps? -- Francisco. -----Original Message----- From: Rubens Kuhl <rubensk@nic.br> Date: Friday, April 4, 2014 3:39 AM To: Alexander Mayrhofer <alexander.mayrhofer@nic.at> Cc: "gtld-tech@icann.org" <gtld-tech@icann.org> Subject: Re: [gtld-tech] Registrar IDs for new gTLDs
It seems the 9998 ID is newer than that, proposed by one back-end registry in order to ease up differentiating non-billable names like NIC, WWW, WHOIS from other registry-owned names.
Rubens
Em 03/04/2014, à(s) 16:07:000, Alexander Mayrhofer <alexander.mayrhofer@nic.at> escreveu:
Maybe that post from 2013 helps? At least, ICANN clarified you can use the 9997 ID for the ICANN required monitoring registrar:
http://mm.icann.org/pipermail/gtld-tech/2013-November/000174.html
However, it doesn't say anything about the 9998 ID...
Alex
-----Ursprüngliche Nachricht----- Von: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Rubens Kuhl Gesendet: Donnerstag, 03. April 2014 20:05 An: gtld-tech@icann.org Betreff: [gtld-tech] Registrar IDs for new gTLDs
Hi there.
After seeing Francisco Arias's presentation during ICANN Singapore, I had a doubt that one person also asked during the session: if the agreement only specifies 9999 as Registrar ID, can we divide the registrations depending on its billable nature between 9998 and 9999 without breaking the agreement ? Agreement text says: "02 iana-id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in http://www.iana.org/assignments/registrar-ids "
Any thoughts on that ? Any ICANN clarifications on this ?
Tks, Rubens NIC.br
Francisco, The updated page helps, thanks. I'm reproducing the updated excerpt below for the list readers: 9995 Reserved for Pre-Delegation Testing transactions #1 reporting Reserved 9996 Reserved for Pre-Delegation Testing transactions #2 reporting Reserved 9997 Reserved for ICANN's Registry SLA Monitoring System transactions reporting Reserved 9998 Reserved for billable transactions where Registry Operator acts as Registrar Reserved 9999 Reserved for non-billable transactions where Registry Operator acts as Registrar Reserved Rubens Em 08/04/2014, à(s) 12:33:000, Francisco Arias <francisco.arias@icann.org> escreveu:
http://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml
Does that explanation helps?
-- Francisco.
-----Original Message----- From: Rubens Kuhl <rubensk@nic.br> Date: Friday, April 4, 2014 3:39 AM To: Alexander Mayrhofer <alexander.mayrhofer@nic.at> Cc: "gtld-tech@icann.org" <gtld-tech@icann.org> Subject: Re: [gtld-tech] Registrar IDs for new gTLDs
It seems the 9998 ID is newer than that, proposed by one back-end registry in order to ease up differentiating non-billable names like NIC, WWW, WHOIS from other registry-owned names.
Rubens
Em 03/04/2014, à(s) 16:07:000, Alexander Mayrhofer <alexander.mayrhofer@nic.at> escreveu:
Maybe that post from 2013 helps? At least, ICANN clarified you can use the 9997 ID for the ICANN required monitoring registrar:
http://mm.icann.org/pipermail/gtld-tech/2013-November/000174.html
However, it doesn't say anything about the 9998 ID...
Alex
-----Ursprüngliche Nachricht----- Von: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Rubens Kuhl Gesendet: Donnerstag, 03. April 2014 20:05 An: gtld-tech@icann.org Betreff: [gtld-tech] Registrar IDs for new gTLDs
Hi there.
After seeing Francisco Arias's presentation during ICANN Singapore, I had a doubt that one person also asked during the session: if the agreement only specifies 9999 as Registrar ID, can we divide the registrations depending on its billable nature between 9998 and 9999 without breaking the agreement ? Agreement text says: "02 iana-id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in http://www.iana.org/assignments/registrar-ids "
Any thoughts on that ? Any ICANN clarifications on this ?
Tks, Rubens NIC.br
On Thu, Apr 03, 2014 at 07:07:00PM +0000, Alexander Mayrhofer wrote:
Maybe that post from 2013 helps? At least, ICANN clarified you can use the 9997 ID for the ICANN required monitoring registrar:
[…] If only there were some way to establish uses of identifiers, and put them all in a single place so that they wouldn't collide. It'd be almost like "registering" them, for global use. And maybe, if we were clever, we could come up with a way that you could put additional details with that identifier, so that it would be possible to know when the identifier was created and updated, and so on. I know, seems like a pipe dream. Best regards, A -- Andrew Sullivan Dyn, Inc. asullivan@dyn.com v: +1 603 663 0448
On Fri, Apr 4, 2014 at 4:45 AM, Andrew Sullivan <asullivan@dyn.com> wrote:
On Thu, Apr 03, 2014 at 07:07:00PM +0000, Alexander Mayrhofer wrote:
Maybe that post from 2013 helps? At least, ICANN clarified you can use the 9997 ID for the ICANN required monitoring registrar:
[...]
If only there were some way to establish uses of identifiers, and put them all in a single place so that they wouldn't collide. It'd be almost like "registering" them, for global use. And maybe, if we were clever, we could come up with a way that you could put additional details with that identifier, so that it would be possible to know when the identifier was created and updated, and so on.
I know, seems like a pipe dream.
Oooh! I know, we could publish it in the DNS. In a big XML encoded TXT RR, published under .arpa... W <run away, giggling that this is why we cannot have nice things...>
Best regards,
A
-- Andrew Sullivan Dyn, Inc. asullivan@dyn.com v: +1 603 663 0448
participants (5)
-
Alexander Mayrhofer -
Andrew Sullivan -
Francisco Arias -
Rubens Kuhl -
Warren Kumari