Section 9.31 - Valid requests for delivery of 911 traffic in Internet Protocol-based formats(a)Phase 1 valid request. A 911 Authority's request for delivery of 911 traffic in the manner specified in § 9.29(a) is a Phase 1 valid request if the requesting 911 Authority- (1) Certifies that it has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format and transmit such traffic to the PSAP(s) connected to it;(2) Certifies that it has obtained commitments from any ESInet provider, Next Generation 911 Core Services provider, and/or call handling equipment provider needed to facilitate and complete connectivity testing within the compliance timeframe applicable to the originating service provider;(3) Certifies that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format;(4) Identifies the NG911 Delivery Point(s) designated pursuant to § 9.32; and(5) Provides notification to the originating service provider that includes the information and certifications set forth in paragraphs (a)(1) through (4) of this section. Notification by the 911 Authority via a registry made available by the Commission in accordance with requirements established in connection therewith, or any other written notification reasonably acceptable to the originating service provider, shall constitute sufficient notification for purposes of this paragraph.(b)Phase 2 valid request. A 911 Authority's request for delivery of 911 traffic in the manner specified in § 9.29(b) is a Phase 2 valid request if the requesting 911 Authority-(1) Certifies that it has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format that complies with NG911 commonly accepted standards and transmit such traffic to the PSAP(s) connected to it;(2) Certifies that its ESInet is connected to a fully functioning Next Generation 911 Core Services network that can provide access to a Location Validation Function and interface with a Location Information Server or its functional equivalent provided by the originating service provider;(3) Certifies that it has obtained commitments from any ESInet provider, Next Generation 911 Core Services provider, and/or call handling equipment provider needed to facilitate and complete connectivity testing within the compliance timeframe applicable to the originating service provider;(4) Certifies that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format that complies with NG911 commonly accepted standards;(5) Identifies the NG911 Delivery Point(s) designated pursuant to § 9.32; and(6) Provides notification to the originating service provider that includes the information and certifications set forth in paragraphs (b)(1) through (5) of this section. Notification by the 911 Authority via a registry made available by the Commission in accordance with requirements established in connection therewith, or any other written notification reasonably acceptable to the originating service provider, shall constitute sufficient notification for purposes of this paragraph.(c)Originating service providers' petitions challenging 911 Authorities' requests. Within 60 days of the receipt of a Phase 1 or 2 request from a 911 Authority, an originating service provider may submit a petition to the Public Safety and Homeland Security Bureau asserting that the 911 Authority's request does not satisfy a condition set forth in paragraph (a) or (b) of this section for a Phase 1 or Phase 2 valid request. The Public Safety and Homeland Security Bureau may review the petition and determine whether to pause the implementation deadline for that originating service provider, affirm the request of the 911 Authority as valid, or take other action as necessary. (1) The petition process shall be subject to the procedural requirements set forth in §§ 1.41 , 1.45 , and 1.47 of this chapter.(2) The petition must be in the form of an affidavit signed by a director or officer of the originating service provider, documenting:(i) The basis for the originating service provider's assertion that the 911 Authority's request does not satisfy one or more of the conditions set forth in paragraph (a) or (b) of this section for a Phase 1 or Phase 2 valid request.(ii) Each of the specific steps the originating service provider has taken to implement the Phase 1 requirements set forth in § 9.29(a) or the Phase 2 requirements set forth in § 9.29(b).(iii) The basis for the originating service provider's assertion that it cannot make further implementation efforts until the 911 Authority satisfies the conditions set forth in paragraph (a) or (b) of this section for a Phase 1 or Phase 2 valid request.(iv) The specific steps that remain to be completed by the originating service provider and, to the extent known, the 911 Authority or other parties before the originating service provider can implement the Phase 1 requirements set forth in § 9.29(a) or the Phase 2 requirements set forth in § 9.29(b).(3) All affidavits must be correct. The originating service provider's director or officer who signs the affidavit has the duty to personally determine that the affidavit is correct. If the affidavit is incorrect, he or she, as well as the originating service provider, may be subject to enforcement action.(4) An originating service provider may not file an inadequate or incomplete petition. If an originating service provider's petition is inadequate and/or incomplete and the originating service provider has not met its obligations as set forth in § 9.29(a) or (b) at the time of the relevant deadline, the originating service provider may be considered noncompliant with the applicable rules as if the petition had not been filed.(5) An originating service provider that challenges a 911 Authority's valid request must describe all steps taken toward implementing the Phase 1 requirements set forth in § 9.29(a) or the Phase 2 requirements set forth in § 9.29(b) that are not dependent on the readiness of the 911 Authority.(6) The 911 Authority may file an opposition to the originating service provider's petition and the originating service provider may file a reply to the opposition in accordance with § 1.45 of this chapter. A copy of the document (petition, opposition, or reply) must be served on the other party (911 Authority or originating service provider) at the time of the filing in accordance with § 1.47 of this chapter.(d) Paragraphs (a), (b), and (c) of this section may contain information collection and recordkeeping requirements that require review by the Office of Management and Budget. Compliance with those paragraphs will not be required until this paragraph (d) is removed or contains a compliance date.