R 291715Z JUN 22
MARADMIN 333/22
MSGID/GENADMIN/CMC DCI IC4 WASHINGTON DC//
SUBJ/MARINE CORPS TRANSITION TO INTERNET PROTOCOL VERSION 6 (IPV6)//
REF/A/DOC/OFFICE OF MANAGEMENT AND BUDGET MEMO M21-07, 16NOV20//
REF/B/DOC/DOD DIRECTIVE TYPE MEMORANDUM (DTM) 21-004, 29JUN21//
REF/C/DOC/DOD IPV6 IMPLEMENTATION PLAN, 30 SEP 2021//
REF/D/DOC/STRATEGIC INTENT FOR MARINE CORPS TRANSITION TO IPV6, 28 APR 2022//
REF/E/DOC/IPV6 LIMITED DEPLOYMENT EXPANSION (LDE) TASKING MESSAGE, 291235Z APR 22//
REF/F/DOC/MFCC TASKORDER 22-042, INTERNET PROTOCOL VERSION SIX, 241931Z MAY 22//
REF/G/DOC/NIST SPECIAL PUBLICATION 500-267A REV 1, NIST IPV6 PROFILE, NOV 2020//
REF/H/DOC/NIST SPECIAL PUBLICATION 500-267B REV 1, USGV6 PROFILE, NOV 2020//
NARR/REF A IS OMB GUIDANCE FOR COMPLETING THE FEDERAL GOVERNMENT TRANSITION TO INTERNET PROTOCOL VERSION 6 (IPV6). REF B IS THE DOD DTM REITERATING OMB MANDATES FOR THE DOD AND ASSIGNING COMPONENTS ADDITIONAL POLICY RELATED TASKS. REF C IS THE DOD IPV6 IMPLEMENTATION PLAN PROVIDING ADDITIONAL GUIDANCE ON COMPLETING THE DOD TRANSITION TO IPV6. REF D IS THE MARINE CORPS STRATEGIC INTENT FOR TRANSITION TO IPV6 DURING FY 2023-2025. REF E IS THE DC I IC4 LIMITED DEPLOYMENT EXPANSION (LDE) TASKING MESSAGE TO MFCC. REF F IS THE MFCC TASK ORDER SUPPORTING COMPLETION OF THE IPV6 LDE NLT 30 SEP 2022. REF G IS THE NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST) IPV6 PROFILE OF TECHNICAL REQUIREMENTS FOR NETWORKED INFORMATION TECHNOLOGY (IT) PRODUCTS. REF H IS THE NIST US GOVERNMENT IPV6 PROFILE USED TO ASSIST AGENCIES IN THE DEVELOPMENT OF ACQUISITION REQUIREMENTS FOR IPV6 PRODUCTS AND THE MEANS TO ASSESS PRODUCT COMPLIANCE TO SUCH REQUIREMENTS.//
POC/PHILIP HOM/CIV/HQMC DC I-IC4-ICN/-/TEL: (571) 256-9068/TEL: DSN 312 260-9068/EMAIL: PHILIP.HOM@USMC.MIL//
POC/MIKE CIRILLO/CIV/MCSC/-/TEL:(703) 432-3134/TEL: DSN 312 378-3134/EMAIL: MICHAEL.R.CIRILLO@USMC.MIL//
POC/CWO3 JUSTIN COFFELT/MARFORCYBER G6/TEL: 667-812-9295/JECOFF3@NSA.GOV/JUSTIN.COFFELT@USMC.MIL//
POC/CWO4 SCOTT PHILLIPS/MARFORCYBER G6/TEL: 667-812-6106/SDPHIL2@NSA.GOV/SCOTT.D.PHILLIPS1@USMC.MIL//
GENTEXT/REMARKS/1. PURPOSE. This is a coordinated DC I IC4, MARFORCYBER, and MARCORSYSCOM message to communicate the near term actions required to plan for and execute Marine Corps transition to IPV6-only operations beginning in FY 2023.
2. situation.
2.a. Per refs a and b, the federal government and the DoD are engaged in deliberate efforts to transition information technology systems and infrastructure from IPV4 to IPV6. Implementing IPV6, when deployed properly, will provide the potential to improve end-to-end security, offer improved node mobility within fixed networks, enable near limitless scalability, enhance Quality of Service (QOS), and reduce system management requirements.
2.b. per ref b, IPV6 transition targets are established as at least 20 percent of IP-enabled assets on DoD networks are operating in IPV6-only environments by the end of FY 2023, at least 50 percent of IP-enabled assets on DoD networks are operating in IPV6-only environments by the end of FY 2024, at least 80 percent of IP-enabled assets on DoD networks are operating in IPV6-only environments by the end of FY 2025. Ref b further directs that any new networked information systems that utilize IP technologies must be IPV6 enabled by the end of FY23. Per ref c, dual stack is the authoritative IPV6 transition methodology for the DoD. At this time, the DoD has no plans to utilize/approve other transition methodologies such as tunneling. Translation methodologies such as NAT64/DNS64 have been approved for connectivity between IPV4-only and IPV6-only networks.
3. Mission. The Marine Corps will, to the maximum extent possible, transition to IPV6-only operations during FY23-25 consistent with the references.
4. Execution.
4.a. commanders intent and concept of operations.
4.a.1. Commander’s intent. The Marine Corps will implement IPV6 at all installations during FY23-25 in a manner that maximizes IPV6-only operations but sustain necessary IPV4 – based operations for an extended period until legacy systems can be sunset or converted to IPV6. Implementation plans and resource strategies will be informed by IPV6 Limited Deployment Expansion (LDE) pilot activities, and synchronized IPV4/IPV6 dual-stack implementation approved by HQMC DC I will be conducted at the direction of Marine Forces Cyber Command (MFCC).
4.a.2. Concept of operations.
4.a.2.a. End state. The end state is one in which the Marine Corps has achieved ref b objectives for IPV6-only operations across the Marine Corps Information Enterprise Environment (MCIEE), has identified the systems/technologies that cannot implement IPV6, and has developed a plan to resource the sunsetting/replacement of non-IPV6 compatible systems/technologies.
4.a.2.b. Implementation phases. Per ref c, Marine Corps IPV6 transition is anticipated to be conducted in three phases:
4.a.2.b.1. In phase 1, MFCC will initiate an IPV6-only Limited Deployment Expansion (LDE) pilot NLT 01 July 2022. The pilot will identify cost drivers and technical requirements for enterprise-wide implementation beginning in FY23.
4.a.2.b.2. In phase 2, transition to IPV6-only operations will take place at bases, posts and stations per an established deployment schedule managed by MFCC. IPV4/IPV6 dual stack operations will be the preferred transition method until legacy IPV4 systems can be upgraded or replaced. It is anticipated the hybrid dual stack state will persist for an extended period, based on available resources and mission requirements.
4.a.2.b.3. In phase 3, legacy IPV4 systems/addresses will be retired per an established and resourced plan.
4.a.2.c. Limited deployment expansion. The Marine Corps will leverage the DoD recommended Limited Deployment Expansion (LDE) methodology to establish initial and follow-on IPV6 implementation at installations throughout the enterprise. Per refs e and f MFCC will conduct LDE planning and execution during 3Q and 4Q, 2022. The MFCC LDE will identify IPV6 transition costs drivers and validate technical procedures and best practices supporting transition to IPV6-only operations, implementation of dual stack architectures, and IPV6 address management.
4.a.2.d. National Security Systems (NSS). NSS are exempted from complying with transition timelines directed by refs a and b. This exemption allows NSS system owners to schedule their transitions to IPV6 with minimal or zero operational impacts or external deadlines. The NSS that should temporarily remain on IPV4 protocol, but have requirements to communicate with IPV6-only enclaves, may implement and utilize translation protocols, such as, network address translation 6to4 and/or domain name service 6to4, (NAT64/DNS64), to maintain those communication channels.
4.a.2.e. Dual stack operations. Dual stack is the authoritative IPV6 transition methodology for the DoD. The DoD has no plans to use or approve other transition methodologies, such as tunneling. Translation methodologies such as NAT64/DNS64 are approved for connectivity between IPV4-only and IPV6-only networks.
4.a.2.f. Ip-based hardware/software procurements. Per ref b, it is DoD policy that all new networked DoD information systems that use Internet Protocol (IP) technologies will be IPV6-enabled before implementation and operational use by the end of Fiscal Year (FY) 2023.
4.a.2.f.1. The Marine Corps must ensure that technology developed, acquired, or procured is capable of IPV6 only functionality, as defined in refs a and b. Marine Corps officials responsible for technology development, acquisition, and procurement decisions must review the references and institute procedures to ensure conformity with the guidance. This effort includes the contracting and funding for the engineering, testing, and maintenance of the systems, applications, hardware, software, and processes built on or for use on that equipment.
4.a.2.g. Public facing services. All known public facing unrestricted services have been verified as IPV6 capable. When transition to IPV6 begins in FY 2023, these public facing services will remain dual stacked until connected external interfaces are fully migrated to an IPV6-only environment. This is to ensure that the operational capability does not impact services delivered to the end user.
4.a.2.h. Training. Initial coordination with TECOM for inclusion of IPV6 in relevant formal training course is ongoing, but inclusion in existing Marine Corps Communication-Electronics School (MCCES) courses won’t occur until FY 2023 or later. In the interim, IPV6 training resources are available at the following link:
https:(slash)(slash)DoD.teams.microsoft.us/_#/files/general?Threadid=19%3aDoD%3a98a6d2ebf09e449d927e3901de46b6cc%40thread.
Skype&ctx=channel&context=IPV6%2520training&rootfoLDEr=%252fsites%252fusmcIPV6%252fshared%2520documents
%252fgeneral%252FIPV6%2520training.
4.a.2.i. IPV6 address management. MFCC is service lead for development of a Marine Corps IPV6 address plan.
4.a.2.i.1. For all Non-Classified Internet Protocol Router Network (NIPRNET) assets that will communicate with the public/commodity internet, DoD components must request a /48 IPV6 address block from the DoD Network Information Center (NIC) for each base, camp, post or installation. The DoD IPV6 address plan can be found at https:(slash)(slash)www.nic.mil/webmenu/docfiles/DoD_IPV6_address_plan.pdf
4.a.2.i.2. DoD CIO, in coordination with the DoD NIC, is currently in the process of updating the DoD IPV6 address plan to clarify independent addressing and assignment block requirements.
4.a.2.i.3. All other closed networks within DoDIN, such as, the secret Internet Protocol Router Network (SIPRNET), Community of Interest (COI), or other mission critical environments that do not connect to the NIPRNET or public internet, should assess their current network and address plans to meet ref a and b requirements. IPV6 addresses for these closed networks should be coordinated with MFCC POCS listed in this message.
4.b. Tasks. In order to adequately plan for and resource Marine Corps IPV6 transition during the FY 2023 – 2025 timeframe, request key stakeholder actions as follows:
4.b.1. DC I IC4.
4.b.1.a. During 4Q, FY 2022, lead coordination efforts necessary to develop a Plan of Actions and Milestones (POAM) for the Marine Corps transition to IPV6 during FY 2023-2025.
4.b.1.b. Based on the POAM and the results of the MFCC LDE, and in conjunction with stakeholders, develop a Program Objective Memorandum (POM) 2025 initiative supporting completion of the IPV6 transition and sustainment of the IPV6 capability in the out years.
4.b.1.c. Develop and staff the USMC IPV6 implementation plan NLT 30 Sep 2022.
4.b.1.d. Coordinate with stakeholders to complete all tasks assigned to components in ref b.
4.b.1.e. Ensure agile-based planning increments account for potential IPV6 transition planning requirements during 4Q, FY 2022 and 1Q, FY 2023.
4.b.1.f. In coordination with Functional Area Managers (FAMS) and system owners, assess the IPV6 capability of warfighting and business system applications and generate a plan for transitioning applications to support IPV6.
4.b.1.g. Ensure that Authority to Operate (ATO) packages are updated with IPV6-enabled language and artifacts, and ensure the Authorizing Official (AO) has approved IPV6 activation in each enclave. ATO packages should be updated to specify IPV6 configuration for circuits and border gateway protocol peering. Ensure that all new ATO packages comport with refs G and h as appropriate.
4.b.2. DC, CD&I.
4.b.2.a. Support POAM and POM 2025 initiative development during 4Q, FY 2022.
4.b.2.b. Ensure agile-based planning increments account for potential IPV6 transition planning requirements during 4Q, FY 2022 and 1Q, FY 2023.
4.b.3. MCSC.
4.b.3.a. Support POAM and POM 2025 initiative development during 4Q, FY 2022.
4.b.3.b. Ensure agile-based planning increments account for potential IPV6 transition planning requirements during 4Q, FY 2022 and 1Q, FY 2023.
4.b.3.c. Assess impact of transitioning to IPV6 for each program and generate an IPV6 transition plan for each program that identifies how technology refresh will support IPV6 capability, the costs associated with transitioning to IPV6, and the anticipated timelines for accomplishing IPV6 transition in accordance with the references. Be prepared to brief the results of the readiness assessment during 4Q, FY 2022 POAM development.
4.b.3.d. Review established procurement processes to ensure procurement of IPV6 capable products leveraging the contracting and technical guidance required by the references.
4.b.3.e. During FY 2022, assess the MCSC portfolio for readiness to achieve IPV6 only end state. Assessment should include identification of systems ready to transition in the near term, systems requiring substantial engineering and funding in order to transition, and systems that must be attritted from the inventory due to IPV4 risks and costs related to duplicative IPV4/IPV6 operational and management burdens.
4.b.4. MCICOM.
4.b.4.a. Support POAM and POM 2025 initiative development during 4Q, FY 2022.
4.b.4.b. Ensure agile-based planning increments account for potential IPV6 transition planning requirements during 4Q, FY 2022 and 1Q, FY 2023.
4.b.4.c. Assess the feasibility of conducting an LDE beginning NLT 1Q, FY 2023. Assessment should include identification of an installation to conduct the LDE and be prepared to outline LDE efforts during 4Q, FY 2022 POAM development.
4.b.5. TECOM
4.b.5.a. Support POAM and POM 2025 initiative development during 4Q, FY 2022.
4.b.5.b. Ensure agile-based planning increments account for potential IPV6 transition planning requirements during 4Q, FY 2022 and 1Q, FY 2023.
4.b.5.c. Assess the feasibility of conducting an LDE beginning NLT 1Q, FY 2023. Assessment should include identification of an installation to conduct the LDE and be prepared to outline LDE efforts during 4Q, FY 2022 POAM development.
4.b.5.d. Assess IPV6-related training requirements and develop plans to update MCCES training curricula as required to support IPV6 transition and sustainment. Be prepared to outline the plan for revisions to curricula and associated costs during 4Q, FY 2022 POAM development.
4.b.6. MFCC.
4.b.6.a. Support POAM and POM 2025 initiative development during 4Q, FY 2022.
4.b.6.b. Ensure agile-based planning increments account for potential IPV6 planning requirements during 4Q, FY 2022 and 1Q, FY 2023.
4.b.6.c. Based on close coordination with DoD CIO, DISA, and Marine Corps activities to identify the scope of IPV6 address needs, develop the Marine Corps IPV6 address plan for approval by HQMC DC I and inclusion in the marine IPV6 implementation plan NLT 30 Sep 2022.
4.b.6.d. Based on LDE execution in accordance with refs e and f, provide IC4 with an itemized IPV6 transition playbook identifying the procedures, equipment, and technical, personnel and policy requirements necessary for successful site/installation transition to IPV6-only and concurrent dual-stack operations at Marine Corps installations. Be prepared to outline implications for enterprise wide IPV6 transition during the 4Q, FY2022 POAM development.
4.b.6.e. Assess available network tools for suitability to identify IPV6-compliant devices on the network, and be prepared to recommend solutions for remote query capability during POAM development in 4Q, 2022.
4.b.7. Acquisition authorities.
4.b.7.a. All commanders and comptrollers will institute appropriate purchase and budget approval procedures to ensure compliance with the IPV6 definitions, IPV6-related joint technical architecture (JTA) standards, and NIST IPV6 profile procedures as described in refs a, b, f and g.
4.b.7.b. Ensure that local purchasing procedures screen for compliance with IPV6 native (only) compatibility consistent with refs f and g.
4.b.7.c. Contracting officers and purchasing officials are directed to use defense information service agency (DISA) Approved product list (APL) for interoperability (IO) and Information Assurance (IA) certification prior to signing contracts or approving purchases.
5. Coordinating instructions.
5.a. All stakeholders are highly encouraged to review the DoD implementation plan (ref c). The DoD IPV6 implementation plan contains essential guidance for acquisition and security professionals and individual appendices describing specific actions necessary for successful IPV6 transition.
5.b. During 4Q, FY 2022, IC4 will establish a regular battle Rhythm for cross functional collaboration among stakeholders To complete tasks enumerated in ref b and identify additional Requirements related to successful IPV6 transition.
5.c. During 4Q, FY 2022, IC4 will coordinate cross functional Technical exchange with stakeholders for the development Of an IPV6 transition POAM and cost estimates. Details Provided in separate correspondence.
6. Administration and logistics.
6.a. Questions concerning this message should be directed to the HQMC DC I IC4 ICN POC listed above.
6.b. Information on USMC IPV6 transition planning can be found At the following teams link: https:(slash)(slash)DoD.teams.microsoft.us/l/team/19%3aDoD%3a98a6d2Ebf09e449d927e3901de46b6cc%40thread.skype/conversations?Groupid=d69b96b5-0fd5-49be-9572-b49b88f2fbc7&tenantid=F4c44cda-18c6-46b0-80f2-e290072444fd
7. Command and signal. Release authorized by BGen J. A. Matos, Director, Information C4 Division, Deputy Commandant for Information.//