Overview

The ARIN Operational Test and Evaluation (OT&E) Environment is a dedicated platform that mirrors ARIN's production environment, allowing users to test and evaluate interactions with ARIN's services without affecting live data. This environment is refreshed monthly, ensuring that users have access to up-to-date data for their testing needs. Key components available in the OT&E Environment include:

• Whois RESTful Web Service (Whois-RWS): Provides access to ARIN's Whois data, allowing users to query and retrieve registration information.
• Registration RESTful Web Service (Reg-RWS): Enables users to manage their ARIN records programmatically.
• Internet Routing Registry (IRR) RESTful API: Facilitates the creation and management of routing policy objects.
• Resource Public Key Infrastructure (RPKI): Allows users to test RPKI functionalities in a non-production setting. By providing a safe and isolated environment, the OT&E platform ensures that users can develop, test, and troubleshoot their interactions with ARIN's services before implementing changes in the production environment.

Features and Capabilities

• Monthly Data Refresh: Ensures that the OT&E Environment has up-to-date data, reflecting the current state of ARIN's production environment.
• Comprehensive Service Access: Provides access to a wide range of ARIN services, including Whois-RWS, Reg-RWS, IRR API, and RPKI.
• Safe Testing Ground: Allows users to test changes and configurations without the risk of impacting live data or services.
• Simulated Production Environment: Mimics the production environment closely, providing realistic testing scenarios.
• No Impact on Production: Changes made in the OT&E Environment do not affect ARIN's live systems or data.
• Access to ARIN Online: Users can interact with ARIN Online services in a test setting, allowing for comprehensive testing of workflows.
• RPKI Testing: Provides a platform to test RPKI functionalities, including certificate management and route origin authorizations.
• IRR Object Management: Enables the creation and management of Internet Routing Registry objects, facilitating routing policy testing.
• Reg-RWS Interaction: Allows users to interact with ARIN's Registration RESTful Web Service, testing record management capabilities.
• No Monitoring of Requests: The OT&E Environment is not actively monitored by ARIN staff, allowing for unrestricted testing.
• Support for RPKI Enrollment: Users can enroll in RPKI within the OT&E Environment, testing the process before production implementation.
• Access to Whois-RWS: Provides access to ARIN's Whois data, allowing for testing of data retrieval and query functionalities.
• Simulated Whois Data: The Whois data in the OT&E Environment is a snapshot of production data, providing realistic testing scenarios.
• No Ticketed Support: The OT&E Environment does not support ticketed requests, encouraging users to test independently.
• No Impact on Live Data: All actions performed in the OT&E Environment are isolated and do not affect live data or services.
• Access to ARIN's APIs: Users can interact with ARIN's APIs in a test setting, allowing for comprehensive testing of integrations.
• Safe Experimentation: Provides a safe platform for users to experiment with ARIN's services and configurations.
• No Risk to Production Systems: Changes made in the OT&E Environment do not impact ARIN's live systems or data.
• Access to ARIN's Documentation: Users can refer to ARIN's documentation while testing in the OT&E Environment, ensuring informed testing.
• No Service Level Agreements: The OT&E Environment does not have service level agreements, as it is intended for testing purposes only.
• No Production Data: The data in the OT&E Environment is a snapshot of production data, ensuring realistic testing scenarios.
• No Production Impact: All actions performed in the OT&E Environment are isolated and do not affect live data or services.
• Access to ARIN's Community Tools: Users can interact with ARIN's community tools in a test setting, allowing for comprehensive testing of integrations.
• No Community Support: The OT&E Environment does not provide community support, encouraging users to test independently.
• No Production Support: The OT&E Environment does not provide production support, as it is intended for testing purposes only.
• No Production Data Access: The OT&E Environment does not provide access to production data, ensuring data privacy and security.
• No Production System Access: The OT&E Environment does not provide access to production systems, ensuring system integrity.
• No Production Data Exposure: The OT&E Environment does not expose production data, ensuring data privacy and security.