The Registrar Element Clause Samples

The Registrar Element. The registrar element has the property "id" and is a container consisting of the following elements: a. password: The password for the registrar. b. name: The name of the registrar. c. status: The registrar status code. d. contact-id: Any number of contact-id associated with this registrar. Contact-id has the property "type" to denote the type of contact. "Type" can be one of: Registrar, Administrative, Technical or Billing An example registrar container appears below: <registrar id="REG-042"> <password>registrarrus</password> <name>Registrar R Us</name> <status>ACTIVE</status> <contact-id type="Registrar">PER-0009</contact-id> <contact-id type="Administrative">PER-0010</contact-id> <contact-id type="Administrative">PER-0011</contact-id> <contact-id type="Technical">PER-0012</contact-id> <contact-id type="Technical">PER-0013</contact-id> <contact-id type="Billing">PER-0014</contact-id> </registrar>
The Registrar Element. The registrar element has the property "id" and is a container consisting of the following elements: a. name: The name of the registrar. b. status: The registrar status code. c. iana-id: The IANA designated number for the Registrar. d. street1: The first part of the street address of the Registrar. e. street2: The second part of the street address of the Registrar. f. street3: The third part of the street address of the Registrar. g. city: The name of the city of the Registrar. h. state-province: The name of the state/province of the Registrar. i. postal-code: The postal/zip code of the Registrar. j. geographic location: The two letter ISO 3166 code for the Registrar 's geographic location. k. voice: The voice phone number of the Registrar in E164a format. l. fax: The fax number of the Registrar in E164a format. m. email: The e-mail address of the Registrar. n. url: The URL of the Registrar. o. created-on: The date/time the Registrar object was originally created. p. updated-on: The date/time the Registrar object was last updated. q. contact-id: Any number of contact-id associated with this registrar. Contact-id has the property "type" to denote the type of contact. "Type" can be one of: Administrative, Technical or Billing. An example registrar container appears below: <registrar id=" 42"> <name>Registrar R Us</name> <iana-id>545</iana-id> <status>ACTIVE</status> <street1>▇▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇▇▇▇</street1> <street2></street2> <street3></street3> <city>New York</city> <state-province>NY</state-province> <postal-code>12345</postal-code> <country>US</country> <voice>+212.1234567</voice> <fax>+212.1234568</fax> <email>▇▇▇▇@▇▇▇▇▇▇▇.▇▇▇▇</email> <url>▇▇▇.▇▇▇▇▇▇▇▇▇-▇▇▇▇▇▇▇.▇▇▇</url> <created-on>2001-06-01 03:01:21</created-on> <updated-on>2001-06-01 03:01:21</updated-on> <contact-id type="Administrative"> 10</contact-id> <contact-id type="Administrative"> 11</contact-id> <contact-id type="Technical"> 12</contact-id> <contact-id type="Technical"> 13</contact-id> <contact-id type="Billing"> 14</contact-id> </registrar>
The Registrar Element. The registrar element has the property "id" and is a container consisting of the following elements:
The Registrar Element. The registrar element has the property "id" and is a container consisting of the following elements: a. name: The name of the registrar. b. status: The registrar status code. c. contact-id: Any number of contact-id associated with this registrar. Contact-id has the property "type" to denote the type of contact. "Type" can be one of: Registrar, Administrative, Technical or Billing An example registrar container appears below: <registrar id="REG-042"> <password>registrarrus</password> <name>Registrar R Us</name> <status>ACTIVE</status> <contact-id type="Registrar">PER-0009</contact-id> <contact-id type="Administrative">PER-0010</contact-id> <contact-id type="Administrative">PER-0011</contact-id> <contact-id type="Technical">PER-0012</contact-id> <contact-id type="Technical">PER-0013</contact-id> <contact-id type="Billing">PER-0014</contact-id> </registrar> 1. The Reports making up the Deposit will first be created according to the format specification. (See Exhibit 2 above, "Escrow Deposit Format Specification"). 2. The Reports making up the Deposit will be concatenated. The resulting file shall be named according to the following format: "bizSEQN", where "SEQN" is a four digit decimal number that is incremented as each report is prepared. 3. Next, the Deposit file will be processed by a program (provided by ICANN) that will verify that it complies with the format specification and contains reports of the same date/time (for a Full Deposit), count the number of objects of the various types in the Deposit, and append to the file a report of the program's results. 4. Registry Operator may optionally split the resulting file using the Unix SPLIT command (or equivalent) to produce files no less than 1 GB each (except the final file). If Deposit files are split, a .MDS file (produced with MDSSUM or equivalent) must be included with the split files to isolate errors in case of transfer fault. 5. The Deposit file(s) will then be encrypted using Escrow Agent's public key for PGP and signed using Registry Operator's private key for PGP, both version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the Deposit file(s) in addition to encrypting it (them).) The formatted, encrypted and signed Deposit file(s) will be sent, by anonymous file transfer, to Escrow Agent's ftp server within the specified time window.
The Registrar Element. The registrar element has the property "id" and is a container consisting of the following elements: a. password: The password for the registrar. b. name: The name of the registrar.