Thus, Telenational's customers and the public were not harmed by the transfer of control. In addition to satisfying the above requirements, there were no changes to Telenational's rates, terms or conditions of service as a result of the transaction. Based on this record, we find that Rapid Link meets the minimum criteria for a CPCN to be granted for purposes of approving the transfer of ownership. of the California Business and Professions Code, or for any actions which involved misrepresentations to consumers, nor is currently under investigation for similar violations. Applicants also represented that no one associated with or employed by Rapid Link as an affiliate, officer, director, partner, or owner of more than 10% of Applicants was previously associated with any telecommunication carrier that filed for bankruptcy, or has been found either civilly or criminally liable by a court of appropriate jurisdiction for a violation of § 17000, et seq. However, the financial statements provided were consolidated for the corporate family and it appears Telenational may be in a better financial position than Rapid Link or one or more of the affiliates.īackground information provided by Applicants on Rapid Link's management is sufficient to satisfy our requirement for technical expertise. In addition, the applicant is required to make a reasonable showing of technical expertise in telecommunications or a related business.Īpplicants provided a copy of audited consolidated financial statements from Rapid Link and its affiliated companies that demonstrate that Rapid Link controls sufficient resources to meet our financial requirements. An applicant who desires to resell local exchange services and/or interexchange services must demonstrate that it has a minimum of $25,000 in cash or cash equivalent, reasonably liquid and readily available to show minimum financial viability. The Commission has established two major criteria for determining whether a CPCN should be granted. Since Telenational possesses a CPCN to provide resold intra- and inter-Local Access and Transport Area services within California, we will apply the requirements for such authority to Rapid Link. In a situation where a company that does not possess a CPCN desires to acquire control of a company that does possess a CPCN, we apply the same requirements as in the case of an applicant seeking a CPCN to exercise the type of authority held by the company being acquired. 10 Where necessary and appropriate, the Commission may attach conditions to a transaction in order to protect and promote the public interest. 9 The Commission may also consider if the transaction will serve the public interest. 8 The primary standard used by the Commission to determine if a transaction should be authorized under § 854(a) is whether the transaction will adversely affect the public interest. The Commission has broad discretion to determine if it is in the public interest to authorize a transaction pursuant to § 854(a). Code § 854(a) states that no person or corporation shall acquire control of any public utility organized and doing business in this state without first securing authorization to do so from the Commission, and any such acquisition without that prior authorization shall be void and of no effect. Public clients should send their client_id as formData parameter.| grant_type | code | client_credentials | password | refresh_token ||-|-|-|-|-|| client_id | required | required | required | required || client_secret | required | required | required | required || code | required | | | || redirect_uri | required | | | || username | | | required | || password | | | required | || scope | | optional | optional | || refresh_token | | | | required |The implicit grant requests, see /oauth2/authorize.D0906024 Authorizing Transfer of Control and Imposing a Fine.ĥ. Alternatively, they may post their client_id and client_secret information as a formData parameter. Client authentication:- Confidential clients should authenticate using HTTP Basic Authentication. Empty cells indicate a parameter is ignored for that specific grant type. The table below indicates the required parameters for each specific grant_type options. This endpoint allows requesting an access token following one of the flows below:- Authorization Code (exchange code for access token)- Client Credentials (2-legged, there is no resource owner information)- Resource Owner Password Credentials (2-legged, client provides resource owner name and password)- Refresh Token (exchange refresh token for a new access code).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |