21 August 2001. Thanks to S.
Source: http://www.askcalea.net/pdf/flexgide2.pdf (843KB)

Jump to FCC order of August 14, 2001 granting CALEA compliance extensions to affected carriers.


[20 pages.]

OMB Control Number: 1110-0030
Expiration Date: April 30, 2003


Communications Assistance for
Law Enforcement Act - CALEA

Flexible Deployment
Assistance Guide

Second Edition

Packet-Mode Communications

August 2001



CALEA
Department of Justice
Federal Bureau of Investigation
CALEA Implementation Section


TABLE OF CONTENTS

INTRODUCTION

What is Electronic Surveillance?
Types of Electronic Surveillance
What is CALEA?
Important CALEA Dates

TECHNICAL SOLUTION

Core J-Standard
Missing Capabilities
Packet-Mode Communications

REIMBURSEMENT

Capability
Capacity

FLEXIBLE DEPLOYMENT

Section 107(c) of CALEA
Law Enforcement Priorities
Carriers' Normal Generic Upgrade Cycle
CommercialAvailability of Solutions
Section 109(b) of CALEA

INFORMATION COLLECTION

Carrier Notification
Paperwork Reduction Act Notice

ADDITIONAL TECHNOLOGIES

FCC's Second Report and Order

ADDITIONAL INFORMATION

How and Where to Provide Flexible Deployment Assistance Guide Information
Contact Information

APPENDIX A - FREQUENTLY ASKED QUESTIONS

APPENDIX B - GLOSSARY

APPENDIX C - SAMPLE FLEXIBLE DEPLOYMENT ASSISTANCE GUIDE TEMPLATE

APPENDIX D - FLEXIBLE DEPLOYMENT ASSISTANCE GUIDE TEMPLATE


INTRODUCTION

The purpose of this Second Edition of the "Communications Assistance for Law Enforcement Act (CALEA) Flexible Deployment Assistance Guide" (Guide) is to further assist telecommunications carriers in meeting certain requirements of CALEA.1 This Guide continues the implementation efforts of the CALEA Implementation Section (CIS) of the Federal Bureau of Investigation (FBI) with respect to packet-mode communications for certain telecommunications carriers. This Guide requests telecommunications carriers voluntarily submit certain information to the FBI, and explains under what circumstances, based on a review of that information, the FBI might support a telecommunications carrier's request of the Federal Communications Commission (FCC) to extend the September 30, 2001 compliance deadline under Section 107(c) of CALEA.2 [See below FCC order of August 14, 2001 granting extensions to carriers.] This Guide also provides some general background information regarding CALEA, and discusses lawfully-authorized electronic surveillance, technical solutions being developed by the industry, and the cost reimbursement provisions of CALEA.

___________________

1 See 47 U.S.C. §1001, et seq.; see also CALEA Cost Recovery Regulations, 28 C.F.R. Part 100; Final Notice of Capacity: Implementation of Section 104 of the Communications Assistance for Law Enforcement Act, Notice, 63 Fed. Reg. 12217; Petition for the Extension of the Compliance Date under Section 107 of the Communications Assistance for Law Enforcement Act, Memorandum Opinion and Order, 13 FCC Red 17990; Second Report and Order, Communications Assistance for Law Enforcement Act, CC Docket No. 97-213 (rel. August 31, 1999); and Third Report and Order, Communications Assistance for Law Enforcement Act, CC Docket No. 97213 (rel. August 31, 1999); USTA v. FBI, 227 F.3d 450 (D.C. Cir. 2000).

2 The FBI believes that submission of the requested information by a carrier could facilitate a mutually beneficial agreement between the FBI and the carrier. However, carriers should be aware that submission of information in response to this Guide is completely voluntary; and does not create any legal obligation on the part of the Federal Government or the carrier. The Guide is not intended to make any offers nor provide legal advice. If carriers have any questions regarding their legal obligations under CALEA they should consult their own legal advisors.

As explained further in this Guide, certain telecommunications carriers3 are under an obligation to meet CALEA assistance capability requirements for packet-mode communications by the September 30, 2001 compliance deadline specified by the FCC. By implementing a Flexible Deployment Plan for packet-mode communications, the FBI intends to use a similar evaluation method as used in the previous iteration of its Flexible Deployment Plan (i.e., extensions of the June 30, 2000 compliance deadline for CALEAs assistance capability requirements). Carriers choosing to submit information in response to this Guide are strongly encouraged to do so on or before September 30, 2001.

____________________

3 The FCC held in its Third Report and Order that telecommunications carriers providing wireline local exchange, cellular, and/or broadband Personal Communications Service (PCS) were subject to the September 30, 2001 compliance date for packet-mode communications. The FCC further stated that all other carriers were required to meet CALEAs assistance capability requirements by June 30, 2000. See Third Report and Order, Communications Assistance for Law Enforcement Act, CC Docket No. 97-213 (rel. August 31, 1999),1135, 36.

If, after reviewing the information submitted, the carrier and the FBI are able to arrive at a mutually agreeable CALEA deployment schedule, the FBI may support the carrier's request to the FCC for an extension, provided that the carrier then proceeded with its deployment in accordance with the schedule. An agreed-to deployment schedule could benefit both parties in many ways, including avoiding a dispute before the FCC regarding an extension request. The FCC has stated that it would accord "significant weight" to such an agreement, in determining whether to grant an extension to a carrier.4 Carriers should note, however, that the ultimate decision on any extension rests solely with the FCC.

____________________

4 See Second Report and Order, Communications Assistance for Law Enforcement Act, CC Docket No. 97-213 (rel. August 31, 1999), ¶ 37, n. 100.

What is Electronic Surveillance?

Lawfully-authorized electronic surveillance is a law enforcement tool that police and other authorized government agencies use to investigate and prosecute criminals. Its use by such agencies is strictly limited by law. Lawfully-authorized electronic surveillance is a law enforcement agency's or organization's lawful collection of (1) the contents5 of communications; and/or (2) the dialing or signaling information that identifies the origin, direction, destination, or termination of any communication generated or received by a subject of surveillance by means of the equipment, facilities, or services of a telecommunications carrier.

____________________

5 Communications "contents" is defined by 18 U.S.C.. § 2510(8) as "any information concerning the substance, purport or meaning of that communication."

In 1968, Congress carefully considered and passed the Omnibus Crime Control and Safe Streets Act (Pub. L. No. 90-351, 82 Stat. 212), which laid out the meticulous procedures law enforcement must follow to obtain the necessary judicial authorization to conduct electronic surveillance in the fight against crime. The law was enacted after Congress exhaustively debated issues concerning law enforcement's need to effectively address serious criminal activity and an individual's right to privacy.

In 1970, Congress amended the federal wiretap statute to confirm the government's authority to lawfully require providers of communications services to provide law enforcement with the ". . . technical assistance necessary to accomplish the interception . . ."6 In the telecommunications environment of that time, only comparatively minor assistance from telephone companies was needed by law enforcement to accomplish the interception (e.g., identity of "access points"). However, in today's telecommunications environment, greater assistance is necessary because newer and more advanced telecommunications technologies, services, and features are now being offered by service providers.

____________________

6 18 U.S.C.§ 2518(4).

