IANA ID for "internal" registrar
I'm wondering what IANA ID "internal" registrars (such as those owning the "nic" 2nd-level domain, or any registrars used for monitoring) should be allocated? I understand that there was some documentation that recommended using 9999 for the "registry" registrar. But since more registrars are likely needed (such as the ICANN monitoring registrar), we probably need more than one ID. Any recommendations on that? Otherwise, we'll proceed with counting "up" from 9999.. or down... or negative IDs? ;) Alex
Maybe nic.tld is used as a NNDN with state of 'blocked'... 齐超 via foxmail Sender: Alexander Mayrhofer Date: 2013年11月21日(星期四) 下午5:22 To: gtld-tech@icann.org Subject: [gtld-tech] IANA ID for "internal" registrar I'm wondering what IANA ID "internal" registrars (such as those owning the "nic" 2nd-level domain, or any registrars used for monitoring) should be allocated? I understand that there was some documentation that recommended using 9999 for the "registry" registrar. But since more registrars are likely needed (such as the ICANN monitoring registrar), we probably need more than one ID. Any recommendations on that? Otherwise, we'll proceed with counting "up" from 9999.. or down... or negative IDs? ;) Alex
Err... no? It *has* to be delegated and live.... Alex Von: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von ?? Gesendet: Donnerstag, 21. November 2013 10:58 An: gtld-tech@icann.org Betreff: Re: [gtld-tech] IANA ID for "internal" registrar Maybe nic.tld is used as a NNDN with state of 'blocked'... ________________________________ 齐超 via foxmail Sender: Alexander Mayrhofer<mailto:alexander.mayrhofer@nic.at> Date: 2013年11月21日(星期四) 下午5:22 To: gtld-tech@icann.org<mailto:gtld-tech@icann.org> Subject: [gtld-tech] IANA ID for "internal" registrar I'm wondering what IANA ID "internal" registrars (such as those owning the "nic" 2nd-level domain, or any registrars used for monitoring) should be allocated? I understand that there was some documentation that recommended using 9999 for the "registry" registrar. But since more registrars are likely needed (such as the ICANN monitoring registrar), we probably need more than one ID. Any recommendations on that? Otherwise, we'll proceed with counting "up" from 9999.. or down... or negative IDs? ;) Alex
The Registry Agreement, specification 2 says: "For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used …" There is another registrar id reserved for the ICANN SLA monitoring registrar: 9997. You will see this in your on boarding request, once you have signed a registry agreement. Regards, -- Francisco. On 11/21/13 6:22 AM, "Alexander Mayrhofer" <alexander.mayrhofer@nic.at> wrote:
I'm wondering what IANA ID "internal" registrars (such as those owning the "nic" 2nd-level domain, or any registrars used for monitoring) should be allocated? I understand that there was some documentation that recommended using 9999 for the "registry" registrar. But since more registrars are likely needed (such as the ICANN monitoring registrar), we probably need more than one ID.
Any recommendations on that? Otherwise, we'll proceed with counting "up" from 9999.. or down... or negative IDs? ;)
Alex
Thanks for the clarification. A colleague just noticed that the respective IANA registry (http://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml) contains two more registrar IDs that look like "usable IDs", namely: 3; Registry Installation 8; Test Registrar Can those be used as well? Our problem is that we also have an "internal monitoring" registrar (which is seperate from the "registry" registrar), and we obviously need a third ID for that registrar as well (besides the 9999 and 9997 ID). Is there a "private ID range" forseen in the registry? thanks, Alex
-----Ursprüngliche Nachricht----- Von: Francisco Arias [mailto:francisco.arias@icann.org] Gesendet: Donnerstag, 21. November 2013 13:00 An: Alexander Mayrhofer; gtld-tech@icann.org Betreff: Re: [gtld-tech] IANA ID for "internal" registrar
The Registry Agreement, specification 2 says: "For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used …"
There is another registrar id reserved for the ICANN SLA monitoring registrar: 9997. You will see this in your on boarding request, once you have signed a registry agreement.
Regards,
-- Francisco.
On 11/21/13 6:22 AM, "Alexander Mayrhofer" <alexander.mayrhofer@nic.at> wrote:
I'm wondering what IANA ID "internal" registrars (such as those owning the "nic" 2nd-level domain, or any registrars used for monitoring) should be allocated? I understand that there was some documentation that recommended using 9999 for the "registry" registrar. But since more registrars are likely needed (such as the ICANN monitoring registrar), we probably need more than one ID.
Any recommendations on that? Otherwise, we'll proceed with counting "up" from 9999.. or down... or negative IDs? ;)
Alex
Hello. So is the 9999 Registrar the right registrar for the 100-for-own-purpose-domains or even premium domains? Or is it just for domains which are needed for operation the registry (nic.versicherung / whois.versicherung)? Thank you! Matthias Pfeifer .versicherung
-----Ursprüngliche Nachricht----- Von: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Alexander Mayrhofer Gesendet: Donnerstag, 21. November 2013 13:05 An: Francisco Arias; gtld-tech@icann.org Betreff: Re: [gtld-tech] IANA ID for "internal" registrar
Thanks for the clarification. A colleague just noticed that the respective IANA registry (http://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml) contains two more registrar IDs that look like "usable IDs", namely:
3; Registry Installation 8; Test Registrar
Can those be used as well? Our problem is that we also have an "internal monitoring" registrar (which is seperate from the "registry" registrar), and we obviously need a third ID for that registrar as well (besides the 9999 and 9997 ID). Is there a "private ID range" forseen in the registry?
thanks,
Alex
-----Ursprüngliche Nachricht----- Von: Francisco Arias [mailto:francisco.arias@icann.org] Gesendet: Donnerstag, 21. November 2013 13:00 An: Alexander Mayrhofer; gtld-tech@icann.org Betreff: Re: [gtld-tech] IANA ID for "internal" registrar
The Registry Agreement, specification 2 says: "For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used …"
There is another registrar id reserved for the ICANN SLA monitoring registrar: 9997. You will see this in your on boarding request, once you have signed a registry agreement.
Regards,
-- Francisco.
On 11/21/13 6:22 AM, "Alexander Mayrhofer" <alexander.mayrhofer@nic.at> wrote:
I'm wondering what IANA ID "internal" registrars (such as those owning the "nic" 2nd-level domain, or any registrars used for monitoring) should be allocated? I understand that there was some documentation that recommended using 9999 for the "registry" registrar. But since more registrars are likely needed (such as the ICANN monitoring registrar), we probably need more than one ID.
Any recommendations on that? Otherwise, we'll proceed with counting "up" from 9999.. or down... or negative IDs? ;)
Alex
participants (4)
-
Alexander Mayrhofer -
Francisco Arias -
Matthias Pfeifer -
齐超