Derived From: Potential Impacts on Communications from IPv4 Exhaustion & IPv6 Transition Robert Cannon, OSP, December 2010 Paper: Word | Acrobat |
In 2005, the Office of Management and Budget mandated that federal agencies initiate the transition to IPv6. 10 According to the CIO Council:
[T]he Office of Management Budget issued Memorandum M-05-22, "Transition Planning for Internet Protocol Version 6 (IPv6)", establishing the goal of enabling all Federal government agency network backbones to support the next generation of the Internet Protocol Version 6 (IPv6) by June 30, 2008. The memorandum require[d] the agency's network backbone to be ready to transmit both IPv4 and IPv6 traffic, and support IPv4 and IPv6 addresses, by June 30, 2008. . . . The requirements for June 30, 2008 [were] for the network backbone (core) only. IPv6 [did] not actually have to be operationally enabled (i.e. turned on) by June 30, 2008. However, network backbones must [have been] ready to pass IPv6 traffic and support IPv6 addresses. Applications, peripherals, and other IT assets which are not leveraged in the execution of the functions mentioned above are not required for the June 30, 2008 deadline. 20
Moving the government's information technology from "ready" to "operational" will require additional work. On September 28, 2010, at a Department of Commerce IPv6 Workshop, OMB released a further memo Transition to IPv6 setting forth additional deadlines for the federal IPv6 transition:
In order to facilitate timely and effective IPv6 adoption, agencies shall:
• Upgrade public/external facing servers and services (e.g. web, email, DNS, ISP services, etc) to operationally use native IPv6 by the end of FY 2012;
• Upgrade internal client applications that communicate with public Internet servers and supporting enterprise networks to operationally use native IPv6 by the end of FY 2014 .
30
In 2005, OMB created an IPv6 Advisory Group 40 and tasked the CIO Council 50 with publishing transition planning guidance. 60 The CIO Council established an Interagency IPv6 Working Group, headed by Peter Tseronis, Senior Advisor, US Department of Energy. 70
OMB also directed the National Institute of Standards and Technology (NIST) to develop standards and testing necessary to support adoption of IPv6 by US Government agencies. The NIST project is known as USGv6. 80 NIST has developed a technical standards profile for US Government acquisition of IPv6 hosts and routers, and a specification for network protection devices. 90 NIST is also actively establishing a testing program in order to test the compliance of products and vendors with the profile. 100The Government Services Administration updated the Federal Acquisition Regulation (FAR) to reflect the IPv6 specifications, 110 and is assisting agencies with IPv6 procurement needs. 120
10 Karen S. Evans, Administrator, Office of E-Government and Information Technology, Transition Planning for Internet Protocol Version 6 (IPv6), M-05-22 (August 2, 2005).
20 IPv6 Transition Guidance, Federal CIO Council Architecture and Infrastructure Committee, CIO Council, p. 1 & 3 (Feb. 2006) ("As of July 2008, all major agencies met the June 30, 2008 deadline for successfully demonstrating their adoption of IPv6 technology."). See also Carolyn Duffy Marsan, Feds: We are ready for IPv6 D-Day, Network World (Jun. 26, 2008).
30 Vivek Kundra, Transition to IPv6, Memorandum for Chief Information Officers and Executive Departments and Agencies, Executive Office of the President, Office of Management and Budget (Sept. 28, 2010).
40 IPv6 Transition Guidance, Federal CIO Council Architecture and Infrastructure Committee, CIO Council, p. 25 (Feb. 2006).
50 "The Chief Information Officers (CIO) Council was established by Executive Order 13011, Federal Information Technology, on July 16, 1996, now revoked. The CIO Council's existence was codified into law by Congress in the E-Government Act of 2002. The CIO Council serves as the principal interagency forum for improving practices in the design, modernization, use, sharing, and performance of Federal Government agency information resources. The Council's role includes developing recommendations for information technology management policies, procedures, and standards; identifying opportunities to share information resources; and assessing and addressing the needs of the Federal Government's IT workforce. The Chair of the CIO Council is the Deputy Director for Management for the Office of Management and Budget (OMB) and the Vice Chair is elected by the CIO Council from its membership." Federal Chief Information Officers Council, About Us (visited Jan. 25, 2010).
60 IPv6 Transition Guidance, Federal CIO Council Architecture and Infrastructure Committee, CIO Council, p. 3 (Feb. 2006).
70 IPv6 Transition Guidance, Federal CIO Council Architecture and Infrastructure Committee, CIO Council, p. 23 (Feb. 2006).
90 A Profile for IPv6 in the US Government - Version 1.0, Recommendations of NIST, NIST SP500-267 (July 2008).
100 USGv6 Testing Program, Advanced Network Technologies Division, NIST. NIST's USGv6 documentation is a good resource for other networks embarked on the IPv6 transition.
110 Federal Acquisition Regulation; FAR Case 2005-041, Internet Protocol Version 6 (IPv6), Final Rule, 74 Fed. Reg. 65605 (Dec. 10, 2009) (" The Civilian Agency Acquisition Council and the Defense Acquisition Regulations Council (Councils) are issuing a final rule amending the Federal Acquisition Regulation (FAR) to require Internet Protocol Version 6 (IPv6) compliant products be included in all new information technology (IT) acquisitions using Internet Protocol (IP)". ).
"OMB is responsible for oversight of the government-wide transition to IPv6. OMB will assess agency progress and compliance with Memorandum 05-22 through the FEA PMO quarterly enterprise architecture review process. As required, OMB will report to Congress on the Federal government's progress with IPv6 transition. As needed, OMB will establish government-wide policy for IPv6 implementation, including consultations with General Services Administration (GSA) to implement Federal government IPv6 acquisition policy. OMB will also engage the support of an IPv6 Advisory Group throughout the transition process to inform and assist in execution of IPv6-related management and oversight activities." CIO Council IPv6 Transition Guidance Sec. 5.2.1
"On August 2, 2005, the OMB Office of E-Gov and IT issued OMB Memorandum 05-22, "Transition Planning for Internet Protocol Version 6 (IPv6)," directing all Federal government agencies to transition their network backbones to the next generation of the Internet Protocol Version 6 (IPv6), by June 30, 2008. The memorandum identifies several key milestones and requirements for all Federal government agencies in support of the June 30, 2008 target date. . . .
The CIO Council will issue guidance to assist agencies with transition planning." White House Information Policy.
In order to facilitate timely and effective IPv6 adoption, agencies shall:
Upgrade public/external facing servers and services (e.g. web, email, DNS, ISP services, etc) to operationally use native IPv6 by the end of FY 2012;
Upgrade internal client applications that communicate with public Internet servers and supporting enterprise networks to operationally use native IPv6 by the end of FY 2014;
Designate an IPv6 Transition Manager and submit their name, title, and contact information to IPv6@omb.eop.gov by October 30, 2010. The IPv6 Transition Manager is to serve as the person responsible for leading the agency's IPv6 transition activities, and liaison with the wider Federal IPv6 effort as necessary; and,
Ensure agency procurements of networked IT comply with FAR requirements for use of the USGv6 Profile and Test Program for the completeness and quality of their IPv6 capabilities
All agency infrastructures (network backbones) must be using IPv62 and agency networks must interface with this infrastructure. Agencies will include progress reports on meeting this target date as part of their EA transition strategy.
To avoid unnecessary costs in the future, you should, to the maximum extent practicable, ensure that all new IT procurements are IPv6 compliant.
OMB: Improving Agency Performance Using Information and Information Technology (Enterprise Architecture Assessment Framework v3.1), June 2009
News
Joab Jackson, Is the OMB IPv6 mandate faltering , GCN (Dec. 18, 2007) (" Managers from AT&T, Global Crossing, NTT America, Qwest, and Verizon all indicate that they have few customers looking into IPv6 options beyond what is required by the OMB mandate ")
An IPv6 Advisory Group has been established and is comprised of selected subject matter experts and other Federal government resources. This group will serve as an IPv6 advisory group to OMB leadership throughout the transition, and will provide information on current market trends and transition best practices related to IPv6. The IPv6 Advisory Group consists of subject matter experts and will be expanded as needed to ensure appropriate representation of the following functions:
IPv4/IPv6 transition
Cybersecurity and personal privacy
Technology standards
Acquisition and procurement
IP address acquisition and management
Network management and testing
The IPv6 Advisory Group is assisting OMB with execution of IPv6 oversight activities, including (but not limited to) development of IPv6 guidance, coordination and documentation of common processes and procedures related to IPv6 transition, communication with agencies, and facilitation of public forums. CIO Council IPv6 Transition Guidance Sec. 5.2.2
Derived From: Potential Impacts on Communications from IPv4 Exhaustion & IPv6 Transition Robert Cannon, OSP, December 2010 Paper: Word | Acrobat |
In 2004, the Department of Commerce (the National Telecommunications and Information Administration (NTIA) and the National Institute of Standards and Technology (NIST)) initiated an investigation into the US Government's policy response to IPv6. This culminated with the release of the 2006 Report Technical and Economic Assessment of Internet Protocol, Version 6 (IPv6) . In the Report, the Department of Commerce stated:
Industry stakeholders and Internet experts generally agree that IPv6-based networks would be technically superior to the common installed base of IPv4-based networks. The vastly increased IP address space available under IPv6 could potentially stimulate a plethora of new innovative communications services. Deployment of IPv6 would, at a minimum, "future proof" the Internet against potential address shortages resulting from the emergence of new services or applications that require large quantities of globally routable Internet addresses.
Current market trends suggest that demand for unique IP addresses could expand considerably in future years. The growing use of the Internet will likely increase pressures on existing IPv4 address resources, as more and more people around the globe seek IP addresses to enjoy the benefits of Internet access. In addition, the potential development of new classes of networked applications (e.g., widely available networked computing in the home, the office, and industrial devices for monitoring, control, and repair) could result in rapid increases in demand for global IP addresses.
Over time, IPv6 could become (as compared to IPv4) a more useful, more flexible mechanism for providing user communications on an end-to-end basis. The redesigned header structure in IPv6 and the enhanced capabilities of the new protocol could also simplify the configuration, and operation of certain networks and services. These enhancements could produce operations and management cost savings for network administrators. In addition, auto-configuration and other features of IPv6 could make it easier to connect computers to the Internet and simplify network access for mobile Internet users. 1a
Addressing the appropriate role for the government in promoting the transition, the Department of Commerce at that time concluded,
The Task Force finds that no substantial market barriers appear to exist that would prevent industry from investing in IPv6 products and services as its needs require or as consumers demand. The Task Force, therefore, believes that aggressive government action to accelerate deployment of IPv6 by the private sector is not warranted at this time. The Task Force believes that, in the near term, private sector organizations should undertake a careful analysis of their business cases for IPv6 adoption and plan for the inevitable emergence of IPv6 traffic on both internal and external networks. 2a
In 2010, the Department of Commerce announced that grantees for the Comprehensive Community Infrastructure Awards, which are part of the NTIA Broadband Technology Opportunity Program (BTOP) stimulus grants, must report on "Internet protocol address utilization and IPv6 implementation." Recipients are required to file quarterly reports until the end of their funding. 3a
On September 28, 2010, NTIA convened an IPv6 Workshop, during which Assistant Secretary of Commerce for Communications and Information Lawrence Strickling stated,
[F]or industry in particular - smart-phone and router manufactures, transport providers, Internet service providers, and chief information and technology officers throughout the industry - action is needed. Today we want to impress upon everyone that this is an urgent issue, but one that can be successfully handled with good planning. And we want to encourage companies to share best practices on IPv6 uptake for all businesses to benefit, particularly for small- and medium-sized enterprises. 4a
The NTIA event, which was moderated by US CTO Aneesh Chopra and US CIO Vivek Kundra, highlighted the importance of industry and government working together, sharing information and best practices that could facilitate the transition. 5a At the event, the CIO Council released its new memo with the new deadlines for the federal IPv6 transition. 6a
1a Technical and Economic Assessment of Internet Protocol, Version 6 (IPv6), IPv6 Task Force, Department of Commerce, Executive Summary (Jan. 2006).
2a Technical and Economic Assessment of Internet Protocol, Version 6 (IPv6), IPv6 Task Force, Department of Commerce, Executive Summary (Jan. 2006).
3a Notice of Funds Availability (NOFA) and Solicitation of Applications, Broadband Technology Opportunities Program, National Telecommunications and Information Administration, US Department of Commerce, 75 Fed. Reg. 3792 (Jan. 22, 2010). See comments of kc claffy, National Broadband Plan Proceeding, Docket 09-51 (filed Jan. 27, 2010) (commenting on the need for good data to research networks).
5a Agenda, Internet Protocol Version 6 (IPv6) Workshop: The Impact of the Adoption and Deployment of IPv6 Addresses for Industry, the US Government, and the Internet Economy, US Department of Commerce, National Telecommunications and Information Administration, September 28, 2010.
6a Vivek Kundra, Transition to IPv6, Memorandum for Chief Information Officers and Executive Departments and Agencies, Executive Office of the President, Office of Management and Budget (Sept. 28, 2010).
Technical and Economic Assessment of Internet Protocol, Version 6 (IPv6) : The U. S. Department of Commerce has released the final report on the technical and economic issues related to IPv6 adoption in the United States, including the appropriate role of government, international interoperability, security in transition, and costs and benefits of IPv6 deployment. The report was developed by the IPv6 Task Force, with the involvement of the NTIA and the National Institute of Standards and Technology, and with the assistance of consultant RTI International (RTI.) IPv6 Final Report [ -- HTML -- Acrobat PDF -- ] Posted 2-17-2006
This report by the Department of Commerce's IPv6 Task Force examines the technical and economic issues related to IPv6 adoption in the United States, including the appropriate role of government, international interoperability, security in transition, and costs and benefits of IPv6 deployment. In developing this report, the Task Force, with the assistance of a consultant, RTI International (RTI), has gathered information from a wide range of stakeholders through a request for comment published in January 2004, a public meeting held on IPv6 issues in July 2004, and numerous contacts with public and private-sector stakeholders.
The public record compiled by the Task Force suggests that although IPv6 has the potential to produce significant benefits for U.S. businesses and consumers over time, the near-term benefits are less clear. Available evidence suggests, for example, that in the initial years of IPv6 deployment, network security will likely be no greater under the new protocol than is currently available in IPv4 networks. Additional evidence suggests that premature adoption of IPv6 (i.e., that which precedes adequate technical and business case planning) could result in unnecessary costs and reduced information technology (IT) security.
. . . . .
Potential Roles of Government
The Task Force finds that no substantial market barriers appear to exist that would prevent industry from investing in IPv6 products and services as its needs require or as consumers demand. The Task Force, therefore, believes that aggressive government action to accelerate deployment of IPv6 by the private sector is not warranted at this time. (emphasis added) The Task Force believes that, in the near term, private sector organizations should undertake a careful analysis of their business cases for IPv6 adoption and plan for the inevitable emergence of IPv6 traffic on both internal and external networks.
With respect to public sector information systems, the Task Force recommends that government agencies initiate near-term activities to analyze their own business cases for IPv6 and to develop appropriate security plans for the inevitable emergence of IPv6 on both internal and external networks. This need for expedited planning and analysis in federal IT systems has also been identified in a recent report by the General Accountability Office and emerging policy guidance from the Office of Management and Budget. Each of these recommendations emphasizes that careful planning, development, and evaluation should precede any agency-specific decision to deploy new IPv6 technologies in operational networks. The results of this study indicate that significant technical and economic risks can be associated with failure to adequately plan for and appropriately schedule IPv6 adoption.
Looking longer term, the Task Force notes that the federal government will need to consider allocation of new resources and to work cooperatively with non-federal authorities and the private sector to address outstanding IPv6 research and development issues, and to expedite the development of suitable deployment, coexistence, and transition plans.
"To help facilitate the address space acquisition process, NTIA, within the Department of Commerce, will assist OMB in its role as the central point of coordination in advising agencies requiring guidance as they proceed with identifying their IPv6 requirements. NTIA will also facilitate and assist agencies, as necessary, as they interface with ARIN. (For information on acquiring IPv6 addresses, refer to Section 4.1.2 of this document.)
NTIA will provide guidance in a manner which reinforces Federal government cyber-security policy and best practices. NTIA will also maintain representation on the IPv6 Advisory Board."
- CIO Council IPv6 Transition Guidance Sec. 5.2.6.2
IPv6 Forum, NTIA 7/20/2004 "comments may be submitted electronically to the following electronic mail address: IPv6@ntia.doc.gov." See notice for further procedural info.
Transition Planning for Internet Protocol Version 6 (IPv6) (August 2, 2005) ("The National Institute for Standards and Technology (NIST) will develop, as necessary, a standard to address IPv6 compliance for the Federal government.")
"As the Federal government technical standards-making body, NIST will work with OMB and the IPv6 Working Group to evaluate the need for common standards and technical guidance.
NIST will work with stakeholders to ensure any standards/guidance developed is in alignment with existing industry standards and is in the best interest of the Federal government. Furthermore, NIST will provide the IPv6 Advisory Group and OMB with additional guidance as necessary and maintain representation on the IPv6 Advisory Board."
- CIO Council IPv6 Transition Guidance Sec. 5.2.6.1
Special Publication 800-119 , Guidelines for the Secure Deployment of IPv6 This document is intended to help with the deployment of the next generation Internet Protocol, IPv6. It describes and analyzes IPv6's new and expanded protocols, services, and capabilities, including addressing, DNS, routing, mobility, quality of service, multihoming, and IPsec. For each component, there is a detailed analysis of the differences between IPv4 and IPv6, the security ramifications and any unknown aspects. It characterizes new security threats posed by the transition to IPv6 and provides guidelines on IPv6 deployment, including transition, integration, configuration, and testing. It also addresses more recent significant changes in the approach to IPv6 transition. Dec. 28, 2010
Feb. 22, 2010 SP 800-119 DRAFT Guidelines for the Secure Deployment of IPv6
NIST announces the public comment release of Special Publication (SP) 800-119, Guidelines for the Secure Deployment of IPv6 . IPv6 (Internet Protocol version 6) is the next generation Internet Protocol, accommodating vastly increased address space. This document describes and analyzes IPv6's new and expanded protocols, services, and capabilities, including addressing, DNS, routing, mobility, quality of service, multihoming, and IPsec. For each component, there is a detailed analysis of the differences between IPv4 and IPv6, the security ramifications and any unknown aspects. It characterizes new security threats posed by the transition to IPv6 and provides guidelines on IPv6 deployment, including transition, integration, configuration, and testing. It also addresses more recent significant changes in the approach to IPv6 transition. NIST requests comments on Draft SP 800-119 by April 23, 2010. Please submit comments to draft-sp800-119-comments@nist.gov with "Comments SP 800-119" in the subject line. draft-sp800-119_feb2010.pdf (2.3 MB)
Notice : NIST has released a second draft of a proposed standards profile to support the implementation of Internet Protocol Version 6 (IPv6) by government agencies. NIST developed the "profile" to help ensure that IPv6-enabled federal information systems are interoperable, secure and able to co-exist with the current IPv4 systems. An initial draft of the NIST profile was released for comment one year ago (see "NIST Issues Draft IPv6 Technical Profile" ). The second draft of A Profile for IPv6 in the U.S. Government - Version 1.0 develops a long-term strategy for 2010 and beyond. It incorporates the feedback from meetings with industry and government groups and input including more than 500 comments. The profile recommends technical standards for common network devices, such as hosts, routers, firewalls and intrusion detection systems. It also outlines the compliance and testing programs that NIST will be establishing to ensure that IPv6-enabled federal information systems are interoperable and secure, and that they work with existing IPv4 systems. NIST is calling for comments on the draft report by Feb. 29. For more information on the profile and to contribute comments, go to www.antd.nist.gov/usgv6 .
D-Link Video
Department of Defense
Derived From: Potential Impacts on Communications from IPv4 Exhaustion & IPv6 Transition Robert Cannon, OSP, December 2010 Paper: Word | Acrobat |
The Department of Defense (DOD), with its network-centric operations, has high network address demands and therefore places a priority on the expanded address space. In 2003, it was the first government branch to announce an IPv6 transition policy, 1 declaring that:
The achievement of net-centric operations and warfare, envisioned as the Global Information Grid (GIG) of inter-networked sensors, platforms and other Information Technology/National Security System (IT/NSS) capabilities (ref a), depends on effective implementation of IPv6 in concert with other aspects of the GIG architecture. 2
The DOD set 2008 as the deadline by which it should complete its IPv6 transition. DOD's transition to IPv6 has been described as "aggressive" and DOD has operational plans that would require a high demand on a network address space. DOD is reported to have received a substantial IPv6 address allocation. 3
--
1 The DOD oversaw the network protocol transition from NCP-to-IPv4.
2 DOD Memo for Secretaries of the Military Departments, From Dept of Defense Chief Information Officer, Subj: Internet Protocol version 6 (IPv6) (June 9, 2003).
3 The US Department of Defense has 42 Million Billion Billion Billion IPv6 Addresses, Royal Pingdom (Mar. 26 th , 2009) (DOD "has a /13 IPv6 block (the smaller the number, the larger the block). No one else in the world is even close to that. The next-largest block after that is a /19 block (which is already huge). In other words the DoD owns a block 64 times larger than anyone else's."); Captain RV Ros Dixon, IPv6 in the Department of Defense, Defense Information Systems Agency.
"This memorandum provides DoD policy for Enterprise-wide deployment of IPv6. Currently, Internet Protocol version 4 (IPv4) represents the mandated internetworking protocol for the DoD. The achievement of net-centric operations and warfare, envisioned as the Global Information Grid (GIG) of inter-networked sensors, platforms and other Information Technology/National Security System (IT/NSS) capabilities (ref a), depends on effective implementation of IPv6 in concert with other aspects of the GIG architecture. . . . The DoD goal is to complete the transition to IPv6 for all inter and intro networking across the DoD by FY 2008."
Defense IT Standards Registry (DISR) Profiles
News
William Jackson, DOD IPv6 Transition Deadline Not Written in Stone, GCN (May 24, 2005) ("
The transition was mandated in 2003 to help enable the department's goal of network-centric warfare. This requires more data sharing for situational awareness in the field. This, in turn, requires intelligent pulling of data rather than centralized pushing.
")
D.S. Onley, “Defense picks consultant for IPv6 transition,” Government Computer News, at 5 (May 24, 2004).
Roswell Dixon, “IPv6 in the Department of Defense,” at 9, Presentation at the North American IPv6 Task Force Summit, San Diego, CA, (June 25, 2003)
"Transitioning to IPv6 is a pervasive and significant challenge for federal
agencies that could result in significant benefits to agency services. But
such benefits may not be realized if action is not taken to ensure that
agencies are addressing key planning considerations or security issues.
Accordingly, we are recommending, among other things, that the Director
of the Office of Management and Budget (OMB) instruct the federal
agencies to begin addressing key IPv6 planning considerations, and that
federal agency heads take immediate actions to address the near-term
security risks."
Federal Acquisition Regulation; FAR Case 2005-041, Internet Protocol Version 6 (IPv6), Final Rule, 74 Fed. Reg. 65605 (Dec. 10, 2009) ("The Civilian Agency Acquisition Council and the Defense Acquisition Regulations Council (Councils) are issuing a final rule amending the Federal Acquisition Regulation (FAR) to require Internet Protocol Version 6 (IPv6) compliant products be included in all new information technology (IT) acquisitions using Internet Protocol (IP)". ).
The profile defines terms USGv6-v1-Capable and USGv6-v1-Complaint
The FAR Clause does not require USG to use USGv6 Profile
"GSA will update the Federal Acquisition Regulation (FAR), as deemed necessary by the FAR Council, for the acquisition of IPv6-capable assets and services. The FAR will reference the acquisition requirements. GSA will also assist OMB, as necessary, with developing an acquisition strategy to support the network backbone transition.
The Core.gov portal (www.core.gov) will be used as the primary Federal government site for interagency IPv6 collaboration and information sharing. GSA will initiate the IPv6 information sharing site on Core.gov, for use by the IPv6 Working Group and other individuals involved in the transition. GSA will be responsible for ensuring individuals have proper instructions for registering and using the site, and will facilitate a Core.gov training session for all agency IPv6 leads. The Core.gov team will respond to agency inquiries about the site. GSA will also ensure this site has the appropriate level of security and access control. GSA and the Core.gov team will work with the IPv6 Working Group throughout this process.
Additionally, GSA will maintain representation on the IPv6 Advisory Board and provide support for cross-agency initiatives related to IPv6 throughout the transition period." - CIO Council IPv6 Transition Guidance Sec. 5.2.6.3
"Internet Protocol version 6 (IPv6) is being considered and deployed throughout the U.S. Government and private industry. The Information Assurance Directorate, Systems and Network Analysis Center (SNAC) of NSA is providing general guidance to make the implementation of IPv6 more secure."
FCC Working Paper #3:
Potential Impacts on Communications from IPv4 Exhaustion & IPv6 Transition
Robert Cannon, OSP, December 2010
Paper: Word | Acrobat | News Release: Word | Acrobat
Sept 28, 2010