In 1978, Congress passed the Foreign Intelligence Surveillance Act (FISA, 50 U.S.C, §§ 1801-1843) to safeguard national security by authorizing sellect government agencies to conduct electronic surveillance of a foreign power or an agent of a foreign power for the purpose of obtaining foreign intelligence information. Section 1805(b)(2)(B) of FISA requires that common carriers furnish ". . . all information, facilities, or technical assistance necessary to accomplish the electronic surveillance in such a manner as will protect its secrecy and produce a minimum of interference . . ." with the services of the target of electronic surveillance.

In 1986, as a result of developments in telecommunications and computer technologies, Congress found it necessary to enact the Electronic Conununications Privacy Act (Pub. L No. 99-508, 100 Stat. 1848), Ahich amended the Omnibus Crime Control and Safe Streets Act by broadening its coverage to include electronic communications (including electronic mail, data transmissions, faxes, and pagers). The provisions of Title III of the 1968 Act, as amended, continue to govern the procedures for obtaining legal authority for initiating and conducting lawful interceptions of wire, oral, and electronic communications for crin-final investigatory purposes.

Types of Electronic Surveillance

For the purpose of this Guide, lawfully-authorized electronic surveillance is considered to consist of both the interception of communications content (commonly referred to as wiretaps) and the acquisition of dialing and signaling information used to identify a call (e.g., dialed number information) through the use of pen registers and/or through the trace devices.

The term interception is defined by law and refers to the lawful acquisition of the contents of any wire, electronic or oral communication (e.g., signs, signals, writing, images, sounds, data, or intelligence of any nature) transmitted from one party to another. Authority for initiating an interception is found in Title III of the Omnibus Crime Control and Safe Streets Act or FISA.

The term pen register is defined by law and refers to the lawful acquisition of certain outgoing dialing or signaling information. Authority for using a pen register is found in 18 U. S.C. § 3123 and 50 U.S.C. § 1842.

The term trap and trace is defined by law and refers to the lawful acquisition of the originating number of any wire or electronic communication. Authority for using a trap and trace device is also found in 18 U.S.C. § 3123 and 50 U.S.C. § 1842.

What is CALEA?

In October 1994, Congress again took action to protect public safety and national security by enacting CALEA, (Pub. L. No. 103-414, 108 Stat. 4279). The law clarifies and further defines the existing statutory obligation of providers of telecommunications services in assisting law enforcement in executing electronic surveillance court orders.

CALEA does not change or expand law enforcement's fundamental statutory authority to conduct various types of electronic surveillance. It seeks to ensure that after law enforcement obtains the appropriate legal authority, telecommunications carriers will have the necessary technical capability and sufficient capacity to fulfill their statutory obligations to assist law enforcement. In many instances, telecommunications carriers do not have the capability to handle all electronic surveillance court orders.

CALEA sets forth, in law, the assistance capability requirements that telecommunications carriers need to meet and maintain within their networks to assist law enforcement in conducting lawfully-authorized electronic surveillance. Specifically, CALEA directs the telecommunications industry to design, develop, and deploy solutions that meet specific assistance capability requirements.7

____________________

7 Section 103 of CALEA, 47 U.S.C. § 1002.

CALEA also recognizes that some existing equipment, services, and features would have to be retrofitted and includes a provision by which the Attorney General could reimburse the industry for modifications made to equipment, facilities, and services installed or deployed on or before January 1, 1995.

Important CALEA Dates

Figure 1 - CALEA Timeline

October 24, 1994 - Date of CALEA enactment

January 1, 1995 - Reimbursement eligibility date for equipment, facilities, and services in stalled or deployed in a carrier's network

October 25, 1998 - Original CALEA assistance capability compliance date

June 30, 2000 - New compliance date for Section 103 assistance capability requirements for all telecommunications services and technologies (e.g., Telecommunications Industry Association [TIA] interim technical standoxd J-STD-025 for wireline, cellular, and broadband Personal Communications Services [PCs])

September 30, 2001 - Compliance date for packet-mode communications to comply with the assistance capability requirements.8

____________________

8 The FCC, in its Third Report and Order, determined that certain telecommunications carriers were required to provide a capability to conduct surveillance regarding packet-mode communications by September 30, 2001. See Third Report and Order, Communications Assistance for Law Enforcement Act, CC Docket 97-213 (rel August 31, 1999), ¶ 55.

TECHNICAL SOLUTION

CALEA was enacted to ensure that ongoing technological changes in the telecommunications industry would not compromise the ability of federal, state, and local law enforcement agencies to conduct lawfully-authorized electronic surveillance. To that end, CALEA obligates telecommunications carriers to ensure that their equipment, facilities, and services are technically capable of expeditiously isolating and delivering to law enforcement agencies all communications content and call-identifying information that law enforcement is authorized to acquire.

Several years before the passage of CALEA, law enforcement began meeting with individual telecommunications companies, as well as industry forums such as the Electronic Communications Service Provider (ECSP) Committee. A primaty objective of those meetings was to develop a common understanding of law enforcement's surveillance requirements and to explore options by which a networkbased or switch-based interception might be implemented. The ECSP Committee, with law enforcement's endorsement, brought electronic surveillance requirements and issues to the attention of industry standards-setting organizations such as the TR45 and TR46 Committees of TIA.

In May 1995, TIAs TR45.2 Subcommittee formed the Lawfully Authorized Electronic Surveillance (LAES) Ad Hoc Group. Its mission was to develop a technical electronic surveillance standard detailing what information should be accessed to support lawfully-authorized electronic surveillance and how intercepted communications and call-identifying information should be delivered by a telecommunications carrier to a law enforcement agency. In late 1995, PCs and wireline standards bodies agreed to work with the TR45.2 group, which normally represents the cellular industry, on a standard for wireline and wireless networks.

Core J-Standard

On December 8, 1997, TIA published an interim technical standard9 (J-STD-025, or J-Standard) concerning electronic surveillance assistance capability requirements for telecommunications carriers providing wireline, cellular, and broadband PCS. J-STD-025 describes advanced electronic surveillance capabilities intended to provide law enforcement the ability to collect call-identifying information and call content pursuant to lawful authorization regardless of whether the telecommunications are carried in circuit-mode or in packet-mode.

____________________

9 An interim technical standard was jointly published by TIA and Committee T1 (sponsored by the Alliance for Telecommunications Solutions) as J-STD-025, Lawfully Authorized Electronic Surveillance.

The original assistance capability compliance date for CALEA, October 25, 1998, was extended by the FCC10 for J-STD-025 to June 30, 2000. The FCC determined that carriers could not comply with the original October 25, 1998 compliance date because of the absence of available technology during the compliance period.

____________________

10 Petition for the Extension of the Compliance Date under Section 107 of the Communications Assistance for Law Enforcement Act, Memorandum Opinion and Order. 13 FCC Rcd 17990.

Missing Capabilities

On March 27, 1998, the Department of Justice (DOJ) and the FBI filed ajoint petition before the FCC. The DOJ/FBI petition argued that the industry's J-STD-025 was deficient in that it failed to include nine capabilities determined by DOJ as necessary to meet the requirements of this law.

On August 31, 1999, the FCC released its Third Report and Order, regarding Section 103 assistance capability requirements.11 The FCC determined that, in addition to the assistance capabilities included in J-STD-025, wireline, cellular, and broadband PCS carriers must provide six additional assistance capabilities sought by the DOJ and FBI.12

____________________

11 Third Report and Order, Communications Assistance for Law Enforcement Act, CC Docket No. 97-213 (rel. August 3 1, 1999).

