Notes from South Pole TDRSS Relay (SPTR) Mtg/Telcon held on 6/9/97

Participants:  GSFC (530, NISN, SN Security)
               WSC (Corbett, Hartman, Von Wolff)
               SP User Rep (Troy Ames)


SECURITY (Tom Buchanan, Ron Dill)

- The Vulnerability Assessment Statement is in work and should be completed
along with necessary signatures by mid July.


NISN ACTIVITIES (John Steedman)

- Mr. Steedman mentioned his replacement to the SPTR Project will be Stan
Rubin effective next week.

- The WSC FOTS costing info (2 drivers and PS) was provided by NISN

- The two WSC Router options for interfacing the Internet T1 were costed:

       -- Phase 1/Option 1 - 5K - Modify (additional I/F cards) and Share the
existing WSC Admin Modem (Cisco CS3).

       -- Phase 2/Option 2 - 10K - New Router (Cisco 2500) for the SPTR function.

       -- MSFC (Rusty Morphew) has recommended Option 2 and the meeting
consensus was for Option 2 as well. The new router fits within the current
budgeted allocation.

- It was noted that the Routers used at the SP are Cisco 4000M. A Router
must be purchased for the SPTR SP interface also. The type of SP Modem to
purchase will be researched further (Andre Fortin) to best take advantage
of existing spare Modem components at the SP. It is assumed that different
models of Cisco Routers could be placed on either end of SPTR without any
adverse operational impact at T1 rates. NISN will procure the needed SPTR
Cisco routers for the Project once the models numbers are decided.

- NISN stated their circuit responsibility for SPTR will end at the WSC
router interface because its an Internet connection.  NISN will help
engineer, interface and test the SPTR capability end-to-end to ensure
operability.
- It was again mentioned that there was a cost savings to be had by
interfacing a T1 capability within an existing T3 that connects at STGT
brought on by VITS removal. The initial SPTR T1 interface for TDRS (F1) is
needed at WSGTU. There would be additional WSC IFL FOTS costs to interface
the NISN offered T1 at WSGTU, unless a separate/different T1 was interfaced
directly at WSGTU. This will be evaluated further. (See the next item)

- A lengthy discussion ensued on "Institutional" vice "Project Unique"
interfacing of SPTR at a single or both ground terminals at WSC. Richard
Von Wolff volunteered to provide, post telcon, simplified diagrams of the
three basic SPTR options discussed for carrier and SPTR equipment
interfacing/integration. Caren Corbett & Frank Hartman (WSC/GTE) also recommended an
Interim (phased) approach to get SPTR ready for testing in the
September/October time frame. These short/long term configurations will be
evaluated and costed (recurring and nonrecurring) ASAP by WSC/SPTR Project
Engineering/NISN personnel for discussion/decision by 530 management.


SSAF TESTING FOR SPTR

- Tests for SSAF maximum data rate without spreading via TDRS (F1)
indicated that up to 6MBPS could be used and verified via the local ETE
system.

- It was agreed that SPTR would baseline the SSAF capability for a 1MB user
data rate (2MSPS with the SPTR SSAF 1/2 encoder).

- WSC will change the Ground Spec Document to reflect a 6MB cap and
implement the necessary ADPE software changes to allow NCC scheduling of a
user date rate up to 6MB (vice current 300 KBPS). The changes are expected
to be implemented in the WSC September delivery.

- SPTR will be using TDRS (F1). F1 SSAF-2 EIRP is set for 40 dBW. WSC would
prefer not to use the Normal 43 dBW or Shuttle 46 dBW EIRP values if at all
possible. Initial indications are this should provide enough margin for the
SPTR SSAF link to the SP. A final CLASS link margin assessment is still to
be performed shortly for the SPTR implementation. A value of 40 dBW EIRP
will be used to evaluate the margin.


SPTR IMPLEMENTATION PROGRESS

- The two racks for housing SPTR equipment at GSFC and at SP are being
pursued. NSF will be contacted to see what racks are available at SP. It is
not intended to ship SPTR equipment within the racks to the SP. Separate
containers generally works best.

- ATSC will be submitting PR's to RSC ASAP for the long lead items.

- It is intended to use a PTP at WSC for the SPTR KSAR TCP/IP store/forward
capability. The use of the PTP will allow parallel MA Demand Access Service
(DAS) development to proceed along with the SPTR implementation. Only the
PC Processor portion of the PTP is needed for SPTR KSAR capability. The PTP
software used for SPTR or DAS will be remotely initialized by Andre Fortin
at GSFC to perform whatever function is required. The SPTR configuration
would essentially be left running all the time until DAS tests need to be
performed. A PC Processor will be used at the SP.

- A SPTR Ops Concept is in work and should be available soon.