Advisory Committee of U.S. Attorneys

The Attorney General's Advisory Committee of United States Attorneys (AGAC), is a committee of the United States Department of Justice.

History

The creation of the committee was first announced in 1973 by Attorney General Elliot Richardson. Attorney General Edward H. Levi defined its function formally by order dated February 13, 1976, setting its responsibilities forth in 28 C.F.R. 0.10.

Composition

"The Committee consists of 17 United States Attorneys selected by the Attorney General. They are intended to represent office size, judicial district, issues and diversity. Service on the Committee normally shall not exceed three years. New members are appointed each year to provide for broad representation of United States Attorneys nationwide. The Attorney General selects a chairperson and vice-chairperson. The Committee establishes such subcommittees as it deems necessary to carry out its functions."[1]

Function

"The Advisory Committee has two functions. It gives United States Attorneys a voice in Department policies and advises the Attorney General of the United States.

In advising the Attorney General, the Committee conducts studies and makes recommendations to improve management of United States Attorney operations and the relationship between the Department and the federal prosecutors. It also helps formulate new programs for improvement of the criminal justice system and the delivery of legal services at all levels.

In serving the United States Attorneys, the Committee coordinates the collective efforts of the United States Attorneys with the divisions and agencies of the Department of Justice, and departments and agencies external to the Department of Justice. It also represents the United States Attorneys with the Department of Justice, other departments and agencies of the government, and occasionally private organizations."[1]

Interpretation

"The Advisory Committee plays a vital role in furthering the Department's law enforcement efforts and gives U.S. Attorneys a key voice in Department policy. Together in partnership with state, local and federal authorities, the Advisory Committee is crucial in advancing the Department's efforts to battle terrorism and prosecute corporate fraud, as well as continue its law enforcement mission in areas such as civil rights, violent crime, and immigration".[2]

Attorney General Eric Holder's Original Advisory Committee

Attorney General Eric Holder appointed his original Advisory Committee in October 2009.[3] Minnesota U.S. Attorney B. Todd Jones was selected to chair the Committee, replacing Northern Illinois U.S. Attorney Patrick Fitzgerald, who remained on the Committee.[3] He also appointed U.S. Attorneys Preet Bharara (Southern District of New York), Dennis Burke (District of Arizona), Jenny Durkan (Western District of Washington), Paul Fishman (District of New Jersey), Neil McBride (Eastern District of Virginia), Peter Nehrona (District of Rhode Island), and Joyce White Vance (Northern District of Alabama), as well as Channing Phillips (Acting U.S. Attorney for the District of Columbia) and John Davis (Criminal Chief, Eastern District of Virginia).[3]

Current Membership

As of January 2017, AGAC membership consists of:

gollark: You should, if you care, probably at least run it through an obufscator for .NET.
gollark: > 5. .net platform is cracker / hacker friendly Any program running on the client can INEVITABLY be reverse-engineered. Do not rely on it not experiencing that, because you will fail.
gollark: > 4. XAML - the incredibly messy UI technologyPerhaps, but this is not a *language* thing.
gollark: > 3. Garbage collector and memory leak detection tools?Again, not sure if anyone actually runs into this sort of issue in practice.
gollark: > 1. Performance penalties.> [some rambling about C++].NET is generally pretty much *fast enough*. If your application somehow hits performance bottlenecks, rewrite the slow bits in native code, don't just immediately take a development speed hit.> 2. Need to interoperate with C++ / Native (Windows) API’sI don't know how often you actually need to bind to a native API not wrapped by .NET or a third-party library, but you can do it, it's just annoying - but probably less than using C++ for everything!

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.