Marine Corps Internet Protocol Version 6 (IPv6) Transition Planning

1. PURPOSE. PROVIDE AMPLIFYING GUIDANCE TO IPV6
TRANSITION TASKS GIVEN IN REF A. ESTABLISH A REPORT DATE OF 14 DAYS
FROM THE RELEASE OF THIS MARADMIN FOR TRANSITION SURVEY COMPLETION.
2. BACKGROUND. THE DEPARTMENT OF DEFENSE CHIEF INFORMATION OFFICER
HAS ESTABLISHED THE GOAL OF TRANSITIONING TO THE USE OF IPV6 BY
2008. THE IMPLEMENTATION OF IPV6 IS NECESSARY TO RESOLVE CURRENT
LIMITATIONS THAT MAKE IPV4 INCAPABLE OF ADEQUATELY SUPPORTING AN
EVOLUTION TO TRANSFORMATIONAL NETWORK CAPABILITIES. THE USE OF IPV6
WILL POTENTIALLY IMPACT THE OPERATION OF ALL SOFTWARE AND HARDWARE
WITHIN THE MARINE CORPS ENTERPRISE NETWORK (MCEN). 
3. FAILURE TO CORRECTLY IDENTIFY AND IMPLEMENT PROPER RE-ENGINEERING
FOR AFFECTED SYSTEMS AND APPLICATIONS, PRIOR TO MARINE CORPS IPV6
TRANSITION, WILL RESULT IN INCIDENTS OF SERVICE LOSS OR SOME SERVICE
DEGRADATION. TO PREVENT THIS, IT IS NECESARY TO CONDUCT AN
ENGINEERING ASSESSMENT OF EVERY MARINE CORPS PROGRAM OF RECORD AND
NON-PROGRAM OF RECORD ACQUISITION. THIS ASSESSMENT WILL DETERMINE
EACH SYSTEM/APPLICATION'S USE OR NON-USE OF INTERNET PROTOCOLS AND
ANY POTENTIAL TRANSITION COMPLICATIONS. ALL SYSTEMS, APPLICATIONS
AND PERIHERALS, TO INCLUDE THOSE PROCURED BY THE LOCAL COMMANDS MUST
BE INCLUDED IN THIS ASSESSMENT. SURVEY FORMS AND A TECHNICAL GUIDE
ARE PROVIDED IN REF B. REF B IS AVAILABLE ON THE HQMC C4 WEBSITE AT
<http:slash slash hqdod.hqmc.usmc.mil c4 ipv6.asp>. 
4. ACTION 
A. ALL PROGRAM MANAGERS, SOFTWARE FUNCTIONAL AREA MANAGERS, AND
NETWORK MANAGERS ARE DIRECTED TO COMPLETE SURVEYS FOR SYSTEMS,
HARDWARE, AND SOFTWARE THEY ACQUIRE OR ARE RESPONSIBLE FOR. SURVEYS
WILL IDENTIFY COST ASSOCIATED WITH BUILDING IPV6 CAPABILITY AND THE
TIMEFRAME FOR ACCOMPLISHING IPV6 TRANSITION. FOR JOINT ACQUISITIONS
AND PROCUREMENTS, REPORT ONLY ON SYSTEMS AND APPLICATIONS THAT ARE
MARINE CORPS OWNED OR FOR WHICH THE MARINE CORPS IS THE LEAD
SERVICE. SOFTWARE FUNCTIONAL AREA MANAGERS ARE DESIGNATED IN REF D. 
SURVEY RESPONSES ARE DUE TO HQMC C4 WITHIN 14 DAYS OF THE RELEASE OF
THIS MARADMIN. 
B. PER REF A, ALL CURRENT INFORMATION TECHNOLOGY (IT) PROCUREMENTS
MUST BE IPV6 CAPABLE AND WAIVERS MUST BE OBTAINED FOR ALL SYSTEMS
AND APPLICATIONS THAT CANNOT OR WILL NOT SUPPORT THE USE OF IPV6
PROTOCOL BY 30 SEP 2007. THE MARINE CORPS IT PROCUREMENTS PROCESS
MANAGED BY MARINE CORPS CIO IS DESCRIBED IN REF C AND INCORPORATES
THE IPV6 REQUIREMENT IN ITS CHECKLIST. IPV6 PROCUREMENT WAIVER FORMS
ARE PROVIDED ON THE PROCUREMENT WEBSITE AT <https:slash slash
ITPROCUREMENT.HQMC.USMC.MIL/>. COMMANDERS AND COMMAND
REPRESENTATIVES RESPONSIBLE FOR LOCAL IT PROCUREMENTS MUST
INCORPORATE THE SAME INFORMATION IN A FORM AND ROUTE AN ELECTRONIC
VERSION OF THAT FORM TO MARINE CORPS CIO FOR APPROVAL.
5. QUESTIONS CONCERNING THIS MESSAGE SHOULD BE DIRECTED TO HQMC C4
POCS LISTED ABOVE.