12 See In the Matter of Establishment of Technical Requirements and Standards for Telecommunications Carrier Assistance Capabilities under the Communications Assistance for Law Enforcement Act, Public Notice, CC Docket No. 97-213, DA 98-762, (rel. April 20, 1998) (encompassing petitions filed by CDT, TIA, CTIA, and DOJ/FBI).

The six capabilities determined by the FCC to be required by CALEA are:

On August 15, 2000, in the case of United States Telecom Association, et al., v. FCC, 227 F.3d 450 (D.C. Cir. 2000) the United States Court of Appeals for the District of Columbia Circuit partially vacated and remanded to the FCC the Third Report and Order. The court vacated the FCC's decision with respect to four "punch list" capabilities: dialed digit extraction, party/hold/join/drop information, subject initiated dialing and signaling, and in-band/out-of-band signaling. The court's ruling requires the FCC to reconsider whether these four punch list items are mandated by CALEA and to enter a new decision in accordance with the court's instructions. The Court did not reverse or remand the FCC's determinations regarding packet-mode communications.

To date, the FCC has not concluded its deliberations regarding those four "punch list" capabilities. Therefore, this Second Edition of the Flexible Deployment Guide is limited to packetmode communications

Packet-Mode Communications

The industry-developed technical standard, J-STD 025 provides descriptions of capabilities that wireline local exchange, cellular, and broadband PCS carriers need to make available to law enforcement regardless of the transmission mode (circuit-mode or packet-mode) utilized by carriers when providing service(s).

In its Third Report and Order (released on August 31, 1999), the FCC determined that wireline, cellular, and broadband PCS carriers could provide the capability to intercept packet-mode communications in accordance with J-STD-025 The FCC also invited TIA ". . . to study CALEA solutions for packetmode technology and report to the Commission in one year on steps that can be taken, including particular amendments to JSTD-025 . . ."13

____________________

13 Third Report and Order ¶ 55.

As a result, TIA convened a series of Joint Experts Meetings (JEM) to study the issue. The final JEM Report, meeting summaries, and technical contributtions made to the meetings are available at TIA's website: www.tiaonline.org.

In its Third Report and Order, the FCC also mandated that the capability to intercept packet-mode communications be made available to law enforcement by September 30, 2001.14

____________________

14 Ibid.

CALEA envisioned the possibility that technical standards would not be developed for (1) carriers to meet the assistance capability requirements of section 103 or (2) manufacturers and providers of telecommunication support services to satisfy the obligations of section 106.15 Section 107(a)(3) of CALEA, Absence of Standards, states that "[t]he absence of technical standards for implementing the assistance capability requirements of section 103 shall not ... relieve a carrier, manufacturer, or telecommunications support services provider of the obligations imposed by section 103 or 106, as applicable. "16

____________________

15 Section 106 of CALEA outlines the responsibilities of equipment manufacturers and providers of telecommunications support services.

16 Section 107 (a)(3) of CALEA, 47 U.S.C. § 1006(a)(3).

REIMBURSEMENT

To facilitate CALEA's implementation, Congress authorized $500 million to be appropriated to reimburse the telecommunications industry for certain eligible costs associated with modifications made to their networks. Section 109 of CALEA grants the Attorney General discretionary authority to allocate appropriated funds in a manner consistent with law enforcement priorities, and mandates the Attorney General to establish the necessary regulations to effectuate timely and costefficient payrnent to telecommunications carriers. The reimbursement of carriers for any eligible costs will occur under the provisions of Section 109 of CALEA, and the associated Cost Recovery Regulations,17 a firm fixed price agreement,18 or other applicable law, and is in no way affected by a carrier's submission of information in response to this Guide.

____________________

17 CALEA Cost Recovery Regulations, 28 C.F.R. Part 100.

18 Pub. L. 106-246, Div. B, Title 11, July 13, 2000, 114 Stat. 542.

The Omnibus Consolidated Appropriations Act of 1997 (P.L. 104-208)19 amended CALEA by adding Title IV which created the Telecommunications Carrier Compliance Fund (TCCF). The purpose of the TCCF is to facilitate the disbursement of funds available for CALEA implementation. Additionally, the Omnibus Consolidated Appropriations Act of 1997 authorized agencies with law enforcement and intelligence responsibilities to transfer unobligated balances into the TCCF, subject to applicable Congressional reprogramming requirements.

____________________

19 The Omnibus Consolidated Appropriations Act of 1997; P.L. 104-208, 110 STAT 3009 (1996).

Capability

The FBI will utilize two alternative approaches for reimbursing CALEA software solutions: (1) right-to-use (RTU) license agreements, or (2) switch-by-switch reimbursement. Both approaches are designed to be consistent with the FBI's goal of maximizing return on TCCF dollars while at the same time responding to industry concerns regarding CALEA compliance costs and deployment schedules. Under the RTU license agreement approach, the FBI has reimbursed a facilitating carrier for that carrier's purchase of the CALEA software RTU license for a switch installed or deployed on or before January 1, 1995. The license fee covers the manufacturer's CALEA software development cost for a particular switch platform type. Manufacturers have then granted CALEA software RTU licenses to all other carriers at no charge for all switches of the same platform type.

In some instances, a manufacturer and its facilitating carrier partner have declined to pursue a RTU license purchase agreement with the FBI, or the FBI, manufacturer, and facilitating carrier partner have been unable to finalize an RTU license arrangement. In these cases, manufacturers are expected to design and develop a CALEA solution in accordance with the industry's normal business practices. When a solution is available for deployment, the telecommunications market will determine the solution's price and carriers are expected to install the developed CALEA solution. Some of the installation costs may be eligible for reimbursement under CALEA. Under a switch-by-switch reimbursement approach, a carrier will be reimbursed for CALEA software on an individual, switch-byswitch basis.

The reimbursement approach chosen is dependent on several factors. These factors include, but are not limited to, availability of TCCF funds, the reimbursement cost for a RTU license for the CALEA solution, per-switch commercial prices for CALEA solutions, and a switching platform's priority status to law enforcement.

Once those CALEA software solutions that the FBI has chosen to reimburse have been completed, it is in the interest of the FBI and industry to minimize, to the extent practicable, the costs associated with deploying the CALEA solution in carriers' networks. The costs associated with deploying CALEA-compliant solutions are expected to be significantly reduced if carriers are allowed to incorporate the deployment of CALEA into their normal generic upgrade cycles.20 To this end, the FBI's Flexible Deployment Plan provides the opportunity for any carrier to voluntarily supply information to the FBI so that the carrier and the FBI may cooperatively develop a CALEA deployment schedule for that carrier. These schedules may be consistent with a carrier's normal deployment processes and schedules if the schedules maximize the timely deployment of solutions on those switches that are of highest priority to law enforcement.

____________________

20 For the purposes of this Guide, normal generic upgrade cycles are carrier-specific timelines of past and / or futureplanned software generic deployments.

To accomplish this, the FBI is soliciting historical electronic surveillance data from carriers in order to refine equipment prioritization based on the most current intercept data available. Prioritized equipment will be compared with the normal deployment plans identified by a carrier. Carriers and the FBI may then agree on a jointly-developed deployment schedule based on this data, deploying first on law enforcement's highest priority equipment. In some cases, this process may result in certain equipment, installed or deployed after January 1, 1995, not having a CALEA-compliant solution deployed by the September 30, 2001 capability compliance date for packetmode communications. In those instances where a carrier and the FBI can agree on a deployment schedule, the FBI will support a carrier's petition of the FCC to issue limited extensions of time for compliance on specific equipment installed or deployed after January 1, 1995, consistent with Section 107(c) of CALEA. The above described concept is the central tenet of the FBI's Flexible Deployment Plan. For more information regarding Flexible Deployment, please see the Flexible Deployment section of this Guide.

