MARINE CORPS INTERNET PROTOCOL VERSION 6 (IPV6) POLICY
Date Signed: 1/23/2004 | MARADMINS Number: 032/04
MARADMINS : 032/04

R 232330Z JAN 04
FM CMC WASHINGTON DC(uc)
TO AL MARADMIN(uc)
MARADMIN
BT
UNCLASSIFIED
MARADMIN 032/04
MSGID/GENADMIN/CMC WASHINGTON DC C4//
SUBJ/MARINE CORPS INTERNET PROTOCOL VERSION 6 (IPV6) POLICY//
REF/A/DOC/ASD NII-DOD CIO 09JUN03/-/NOTAL//
REF/B/DOC/ASD NII-DOD CIO 29 SEP 2003/-/NOTAL//
NARR/REF A IS ASD NII MEMORANDUM ESTABLISHING DOD POLICY FOR
TRANSITION TO INTERNET PROTOCOL VERSION 6 (IPV6). REF B IS DOD CIO
MEMORANDUM PROVIDING INTERIM IPV6 TRANSITION GUIDANCE.//
POC/RODDY STATEN/LTCOL/HQMC C4 CP/-/TEL:(703) 693-3490
/TEL:DSN 223-3490/EMAIL:STATENR@HQMC.USMC.MIL//
POC/DAVE WALLACE/CAPT/HQMC C4 CP/-/TEL:(703) 693-3491
/TEL:DSN 223-3491/EMAIL:WALLACEDT@HQMC.USMC.MIL//
GENTEXT/REMARKS/1. SITUATION. REF A DIRECTS A DEPARTMENT OF DEFENSE
(DOD) TRANSITION TO IPV6, BY FY 2008, IN ORDER TO ACHIEVE
NET-CENTRIC OPERATIONS AND WARFARE GOALS. PER REF A AND B, AS OF
OCTOBER 1, 2003, ALL MARINE CORPS INFORMATION TECHNOLOGY DEVELOPED,
ACQUIRED, OR PROCURED WILL BE IPV6 CAPABLE AS DEFINED IN REF B AND
THE JOINT TECHNICAL ARCHITECTURE (JTA) STANDARDS PROFILE FOUND ON
THE JTA WEB PAGE AT HTTP://JTA.DISA.MIL/IPV6/INDEX-PUBLIC.HTML.
2. MISSION. TO ENSURE THAT MARINE CORPS INFORMATION TECHNOLOGY
DEVELOPED, ACQUIRED, OR PROCURED IS IPV6 CAPABLE AS DEFINED IN REF
B, MARINE CORPS OFFICIALS RESPONSIBLE FOR INFORMATION TECHNOLOGY
DEVELOPMENT, ACQUISITION, AND PROCUREMENT DECISIONS WILL REVIEW THE
REFERENCES AND INSTITUTE PROCEDURES TO ENSURE CONFORMITY WITH THE
DIRECTED GUIDANCE.
3. EXECUTION.
A. CONCEPT OF OPERATIONS. ALL MARINE CORPS OFFICIALS RESPONSIBLE FOR
INFORMATION TECHNOLOGY DEVELOPMENT, ACQUISITION, AND PROCUREMENT
DECISIONS WILL ESTABLISH AND/OR MODIFY PURCHASING PROCEDURES AND
CONTRACT APPROVAL TO ENSURE COMPLIANCE WITH THE IPV6 CAPABLE
DEFINITION AND JTA STANDARDS PROFILE SPECIFIED IN THE REFERENCES.
REF A AND REF B ARE AVAILABLE ON THE HQMC C4 WEBSITE AT
HTTP:(SLASH_SLASH) HQINET001.HQMC.USMC.MIL/C4/DEFAULT.ASP.
B. TASKS.
(1) DIR C4/MARINE CORPS CHIEF INFORMATION OFFICER (CIO).
(A) MODIFY THE CURRENT INFORMATION TECHNOLOGY WAIVER PROCESS TO
INCLUDE PROCEDURES THAT ENSURE PRODUCTS PURCHASED WILL BE IPV6
CAPABLE IN ACCORDANCE WITH THE GUIDANCE SPECIFIED IN REF A AND B.
THE IPV6 CAPABLE DEFINITION LANGUAGE WILL BE ADDED TO THE CIO
CERTIFICATION CHECKLIST.
(B) DEVELOP AN IPV6 WAIVER PROCESS WHEREBY IPV6 CAPABILITY
REQUIREMENTS CAN BE WAIVED.
(C) ASSESS THE IPV6 CAPABILITY OF APPLICATIONS ON THE BASELINE AND
GENERATE A PLAN FOR TRANSITIONING APPLICATIONS TO SUPPORT IPV6.
(2) PROGRAM MANAGERS AND ACQUISITION PROFESSIONALS.
(A) VIA EMAIL, IDENTIFY ACTION OFFICERS RESPONSIBLE FOR PROVIDING
MARINE CORPS IPV6 TRANSITION PLAN INPUT AND COORDINATING PLANNING
ACTIVITY WITHIN THEIR COMMANDS. SEND ORGANIZATION, NAME, PHONE, AND
EMAIL ADDRESS TO THE HQMC C4 POC LISTED ABOVE.
(B) ASSESS IMPACT OF TRANSITIONING TO IPV6 FOR EACH PROGRAM.
GENERATE AN IPV6 TRANSITION PLAN FOR EACH PROGRAM THAT IDENTIFIES
HOW TECHNOLOGY REFRESH WILL SUPPORT IPV6 CAPABILITY, COST ASSOCIATED
WITH BUILDING IPV6 CAPABILITY, AND TIMEFRAME FOR ACCOMPLISHING IPV6
TRANSITION.
(C) ESTABLISH A PROCESS BY WHICH MARINE CORPS PROCURES IPV6 CAPABLE
PRODUCTS.
(3) COMMANDERS AND COMPTROLLERS WILL INSTITUTE APPROPRIATE PURCHASE
AND BUDGET APPROVAL PROCEDURES TO ENSURE COMPLIANCE WITH THE IPV6
DEFINITIONS AND JTA STANDARDS PROFILE PROCEDURES AS DESCRIBED IN REF
A AND B. IN ADDITION THEY WILL ENSURE THAT LOCAL PURCHASING
PROCEDURES SCREEN FOR COMPLIANCE WITH THE IPV6 COMPATIBILITY.
(4) CONTRACTING OFFICERS AND PURCHASING OFFICIALS ARE DIRECTED TO
SCREEN INFORMATION TECHNOLOGY PRODUCTS AND SERVICES FOR IPV6 CAPABLE
COMPLIANCE PRIOR TO SIGNING CONTRACTS OR APPROVING PURCHASES.
C. COORDINATING INSTRUCTIONS. HEADQUARTERS MARINE CORPS C4 WILL
ORGANIZE A WORKING GROUP COMPRISING SUBJECT MATTER EXPERTS TO
IDENTIFY AFFECTED MARINE CORPS PROGRAMS AND EXECUTE SPECIFIC TASKS
NECESSARY TO TRANSITION TO IPV6.
4. ADMINISTRATION AND LOGISTICS. HEADQUARTERS MARINE CORPS C4 WILL
LEAD DEVELOPMENT OF A MARINE CORPS IPV6 TRANSITION PLAN TO BE
RELEASED BY 30 APRIL 2004. THE MARINE CORPS TRANSITION PLAN OUTLINE
IS AS FOLLOWS:
A. INTRODUCTION
(1) OVERVIEW
(2) IPV6 DRIVERS
(3) MARINE CORPS IPV6 TRANSITION PLAN APPROACH
(4) STRUCTURE OF MARINE CORPS IPV6 TRANSITION PLAN
B. IPV6 TRANSITION GOVERNANCE
(1) POLICIES
(2) MARINE CORPS TRANSITION MANAGEMENT STRUCTURE
(3) ROLES AND RESPONSIBILITIES
C. ACQUISITION AND PROCUREMENT OF IPV6 CAPABILITIES
(1) ACQUISITION GUIDANCE
(2) COMPLIANCE WITH PROCUREMENT POLICY AND WAIVER PROCESS
(3) ROLES AND RESPONSIBILITIES
D. MARINE CORPS TRANSITION PLAN OF ACTION AND MILESTONES
(1) NETWORKING AND INFRASTRUCTURE
(2) ADDRESSING
(3) INFORMATION ASSURANCE
(4) IPV6 PILOTS
(5) APPLICATIONS
(6) LEGACY TRANSITION
(7) STANDARDS
E. PROGRAMS AND BUDGETS
(1) DOD FUNDING FOR IPV6 TRANSITION
(2) MARINE CORPS FUNDING PROFILE
(3) BUDGET EXECUTION
F. APPENDICES
(1) IPV6 IMPLEMENTATION TEMPLATE FOR SYSTEMS
(2) IPV6 IMPLEMENTATION TEMPLATE FOR APPLICATIONS
(3) LIST OF PROGRAMS
(4) APPLICATION BASELINE
5. COMMAND AND SIGNAL. QUESTIONS CONCERNING THIS MESSAGE SHOULD BE
DIRECTED TO HQMC C4 POCS LISTED ABOVE.//