turnerb@IMO-UVAX5.DCA.MIL ("turner, betsy") (06/07/91)
D C A I N T E R O F F I C E M E M O R A N D U M
Date: 07-Jun-1991 08:17am EST
From: Betsy Turner
TURNERB
Dept: DCSO/DISDA
Tel No: 285-5040/AV356 (703)
TO: See Below
Subject: DDN GOSIP Plans
Mr. Gary Dunn,
I received your inquiry on DDN GOSIP Plans from Roger Fradenburg, BBN
and George Bradshaw, DCA (thanks guys from passing to me). My name is
Betsy Turner and I am working GOSIP Implementation for COL Thacher, DDN
Program Manager. George Bradshaw, DCEC, is the primary supporting
engineer.
Currently, DDN can support GOSIP X.25 host to host communications.
Subscribers could use the DDN as the transmission medium to communicate
directly GOSIP X.25 to GOSIP X.25. Our implementation plans (still in
working phase) are to posture the network to support GOSIP
internetworking (TP4/CLNP). Our DDN Pilot Internet (10 cisco IP
routers) have the capability to do TP4/CLNP but are not currently
configured to do so. As you may be aware, the routing and directory
standards are not fully mature but are expected to be so in GOSIP V3
due around next year for draft publication. We are currently querying
the Services/Agencies for their GOSIP router plans over the next couple
years in order to adequately plan the support required.
Our "tentative" plans then are thus, we could implement TP4/CLNP during
FY 92 if subscribers express the requirement for support. We would
"all" have to live with some limited services; i.e. static routing
tables, limited interoperability with DOD Standardard communications
(I'll address more later), etc. We anticipate COTS products based on
the mature routing/directory standards within 1 to 2 years after the
appropriate GOSIP version is published/mandated. In summary, our
implementation plans will be based on/affected by, the state of the
standardization efforts, availability of COTS products, level of any
DDN development required (should be little if any), feedback from S/A
on their GOSIP plans/timeframes, and of course, availablity of funding.
Our plans also call for providing some number of Application Layer
Gateways, to ensure GOSIP/DOD Standard email and file transfer systems
interoperate. This AL GW does protocol conversions between the two
standards (GOSIP X.400/DOD SMTP and GOSIP FTAM/DOD FTP). We have a
prototype AL GW and support at Navy Computer and Telecommunications
Station (NCTS) Wash D.C. (old NARDAC folks recently reorganized).
Again, the routing and directory services are not fully
mature/automated but we have tasking with the NCTS folks to provide
support to users as requested. NCTS has an OSI Lab and have been
actively researching/testing OSI and have gained valuable experience
that they share with us thru our InterService Support Agreement with
them. A side note, we are currently planning testing with the Marine
Corps, Quantico, to test their GOSIP systems using DDN and the
Application Layer Gateway (performance stress test). We anticipate
that for performance and perhaps management considerations AL GW
may/should be a local asset in some cases (a study is being done this
FY) but DDN PMO has been tasked by ASDC3I to provide some number of the
boxes on DDN for backup and support to users who would not have AL GWs
locally for a variety of reasons.
In summary, our plans are to posture the network to support both GOSIP
and DOD standard communications user until such time that all S/A are
transitioned to GOSIP, and to provide interoperability for the GOSIP
and DOD standard file transfers and email systems. We hope to complete
our engineering analysis, based on GOSIP V2, shortly and begin near
term implementation planning.
Thanks for your interest in our plans. Hope I have provided some
clarification for you and others in the community. If we can be of
assistance in your GOSIP plans let us know; and of course, please keep
us advised of your timeframes so we can ensure we have the DDN postured
to support your requirements.
Betsy Turner
DDN PMO
DCA Code DISDA
DSN 356-5040 (soon to move to X-5218)
Comm 703-285-5040 (5218 approx 2 weeks)
George Bradshaw
DCEC
DDN Systems Engineering Division
703-487-3029
Distribution:
TO: APRM%GD@SHAFTER-EMH2.ARMY.MIL ( REMOTE )
CC: TCP-IP@NIC.DDN.MIL ( REMOTE )
CC: RFRADENB@BBN.COM ( REMOTE )
CC: TKENNEDY@WSMR-EMH05.ARMY.MIL ( REMOTE )
CC: CAIN@RIGEL.DCA.MIL ( REMOTE )
CC: TONTONOZ@EDN-VAX.DCA.MIL ( REMOTE )
CC: George Bradshaw ( BRADSHAWG )
CC: COONEY@WNYOSE.NCTSW.NAVY.MIL ( REMOTE )
CC: KENNY@NEMS.DT.NAVY.MIL ( REMOTE )
CC: CCOX@WNYOSE.NCTSW.NAVY.MIL ( REMOTE )beach@SERVER.AF.MIL (Darrel Beach) (06/13/91)
betsy, We're using the Milnet to transport OSI protocols between some Unisys systems(all on node 204) and some systems on our LAN at Gunter AFB. We're using a cisco AGS with static NSAP to net address maps. It works. The Unisys guys tell us their system uses Standard X.25 for both OSI and DoD suites rather than trying to distinguish between basic and standard. It such a trivial thing I'm amazed people worry much about it... darrel beach sends... --------- Darrel Beach beach@server.af.mil snail-mail: SAIC Montgomery Network Systems Engineer 205-279-4075 SSC/SSMT USAF DDN Program Office AV: 446-4075 Gunter AFB, AL 36116