Capacity

On March 12, 1998, the FBI published in the Federal Register a Final Notice of Capacity21 which delineates the estimated actual and maximum number of simultaneous call content interceptions, pen registers, and trap and trace devices that law enforcement may conduct in a given geographic area. The Final Notice of Capacity, with a compliance date of March 12, 2001, was published pursuant to Section 104 of CALEA22 and applies to carriers providing wireline local exchange, cellular and broadband PCS services. The Final Notice of Capacity is also available on the FBI's CALEA Implementation Section (CIS) Web site www.AskCALEA.net.23

____________________

21 See Implementation of Section 104 oj'the Communications Assistance for Law Enforcement Act; Notice, 63 Fed. Reg. 12217 (March 12, 1998).

22 47 U.S.C. § 1003.

23 The link to the Final Notice of Capacity can be found at www.AskCALEA.net/programs/capacity.html.

In addition to the reimbursement of certain costs associated with complying with the assistance capability requirements of Section 103, CALEA also provides that the Attorney General may agree to reimburse certain costs of modifications made to systems or services, identified in a carrier statement filed in accordance with CALEA Section 104(d), to attain the capacity requirements set forth in the Notice of Capacity.

In July of 1998, the FBI published a Small Entity Compliance Guide for the Final Notice of Capacity. That publication sets forth guidelines and procedures to assist carriers in complying with the Final Notice of Capacity as required by Section 104 of CALEA. The Small Entity Compliance Guide for the Final Notice of Capacity is also available on the FBI's CIS Web site at www.AskCALEA.net.24

____________________

24 The Small Entity Compliance Guide can be found at www.AskCALEA.net/programs/capacity.html.

FLEXIBLE DEPLOYMENT

The FBI's overall CALEA implementation approach includes supporting telecommunications carriers' deployment of CALEA-compliant solutions in accordance with their normal generic upgrade cycles, where such deployment will not delay implementation of CALEA solutions in areas of high priority to law enforcement. This approach is the result of the FBI's recognition of the issues facing carriers and represents an attempt to minimize the costs and operational impact of CALEA compliance on all carriers. Specifically, carriers wishing to participate in this effort may provide the FBI with their projected CALEA deployment schedules for all switches in their network, as well as information pertaining to any recent lawfully-authorized electronic surveillance activity. Using this information, tlie FBI and carrier will attempt to develop a mutually agreeable deployment schedule.25 This approach is also the FBI's attempt to minimize the cost to the Government of implementing CALEA by providing the opportunity for carriers and the FBI to agree on deferring the installation of CALEA-compliant solutions in those instances where public safety and national security would not be jeopardized.

____________________

25 In the event that unforeseen circumstances do not allow a carrier to deploy CALEA-compliant solutions according to the mutually agreed-to schedule, the carrier should notify the FBI as soon as possible. In the interest of public safety and/or national security, emergency or exigent law enforcement circumstances rnay result in the modification of a previously agreed-to schedule between the carrier and FBI.

If the FBI and carrier are able to agree upon a deployment schedule, theFBI intends to provide support to an individual carrier's petition before the FCC for extensions of CALENS September 30,2001 assistance capability compliance date. In order to reach such an agreement, the FBI must have an opportunity to: (1) review and comment on proposed carrier deployment schedules, and (2) review information provided by carriers pertaining to recent lawfully-authorized electronic surveillance activity. The FBI's support of a carrier's systemwide extension petition will be conditioned upon the carr ier's meeting the agreed-to deployment schedule. In addition, the FBI will request the FCC incorporate such a condition into any final decision on a carrier's extension petition.

Section 107(c) of CALEA

Under Section 107(c) of CALEA, a carrier is permitted to file one or more petitions with the FCC for an extension of the Section 103 assistance capability compliance deadline. The maximum extension the FCC may grant under this provision is two years. The FCC is required, by statute, to consult with the Attorney General prior to deciding whether to grant the extension. Under a flexible deployment arrangement, the FBI would fulfill this consultative role for the Attorney General, by providing support for the carrier's flexible deployment plan.

The FBI's support would be conditioned upon an agreement between the carrier and the FBI on a deployment schedule. The schedule must ensure that CALEA-compliant solutions are deployed on priority equipment in the near term and that other equipment is modified within a reasonable time. Assuming these conditions are met, a carrier would then be able to deploy solutions on the lower priority equipment in accordance with its normal business cycle.

Law Enforcement Priorities

One important factor to the FBI in considering a carrier's proposed CALEA solution deployment schedule is the historical electronic surveillance activity of law enforcement. The equipment, facilities, and services26 of a carrier which have previously played a role in the execution of lawfully-authorized electronic surveillance are considered by the FBI to be of high priority to law enforcement. These equipment, facilities, and services should be taken into consideration by a carrier when developing its proposed CALEA solution deployment schedule. High priority equipment, facilities, and services scheduled to be replaced should also be identified by a carrier. Figure 2 shows how law enforcement's priorities can be incorporated into a carrier's normal generic upgrade cycle.

____________________

26 In those cases where a carrier has replaced circuit-mode equipment with packet-mode equipment, the carrier should provide historical electronic surveillance information for the area served by both types of equipment.

Figure 2 - Law Enforcement Priorities and Carriers' Generic Upgrade Cycle


Carriers' Normal Generic Upgrade

A central element to the FBI's Flexible Deployment Plan is a carrier's non-nal, or planned, generic upgrade cycle. Individual carriers plan, engineer, and deploy services at different times and at different frequencies. In order to ensure that carriers can meet their CALEA obligations without being overly burdensome, carriers have the opportunity to advise the FBI of their normal generic upgrade cycles. Past generic upgrades and associated dates can be provided to establish a baseline of previous generic upgrades and validate future expected generic upgrades. See the information descriptions in the following section, "Information Collection," and Appendix C for a Sample Flexible Deployment Assistance Guide Template.

Under the FBI's Flexible Deployment Plan, a carrier's normal generic upgrade cycle will play a role in when CALEA-compliant solutions are to be deployed in a carrier's network (see Figure 3). CatTiers will develop their own deployment cycles based on: (1) the commercial availability of CALEA-compliant solutions; (2) market conditions and business plans; and (3) historical lawfully-authorized electronic surveillance activity (i.e., law enforcement priorities). The six-, twelve-, and twenty-four-month deploymerit cycles shown in Figure 3 are illustrative examples of normal generic upgrade cycles. Actual carrier generic upgrade cycles are expected to differ based on the considerations outlined above.

Figure 3 - CALEA Capability Development, Commercial Availability, and Carriers'Generic Upgrade Cycles

Commercial Availability of Solutions

In setting the carriers'packet-mode communicatioiliN aNsistance capability requirement compliance date of September 30,2001, the FCC did not stipulate a specific date by which manufacturers of telecommunications equipment (i.e., equipment used in wireline, cellular, and broadband PCS services) must make compliant solutions commercially available to carriers. However, the FCC did note that the September 30, 2001 ". . . date is 15 months after the June 30,2000 CALEA compliance deadline, and will afford manufacturers that have not yet developed a packet-mode capability the time needed to do so."27

