Federal Information Processing Standards

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Federal Information Processing Standards (FIPS) are publicly announced standards developed by the United States federal government for use in computer systems by non-military government agencies and government contractors.[1]

FIPS standards are issued to establish requirements for various purposes such as ensuring computer security and interoperability, and are intended for cases in which suitable industry standards do not already exist.[1] Many FIPS specifications are modified versions of standards used in the technical communities, such as the American National Standards Institute (ANSI), the Institute of Electrical and Electronics Engineers (IEEE), and the International Organization for Standardization (ISO).

Specific areas of FIPS standardization

The U.S. government has developed various FIPS specifications to standardize a number of topics including:

  • Codes: for instance, standards for encoding data (such as FIPS county codes or codes to indicate weather conditions or emergency indications). In 1994 NOAA began broadcasting coded signals called FIPS codes along with their standard weather broadcasts from local stations. These codes identify the type of emergency and the specific geographic area, such as a county, affected by the emergency.
  • Encryption standards, such as the Data Encryption Standard (FIPS 46-3[2]) and the Advanced Encryption Standard (FIPS 197[3])

Data security standards

Some FIPS standards have related to the security of data processing systems.[4] Some of these included the use of key escrow systems.[5][6]

Withdrawal of geographic codes

Some examples of FIPS Codes for geographical areas include FIPS 10-4 for country codes or region codes and FIPS 5-2 for state codes. These codes were similar to or comparable with, but not the same as, ISO 3166, or the NUTS standard of the European Union. In 2002, the National Institute of Standards and Technology (NIST) withdrew several geographic FIPS code standards, including those for countries (FIPS 10-4), U.S. states (FIPS 5-2), and counties (FIPS 6-4).[7][8] These are to be replaced by ISO 3166 and INCITS standards 38 and 31, respectively.[9] Some of the codes maintain the previous numerical system, particularly for states.[10]

In 2008, NIST withdrew the FIPS 55-3 database.[7] This database included 5-digit numeric place codes for cities, towns, and villages, or other centers of population in the United States. The codes were assigned alphabetically to places within each state, and as a result changed frequently in order to maintain the alphabetical sorting. NIST replaced these codes with the more permanent GNIS Feature ID, maintained by the U.S. Board on Geographic Names. The GNIS database is the official geographic names repository database for the United States, and is designated the only source of geographic names and locative attributes for use by the agencies of the Federal Government.[11] FIPS 8-6 "Metropolitan Areas" and 9-1 "Congressional Districts of the U.S." were also withdrawn in 2008, to be replaced with INCITS standards 454 and 455, respectively.[9]

The U.S. Census Bureau used FIPS place codes database to identify legal and statistical entities for county subdivisions, places, and American Indian areas, Alaska Native areas, or Hawaiian home lands when they needed to present census data for these areas.[12] In response to the NIST decision, the Census Bureau is in the process of transitioning over to the GNIS Feature ID, which will be completed after the 2010 Census. Until then, previously issued FIPS place codes, renamed "Census Code," will continue to be used, with the Census bureau assigning new codes as needed for their internal use during the transition.[10][13]

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. FIPS 46-3
  3. FIPS 197
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.

External links