Department of Defense
High Performance Computing Modernization Program

A Federal Acquisition Regulation (FAR) amendment (parts 7, 11, 12, and 39) for Internet Protocol version 6 (IPv6) acquisitions can be found here . As of July, 2010, all United States (US) Federal government organizations can only make Internet Protocol technology acquisitions that are known to meet the requirements contained in the National Institute of Standards and Technology (NIST) Special Publication 500-267 US Government (USG) version 6 (USGv6) Profile Node Requirements Table in section 8 (i.e., using the USGv6 Capabilities Check List) and whose vendors have documented their product’s support of those IPv6 capabilities, through USGv6 Test programs (i.e., using the USGv6 Suppliers Declaration of Conformity). (Note: Additional information about the USGv6 Profile and USGv6 Test program can be found here. Scroll down to the bottom of that web page and click on the line

Additional Technical Details                               +

and then scroll down to "USGv6 Program" for additional information. NIST previously provided a "Buyer's Guide" to USGv6 to help simplify the purchase of IPv6 products for US Government consumption.)

Note: NIST is in the midst of revising the USGv6 Program documents. To see the draft documents, go here and scroll down that web page to:

DRAFT3 of USGv6 Revision 1 Specifications Available for Public Comment

Detailed technical IPv6 Profiles for Department of Defense (DoD), other USG organizations, and some European organizations are identified in the IPv6 Standards and RFCs article in the General Information section.

Recommended Acquisition Best Practices based on the above FAR, Memorandum M-05-22 below, and technical IPv6 profiles are available here.

The Internet Engineering Task Force (IETF) in Jan 2019 issued Request for Comments (RFC) 8504 defining common functionality required in all routers and other network devices that support IPv6. In April 2012 the IETF issued RFC 6540 requiring that all new products must support IPv6 and updates to existing products should support IPv6. That RFC further requires that IPv6 support must be equivalent or better in quality and functionality when compared to IPv4 support.

Additional guidance for the Federal organization audience is provided in the Administrator, Office of E-Government and Information Technology, Memorandum M-05-22 of August 2, 2005 , and reads as follows: “An IPv6 compliant product or system must be able to receive, process, and transmit or forward (as appropriate) IPv6 packets and should interoperate with other systems and protocols in both IPv4 and IPv6 modes of operation. Specifically, any new IP product or system developed, acquired, or produced must:

  • Interoperate with both IPv6 and IPv4 systems and products,
  • If not initially compliant, provide a migration path and commitment to upgrade to IPv6 for all application and product features by June 2008, and
  • Have available contractor/vendor IPv6 technical support for development and implementation and fielded product management.”

The Federal IPv6 Task Force website provides sample waivers for various Federal organizations in the Procurement Templates and Best Practices section Acquisitions IPv6 Compliance Resources subsection under Agency CIO Waivers. See this IPv6 Points of Contact article in the General Information section for the address of the Federal IPv6 Task Force website.

The DoD IPv6 Transition Office (which was disestablished in July 2011) provided this summary of policy, guidance, and sample contract clauses in Oct 2010. Examples of suggested warranty clauses and guidance for DoD Services/Agencies seeking a waiver for acquisitions of non-IPv6 capable items are included.

Other sample contract clauses and contracting guidance are contained in:

  1. This Statement of Work (SOW) template suitable for Federal Agencies wishing to purchase services to deploy IPv6 under the Connections II contract administered by the US General Services Administration (GSA). (Note: The scope of this SOW is limited to deployment of IPv6 on a network that is currently IPv4-only or partially dual-stacked.) This template includes evaluation criteria, offeror instructions, past performance form, a sample work breakdown structure, a sample project management plan template, pricing language and template, a deliverables chart, and a sample warranty spreadsheet. GSA offers other IPv6-compliant equipment, applications, transition support and integrated solutions contracts here. GSA has also provided answers to Networx IPv6 Frequently Asked Questions

    (Note: The GSA is in the midst of an Enterprise Infrastructure Solutions (EIS) acquisition. The Networx contract (and others) are transitioning to EIS. See this web page describing the multi-year transition.)

  2. The ATTACHMENT found at the end of the Department of Energy Acquisition Letter Al-2010-06, May, 2010,
  3. Section 6-5b of the Army Regulation 25-1 Army Knowledge Management and Information Technology, 25 June 2013,
  4. Section 2-6 and 4-6 of the Army Regulations 25-13 Army Telecommunications and Unified Capabilities, 11 May 2017,
  5. This Department of Veterans Affairs Memorandum contains guidance summarizing IPv6 procurement policies and a sample waiver, 
  6. The National Aeronautics and Space Administration (NASA) FAR Supplement (NFS) PN16-10 to revise NASA IPv6 acquisition procedures,
  7. This Performance Work Statement, July 2011, for the Defense Research and Engineering Network (DREN) III (DoD PKI Required).
  8. This DREN4 draft Performance Work Statement (PWS) on the DREN4 Draft RFP Documents page (scroll down to Government Files, go to page 2 of the list of Government Files, and click on DREN4-PWS-DRAFT2-20190809 or later), and 
  9. This excerpt from a Dec 2016 Army Contract W52P1J-17-D-0006:
    The Contractor shall warrant that each item delivered under the Contract shall accurately transmit, receive, process, and function correctly using the Internet Protocol Version 6 (IPv6). Specifically, the Contractor warrants that:
    a. each item delivered complies with the current DISR developed IPv6 standards profile;
    b. each item delivered maintains interoperability with IPv4 (specifically, shall operate on/coexist on a network supporting IPv4 only, IPv6 only, or a hybrid of IPv4 and IPv6); and
    c. each item delivered is supported by the Contractors IPv6 technical support.
    Additionally, as IPv6 evolves, the Contractor shall upgrade or provide an appropriate migration path for each item delivered. The duration of this warranty and the remedies available to the Government for breach of this warranty shall be as defined in, and subject to, the terms and limitations of the Contractors standard commercial warranty or warranties contained in this Contract, provided that notwithstanding any provision(s) to the contrary in such commercial warranty or warranties, the remedies available to the Government under this warranty shall include repair or replacement of any product whose non-compliance is discovered and made known to the Contractor no later than one year after acceptance. Nothing in this warranty shall be construed to limit any rights or remedies the Government shall otherwise have under this Contract with respect to defects other than IPv6 performance.