____________________

27 FCC Third Report and Order, FCC 99-230, ¶ 55.

CALEA-compliant solutions are commercially available on the date a manufacturer first makes its solution available. The FBI recognizes that manufacturers' production cycles may delay a particular carrier's ability to deploy CALEA-compliant software. The FBI expects carriers to incorporate the actual availability of CALEA-compliant solutions (i.e., available to the carrier) when developing their proposed deployment schedules. Additionally, the FBI recognizes that some manufacturers may not have CALEA-compliant solutions available in order for carriers to deploy and meet the September 30, 2001 deadline.

Section 109(b) of CALEA

In those instances where compliance by a carrier is not reasonably achievable, CALEA provides a remedy under Section 109(b). The carrier may choose to petition the FCC with respect to any equipment, facilities, or services on which compliance would not be "reasonably achievable." In its Second Report and Order, the FCC articulated its basis for consideration of individual carrier petitions under CALEAs "reasonably achievable" provision. The FCC stated that: (1) it would be premature to adopt factors in addition to those set forth in Section 109(b), or to assign special weight to any one factor; (2) the Section 109 process should be reserved for the examination of specific carrier compliance problems, not to revisit broad policy goals; and (3) carrier requests for relief from CALEA compliance based on CALEA's costs or impact on rates, quality of service, or introduction of services to the market must be supported by specific facts, including quantitative data. Finally, the FCC stated that ". . . it may be necessary to provide relief under section 109 only in unusual cases."28

____________________

28 Second Report and Order, Communications Assistance for Law EnforcetnentAct, CC Docket No. 97-213 (rel. August 3 1, 1999), ¶ 37.

INFORMATION COLLECTION

As stated previously in this Guide, the FBI's Flexible Deployment Plan is based on (1) a carrier's normal generic upgrade cycle - necessary to deploy a completely CALEA-compliant solution, and (2) law enforcement priorities. In order for the FBI to make an informed decision regarding a carrier's proposed deployment schedule, a carrier is encouraged to provide information identifying its specific equipment, geographic area(s) served by the equipment, previous generic deployments, future planned generic deployments, and historical lawfully-authorized electronic surveillance activity.

In the following table, the term "componenf' refers to any switch, other telecommunications equipment, or peripheral piece of telecommunications equipment which would need to undergo modification to be compliant with the requirements of CALEA. Examples of "components" include (but are not limited to) end office switches, packet-mode only network edge devices, and peripheral equipment (e.g., Home Location Registers [HLR], and InterWorking Function [IWFI). Additionally, carriers with multiple TRS (Telecommunications Relay Service) numbers must submit an individual template for each TRS number.

A Sample Flexible Deployment Assistance Guide Template is provided in Appendix C. A blank Flexible Deployment Assistance Guide Template is provided in Appendix D. Carriers may use the blank form to provide the above described information. An electronic version of this form, prepared in Microsoft Excel®, is also available on the FBI's CIS CALEA Web site at www.AskCALEA.net. Carriers may submit electronic versions of the Flexible Deployment Assistance Guide Template to the following web e-mail address: [email protected] or to the address provided at the end of this Guide.

The intent of the FBI's collection of information is to analyze a carrier's proposed deployment schedule and to assess whether or not the FBI would be willing to support a carrier's petition for an extension of CALEA's assistance capability compliance date. Any carrier-provided information marked as proprietary will be treated accordingly by the FBI, and the FBI will enter into an appropriate non-disclosure agreement with any carrier who believes it to be necessary.

In order for the FBI to make informed decisions regarding a carrier's proposed deployment schedule, a carrier may provide information identifying its specific equipment, geographic area(s) served by the equipment, previous generic deployments, future planned generic deployments, and historical lawfully-authorized electronic surveillance activity.

In the event that a carrier believes the template provided in Appendix D of this Guide requests information that is not applicable to its network or equipment, or is insufficient for a carrier to characterize its deployment schedule on an equipment-specific basis, a carrier is free to provide deployment information in any form. However, a carrier should provide the name of a contact person and their telephone number, as well as the following component-specific information: unique component identifier; component location; service area; current software generic; historical software generic deployment dates; future planned software generic deployment dates; and historical electronic surveillance intercept activity.

Data Type Description
Carrier Name The name of the telecommunications carrier that owns the identified component (e.g.,
switch, other telecommunications equipment, or peripheral telecommunications
equipment.) This name will appear on all correspondence between the FBI and
carrier.
TRS Number The TRS (Telecommunications Relay Service) number assigned by the FCC. If the
TRS number(s) are unknown, contact the FCC to obtain. Carriers with multiple TRS
numbers must submit an individual template for each TRS number.
Contact Person, Telephone,
and Facsimile Number
The name, telephone, and facsimile number of a person the FBI can contact in the
event questions arise with the submitted data.
Consultant of Record
(COR) Information
The name of the consulting or law firm; name of a contact person providing the
requested information; and the physical address, telephone, and facsimile number of
the COR, if applicable. A carrier may designate only one COR. A COR will be
contacted in the event that questions arise regarding submitted information.
CLLI Code or Other
Identifier
Common Language Location Identifier or other unique component identification.
Component-specific CLLI Codes are eleven characters long (e.g., CHANVAWFDS0).
Component Location The city and state where the component(s) is located.
Manufacturer and
Component Type
The manufacturer and type of host or stand-alone component identified by each CLLI
Code. For example: 5ESS, DMS-100, EWSD, DMS-MTX, EMX-2500, IWF. Only
in the event that a remote device needs to be upgraded, include the remote device type
and corresponding host.
Service Area(s) The name(s) of the counties, market service areas, or other appropriate geographic
areas where service is provided by each identified component. In the event that a
component serves multiple areas, each area (county, market service area, or other
appropriate geographic area) should be identified. For components with remotes,
include counties, market service areas, or other appropriate geographic areas where
service is provided by each remote.
Current Software Generic The software generic deployed as of the submission date of the carrier's completed
template on the component identified by each CLLI Code. For example: 5E14,
NAO12, MTX-10, 1.1 (IWF).
Historical Software
Deployment Dates
Previous software deployment dates (in a month/year forinat) to establish an
individual carrier's normal generic upgrade cycle. Every identified generic needs to
be accompanied by a date, and every date needs to be accompanied by a generic.
Future Planned Software
Generic Deployment Dates
The future planned software generic, and deployment dates (in a month/year forinat),
to be installed in the identified switch or equipment. Every identified generic needs to
be accompanied by a date, and every date needs to be accompanied by a generic.
Historical Intercept Activity Number of lawfully-authorized electronic surveillance intercepts (i.e.,
communications content, pen registers, and traps and traces) conducted on each
identified component by a municipal, county, state, or federal law enforcement agency
for the years 1997, 1998, 1999, and 2000. Please provide an integer for each available
space. If no intercept activity occurred during a given year, include a zero (0).

Table 1 - Flexible Deployment Information Elements

Carrier Notification

Upon receipt of carrier-submitted Flexible Deployment information, the FBI will provide the carrier a receipt notification letter. Following the FBI's analysis of carrier-subm itted information, the FBI will either: ( 1) contact the carrier to initiate the process by which it and the carrier can develop a mutually agreeable deployment schedule; (2) provide a letter of support for the carrier's deployment schedule (a copy of that letter will also be provided to the FCC); or (3) notify the carrier and FCC that the FBI cannot support that carrier's extension petition.

