1 / 11

JAG/CCM Update COPC Spring 2006

JAG/CCM Update COPC Spring 2006. Mr. Walter Coley JAG/CCM Chairman . Distribution Authorized to U.S. Government Agencies and their Contractors only. Overview. Action Items AFCCC Migration to NIPRNET Current Architecture Transition to Government Gateways Projection 2010+.

buzz
Download Presentation

JAG/CCM Update COPC Spring 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. JAG/CCM UpdateCOPCSpring 2006 Mr. Walter Coley JAG/CCM Chairman Distribution Authorized to U.S. Government Agencies and their Contractors only

  2. Overview • Action Items • AFCCC Migration to NIPRNET • Current Architecture • Transition to Government Gateways • Projection 2010+

  3. Action Item Update • Collaboration Efforts Still On Track • Completed Communications Portion Of WJIP • Bandwidth Adjustments Made To Meet Current Needs • Received Data Projections From JAG/ODAA • Fall Within Forecast Projections

  4. Action Item Update • Public Key Infrastructure/Enabling • Government IPv6 Transition Is On Track • DoD Ports and Protocols; FTP Port Closure • Large Scale Government Gateways Delayed ~2 years

  5. FNMOC/NMCIOperational Impacts • NMCI is in the process of trying to rehome all NAVY NIPRNET connections to NMCI gateways. • Due to the impact on FNMOC operational capabilities, a waiver is being requested to retain our direct connection into the NIPRNET. • If waiver is not granted, this could affect our current connectivity to DATMS-U and DREN because all three network connections are on the same external routers. This could jeopardize our DISA Security Accreditation.

  6. AFCCC Migration to NIPRNET • AFCCC Originally On 4 Mbps ATM Connection to AFWA • Not As Flexible As NIPRNet • 6 Mbps NIPRNet Connection Installed 03 Jun 05 • Required Infrastructure Changes • Formal Testing Completed 13 - 15 Feb 06 • Operations Moved To NIPRNet 16 Feb 06 • DATMS-U To AFCCC Will Be Discontinued 31 Sep 06 • NIPRNET expandable to~44Mb/sec

  7. Current ATM Architecture AFWA 44Mb total 6 Mb Asheville 6 Mb 14 Mb 22 Mb 22 Mb 14Mb NOAA/NWS Gateway 45 Mb total 6 Mb OC-3 FNMOC 26 Mb total NAVICE 6 Mb OC-3 6 Mb Fast-E 6 Mb 6 Mb NESDIS 6 Mb NWS Monterey Pass thru to NOAA NAVO 12 Mb total OC-12 NCEP Legend _ _ _ Connection backside to DATMS-U ____ DATMS-U connection Mb = Mbits/sec 10/2004

  8. Transition to Government Gateways • Funding issues • Interagency Government Network Connections Expand At Slower Rate • Information Assurance and FISMA Compliance • Update All Interagency Agreements To Satisfy Security Requirements • Work Security Boundary Issues Now

  9. 2010+ NIPRNET/NOAANET Connectivity with DREN/Internet AFWA 70 Mb NIPRNET (proj 150Mb) Asheville 16-44 Mb NIPRNET 100 Mb (current 54 Mb) 16 Mb NOAA/NWS Gateway 150 Mb NIPRNET (To NOAANET) 16 Mb OC-3+ NAVICE GIG 36 Mb NOAANET OC-3+ 65 Mb (current 21 Mb) DREN/Internet NESDIS FNMOC 65 Mb NIPRNET (current 21 Mb) OC12 DREN (backup) 33 Mb (current 7 Mb) OC-12+ Fast-E NCEP NAVO 33 Mb NIPRNET (current 7 Mb) OC48 DREN (possible Backup) NWS Monterey Pass thru to NOAA Legend NIPRNET Connection _ _ _ Connection backside to DATMS-U Mb = Mbits/sec DREN/Internet connection (could be used as a backup to NIPRNET) 4/2006

  10. Projected Communications 2010+ • Leverage All Available Network Resources • AFWA Location Data Ingest Estimate 20Gb/sec by 2010 • Diverse Communications • Leverage NOAA/AFW Connections • Enterprise Storage Solutions Used For Secure Data Transfer and Staging • End to End Efficiency May Be Hampered By Enterprise Infrastructure If Not Considered • Communications Engineered Throughout Production Process

  11. Questions?

More Related