4/12/2021

FCC INFORMATION TECHNOLOGY (IT) INTERNET PROTOCOL VERSION 6 (IPV6) Procurement Checklist Record of Approval

UNITED STATES

FEDERAL COMMUNICATIONS COMMISSION 

INFORMATION TECHNOLOGY

FCC INFORMATION TECHNOLOGY (IT) 

INTERNET PROTOCOL VERSION 6 (IPV6) 

PROCUREMENT CHECKLIST

OFFICE OF THE MANAGING DIRECTOR

45 L Street NE, Washington, DC 20554
 

 

 

 

 

 

Information 

Technology 

FCC INFORMATION TECHNOLOGY (IT) INTERNET PROTOCOL VERSION 6 (IPV6) Procurement Checklist Record of Approval

Record of Approval 

Document Approval

<Document POC>

Printed Name: Arecio Dilone (ACIO-D&P)

Signature:

Arecio Dilone Digitally signed by Arecio Dilone 

Date: 2021.04.21 11:48:22 

-04'00' 

Date:

4/21/2021

<Approval Structure>

Printed Name: Mark Stephens (Managing Director) 

Signature:

Mark Stephens Digitally signed by Mark 

Stephens

Date: 2021.04.22 15:43:52 -04'00' 

Date

Printed Name: Francisco Salguero (CIO)

Signature: Digitally signed by FRANCISCO SALGUERO 

DN: c=US, o=U.S. Government, ou=Federal 

Communications Commission, cn=FRANCISCO 

SALGUERO, 

0.9.2342.19200300.100.1.1=27001000021809 

Date: 2021.04.22 12:11:52 -04'00' 

Adobe Acrobat Reader version: 2021.001.20149 

Date:

Printed Name: Jennifer Bilbrey (DCIO-M/L)

Signature:

Kevin Baker Digitally signed by Kevin Baker 

DN: cn=Kevin Baker, o, ou,

email=kevin.baker@fcc.gov, c=US FOR: Date: 2021.04.21 12:09:00 -04'00' 

Date:

4/21/2021 

Printed Name: Andrea Simpson (CISO)

Signature: ANDREA 

SIMPSON 

Digitally signed by ANDREA SIMPSON 

DN: c=US, o=U.S. Government, ou=Federal

Communications Commission, cn=ANDREA 

SIMPSON, 

0.9.2342.19200300.100.1.1=27001002878969

Date: 2021.04.21 13:15:49 -04'00' 

Date:

Printed Name: Shaun Costello (DCIO-T/R)

Signature:

Shaun Costello Digitally signed by Shaun 

Costello

Date: 2021.04.22 11:49:59 -04'00' 

Date:

Printed Name: Erik Scheibert (Enterprise Architect)

Signature: Date:

04/21/2021
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FCC INFORMATION TECHNOLOGY (IT) INTERNET PROTOCOL VERSION 6 (IPV6) Procurement Checklist

Information 

Technology 

Federal Communications Commission 

Office of Chief Information Officer 

_________________________________________________Choose an item. 

Product/Program/Project/Service Title 

_______________OMD – Information Technology_______________ 

4/6/2021 

IPv6 Procurement Checklist

TOPIC DESCRIPTION

1. STRATEGIC LINKAGE Choose an item.

2. FUNCTIONAL RESPONSIBILITY ALIGNING

WITH RESPECTIVE STRATEGIC LINKAGE IN 

TOPIC 1

Choose an item.

. 

3. ENTERPRISE ARCHITECTURE The technology design has been vetted through the FCC Information 

Technology (IT) department to ensure compliance and usability with

current and future IT infrastructure including dual stack (IPv4 over IPv6).

Yes □ No □

4. COMPLIANCE Ensure compliance with Federal direction, including, but not limited to, the

FAR 11.002(g) and OMB Memorandum M-21-07.

Are the products and services that use IP provide full feature functionality

in both dual stack (IPv4 and IPv6) and IPv6-only environments in 

compliance with the NIST USGv6 Testing Program?

Yes □ No □

5. REQUESTOR RESEARCH Conduct research when evaluating IPv6 readiness. Yes □ No □

6. SUPPLIER DECLARATION OF CONFORMITY

(SDoC)

A vendor, when responding to a request for an IT service or product using

IP, must complete and return a signed Supplier’s Declaration of Conformity 

(SDoC) to requestor. Did the vendor provide the SDoC?

Yes □ No □

7. ACQUISITION WAIVERS A requestor in a B/O seeking a waiver to procure an IT product or service

that does not meet the IPv6 compliance requirements in FAR 11.002(g) and

on the FCC IPv6 policy must submit a signed request via memorandum

from his/her B/O Chief to the Deputy CIO for Technology and Resiliency.

Will the requester be submitting a request for waiver?

Yes □ No □

8. RISKS Are there any risks that management should be considering?

Yes □ No □

If including risks, please provide explanation using the IF/THEN format:

9. TECHNICAL POINT OF CONTACT (TPOC)

INFORMATION

Please use this space to provide the TPOC’s contact information 

4/12/2021
 

 

 

 

 

Information 

Technology 

FCC INFORMATION TECHNOLOGY (IT) INTERNET PROTOCOL VERSION 6 (IPV6) Procurement Checklist

EXPLANATIONS OF IPV6 PROCUREMENT CHECKLIST TOPICS: 

Strategic Linkage – The planned procurement shall align with the FCC’s Strategic Plan (current version 2018-

2022). Select the appropriate choice from the dropdown menu. 

Functional Responsibility Aligning with Respective Strategic Linkage – The planned procurement shall 

align with FCC IT’s strategic goals relative to the FCC Strategic Plan. Select the appropriate choice from the 

dropdown menu. 

Enterprise Architecture – FCC IT urges requestors to contact the Enterprise Architecture Group to verify 

planned procurements will be compatible with existing IPv6 and/orIPv4 assets. 

Compliance – Unless the agency Chief Information Officer waives the requirement, when acquiring 

information technology using Internet Protocol, the requirements documents must include reference to the 

appropriate technical capabilities defined in the USGv6 Profile (NIST Special Publication 500-267) and the 

corresponding declarations of conformance defined in the USGv6 Test Program. The applicability of IPv6 to 

agency networks, infrastructure, and applications specific to individual acquisitions will be in accordance with 

the agency's Enterprise Architecture and OMB Memorandum M-21-07. 

Requestor Research – FCC IT urges requestors to conduct vendor research into the planned asset’s IPv6 

capability; if necessary, research should include alternatives in case the original asset is not capable. 

Supplier Declaration of Conformity (SDoC) – The SDoC is a document which declares that a product, 

process, or service conforms to a standard or technical regulation. The supplier provides written assurance of 

conformity to the specified requirements. This is also sometimes called Self Declaration of Conformity. 

Acquisition Waivers – A waiver request memorandum shall include language indicating the reason(s) for 

which: 

1) The requiring of IPv6-capability would be an undue burden on an acquisition, and 

2) The requested non-compliant system/service/asset is needed. 

The waiver request shall also include the vendor documentation detailing timelines to incorporate IPv6 

capability into the respective product. FCC IT will issue waivers case-by-case only. 

Risks – The requestor may insert risks into the field, provide links to the respective project risk register (e.g. via 

Teams or SharePoint), or may attach in a separate document. 

4/12/2021
 

 

Information 

Technology 

FCC INFORMATION TECHNOLOGY (IT) INTERNET PROTOCOL VERSION 6 (IPV6) Procurement Checklist

Technical Point of Contact (TPOC) Information – Along with the TPOC’s contact information, please 

include any additional information or necessary context that has not been captured in previous sections. 

4/12/2021