The final determination regarding carriers'extension petitions rests solely with the FCC. The FCC will determine whether or not to grant any carrier's extension petition using the FBI's support as one factor in its decision-making process, and will notify carriers of its decision(s) accordingly.

Carriers unfamiliar with the FCC's process regarding compliance with the assistance capability requirements of section 103 of CALEA and section 107(c) petitions for extensions of the capability compliance date should refer to the FCC's Public Notice, released on April 25, 2000.29 In its Public Notice, the FCC provided instructions for carriers to file with the FCC petitions for extensions of the June 30, 2000 capability compliance date. The FBI expects the FCC to modify its requirements and release a new Public Notice applicable to the September 30, 2001, capability compliance date for packet-mode communications.

____________________

29 Public Notice, CALEA Section 103 Compliance and Section 107(c) Petitions, CC Docket No. 97-213, FCC 00- 154 (rel. April 25, 2000).

Paperwork Reduction Act Notice

The FBI has created this Second Edition of the Flexible Deployment Assistance Guide and the associated information collection ternplate (see Appendix D) with the intent for it to be easily understood, and to impose the least possible burden on carriers choosing to provide the FBI with deployment information.

This Guide does not contain any substantive or material modifications to the previously approved information collection authorization, and will only update existing requirements for certain telecommunications carriers. In view of this fact, and because the Second Edition of the Guide does not change existing requirements for the voluntary submission of information by carriers, the Second Edition of the Guide creates no additional paperwork requirements above those already approved by the Office of Management and Budget (control number 1110-0030).

The estimated average time to read this Second Edition of the Flexible Deployment Assistance Guide, complete the template, and file the information is as follows: (1) 1 hour to read the Flexible Deployment Assistance Guide; (2) 2 hours to gather the information to complete the Flexible Deployment Assistance Guide Template; (3) 1 hour to complete the Template; (4) 15 minutes to assemble and file the Template; for a total estimated average time of 4 hours and 15 minutes per Template. If you have comments regarding this estimate, or suggestions for simplifying this Guide and the associated information collection template, you can write to both the CALEA Implementation Section (CIS), 14800 Conference Center Drive, Suite 300, Chantilly, Virginia 2015 1; and the Office of Management and Budget, Paperwork Reduction Project, OMB No. 1110-0030, Washington, D.C. 20503.

ADDITIONAL TECHNOLOGIES

FCC's Second Report and Order

On August 31, 1999, the FCC adopted its Second Report and Order30 regarding CALEA. In its Second Report and Order, the FCC examined the definition of "telecommunications carrier" set forth in Section 102 of CALEA. The FCC determined that the requirements of CALEA apply to:

____________________

30 Second Report and Order, Communications Assistance for Law EnforcementAct, CC Docket No. 97-213 (rel. August 31, 1999).

31 47 U.S.C. § 153(10).

32 See Second Order on Reconsideration, Communications Assistance for Law Enforcement Act, CC Docket No. 97-213 (rel. April 16, 2001), ¶¶ 37, 38.

The FCC concluded that sortie categories of entities are not telecommunications carriers subject to CALEA:

Participation in this phase of the FBI's Flexible Deployment Plan is available to those telecommunications carriers subject to the September 30, 200 1, deadline for compliance as set forth in the Third Report and Order. The FCC provided that all other telecommunications carriers are subject to the June 30, 2000, capability requirement compliance date.

ADDITIONAL INFORMATION

How and Where to Provide Flexible Deloyment Assistance Guide Information

Carriers can download an electronic Flexible Deployment Assistance Guide Template from the FBI's CIS Web site at www.AskCALEA.net. The Flexible Deployment Assistance Guide page is available by selecting the Flexible Deployment hyperlink.

