Per-­‐Registrar Transactions Report Sample Clauses

Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-­‐TLD, the A-­‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 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 xxxx://xxx.xxxx.xxx/assignments/registrar-­‐ids 03 total-­‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-­‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-­‐adds-­‐1-­‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
AutoNDA by SimpleDocs
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-name Registrar’s full corporate name as registered with IANA 03 total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-adds-1-yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-­‐TLD, the A-­‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 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 xxxx://xxx.xxxx.xxx/assignments/registrar-­‐ids 03 total domains total domains under sponsorship 04 total-­‐nameservers total name servers registered for TLD 05 net-­‐adds-­‐1-­‐yr number of domains successfully registered with an initial term of one year (and not deleted within the add grace period) Field # Field name Description 06 net-­‐adds-­‐2-­‐yr number of domains successfully registered with an initial term of two years (and not deleted within the add grace period) 07 net-­‐adds-­‐3-­‐yr number of domains successfully registered with an initial term of three years (and not deleted within the add grace period) 08 net-­‐adds-­‐4-­‐yr number of domains successfully registered with an initial term of four years (and not deleted within the add grace period) 09 net-­‐adds-­‐5-­‐yr number of domains successfully registered with an initial term of five years (and not deleted within the add grace period) 10 net-­‐adds-­‐6-­‐yr number of domains successfully registered with an initial term of six years (and not deleted within the add grace period) 11 net-­‐adds-­‐7-­‐yr number of domains successfully registered with an initial term of seven years (and not deleted within the add grace period) 12 net-­‐adds-­‐8-­‐yr number of domains successfully registered with an initial term of eight years (and not deleted within the add grace period) 13 net-­‐adds-­‐9-­‐yr number of domains successfully registered with an initial term of nine years (and not deleted within the add grace period) 14 net-­‐adds-­‐10-­‐yr number of domains successfully registered with an initial term of ten years (and not deleted within the add grace period) 15 net-­‐renews-­‐1-­‐yr number of domains successfully renewed either automatically or by command with a new renewal period of one year (and not deleted within the renew gr...
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated- value formatted file as specified in RFC 4180. The file shall be named “net-transactions- yyyymm.csv.” The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-name Registrar’s full corporate name as registered with IANA 03 total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-adds-1-yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD- transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: (including area/country code)
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-­‐TLD, the A-­‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated- value formatted file as specified in RFC 4180. The file shall be named “net-transactions- yyyymm.csv.” The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-name Registrar’s full corporate name as registered with IANA 03 total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged
AutoNDA by SimpleDocs
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-­‐TLD, the A-­‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 03 total-­‐domains total domainsdomain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-­‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged
Per-­‐Registrar Transactions Report. This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. The last line of each report shall include totals for each column across all registrars; the first field of this line shall read “Totals” while the second field shall be left empty in that line. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in XXX 0000.

Related to Per-­‐Registrar Transactions Report

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Registrar Data 1.6.1 Query format: whois “registrar Example Registrar, Inc.”

Time is Money Join Law Insider Premium to draft better contracts faster.