Standards Compliance. DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
Standards Compliance. Flexera has and will maintain SOC2 certification throughout the subscription term of the Order and will and make reports on the same available to the Customer upon request.
Standards Compliance. 2.1 Stds. Comp. All work and materials covered by this Solicitation and resulting Master Contract(s) shall be performed in compliance with Chapter 19.28.410 Revised Code of Washington, Chapter 296-46B-010 Washington Administrative Code, and the most current versions of the following mandatory standards: • NFPA-70 National Electrical Code • ANSI\TIA\EIA 568 series, Commercial Building Telecommunications Cabling Standard • ANSI\TIA\EIA 569-E , Commercial Building Standard for Telecommunications Pathways and Spaces, o Ex. Pathways, Work area outlets, Patch panels, Racks and cabinets, Ports, Grounding, busbars, Cabling, Firestop locations, Telecommunications space, Data center room grid • ANSI\TIA\EIA 606-C Commercial Building Telecommunication standard for Labeling • ANSI-J-STD-607-C, Commercial Building Grounding (Earthing) and Bonding Requirements for Telecommunications • ANSI\EIA\TIA 862-B Structured Cabling infrastructure Standard for Intelligent building Systems (Building Automation standard) • ANSI\EIA\TIA 942-B Telecommunications standard for Data centers • OSHA/WISHA Construction and safety standards Any additional codes/standards required under a Purchaser’s Purchase Order/SOW or by state or federal regulation. Bidder will be held responsible for compliance with the most recent versions of the specified codes/standards/regulations and any revisions or updates. Should conflicts arise with the foregoing, the Department of Enterprise Services will have responsibility for making final interpretation. MANDATORY Fully Meets 3.0 Cert. CERTIFICATION: 3.1 Cert. COMPANY CERTIFICATIONS. Bidder must maintain certification from the Manufacturer(s) that provides structured cabling system twenty-five (25) year or more warranties as identified in Bidder’s response to this RFQQ. Written Response Required. List the Manufacturer(s) Certifications you maintain that meet this requirement. MANDATORY SCORED Fully Meets Xxxxxxx: Ortronics/Superior Essex 3.2 Cert. COMPANY CERTIFICATIONS. The Bidder response must provide documentation that the company is certified by at least one (1) manufacturer that provides structured cabling-system 20-year-or-more warranties in Washington state. For example: • Commscope (Systimax) Ortronics, Inc. (Certified Installer-Plus Program); • AMP (Netconnect Design and Installation Program); • Leviton (Certified Cabling System); • Xxxxxx (IBDN). These manufacturers are examples only – the list is not all-inclusive. Written Response Required. Bidde...
Standards Compliance. All work and materials covered by this Master Contract shall be performed in compliance with Chapter
Standards Compliance. Registry Operator shall implement and comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to (i) the DNS and name server operations including without limitation RFCs 1034, 1035, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 3901, 4343, 4472, and 5966; and (ii) provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 3735, 5910, 5730, 5731, 5732, 5733 and 5734. If Registry Operator implements Registry Grace Period (RGP), it will comply with RFC 3915 and its successors. If Registry Operator requires the use of functionality outside the base EPP RFCs, Registry Operator must document EPP extensions in Internet- Draft format following the guidelines described in RFC 3735. Registry Operator will provide and update the relevant documentation of all the EPP Objects and Extensions supported to ICANN prior to deployment. Registry Operator shall sign its TLD zone files implementing Domain Name System Security Extensions (“DNSSEC”). During the Term, Registry Operator shall comply with RFCs 4033, 4034, 4035, 4509 and their successors, and follow the best practices described in RFC 4641 and its successors. If Registry Operator implements Hashed Authenticated Denial of Existence for DNS Security Extensions, it shall comply with RFC 5155 and its successors. Registry Operator shall accept public-key material from child domain names in a secure manner according to industry best practices. Registry shall also publish in its website the DNSSEC Practice Statements (DPS) describing critical security controls and procedures for key material storage, access and usage for its own keys and secure acceptance of registrants’ public-key material. If the Registry Operator offers Internationalized Domain Names (“IDNs”), it shall comply with RFCs 5890, 5891, 5892, 5893 and their successors. Registry Operator shall comply with the ICANN IDN Guidelines at <xxxx://xxx.xxxxx.xxx/en/topics/idn/implementation-guidelines.htm>, as they may be amended, modified, or superseded from time to time. Registry Operator shall publish and keep updated its IDN Tables and IDN Registration Rules in the IANA Repository of IDN Practices as specified in the ICANN IDN Guidelines. Registry Operator shall be able to accept IPv6 addresses as glue records in its Registry System and publish them in the DNS. Registry Opera...
Standards Compliance. Genesys complies with applicable legal, financial, data privacy, and regulatory requirements, and conforms with the following compliance certifications and external audit reports: • International Organization for Standardization – ISO/IEC 27001:2013 Information Security Management System (ISMS) Certification • American Institute of Certified Public Accountants (AICPA) Service Organization Control (SOC) 2 Type II attestation report incl. BSI Cloud Computing Catalogue (C5) • American Institute of Certified Public Accountants (AICPA) Service Organization Control (SOC) 3 Type II attestation report • Xxxxxxxx-Xxxxx Act (SOX) • Payment Card Industry Data Security Standard (PCI DSS) Compliance for Genesys’ eCommerce and Payment Environments
Standards Compliance. Revenera has and will maintain SOC2 certification throughout the subscription term of the Order and will and make reports on the same available to the Customer upon request.
Standards Compliance. The Rogers Core Network hardware and management systems are compliant to the following telecom industry organization standards: • The following Telcordia standards are supported: GR-253-CORE, GR-474-CORE, GR-499-CORE, GR-1089-CORE, GR-820-CORE, GR-2918-CORE. • The following ITU-T standards are supported: G.664, G.692, G.709, G.825, G.826, G. 957, G.959.1, G.8021, and ITU-T 100-GHz- spacing, C-band channels. • The following Request for Comments (RFC) standards are supported: 4209, 2766.
Standards Compliance. 2.1. Service Provider shall be and remain ISO 27001 certified, and its Statement of Applicability shall apply to the Services. The scope of ISO 27001 certification shall include all the sites and teams which are delivering services to Subscriber.
Standards Compliance. Airship adheres to an “out of the box” default security standard in alignment with OWASP Top 10 best practices, CIS controls, and SOC 2 Type II principles.
