Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.
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).
zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.
Electronic Files a. It is the Buyer's responsibility to maintain a copy of any original Electronic File provided by the Buyer. b. The Seller shall not be responsible for checking the accuracy of supplied input from an electronic file unless otherwise agreed in writing. c. Without prejudice to clause 5.2(b), if an electronic file is not suitable for outputting on equipment normally adequate for such purposes without adjustment or other corrective action the Seller may make a charge for any resulting additional cost incurred or may reject the file without prejudice to his rights to payment for work done/material purchased.
How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.
Electronic Format If requested by the Purchaser, the Servicer shall supply any and all information regarding the Mortgage Loans and the REO Properties, including all reports required to be delivered pursuant to Section 5.03, Section 6.02 and this Section 8.01, to the Purchaser in electronic format reasonably acceptable to Purchaser, unless otherwise limited by the servicing system utilized by the Servicer.
Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to Comcast Phone via an agreed medium with CONNECT:Direct being the preferred transport method. The ODUF feed will be a variable block format (2476) with an LRECL of 2472. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. 6.2.2 Data circuits (private line or dial-up) will be required between BellSouth and Comcast Phone for the purpose of data transmission. Where a dedicated line is required, Comcast Phone will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Comcast Phone will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Comcast Phone. Additionally, all message toll charges associated with the use of the dial circuit by Comcast Phone will be the responsibility of Comcast Phone. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on Comcast Phone end for the purpose of data transmission will be the responsibility of Comcast Phone.
Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, MyLineToo must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