Carriers that do not have access to the Internet and wish to acquire the Flexible Deploytnent Assistance Guide Template in electronic form can request 3.5 inch diskettes containing the electronic template from the address and/or telephone listed below. Carriers may either submit a completed Flexible Deployment Assistance Guide Template in electronic form (e.g., Microsoft Excel") or use the Flexible Deployment Assistance Guide Template provided in Appendix D of this Guide. Carriers are strongly encouraged to file their Flexible Deployment Assistance Guide Templates by September 30, 2001, and all completed Flexible Deployment Assistance Guide Templates should be sent to only one of the following:

Electronic submissions of the Flexible Deployment Assistance Guide Template may be made to:

[email protected]

Facsimile submissions of the Flexible Deployment Assistance Guide Template may be made to:

703-814-4750

Standard postal delivery submissions of the Flexible Deployment Assistance Guide Template may be made to:

CALEA Implementation Section (CIS)
Attention: Flexible Deployment Assistance Guide
14800 Conference Center Drive, Suite 300
Chantilly, VA 20151-0450

Contact information

Carriers that have additional questions or comments concerning this Second Edition of the Flexible Deployment Assistance Guide can call the following toll-free number:

Communications Assistance for Law Enforcement Act
(CALEA)
Flexible Deployment Assistance Guide
Help Desk

800-551-0336



APPENDIX A - FREQUENTLY ASKED QUESTIONS

Q: Why has the FBI published a second Flexible Deployment Assistance Guide?

A: In its Third Report and Order, the FCC determined September 30, 2001, to be the compliance date for wireline local exchange, cellular, and broadband PCS carriers that offer services using packet-mode communications technology. The Second Edition of the FBI's Flexible Deployment Assistance Guide is intended to assist those carriers that may not be able to meet the September 30, 2001 compliance deadline.

Q: What information does a carrier need to provide the FBI in order to participate in the FBI's Flexible Deployment Plan?

A: As described in the Information Collection Section of 1-1 this Guide, a carrier should provide the name of a contact person, their telephone and fax numbers, and address, as well as the following component-specific information: (1) CLLI Code or other unique component identifier; (2) component location; (3) service area(s); (4) current software generic; (5) historical software generic deployments and corresponding deployment dates; (6) future planned software generic deployments and corresponding dates; (7) historical intercept activity. In the event that a carrier chooses to make use of a consultant or law firm, the template should include: (1) the name of the consultant of record (COR); (2) the COR company name; (3) COR address; and (4) COR telephone and fax numbers. Additionally, carriers with multiple TRS (Telecommunications Relay Service) numbers must submit an individual template for each TRS number.

Q: Is it mandatory that a carrier complete the Flexible Deployment Assistance Guide Template?

A: No. There is no legislative, regulatory, or other mandate for carriers to provide the information outlined in this Flexible Deployment Assistance Guide. Carrier submission of informatiori to the FBI under the Flexible Deployment Plan is voluntary. However, the FBI will not be in a position to provide its support for any carrier's petition for an extension of CALEAs September 30, 2001 assistance capability compliance date (for packet-mode communications) without specific solution deployment infonnation.

Q: What are CALEA's compliance dates that a carrier needs to know?

A: All carriers had until June 30, 2000, to comply with the assistance capability requirements of CALEA. For wireline local exchange, cellular, and broadband PCS carriers compliance with a technical standard known as the J-Standard (TIA Standard J-STD-025) provided safe harbor from enforcement. Certain carriers (including, but not limited to wireline local exchange, cellular, and broadband PCS carriers) petitioned and received extensions of the June 30, 2000, assistance capability compliance date based on individual solution deployment schedules. Any wireline local exchange, cellular, and broadband PCS carrier using packet-mode communications has until September 30, 2001 to comply with the assistance capability requirements of CALEA. Additionally, wireline local exchange, cellular, and broadband PCS carriers had until March 12, 2001, to comply with the capacity requirements as enumerated in the Final Notice of Capacity (63 Fed. Reg. 12217).

Q: Will filling out the Flexible Deployment Assistance Guide Template ensure that a carrier receives an extension of the assistance capability requirements compliance date?

A: No. If the FBI, with the aid of the law enforcement community, determines that a carrier's proposed deployment schedule is consistent with law enforcement priorities, it may provide support for the carrier's petition under section 107(c) of CALEA. The FCC decides whether or not to grant any carrier's petition.

Q: How will carriers be notified of their status after submitting the information identified in this Flexible Deployment Assistance Guide?

A: Upon receipt of carrier-submitted Flexible Deployment information, the FBI will provide the carrier (and consultant of record) a receipt notification letter. Following the FBI's analysis of carrier-submitted information, the FBI will either: (1) contact the carrier (or consultant of record) to develop a mutually agreeable deployment schedule; (2) provide a letter of support for the carrier's deployment schedule (a copy of that letter will also be provided to the FCC); or (3) notify the carrier and FCC that the FBI cannot support that carrier's extension petition.

Q: Where can a carrier get more information regarding the y FBI's Flexible Deployment Plan?

A: The CALEA Implementation Section of the FBI maintains a Web site (www.AskCALEA.net) to provide carriers information regarding CALEA. Electronic versions of this Guide, as well as the information submission template, are available on the AskCALEA website.

APPENDIX B - GLOSSARY1

___________________

1 This Glossary is provided herein solely for the assistance of the reader.

Actual Capacity - defined in 47 U.S.C. § 1003(a)(1) as a notice of the actual number of communications interceptions, pen registers, and trap and trace devices, representing a portion of the maximum capacity, that the Attorney General estimates that government agencies authorized to conduct electronic surveillance may conduct and use simultaneously by a certain date.

Basic Trading Area (BTA) - a PCS service area defined by the FCC as a collection of counties, based on the Rand McNally 1992 Commercial Atlas & Marketing Guide.

Broadband Personal Communications Services (PCS) - radio communications operating within the 2 GHz; band of the electromagnetic spectrum (from 1850 to 1990 MHz), which encompass mobile and ancillary fixed communication services, including a family of communications devices utilizing very small, lightweight, multifunction portable phones, portable facsimile and other imaging devices, new types of multifunction cordless phones, and advanced devices with two-way data capabilities.

Call Content - the "contents" of a communication is defined by 18 U.S.C. § 2510(8) as "any information concerning the substance, purport, or meaning of that communication." The phrase "call content" used in this Guide refers to the contents of lawfully intercepted communications.

Call-identifying Information - defined in 47 U.S.C. §1001(2) to mean "dialing or signaling information that identifies the origin, direction, destination, or termination of each communication generated or received by a subscriber by means of any equipment, facility, or service of a telecommunications carTier."

Cellular Service - a mobile radiotelephone service in which common carriers are authorized to offer and provide a mobile telecommunications service for hire to the general public using cellular systems. A cellular radio system is an automated, high-capacity system of one or more multichannel base stations designed to provide radio telecommunications services to mobile stations.

CLLI Code - Common Language Location Identifier or equivalent identifier for carrier equipment.

Commercial Availability - ithe date on which a manufacturer of telecommunications equipment makes software available.

Electronic Communication - defined in 18 U.S.C. §2510(12), in substance, to include any transfer of signs, signals, writing, images, sounds, data, or intelligence of any nature transmitted in whole or in part by a wire, radio, electromagnetic, photoelectronic, or a photooptical system.

Electronic Surveillance - for purposes of this Guide, the word "electronic surveillance" is used to refer to either the interception of call content and/or acquisition of call-identifying information. The telecommunications service targeted for electronic surveillance includes all of the services and features associated with the subject's facilities, equipment and services, as specified in a court order or lawful authorization.

Interception - defined in 18 U.S.C. § 2510(4) as the acquisition of the contents of a communication through the use of a device. See Electronic Surveillance above.

J-STD-025 - industry interim technical standard developed to meet the assistance capability requirements of Section 103 of CALEA published in December 1997.

Local Exchange Carrier - any person or entity that is engaged in the provision of telephone exchange service or exchange access. Such term does not include persons or entities engaged in the provision of a commercial mobile service.

Local Loop - the physical connection between a service provider's end office equipment, most often a switch, and a telephone subscriber's home or office.

Major Trading Area (MTA) - a PCS service area defined by the FCC as a collection of BTAs, based on the Rand McNally 1992 Commercial Atlas & Marketing Guide.

Maximum Capacity - defined in 47 U.S.C. § 1003(a)(1)(B) as the maximum capacity required to accommodate all of the communication interceptions, pen registers, and trap and trace devices that the Attorney General estimates that government agencies authorized to conduct electronic surveillance may conduct and use simultaneously by a certain date.

Metropolitan Statistical Area (MSA) - a geographic area based on counties, as defined by the U.S. Census Bureau, th contain cities with populations of 50,000 or more.

Normal Generic Upgrade Cycle - carrier-specific timeliDe of past- and future-planned software generic deployments.

Notice of Capacity - the notice required by 47 U.S.C. § 1003(a) of the estimated actual and maximum number of simultaneous call content interceptions, pen registers, and trap and traces that law enforcement may conduct at some future date.

Packet Mode Communications - defined in the FCC's Third Report and Order as "a communication where individual packets or virtual circuits of a cor-imunication within a physical circuit are switched or routed by the accessing telecommunication system. Each packet may take a different route through the intervening network(s)" (Third Report and Order, 16).

Pen Register - see generally 18 U.S.C. § 3121, et seq. Pursuant to these provisions, a law enforcement agency can be authorized to acquire certain outgoing dialing and signaling inforrnation.

Rural Service Area (RSA) - a geographic area not included within either an MSA or a New England Country Metropolitan Area for which a common carrier may have a license to provide cellular service.

Title III -- the provisionof the Omnibus Crime Control and Safe Streets Act of 1968 (Pub. L. No. 90-351, 82 Stat. 212) that, among other things, governs the conduct of lawful interceptions.

Telecommunications Carrier - defined in 47 U.S.C. § 1001(8), in pertinent part, as a person or entity engaged in the transmission or switching of wire or electronic communications as a common carrier for hire; or a person or entity engaged in providing commercial mobile service (See also 47 U.S.C. § 332(d)).

Trap and Trace Device -- see generally 18 U.S.C. § 3121, et seq. Pursuant to these provisions a law enforc be authorized to acquire certain information identifying originating numbers.

Wire Communication - defined in 18 U.S.C. § 25 1 0(l), in substance, to mean any transfer involving the human voice made in whole or in part through the use of wire, cable, or other like transmission facilities. The term includes communications via cellular telephones.

[Note: Templates are available in Excel at: http://www.askcalea.net/template2.xls ]

APPENDIX C - SAMPLE FLEXIBLE DEPLOYMENT ASSISTANCE GUIDE TEMPLATE


APPENDIX D - FLEXIBLE DEPLOYMENT ASSISTANCE GUIDE TEMPLATE



CALEA Implementation Section
Attention: Flexible Deployment Assistance Guide
Second Edition - Packet-Mode Communications
14800 Conference Center Drive, Suite 300
Chantilly, Virginia 20151-0450


Source: http://www.askcalea.net/pdf/da011902.pdf

Federal Communications Commission                   DA 01-1902

Before the
Federal Communications Commission
Washington, DC 20554

In the Matter of

The Communications Assistance For
Law Enforcement Act (CALEA),
Section 107(c) Extension of Capability               
Requirements

)
)
)
)
)
)
CC Docket No. 97-213
NSD-L-00-234

ORDER

Adopted: August 14, 2001                                                         Released: August 15, 2001

By the Common Carrier Bureau:

1. The wireline telecommunications carriers listed in the attached Appendix are among more than one thousand carriers that have filed petitions with the Federal Communications Commission (Commission or FCC) seeking extensions of the deadline for complying with the capability requirements of section 103 of the Communications Assistance for Law Enforcement Act (CALEA),1 as provided in section 107(c) of CALEA.2 In discharging the Commission’s statutory obligation to consult with the Attorney General,3 we have consulted fully with the Federal Bureau of Investigation (FBI) with regard to each petition. As explained below, we find that compliance with the assistance capability requirements under section 103 is not reasonably achievable by the telecommunications carriers listed in the attached Appendix through application of technology available within the compliance period. Accordingly, pursuant to our authority under section 107(c) of CALEA, we grant the petitions for extension listed in the attached Appendix to the extent described herein.

____________________

1 47 U.S.C. § 1002.

2 Id. § 1006(c). Pursuant to section 107(c)(1) of CALEA, telecommunications carriers may seek extensions of the deadline for complying with the capability requirements of section 103.

3 Id. § 1006(c)(2).

2. CALEA, enacted on October 25, 1994, was intended to preserve the ability of law enforcement officials to conduct electronic surveillance effectively and efficiently in the face of rapid advances in telecommunications technology. To achieve this goal, section 103 of CALEA sets forth four general assistance capability requirements with which carriers must comply.4 Pursuant to section 107(c)(1) of CALEA, telecommunications carriers may petition the Commission for an extension of the compliance deadline.5 Before taking final action in granting a carrier’s petition for extension pursuant to section 107(c), the Commission must consult with the Attorney General.6 An extension may be granted if the Commission determines that “compliance with the assistance capability requirements under section 103 is not reasonably achievable through application of technology available within the compliance period.”7 In granting the petition, the Commission can extend the compliance deadline no longer than two years from the date of grant.8

____________________

4 Id. § 1002(a).

5 Id. § 1006(c)(1).

6 Id. § 1006(c)(2).

7 Id.

8 Id. § 1006(c)(3).

3. The Commission previously has set forth procedures for the operating Bureaus to follow in considering section 107(c) petitions for extension.9 The Commission required that all section 107(c) petitions must contain certain basic information, including the identity of the carrier’s switching equipment (by manufacturer; type, make and model; software version or generic currently operating; Common Language Location Identification (CLLI) Code and geographic areas served; and the date or dates that the equipment will become compliant with section 103, to the extent such information is available to the carrier) and a brief statement or showing as to why the extension is necessary.10 In Public Notices dated November 20, 2000, February 22, 2001, May 31, 2001, and June 22, 2001, the Common Carrier Bureau (Bureau) found that more than one thousand wireline petitioners had satisfied the requirements set forth in the April 2000 Public Notice for a preliminary determination that their circumstances warranted an extension of the deadline for complying with CALEA section 103 until September 30, 2001, unless earlier revoked by the Commission or superseded by a final determination on the underlying extension request.11 In this Order, we take final action regarding the section 107(c)petitions filed by the carriers listed in the attached Appendix.

____________________

9 See CALEA Section 103 Compliance and Section 107(c) Petitions, Public Notice 15 FCC Rcd 7482 (2000), as modified by Public Notice 15 FCC Rcd 9518 (2000)(hereinafter the April 2000 and June 2000 Public Notices), available at http://www.fcc.gov/ccb/nsd/documents/CALEA2001.HTML.

10 April 2000 Public Notice.

11 See Public Notice 15 FCC Rcd 22308 (2000); Public Notice 16 FCC Rcd 4649 (2001); Public Notice DA 01-1316 (rel. May 31, 2001); and Public Notice DA 01-1494 (rel. June 22, 2001)(hereinafter the November 2000, February 2001, May 2001, and June 2001 Public Notices), available at http://www.fcc.gov/ccb/nsd/documents/CALEA2001.HTML.

4. In January 2000, the FBI established a Flexible Deployment Program to assist telecommunications carriers in meeting certain requirements of CALEA. In its Flexible Deployment Assistance Guide, the FBI requested that carriers voluntarily submit to it certain information and explained under what circumstances, based on a review of that information, the FBI might support a carrier’s petition for extension filed with the FCC. As the Commission has previously indicated, under certain circumstances, a carrier’s participation in the FBI’s Flexible Deployment Program enables the FCC to satisfy its statutory obligation to consult with the Attorney General, and assists the FCC both in determining whether an extension of the compliance deadline is warranted and the length of any extension.12 Under the Program’s procedures, the FBI independently reviews each carrier’s extension request in light of the CALEA priorities of law enforcement agencies, among other things. If, after reviewing the information submitted, the carrier and the FBI are able to arrive at a mutually agreeable CALEA deployment schedule, the FBI issues a letter (FBI support letter) stating whether the FBI supports an extension request and, if so, the length of such extension. Each carrier listed in the attached Appendix participated in the FBI’s Flexible Deployment Program and received a letter of support from the FBI.

____________________

12 47 U.S.C. § 1006(c)(2); See April 2000 Public Notice.

5. After reviewing the record of each petition and consulting fully with the FBI, we determine that compliance with the assistance capability requirements under section 103 is not reasonably achievable through application of technology available within the compliance period for the petitioners listed in the attached Appendix. Accordingly we find that these petitioners have satisfied the statutory requirements for an extension of the CALEA compliance deadline. We therefore grant the wireline petitioners listed in the attached Appendix extensions of the deadline for complying with CALEA section 103 until the dates agreed to by the FBI, as set forth in each carrier’s individual FBI support letter. If a carrier has questions regarding the exact date(s) of its individual extension grant, it should contact the FBI’s Flexible Deployment Program Manager, CALEA Implementation Section at (800) 551-0336 or (703) 814-4700. As the Bureau continues to consult with the FBI, the Bureau will release further orders resolving the remaining petitions filed by wireline carriers requesting extensions.

6. Accordingly, IT IS ORDERED that, pursuant to sections 4(i) and 4(j) of the Communications Act of 1934, as amended, 47 U.S.C. §§ 154(i) and 154(j), and sections 107(c) of the Communications Assistance for Law Enforcement Act, 47 U.S.C. § 1006(c), the carriers listed in the Appendix attached to this Order are HEREBY GRANTED AN EXTENSION of the compliance date of the assistance capability requirements of section 103 of CALEA, 47 U.S.C. §1002(a)(1)-(4), until the dates agreed to by the FBI as set forth in each carrier's individual FBI support letter.

FEDERAL COMMUNICATIONS COMMISSION

Jeffrey J. Carlisle
Senior Deputy Chief
Common Carrier Bureau

Appendix

Carriers Granted Extensions of the Deadline
for Complying with CALEA Section 103

[22 pages listing of carriers omitted.]


Transcription and HTML by Cryptome.