![](media/image1.wmf){width="1.4694444444444446in"
height="0.9736111111111111in"} *NASA Integrated Services Network*

  -----------------------------------------------------------------------
  National Aeronautics and Space Administration (NASA) Integrated
  Services Network (NISN) Services Document

  March 31, 2008

  -----------------------------------------------------------------------

Change Information Page

  --------------------- ---------------- ------------ --------------- ----------------
  List of Effective                                                   
  Pages                                                               

  Page Number                            Version      Nature of       
                                                      Change          

  Title                                  9            Added date      

  11                                     9            Added VTC       
                                                      paragraph       

  21                                     9            Added MTTR in   
                                                      table           

  28                                     9            Added MTTR      
                                                      footnote,       
                                                      updated table   

  40                                     9            Removed text on 
                                                      customer NSRS   
                                                      access          

  27                                     9            CVPN folded in  
                                                      DCNSS Service   

  37                                     9            Added Level 2   
                                                      VPN Service     

                                                                      

                                                                      

                                                                      

                                                                      

                                                                      

  Document History                                                    

  Document Number       Version/Change                Issue Date      Effective Date

  NISN-001-001          Original                      UNK             UNK

                        Revision 1                    UNK             UNK

                        Revision 2                    February 1998   February 1998

                        Revision 3 --                 November 2000   December 31,
                        CSOC                                          2000

                        Revision 4 --                 May 2003        May 30, 2003
                        CSOC                                          

                        Revision 5 --                 February 20,    February 20,
                        CSOC                          2004            2004

                        Revision 5a -                 May 2004        May 2004
                        UNITeS                                        

                        Revision 6 --                 August 2004     August 2004
                        UNITeS                                        

                        Revision 6a --                November 16,    November 16,
                        UNITeS                        2004            2004

                        Revision 7 --                 April 2005      April 2005
                        UNITeS                                        

                        Revision 8 --                 April 2006      April 2006
                        UNITeS                                        

                        Revision 9                    May 2007        May 21, 2007
                        --UNITeS                                      

                        Revision 10 --                December 2007   March 31, 2008
                        UNITeS                                        
  --------------------- ---------------- ------------ --------------- ----------------

[]{#__RefHeading___Toc185737009 .anchor}Preface

The National Aeronautics and Space Administration (NASA) Integrated
Services Network (NISN) Services Document (NSD) is prepared in document
format to aid NISN customers when requesting communications and network
services available to them from NASA. Comments or questions pertaining
to this document should be forwarded to the
[E-Mail](mailto:Kim.Wright@nasa.gov) address appearing in Appendix C,
paragraph
[C.3.](#nasa-integrated-services-network-nisn-point-of-contact-poc)

This revision of the NSD updates the document with respect to current
service offerings and is intended to serve as a single point source for
authoritative information on NISN services and their associated pricing.

This document is under the Configuration Management (CM) of the NISN
Configuration Control Board (CCB). This document shall be changed either
by Documentation Change Notice (DCN) or complete revision. Proposed
changes to this document shall be submitted to the NISN CCB along with
supportive material justifying the proposed change before incorporation
into the document.

[]{#__RefHeading___Toc185737010 .anchor}Abstract

This document provides information for requesting NASA Wide Area Network
(WAN) communications services available through the NISN organization.
The NISN organization is an entity of Office of Space Communications,
and the Space Communications and Navigation (SCaN) Systems Directorate.
Available services are described, instructions on how to request
services are provided, and key personnel are listed within this
document.

**Keywords**: Activity and Outage Posting and Notification System
(AOPNS), Basic Rate Interface (BRI), Broadcast Fax Service, Corporate
Virtual Private Network (CVPN), Custom Services, Data Center Network and
Security Services (DCNSS), Dedicated Mission Data Services, Dedicated
Mission Voice Service, Desktop ViTS Appliance (DVA), Domain Name Service
(DNS), High Rate Data/Video Service (HRDVS), Federal Telecommunications
Services (FTS), Integrated Services Digital Network (ISDN),
International Service, International Teleconferencing Union (ITU), Layer
2 Virtual Private Network (L2VPN), Mission Critical Routed Data Service,
Mission Outage Notification System (MONS), Network Timing Protocol
(NTP), NISN Integrated Information System (NIIS), NASA X.500 Directory
Services, Network Modeling Service, Organization Responsibility Document
(ORD), Premium Routed Data Service, Primary Rate Interface (PRI),
Real-time Mission Critical Routed Data Service, Russia Services,
Standard Routed Data Service, Switched Voice Service (SVS), Video
Teleconferencing Service (ViTS), ViTS Roll-about (VRA), Voice
Teleconferencing Service (VoTS), Video Teleconferencing Center (VTC).

Contents

**Preface [iii](#__RefHeading___Toc185737009)**

Abstract [iv](#__RefHeading___Toc185737010)

1\. Introduction [1](#introduction)

1.1 Purpose [1](#purpose)

1.2 Scope [1](#scope)

1.3 Document Organization [1](#document-organization)

1.4 Related Documents [2](#related-documents)

1.4.1 Applicable Documents [2](#applicable-documents)

1.4.2 References [3](#references)

1.5 NISN Organization and Functions
[3](#nisn-organization-and-functions)

1.5.1 NASA Integrated Services Network (NISN) Project Office
[3](#nasa-integrated-services-network-nisn-project-office)

1.5.2 Customer Interface Group (CIG) [3](#customer-interface-group-cig)

1.5.3 Business Management Group (BMG)
[3](#business-management-group-bmg)

1.5.4 Network Services Group (NSG) [3](#network-services-group-nsg)

1.5.5 Information Technology (IT) Security
[3](#information-technology-it-security)

1.5.6 NASA Integrated Services Network (NISN) Russia Services Project
[3](#nasa-integrated-services-network-nisn-russia-services-project)

1.6 Standard Practices [4](#standard-practices)

1.6.1 General [4](#general)

1.6.2 Guidelines [4](#guidelines)

1.6.3 Acceptable Use Policy [4](#__RefHeading___Toc185737028)

1.6.4 Security [5](#security)

1.6.5 NASA Integrated Services Network (NISN) Support Applications
[6](#nasa-integrated-services-network-nisn-support-applications)

2\. Services [7](#services)

2.1 Introduction [7](#introduction-1)

2.1.1 Service Implementation Test and Acceptance
[7](#service-implementation-test-and-acceptance)

2.1.2 NISN Value Added Services [7](#nisn-value-added-services)

2.2 Video Teleconferencing System (ViTS)
[8](#video-teleconferencing-system-vits)

2.2.1 General Service Description [8](#general-service-description)

2.2.2 Video Teleconferencing System (ViTS) Interface Types
[9](#video-teleconferencing-system-vits-interface-types)

2.2.3 Video Teleconferencing System (ViTS) Facilities
[9](#video-teleconferencing-system-vits-facilities)

2.2.4 Service Operation [10](#service-operation)

2.2.5 Service Performance [11](#service-performance)

2.2.6 Service Maintenance [11](#service-maintenance)

2.3 Voice Teleconferencing System (VoTS)
[12](#__RefHeading___Toc185737042)

2.3.1 General Service Description [12](#general-service-description-1)

2.3.2 Service Levels Description [12](#service-levels-description)

2.3.3 Voice Teleconferencing System (VoTS) Facilities
[13](#voice-teleconferencing-system-vots-facilities)

2.3.4 Service Operations [13](#service-operations)

2.3.5 Service Performance [15](#service-performance-1)

2.3.6 Service Maintenance [15](#service-maintenance-1)

2.4 Switched Voice Services (including Calling Cards and Toll-Free
Services)
[15](#switched-voice-services-including-calling-cards-and-toll-free-services)

2.4.1 General Service Description [15](#general-service-description-2)

2.4.2 Service Operations [16](#service-operations-1)

2.4.3 Service Performance [16](#service-performance-2)

2.4.4 Service Maintenance [16](#service-maintenance-2)

2.5 Broadcast Fax Services [17](#broadcast-fax-services)

2.5.1 General Service Description [17](#general-service-description-3)

2.5.2 Service Operations [17](#service-operations-2)

2.5.3 Service Maintenance [18](#service-maintenance-3)

2.6 Routed Data [18](#routed-data)

2.6.1 General Service Description [18](#general-service-description-4)

2.6.2 Internet Protocol (IP) Routed Data - Security
[19](#internet-protocol-ip-routed-data---security)

2.6.3 Service Operations [20](#service-operations-3)

2.6.4 Service Performance [20](#service-performance-4)

2.6.5 Service Maintenance [22](#service-maintenance-4)

2.7 NASA Internet Protocol (IP) Address Space
[22](#nasa-internet-protocol-ip-address-space)

2.8 Dedicated Mission Voice and Data
[22](#dedicated-mission-voice-and-data)

2.8.1 Dedicated Mission Voice Services
[22](#dedicated-mission-voice-services)

2.8.2 Dedicated Mission Data [24](#dedicated-mission-data)

2.9 High Rate Data/Video Services (HRDVS)
[25](#high-rate-datavideo-services-hrdvs)

2.9.1 General Service Description [25](#general-service-description-7)

2.9.2 Service Operations [26](#service-operations-6)

2.9.3 Service Performance [26](#service-performance-7)

2.9.4 Service Maintenance [26](#service-maintenance-7)

2.10 Data Center Network and Security Services (DCNSS)
[26](#data-center-network-and-security-services-dcnss)

2.10.1 General Service Description [26](#general-service-description-8)

2.10.2 Service Operations [27](#service-operations-7)

2.10.3 Service Performance [27](#service-performance-8)

2.10.4 Service Maintenance [29](#service-maintenance-8)

2.11 Directory Services (X.500) [29](#directory-services-x.500)

2.11.1 General Service Description [29](#general-service-description-9)

2.11.2 Service Operations [29](#service-operations-8)

2.11.3 Service Performance [30](#service-performance-9)

2.11.4 Service Maintenance [30](#service-maintenance-9)

2.12 Domain Name Service (DNS) [30](#domain-name-service-dns)

2.12.1 General Service Description [30](#general-service-description-10)

2.12.2 Service Operations [30](#service-operations-9)

2.12.3 Service Performance [30](#service-performance-10)

2.12.4 Service Maintenance [30](#service-maintenance-10)

2.13 International Services [31](#international-services)

2.13.1 General Service Description [31](#general-service-description-11)

2.13.2 Service Operations [31](#service-operations-10)

2.13.3 Service Performance [32](#service-performance-11)

2.13.4 Service Maintenance [32](#service-maintenance-11)

2.14 Russian Services [32](#russian-services)

2.14.1 General Service Description [32](#general-service-description-12)

2.14.2 Service Operations [32](#service-operations-11)

2.14.3 Service Performance [32](#service-performance-12)

2.14.4 Service Maintenance [33](#service-maintenance-12)

2.15 Network Modeling Services [33](#network-modeling-services)

2.15.1 General Service Description [33](#general-service-description-13)

2.15.2 Service Operations [33](#service-operations-12)

2.15.3 Service Performance [33](#service-performance-13)

2.15.4 Service Maintenance [34](#service-maintenance-13)

2.16 Custom Services [34](#custom-services)

2.16.1 General Service Description [34](#general-service-description-14)

2.16.2 Service Operations [34](#service-operations-13)

2.16.3 Service Performance [34](#service-performance-14)

2.16.4 Service Maintenance [34](#service-maintenance-14)

2.17 Intrusion Detection Services (IDS)
[34](#intrusion-detection-services-ids)

2.17.1 General Service Description [34](#general-service-description-15)

2.17.2 Service Operations [35](#service-operations-14)

2.17.3 Service Performance [36](#service-performance-15)

2.17.4 Service Maintenance [36](#service-maintenance-15)

2.18 Network Timing Protocol (NTP) Service
[36](#network-timing-protocol-ntp-service)

2.18.1 General Service Description [36](#general-service-description-16)

2.18.2 Service Operations [36](#service-operations-15)

2.18.3 Service Performance [37](#service-performance-16)

2.18.4 Service Maintenance [37](#service-maintenance-16)

2.19 Layer 2 Virtual Private Network (L2VPN) Service
[37](#layer-2-virtual-private-network-l2vpn-service)

2.19.1 General Service Description [37](#general-service-description-17)

2.19.2 Service Operations [38](#service-operations-16)

2.19.3 Service Performance [38](#service-performance-17)

2.19.4 Service Maintenance [39](#service-maintenance-17)

3\. How to Request Services [40](#how-to-request-services)

3.1 General [40](#general-1)

3.2 The Requirements Process [40](#the-requirements-process)

3.2.1 Customer Actions [40](#customer-actions)

3.2.2 NASA Integrated Services Network (NISN) Actions
[40](#nasa-integrated-services-network-nisn-actions)

3.3 Rough Order of Magnitude (ROM) Costs and Detailed Cost Estimates
[41](#rough-order-of-magnitude-rom-costs-and-detailed-cost-estimates)

3.3.1 Detailed Cost Estimate Vs Rough Order of Magnitude (ROM) Cost
[41](#detailed-cost-estimate-vs-rough-order-of-magnitude-rom-cost)

3.3.2 Rough Order of Magnitude (ROM) Cost
[41](#rough-order-of-magnitude-rom-cost)

3.3.3 Detailed Cost Estimate [41](#detailed-cost-estimate)

4\. Fiscal Year 2008 (FY08) Pricing [41](#fiscal-year-2008-fy08-pricing)

4.1 Pricing Overview [41](#pricing-overview)

4.2 Budgeting Process [42](#budgeting-process)

Appendix A. Supported Interfaces and Protocols
[44](#supported-interfaces-and-protocols)

Appendix B. NISN Service Standard Intervals
[45](#nisn-service-standard-intervals)

Appendix C. NASA Integrated Services Network (NISN) Point of Contact
(POC) [47](#nasa-integrated-services-network-nisn-point-of-contact-poc)

Appendix D. Key Personnel [48](#key-personnel)

Appendix E. Abbreviations and Acronyms [49](#abbreviations-and-acronyms)

Appendix F. Glossary [53](#glossary)

Appendix G. NASA Integrated Services Network (NISN) IT Security Check
Lists.
[58](#nasa-integrated-services-network-nisn-it-security-check-lists.)

List of Tables

[Table 2-1 VoTS Service Performance (by Service Category)
15](#__RefHeading___Toc185737168)

[Table 2-2 Performance Standards for Switched Voice
16](#__RefHeading___Toc185737169)

[Table 2-3 Performance Standards for Broadcast Fax Service
17](#__RefHeading___Toc185737170)

[Table 2-4 Performance Standards for IP Routed Data (by Service
Category) 21](#__RefHeading___Toc185737171)

[Table 2-5 Performance Standards for Dedicated Mission Voice (by Service
Category) 24](#__RefHeading___Toc185737172)

[Table 2-6 Performance Standards for Dedicated Mission Data (by Service
Category) 25](#__RefHeading___Toc185737173)

[Table 2-7 Performance Standards for High Rate Data/Video Services
26](#__RefHeading___Toc185737174)

[Table 2-8 Current Service Performance Parameters
28](#__RefHeading___Toc185737175)

[Table 2-9 Russia IT Services and Performance Standards
32](#__RefHeading___Toc185737176)

[Table 2-10 IDS Service Performance 36](#__RefHeading___Toc185737177)

[Table 2-11 Performance Standards for L2VPN (by Service Category)
38](#__RefHeading___Toc185737178)

[Table 4-1 General Annual PSLA Requirements Validation
42](#__RefHeading___Toc185737179)

[Table B-1 NISN Service Standard Intervals
46](#__RefHeading___Toc185737180)

NASA Integrated Services Network (NISN)\
Services Document (NSD)

# Introduction

## Purpose

The purpose of this document is to furnish NISN
[customers[^1]](#Customer) and [users](#User) with a description of Wide
Area Network (WAN), data, voice, video and other communications services
available through NISN. This document also provides performance metrics
and standard lead time information associated with these services and
describes the processes to be followed for initiating NISN Service
Requests (NSRs) to the appropriate organization(s).

## Scope

This document encompasses all the information that a user of NISN
services may need to request services. The requirements submission
processes described in this document are consistent with and part of the
larger processes whereby the officials in charge of NASA Mission
Directorates, Mission Support Offices, Program Offices, and the
Directors of NASA Centers and Field Installations submit their
requirements in support of Human Space Flight (HSF) missions and
non-Human Space Flight, sub-orbital and aeronautical missions.

## Document Organization

This document is organized as follows:

a.  Section 1 contains introductory information.

b.  Section 2 contains information on NISN's standard commodity and
    custom service offerings.

c.  Section 3 contains information on how one requests services from the
    NISN organization.

d.  Section 4 contains information on the methodology to be used in
    pricing and charging for services.

e.  Appendix A contains information on supported interfaces and
    protocols.

f.  Appendix B contains information on NISN Service Standard Intervals.

g.  Appendix C contains NISN Point of Contact (POC) information.

h.  Appendix D contains listings of key personnel.

i.  Appendix E contains a list of Abbreviations and Acronyms.

j.  Appendix F contains a Glossary of terms.

k.  Appendix G contains a link to the NISN PIP/SIP Security Checklist.

Glossary terms appearing in this document are underlined at their first
appearance and [hyperlinked](#impacted) to their glossary location.

## Related Documents

The following documents have been determined to be either applicable or
have been referenced in the context of NISN. Where a document is known
to be available on-line, a hyperlink to that document has been
established.

### Applicable Documents

Applicable documents are those which by virtue of their inclusion in
this paragraph become part of this document. Additionally, they have the
same force and authority as if physically reproduced and incorporated as
part of this document.

a.  NISN Project Management Plan, December 2005 and subsequent revisions

b.  []{#Applicable_Documents_141b .anchor}NASA-STD-2806, [Network
    Protocol](http://www.hq.nasa.gov/office/codea/codeao/pdfs/2806.pdf)

c.  []{#Applicable_Documents_141c .anchor}Chief Information Officer
    (CIO) Executive Notice 16-96, effective September 23, 1996

d.  NASA Policy Directive (NPD) 2800.1A, Managing Information
    Technology, expires August 18, 2009 and subsequent revisions.

e.  NPD 2810.1C, NASA Information Security Policy, expires June 30, 2009
    and subsequent revisions.

f.  []{#Applicable_Documents_141e .anchor}NASA Procedure Requirement
    (NPR) 2810.1A, Security of Information Technology, expires May 16,
    2011 and subsequent revisions,

g.  NASA Policy Directive (NPD) 2540.1F, Personal Use of Government
    Office Equipment Including Information Technology, expires May 25,
    2010 and subsequent revisions.

h.  NPR 2830.1 NASA Enterprise Architecture, expires December 16, 2010
    and subsequent revisions

i.  3000-4519, [NISN Services Request System (NSRS) Process]{.underline}

j.  NISN-Standard Operating Procedure
    [(SOP)-000002](http://www.nisn.nasa.gov/DOCUMENTS1/SOP_OperationsStandards.doc),
    NISN SOP for Trouble Reporting, Activity Scheduling, Mission Freeze
    and Major Outage Notifications Effective June 2006.

k.  Internet Protocol Operational Network (IONet) Access Protection
    Policy and Requirements,
    [290-004](http://www.nisn.nasa.gov/DOCUMENTS1/IONet_Access_Policy_Rev3.doc)
    Revision 3 dated June 2004.

l.  NPD 2190.1A, NASA Export Control Program (Revalidated 5/5/06),
    expires November 24, 2011 and subsequent revisions.

m.  NPR 2190.1, NASA Export Control Program, Revalidated w/changes
    February 1, 2007, expires April 10, 2013 and subsequent revisions.

n.  Federal Information Security Management ([FISMA) Act of
    2002](http://csrc.nist.gov/publications/index.html)

o.  NISN-0030, Video Teleconferencing Services (ViTS) Maintenance
    Implementation Plan Volume I: Maintenance Fee Rooms

### References

Reference documents are those which may be used to further understand
NISN, its organization and the principles by which it operates in
meeting the communications and networking requirements of those who use
NASA-provided WAN services.

-   NPR 2830 NASA Enterprise Architecture Procedures

## NISN Organization and Functions

### NASA Integrated Services Network (NISN) Project Office

Marshall Space Flight Center (MSFC) has been delegated primary
responsibility for NASA WAN services. The NISN Project Office is located
within the Office of the CIO at MSFC and the Information Technology and
Communications Directorate at Goddard Space Flight Center (GSFC). The
office provides management direction for the integrated NASA networks
and is the focal point for NASA wide area communications. A NISN
Organizational Chart and listing for key points of contact may be found
on the [NISN](http://nisn.nasa.gov/ContactPages/Contact.html) website.

### Customer Interface Group (CIG)

The NISN CIG focuses primarily on the customers of NISN. The CIG
analyzes the customers' requirements and works closely with the
customers to provide a communications service that shall meet the
requirements.

### Business Management Group (BMG)

The NISN BMG is responsible for the accounting and funding of NISN
services, specifically for business management activities, performance
measurement, budget planning and development, and contract management.

### Network Services Group (NSG)

The NISN NSG focuses primarily on technology assessment to intelligently
procure IT services that shall best meet the needs of the Agency and the
efficient operations, maintenance, management, and implementation of
NISN network architecture elements and services. NSG personnel also
serve as NISN Service Owners for the various NISN services. The Service
Owners primarily partner with the NISN support contractor to maintain a
clear insight into: the architecture and service delivery method of the
NISN service, the operational performance of the service, and new
technology that may improve the service.

### Information Technology (IT) Security

The IT Security contacts are primarily responsible for maintaining
agency wide security policies, assessing security impact across the NISN
architecture, performing security operations, and representing NISN in
the IT Security community.

### NASA Integrated Services Network (NISN) Russia Services Project

The NISN Russia Services Project provides project management, planning,
engineering, installation, implementation and sustaining Information
Technology and Telecommunications services for NASA programs and
projects within Russia.

## Standard Practices

### General

NISN provides communications and networking services to its customers.
Domestic services shall, in so far as they are available, be obtained as
standard commodity services. International services shall be obtained by
making use of existing contract vehicles, by individual competitive
procurements, or via agreements with international partners.

### Guidelines

NISN practices are governed by the following guidelines:

a.  It is the goal of NASA to provide communications in support of
    mission and non-mission activities at a minimum total cost
    consistent with requirements for capacity, performance, efficiency,
    reliability and security in accordance with applicable regulations.

b.  NPR 2830.1 NASA Enterprise Architecture Procedures requires NASA to
    ensure that IT expenditures are aligned with Agency goals, while
    reducing unnecessary duplication of resources. This NPR also
    requires that IT providers document their current state, future
    state, and plan to migrate to the future state, from an
    architectural standpoint. NISN's services were EA-approved in April
    2005, and will be updated annually.

c.  Local standards and/or architectures may be implemented to the
    extent that there is no conflict or incompatibility with Federal or
    NASA standards and/or the NISN approved EA. The proposed local
    standard and/or architecture shall have the concurrence of the
    Center CIO Representative which ensures that there are no
    incompatibilities or conflicts with existing Federal or NASA
    standards and/or approved EAs.

d.  NASA security policy forbids the unauthorized access to all
    operational WAN systems and requires appropriate management controls
    to assure that all use of NASA communications assets are in pursuit
    of official Government activities. Management controls shall
    effectively prevent unauthorized traffic.

### [[]{#__RefHeading___Toc185737028 .anchor}Acceptable Use Policy](http://www.nisn.nasa.gov/DOCUMENTS1/acceptable.html)

[The following Acceptable Use Policy, along with the official NASA
policy on IT Security (ITS) and relevant U.S. federal laws, comprises
the basic doctrine of the NISN
Program.](http://www.nisn.nasa.gov/DOCUMENTS1/acceptable.html)

#### Summary:

a.  NISN supports all NASA Mission Directorates, centers, programs,
    projects and field locations.

b.  NISN is not to be used for private gain or profit.

#### Specific:

a.  Use of NISN shall be in support of official NASA programs. All user
    requests for NISN connectivity shall be validated and supported by
    [NISN Center/Program Representatives](#NISNCTRREP) or a SCDS
    [Customer Commitment
    Manager](http://www.nisn.nasa.gov/DOCUMENTS1/POC_ctr_program_representatives.html)
    (CCM) (refer to [Appendix D](#key-personnel) of this document).

b.  Use of NISN to support coordination and administrative execution of
    NASA business is permissible.

c.  Use of NISN to support NASA missions, research, related training and
    associated technical activities at non-profit institutions of
    research and education is acceptable.

d.  Use of NISN for commercial or intellectual gain by for-profit
    organizations is not acceptable, unless those organizations are
    using NISN to satisfy specific NASA contract or grant requirements.

e.  Use of NISN for research or education at for-profit institutions
    shall be reviewed on a case-by-case basis to ensure consistency with
    NASA programs. Lack of program approval shall result in a denial of
    service implementation or disconnection.

f.  Use of NISN to gain unauthorized use of resources attached to NISN
    may result in disconnection and legal prosecution.

g.  Use of NISN for the introduction of
    [worms](#nasa-integrated-services-network-nisn-it-security-check-lists.),
    [viruses](#nasa-integrated-services-network-nisn-it-security-check-lists.),
    [trojans](#Trojan) or other software that maliciously interferes
    with NISN operations is unlawful.

h.  Users shall place particular emphasis on restricting their
    disclosure of data and information to those persons who have a
    definite need for the data in order to perform their official
    duties.

i.  Users shall not attempt to access any data or programs contained on
    the NISN network for which they do not have authorization or
    explicit consent from the owner of the data or program, the NISN
    Project Manager or the NISN ITS Manager.

j.  Users shall not divulge dialup or dial-back modem phone numbers to
    unauthorized users.

k.  Users shall not share account(s).

l.  Users shall not purposely engage in activity with the intent to:

```{=html}
<!-- -->
```
1.  Harass other users

2.  Degrade the performance of systems

3.  Deprive an authorized NISN user of access to a NISN resource

4.  Obtain resources beyond those allocated

5.  Circumvent NISN security measures

6.  Gain access to a NISN IT resource for which proper authorization has
    not been given

```{=html}
<!-- -->
```
m.  Electronic communication facilities (such as [E-mail](#impacted),
    newsgroups or World Wide Web) are for authorized government use
    only. Fraudulent, harassing or obscene messages and/or materials
    shall not be sent from, to, or over, nor stored on NISN resources.

n.  Users shall use the appropriate NISN service that meets security and
    operational requirements of the program data to be transferred.

### Security

The objective of NASA security policies is to assure the integrity,
[Availability](#Availability) and confidentiality of NASA IT resources.
These policies preclude deliberate or accidental corruption of IT
resources, protect information from unauthorized disclosure and ensure
that disaster recovery and contingency planning (as defined in the
Office of Management and Budget [Circular
A-130](http://www.whitehouse.gov/omb/circulars/a130/a130trans4.html)) is
incorporated for all IT resources. NISN customers will be required to
submit an IT security checklist prior to connection to the NISN network.

#### Information Confidentiality

NISN security procedures place significant emphasis on protecting
customers' unique information requirements. This focus is predicated on
the following:

a.  A customer's security level within the NISN shall be based on the
    sensitivity level given to the information. The productivity
    associated with that information should only be marginally affected
    by security safeguards required for protection and the information's
    degree of sensitivity as defined in [applicable document
    1.4.1.e](#Applicable_Documents_141e).

b.  A customer's communication access shall be based on the premise that
    what is not expressly permitted is prohibited.

Customer-focused security procedures shall include the reporting and
subsequent handling of violations, and accountability for any access
controls requested.

#### Internal Safeguards

NISN internal security policies shall adhere to the following principles
and practices:

a.  Sensitivity levels shall be used to minimize the impact of failures
    in the network

b.  Customers shall be afforded the least access consistent with their
    requirements

c.  Technical controls, such as access lists, packet filters,
    [firewalls](#impacted) and [intrusion detection
    system](#IDS)[s]{.underline} shall be employed to ensure that trust
    is not violated

d.  Remote access to the network shall be permitted, but only in
    conformance with network policies and practices governing such
    accesses

e.  NISN shall actively manage firewalls both by technical means and
    human oversight

### NASA Integrated Services Network (NISN) Support Applications

Information concerning NISN applications available to customers,
including access information, is available at the NISN Web site
[http://www.nisn.nasa.gov](http://www.nisn.nasa.gov/). A brief
definition of these applications is shown below:

a.  Activity and Outage Posting Notification System (AOPNS): Provides an
    active key word and/or key phrase email subscription capability for
    receiving NISN activity and outage notifications. [Subscribe
    here](https://nisn-webprod.nisn.nasa.gov/cgi-bin/aopns/aopns_subscribe.cgi?SIGNUP_SUBSCRIBER=1)

b.  Call Detail: Provides FTS billing information for switched voice
    services. The information is available by month, NASA location, and
    frequency.

c.  Mission Outage Notification System (MONS): Provides an active key
    word and/or key phrase email subscription capability for receiving
    NISN mission services outage notifications. [Subscribe
    here](https://nisn-webprod.nisn.nasa.gov/cgi-bin/mons/mons_subscribe.cgi?MENU=1)

# Services

## Introduction

NISN provides both Standard and Custom services. Standard services are
those that can be ordered directly as commodities from the supplying
vendor, e.g., from a menu or catalogue. Standard services require
neither customization nor special engineering to meet the particular
requirements of a customer. Custom services are those that require some
engineering prior to ordering or providing the service. NISN can supply
custom services tailored to fit a customer's requirements; however, the
customer will be charged the additional costs that are associated with
implementing and sustaining the customized solution.

NISN interfaces shall conform to American and International standards
commonly accepted within and supported by industry. Procured equipment
and software are, wherever possible, to be available on a
Commercial-Off-the-Shelf (COTS) basis. Circuits shall be procured using
General Services Administration (GSA) contracts and centralized billing
wherever possible.

The provisioning of NISN services entails certain lead times. Such lead
times vary from a few days through several months up to two or three
years, depending upon the complexity of the solution (e.g., the extent
of customization) required in meeting the customer's requirement.
[Appendix B](#nisn-service-standard-intervals) contains a specific
discussion of lead times, based on different scenarios, which are
intended for use as planning guidelines only; it is entirely possible
that similarly appearing requirements have distinctive aspects that may
increase or decrease the actual lead times from those shown.

### Service Implementation Test and Acceptance

NISN performs testing during service implementation to verify service
delivery. The testing performed by NISN normally falls within two
categories:

a.  Testing of purchased services such as carrier provided circuits

b.  Testing of services provided by the existing NISN infrastructure
    such as routed IP data, voice, and video.

When implementing new services, NISN works with the requesting Customer
organization to verify, as closely as practical, the true end-to-end
service delivery before agreeing that the NSR is "in service". In
instances where the Customer is not prepared to test the service at
implementation, NISN shall perform testing consistent with the type of
service requested and the corresponding performance parameters as
described elsewhere in the NSD for each category of service.

### NISN Value Added Services

In support of the direct services NISN provides to its customers, there
are numerous Value Added Services. Many are additional resources for the
customer's use, while others may be transparent to the user. These Value
Added Services are part of the normal day-to-day support work performed
by the NISN organization. They augment the primary customer services and
help to provide the continuing quality of the direct services available
to our customers. Some of these services are:

-   Centralized number for problem reporting

-   Problem identification and resolution

-   24X7 Help Desk

-   Real-time network monitoring

-   Automated outage notifications

-   Trouble ticket management

-   Dedicated Customer Service Representatives (CSR)

-   Gateway technician service support

-   Multi-vendor service provisioning and coordination

-   Requirements analysis and integration

-   Rough Order of Magnitude (ROM) costing

-   Project Service Level Management

-   Sustaining engineering

-   Hardware and software maintenance

-   NPG2810 compliance

-   Certification and Accreditation (C&A)

-   Customer Forums

-   Property management

-   Contract management

-   Virtual modeling for conference rooms

-   Network integration and consulting

-   Transition of applications and protocols to the NISN operational
    network

-   Maintenance and operations of NISN laboratories

-   Development of engineering expertise in emerging systems and
    technologies

-   24X7 Intrusion Detection

## ![](media/image2.jpeg){width="2.125in" height="1.5916666666666666in"}Video Teleconferencing System (ViTS)

### General Service Description

The NASA ViTS provides interactive point-to-point and multipoint video
conferencing capabilities to NASA locations, select contractor
facilities, Department of Defense, and public video conferencing
services. ViTS services include provisioning, installation and
maintenance of video conferencing facilities, scheduling of multipoint
videoconferences, and the transmission and distribution of the video and
audio among the participating locations. ViTS is capable of supporting
both Internet Protocol (IP) and Integrated Services Digital Network
(ISDN) connected room locations. A centralized web-based scheduling
system, for recurring or one-time conferences, is also provided for
determining room and network availability.

### Video Teleconferencing System (ViTS) Interface Types

NASA ViTS is based upon both Circuit Switching ISDN and IP technology.
These mediums support ITU compression standards H.323, H320, H.264,
H.263, G.722 and G.728. ISDN connections are based upon interface type
and can vary from a Basic Rate Interface (BRI) to a Primary Rate
Interface (PRI). As circuit-switching technology has evolved, NISN has
migrated the majority of its ViTS facilities to PRI interfaces.
Integrated Services Digital Network (ISDN)

ISDN data rates vary from a BRI to a PRI that provide up to 1.4 megabits
per second (Mbps)

It is recommended that any new service implementation using ISDN be
implemented with a PRI connection. ViTS facilities connected via ISDN
are capable of supporting point-to-point calls ranging from 128 kbps to
1.4 Mbps and NISN Video Bridge assisted multipoint calls ranging from
128 Kbps to 768 Kbps.

######### Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI)

ISDN BRI is the most basic ISDN interface. ISDN BRI provides the
customer with two 64 Kbps Bearer (B)-channels and one 16 Kbps Data
(D)-channel, each of which can be shared by numerous ISDN devices.

######### Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI)

In North America, ISDN PRI includes one 64 Kbps D-channel and 23
B-channels (30 B-channels in most other parts of the world). The number
of B-channels is limited by the size of the standard trunk line used in
the region, T-1 in North America and Japan and E-1 most everywhere else.
Unlike BRI, PRI does not support a bus configuration, and only one
device can be connected to a PRI line.

#### Internet Protocol (IP)

ViTS facilities connected via IP are capable of supporting
point-to-point calls ranging from 128 kbps to 2 Mbps; however, NISN has
limited the majority of these connections to 384 Kbps to ensure call
quality and network loading are optimized for all NISN video traffic. As
required, select NASA sites may be configured for the maximum data rate.

### Video Teleconferencing System (ViTS) Facilities

ViTS Facilities consist of Full-Service Conference Rooms and ViTS
Roll-About (VRA) Systems. For on-demand conferencing, these facilities
have built-in bridging support for up to three additional participants
that can be audio-only or video. Additional capabilities exist within
each facility for graphics, external video sources, as well as audio
add-on support. NISN also provides Desktop Video Appliances (DVAs),
which is geared to one participant participating in a conference from
their office. The DVA rely on external bridging for conference
connections.

#### Full-Service Conference Rooms

![](media/image3.jpeg){width="2.125in"
height="1.5868055555555556in"}There are Full-Service Conference Rooms
located at each NASA center that are usually supported by
center-provided room operators. These rooms are normally used for large
videoconferences and can accommodate 30-50 persons. A new Full-Service
Conference Room can be designed to the customer's specification and
requires the development of an Organization Responsibility Document
(ORD) stating the functional requirements for the room and associated
funding for implementation. Standard capabilities include dual Plasma or
rear projector screens, Video Cassette Recorder (VCR)/Digital Video Disc
(DVD) combination unit, front and rear cameras, and standalone (not
connected to center local area network) computer connections. Additional
features such as room lighting control, extra microphones, and computer
pop-ups are also available.

#### ViTS Roll-About (VRA) Systems

VRA systems are designed for smaller conference facilities and can be
integrated with existing voice conferencing hardware or, with the
addition of a phone line, provide audio add-on capability directly from
the unit itself. The on-board Multipoint Control Unit (MCU) has the
capability of supporting up to three additional 384 Kbps calls.
Additional devices, such as computers and projectors, can also be
connected to the system. VRAs are portable and can be easily relocated
to different rooms that contain either ISDN or IP network drops. The VRA
consists of a 50-inch Plasma screen and Video Codec mounted on a
roll-about cart, with VCR / DVD combination unit and document camera.
These rooms are designed for user-friendly operations and should not
require a dedicated room operator.

#### Desktop ViTS Appliance (DVA)

The DVA is a small, standalone desktop appliance designed for personal
videoconferencing. It is configured to operate on ISDN or IP networks,
supporting video calls ranging from 128 to 768 Kbps (384 Kbps ISDN). The
recommended configuration for the DVA is an IP-Only connection via the
NISN Premium Internet Protocol (PIP) network. The DVA consists of a
remote control, built-in camera, viewing screen, microphone, and
internal speaker. A headset accessory is optional.

The DVA is completely functional as a stand-alone appliance for
point-to-point calls to other IP ViTS devices on the PIP network. For
calls outside the PIP network or multipoint calls, the NASA Video
Teleconference Center (VTC) is required to provide video bridging
support.

### Service Operation

The use of NISN ViTS facilities is coordinated locally at each Center.
ViTS Facilities have the capability to connect to other video
conferencing facilities either within or outside NASA's ViTS Network. As
required, some external or off-network ViTS connections shall need to be
coordinated with the NASA VTC or the vendor Video Bridging Service
(VBS). The NASA VTC is primarily used to support specific IP ViTS
devices, such as the ViTS Roll About System or Desktop Video Appliance,
but may also be used to support ISDN to IP connections. The VBS is a
vendor-provided service that is primarily used to support the majority
of NASA's videoconference needs. Currently VBS does not support ISDN to
IP connections.

The VTC acts as a back-up monitoring station for the vendor VBS during
periods of high visibility mission activities. The VTC operation is
normally located at an off site contractor facility. As directed, during
these special events, the VTC operations staff will be in the MSFC
Gateway.

Any Multipoint ViTS conferences requiring the use of the VTC or VBS
shall be scheduled through each Center's room operators/schedulers. The
NASA VTC hours of operation are Monday-Friday, 6 am-5pm CT, and can be
contacted at 256-961-9387 or 256-961-9388. The NASA VBS can be contacted
at 1-877-789-0670.

ViTS documentation is available on-line. To view NISN's VBS/VTC
scheduling procedures, Videoconference Room Directories, or to learn
more about ViTS, please refer to the Video Conferencing Home Page at
<http://www.nisn.nasa.gov/ServicesPages/Video.html>.

### Service Performance 

a.  As a minimum, ViTS Full Service Conference Rooms shall support up to
    20 NASA community locations participating in 1 to 10 simultaneous
    and independent conferences.

b.  As a minimum, VRA shall support connections to any NASA IP (via the
    NASA VTC) or ISDN room up to 20 simultaneous connections.

c.  As a minimum, DVA (via the NASA Video Teleconferencing Center) shall
    support connections to any NASA IP or ISDN resource up to 20
    simultaneous connections.

d.  The mean time to restore network service for an in-progress
    conference shall be less than or equal to 4 hours.

e.  The mean time to restore service for non-conference impacting
    problems shall be less than 2 business days.

f.  Impacted conferences shall be less than nine per month agency-wide.

g.  Conference availability shall be at least 99.5 percent to include
    room systems, NISN provided transport, and multipoint control
    system.

h.  IP service shall be provided at the [Premium Routed Data Service
    Level](#__RefHeading___Toc185737171).

### Service Maintenance

Maintenance of one designated Full Service Conference Rooms at each NASA
center is provided by NISN. Maintenance for all other Full Service
Teleconferencing rooms is customer funded. Labor for maintenance is NISN
provided; though customers may be asked to fund labor for major ViTS,
VRA, or DVA implementation projects.

Beginning in FY07, NISN has implemented a ViTS Facility Maintenance
Plan. This plan is enacted on all new implementations and existing rooms
can be assessed to be put under the maintenance plan (some upgrades may
be needed in existing rooms to bring equipment up to date prior to the
use of the maintenance plan). It is recommended that all customers
continue to plan for technology refresh of their rooms at the end of the
maintenance plan period, normally every five years. Details of the ViTS
maintenance plan can be found in document [Video Teleconferencing
Services (ViTS) Maintenance Implementation Plan Volume I: Maintenance
Fee
Rooms](http://www.nisn.nasa.gov/DOCUMENTS1/NISN-0030ViTSMaintenanceFee.doc)

## Voice Teleconferencing System (VoTS)

### General Service Description

![](media/image4.jpeg){width="2.609722222222222in" height="2.125in"}NASA
VoTS provides the audio meeting and conferencing needs of the Agency.
VoTS supports the scheduling and setup of operator initiated or meet-me
conferences. VoTS has an analog audio bridging service, which provides
unlimited access to both domestic and international locations. In
addition, this service includes the provisioning and maintenance of
large room audio conferencing systems.

VoTS service is intended to augment the teleconferencing capabilities of
NASA's desktop and conference room telephones. Most NASA telephones are
capable of conferencing at least 4 participants using each Center's
local voice switch. The use of VoTS is not necessary for conferences
with fewer than 5 participants.

Depending on the service level selected, additional features such as
conference recording, transcription and attendees lists are available at
an additional cost.

### Service Levels Description

The VoTS audio bridging service provides four types of teleconference
service levels: Premier, Standard, Unattended and Instant Meeting. Each
service level is separated by specific features available and whether or
not operator assistance is provided.

#### Premier

In a Premier conference, an Operator calls each participant
approximately 10 minutes prior to the scheduled call time, and announces
each participant into the conference. The Operator monitors the meeting
for its duration and can be notified for assistance by using \*0 on the
telephone keypad. This is the most expensive of all the conference
service levels and as such should be used only for critical NASA
conferences that require conference monitoring and/or controlled
participation. This type of conference does need to be scheduled and
failure to cancel a reservation at least 30 minutes prior to the
scheduled start time will incur cancellation charges.

#### Standard

In a Standard conference, an Operator greets the NASA participants as
they join the conference. The Operator frequently monitors the meeting
and can be notified for assistance by using \*0 on the telephone keypad.
The Standard Service level should be used for NASA conferences that
require limited conference monitoring and/or controlled participation.
This type of conference does need to be scheduled and failure to cancel
a reservation at least 30 minutes prior to the scheduled start time will
incur a cancellation charge.

#### Unattended

In an Unattended conference, participants initiate the telephone call
into the conference using a toll free number. The Operator is available
for technical assistance only and does not initiate the conference.
Unattended Service can be used for NASA conferences where participants
require a recurring meeting time. This type of conference does need to
be scheduled and failure to cancel a reservation at least 30 minutes
prior to the scheduled start time will incur a cancellation charge.

#### Instant Meeting

The Instant Meeting is an Unattended Service that is available for use
24-hours a day, 7-days a week and does not require going through the
reservation system. This is NISN's preferred service. It is the least
expensive and cancellation fees do not apply. Each user is set-up with
an account that provides them with a personal toll-free number.
Participants dial into this conference using the toll free number and
Personal Identification Number (PIN) provided by the Call Leader.
Standard Instant Meeting accounts allow for up to 50 participants. Call
Leaders requiring more than 50 ports should contact NISN VoTS Customer
Advocate at 256.961.9402 or 9403. The Call Leader will need to provide
justification for the request.

### Voice Teleconferencing System (VoTS) Facilities

VoTS room systems are differentiated by the number of participants
supported (anywhere from 4-36 microphones). Typical system configuration
consists of an audio mixer, mutable microphones, power amplifier, and
speakers. Additional customization is available to meet specific
customer requirements. All Full Service ViTS rooms have VoTS service and
VoTS can also be integrated with a Video Roll-About (VRA) system for
video teleconferencing.

### Service Operations

#### Reservations

NASA users and NASA contractors can make reservations for voice
conferences by using the Internet based reservation system e-Scheduling,
by calling NASA Reservations at 1-877-232-6272 (NASA), or by faxing the
NASA VoTS Reservation Form to 1-800-728-1300.

E-Schedule features include the ability to:

-   Review your scheduled conference calls

-   Schedule, modify or delete your Unattended and Standard conferences
    in real-time

-   Receive immediate on-line confirmations as well as request email and
    fax confirmations

Features currently not available through E-Scheduling are:
Pre-Notification and Secured Call. To schedule one of these features,
please contact the NASA Reservations Center at 1-877-232-6272 (NASA) to
speak with a reservationist. In addition, contact the NASA Reservations
Center at 1-877-232-6272 (NASA) for voice conferences that have more
than 20 participants or are longer than 8 hours.

Information on how to request an e-Scheduling user name and the NASA
Reservation Form is located on the NISN web site at:
<http://www.nisn.nasa.gov/ServicesPages/Voice_VoTS.html>. A written
confirmation of a conference reservation is available by request. NISN
recommends that all VoTS users request a written confirmation. User
training on the e-Scheduling system is available on the [NISN web
site](http://www.nisn.nasa.gov/ServicesPages/Voice_VoTS.html) in the
section "e-Scheduling".

#### Voice Teleconferencing System (VoTS) Problem Reporting

a.  During the Conference

During a voice conference, if a problem occurs, press \*0 to request the
assistance of an Operator. The Operator shall enter the conference,
attempt to resolve any technical problem and offer further assistance to
the users.

b.  After the Conference

If a problem occurred that prevented the successful completion of the
conference to your satisfaction, contact the NASA Information Support
Center (NISC) at 1-800-424-9920 or submit a trouble ticket at
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. Help Desk Analysts create a
trouble ticket and dispatch it to the NISN Customer Advocates for them
to address during the next business day.

Note:

Using \*0 for Operator assistance during the conference does not report
the problem to the NISC. If you wish to have further assistance, contact
the NISC and ask to open a trouble ticket. A Customer Advocate will
resolve your problem and provide a status.

#### Voice Teleconferencing System (VoTS) Cancellation Policy

VoTS Service Levels of Premier, Standard and Unattended incur
cancellation fees if not cancelled at least 30 minutes prior to the
scheduled conference start time. Cancellation can be made using
e-Scheduling or the NASA Reservation Center at 1-877-232-6272 (NASA). If
there is not time to provide the 30 minutes notice, have at least 2
participants join the conference for a minimum of 2-minutes so that NASA
will be charged a usage fee and not a cancellation fee. If there is a
day or week where a scheduled recurring call (Standing Reservation) will
not take place, just this individual call can be cancelled. Canceling
individual calls shall not change the next recurring scheduled call. The
NASA policy for canceling calls can be found at
<http://www.nisn.nasa.gov/ServicesPages/Voice.html>.

NOTE:

The conference facility does NOT observe holidays. Please cancel any
recurring conferences that fall on a holiday.

To learn more about VoTS and utilizing E-Scheduling for voice
teleconferences, please refer to
<http://www.nisn.nasa.gov/ServicesPages/Voice_VoTS.html>.

### Service Performance

Current performance parameters are in the following paragraph and in
table 2-1. As a minimum, the service shall support up to 350 NASA
community users participating in up to 70 simultaneous and independent
conferences. Service capacity is planned such that Denial of Service
shall be less than 3 percent for any given 30-day period.

[]{#__RefHeading___Toc185737168 .anchor}Table 2-1 VoTS Service
Performance (by Service Category)

+-----------------+---------+----------+---------------+--------------+
| Service         | Av      | Restoral | Coverage      | Impacted     |
|                 | ailabil | Time[^3] | Period        | Conferences  |
| Category        | ity[^2] |          |               |              |
|                 |         |          |               |              |
|                 | **(Per  |          |               |              |
|                 | cent)** |          |               |              |
+=================+=========+==========+===============+==============+
| **In progress   | 99.95   | 4 hr[^4] | 6 a.m.        | \< 9 per     |
| conference**    |         |          | Eastern       | month        |
|                 |         |          | Monday to 6   |              |
|                 |         |          | p.m. Pacific, |              |
|                 |         |          | Friday        |              |
+-----------------+---------+----------+---------------+--------------+
| *               | N/A     | \<2 days | 6 a.m.        | N/A          |
| *Non-conference |         |          | Eastern       |              |
| Impacting       |         |          | Monday to 6   |              |
| Problems**      |         |          | p.m. Pacific, |              |
|                 |         |          | Friday        |              |
+-----------------+---------+----------+---------------+--------------+

### Service Maintenance

Large voice conferencing systems are maintained by NISN with customer
funding. Technology upgrades of the rooms are the funding responsibility
of the customer.

## Switched Voice Services (including Calling Cards and Toll-Free Services)

### General Service Description

NASA\'s Long Distance (LD) telephone requirements are provided using
this service. It includes both domestic and international switched voice
LD services for NASA sites and selected contractor sites. Toll free and
calling cards are part of the service. The GSA Networx, FTS2001 and
Crossover contracts are used to provide these services.

#### Switched Voice Service

Switched Voice Service is primarily used to provide voice service
between NASA centers and to off net (non-NASA) locations, including
international sites.

#### Calling Cards

Calling Cards are primarily used to provide customers voice services
while on official travel or in emergency situations.

#### Toll Free Services

Toll Free Services are primarily used to provide public and NASA
personnel access to NASA information, access to remote electronic mail
(e-mail), voice mail and to contact service help desks around the
Agency.

### Service Operations

Service problems related to Switched Voice Service should be reported to
the NASA Information Support Center (NISC) at 1-800-424-9920 or submit a
trouble ticket at <https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC
is a 24-hours a day, 7 days a week, 365 days a year organization. Help
Desk Analysts create a trouble ticket and dispatch it to the NASA
Customer Advocates for resolution.

### Service Performance

The Long Distance (LD) service performance parameters will be consistent
with the GSA Networx, FTS2001 and Crossover contract terms. Current
service performance parameters are listed in table 2-2

[]{#__RefHeading___Toc185737169 .anchor}Table 2-2 Performance Standards
for Switched Voice

+--------------+---------+---------+--------------+------------------+
| Service      | Av      | M       | Coverage     | Probability Of   |
|              | ailabil | TTR[^6] | Period       | Call Blockage    |
| Category     | ity[^5] |         |              |                  |
|              |         |         |              |                  |
|              | **(Per  |         |              |                  |
|              | cent)** |         |              |                  |
+==============+=========+=========+==============+==================+
| **Switched   | 99.5    | \< 4    | 24X7         | \<1% (P.01 or    |
| Voice**      |         | ho      |              | better)          |
|              |         | urs[^7] |              |                  |
+--------------+---------+---------+--------------+------------------+

### Service Maintenance

Switched Voice Services are maintained by NISN and are provisioned as
part of the service.

## Broadcast Fax Services

### General Service Description

Broadcast Fax provides the capability for NASA users to send a document
to multiple recipients, as established on a preset distribution list,
via a single transmission. The service is a fully managed and
IP-enhanced for in-bound and out-bound fax needs. It supports
traditional fax and integrated web technologies such as Internet-based
fax management, list creation, maintenance and tracking and
administration. This service enables sending to and from fax machines,
e-mail, mainframe systems and the provider's Web page. This service
supports virtually any types of fax application including
desktop-to-fax, broadcasts and customized documents. Broadcast Fax
services are offered via a cost per page.

Broadcast Fax account requests are handled through each Center's
Customer Service Representative via an NSR. Expedited account requests
can be handled though NISN customer service at 256-544-6070.

### Service Operations

If a problem occurs with Broadcast Fax Service, contact the NASA
Information Support Center (NISC) at 1.800.424.9920 or submit a trouble
ticket at <https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a
24-hours a day, 7 days a week, 365 days a year organization. Help Desk
Analysts create a trouble ticket and dispatch it to the NASA Customer
Advocates for resolution.

#### Service Performance

Current service performance parameters are in table 2-3.

[]{#__RefHeading___Toc185737170 .anchor}Table 2-3 Performance Standards
for Broadcast Fax Service

+--------------+---------+---------+--------------+------------------+
| Service      | Av      | M       | Coverage     | Service          |
|              | ailabil | TTR[^9] | Period       | Implementation   |
| Category     | ity[^8] |         |              |                  |
|              |         |         |              |                  |
|              | **(Per  |         |              |                  |
|              | cent)** |         |              |                  |
+==============+=========+=========+==============+==================+
| **Broadcast  | 99.5    | \< 48   | 24X7         | One (1) business |
| Fax**        |         | hou     |              | day\*            |
|              |         | rs[^10] |              |                  |
+--------------+---------+---------+--------------+------------------+

### Service Maintenance

Broadcast Fax Services are maintained by NISN and are provisioned as
part of the service.

## Routed Data

### General Service Description

The Routed Data Service utilizes a backbone infrastructure that includes
both a Resilient Packet Ring (RPR) Core and a carrier managed MPLS
backbone service. Agency policy dictates the use of IP as the Agency
standard protocol for data networking; other protocols are supported on
a legacy basis. A routed data tail circuit is required to provide access
from a location remote from one of the NASA centers or NISN Hubs.

#### Routing Protocols

NISN currently supports several intra-domain routing protocols,
including Static, Routing Information Protocol (RIP), Enhanced Interior
Gateway Routing Protocol (EIGRP) and Open Shortest Path First (OSPF),
and inter-domain routing protocols such as Border Gateway Protocol
(BGP). NISN engineers shall work with customers to select a protocol
consistent with both the customer's requirement and the common network
architecture.

#### Service Demarcation Points

The Service Demarcation Point for NISN IP Routed Data Services shall be
the Local Area Network (LAN) interface of the Wide Area Network (WAN)
router. The LAN interfaces available include 10 Base T, 100 Base-TX, 100
Base FX, and Gigabit (SX, LH, and ZX) Ethernet. Several legacy
interfaces that have been deemed End of Sales shall continue to be
supported until End of Life declarations are issued.

#### Routed Data Category Descriptions

Four service performance categories for routed data services have been
defined: (1) Real-time Critical (2) Mission Critical, (3) Premium, and
(4) Standard. NISN expects that the definitions of these performance
categories shall evolve as they are mapped against the existing and
planned needs of our customers. Note that requirements not satisfied by
these performance categories may be supportable under a custom service.
Real-time Critical and Mission Critical data services are routed over a
carrier managed MPLS backbone. Networks comprised of different service
performance categories can be installed at a customer location to
provide increased reliability.

Service performance metrics for the four categories of domestic IP
routed data service are listed in [Table
2-4.](#__RefHeading___Toc185737171)

######### Real-time Critical Internet Protocol (RCIP) Service

This service provides a real-time critical level of data networking
connectivity with emphasis on meeting real-time telemetry transport
using the Internet Protocol suite. Real-time Critical IP (RCIP) service
is primarily differentiated from Mission Critical IP (MCIP) service in
that it is engineered with a high level of redundancy to achieve the
added level of availability and higher priority for problem resolution.
This service employs the same security and connectivity features and
limitations as the Mission Critical service.

RCIP service is most appropriate for critical space flight mission
support command data and telemetry flows that require (1) a very high
level of availability for mission success and (2) no general Internet
access.

######### Mission Critical Internet Protocol (MCIP) Service

This service provides a mission critical level of data networking
connectivity using the IP suite with controlled access and security
measures. MCIP service is differentiated from RCIP service in that it is
engineered with a lower level of availability. Both function as a closed
system to support space flight mission critical telemetry and data
flows. All systems and facilities connected to the MCIP service shall
meet the specified IT security level. Access to and from the general
Internet and other NASA IP services is extremely limited and provided on
a strictly managed \"by exception\" basis.

MCIP service is most appropriate for critical space flight mission
support data and telemetry flows that require (1) a high level of
availability for mission success and (2) no general Internet access.

######### Premium Internet Protocol (PIP) Service

This service provides a premium level of data networking connectivity
using the IP suite. PIP service is differentiated from Standard Internet
Protocol (SIP) service in that it provides a higher performance level,
higher priority for problem resolution, and is not directly connected to
the general Internet.

PIP service is most appropriate for internal Agency networking
requirements where the Agency\'s operations should be isolated from the
general Internet and is used as a project specific resource.

######### Standard Internet Protocol (SIP) Service

This service provides for basic data networking connectivity using the
IP suite. SIP service is the commodity Internet service that provides
the Agency's link to the Internet in general. It provides basic
universal Internet connectivity with lower performance guarantees or
restrictions on acceptable use.

SIP service is open to the public to enable access to publicly available
NASA information sources such as World Wide Web services.

### Internet Protocol (IP) Routed Data - Security

While security is inherent in the definition of Mission Critical
Service, security features can also be implemented within the context of
Premium Service or Standard Service. For example, route and/or traffic
[filtering](#filtering) may be implemented to provide
[restricted](#restricted) access to certain sub-networks as indicated by
customer or IT Security (ITS) requirements. It is important to note that
NISN views security as a responsibility that is shared with the
customer. NISN works with the customer to identify potential threats and
solutions for satisfying customer needs.

New users or services must complete a [NASA IT Security
Checklist](#nasa-integrated-services-network-nisn-it-security-check-lists.)
to connect to the network.

### Service Operations

If a problem occurs with RCIP or MCIP Routed Data Service, contact the
NISN Communications Managers (Comm Manger) at 301-286-6141 or via
dedicated Mission Voice Loops. The Comm Manager is available 24-hours a
day, 7 days a week, and 365 days a year. The Comm Manager will work with
the appropriate support organizations to resolve service performance
concerns.

If a problem occurs with PIP or SIP Routed Data Service, contact the
NASA Information Support Center (NISC) at 1-800-424-9920 or submit a
trouble ticket at <https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC
is a 24-hours a day, 7 days a week, 365 days a year organization. Help
Desk Analysts create a trouble ticket and dispatch it to the NASA
Customer Advocates for resolution.

### Service Performance

The performance specifications in Table 2-1 are stated from
NISN-location to NISN-location, e.g., center-to-center, and these
specifications apply to Continental United Stated (CONUS) connections
only. The customer is also advised that NISN cannot guarantee
performance beyond NISN's connections to the Internet.

[]{#__RefHeading___Toc185737171 .anchor}Table 2-4 Performance Standards
for IP Routed Data (by Service Category)

+-----------+-------+-------+--------------+-----------+-------------+
| Service   | Av    | Res   | Coverage     | A         | Round Trip  |
|           | ailab | toral | Period       | cceptable | Time[^12]   |
| Category  | ility | Ti    |              | Packet    |             |
|           | [^11] | me^^ |              | Loss      |             |
|           |       |       |              |           |             |
|           | **(   |       |              | (Percent) |             |
|           | Perce |       |              |           |             |
|           | nt)** |       |              |           |             |
+===========+=======+=======+==============+===========+=============+
| **        | 99.98 | \< 1  | 24X7         | 0.001     | \<120 ms    |
| Real-time |       | min   |              |           |             |
| C         |       | [^13] |              |           |             |
| ritical** |       |       |              |           |             |
+-----------+-------+-------+--------------+-----------+-------------+
| **Mission | 99.95 | 2     | 24X7         | 0.001     | \<120 ms    |
| C         |       | hr^^ |              |           |             |
| ritical** |       |       |              |           |             |
+-----------+-------+-------+--------------+-----------+-------------+
| **        | 99.50 | 4     | 24X7         | \<1.0     | \<100 ms    |
| Premium** |       | h     |              |           |             |
|           |       | r[^14 |              |           |             |
|           |       | ]MTTR |              |           |             |
+-----------+-------+-------+--------------+-----------+-------------+
| **S       | 99.50 | \<24  | 6 a.m.       | 1.0       | \<250 ms    |
| tandard** |       | hr^   | Eastern      |           |             |
|           |       | ^[^1 | Monday to 6  |           |             |
|           |       | 5]^,^ | p.m.         |           |             |
|           |       | MTTR  | Pacific,     |           |             |
|           |       |       | Friday       |           |             |
+-----------+-------+-------+--------------+-----------+-------------+

#### Internet Protocol (IP) Routed Data - Definition of Terms

######### Packet Loss

Packets transmitted from the source NISN/customer interface, i.e., the
connection between the NISN router and the customer router, but not
received at the destination NISN/customer interface. Acceptable loss is
measured over any 24-hour interval.

######### Time to Restore a Service 

NISN shall make every effort through its contractors and carriers to
restore interrupted service in a timely manner. A requirement has been
levied by NISN on itself, its contractors and its carriers to return
NISN services to an operational state as indicated in table 2-4

PIP and SIP time to restore is based on a calculated mean.
Mean-Time-To-Restore (MTTR) for PIP and SIP services is calculated on
outage data gathered in the proceeding 90 days and is based on the time
NISN receives an outage notification to the time the service is
restored. A mean time calculation can result in individual PIP or SIP
service outages that exceed 4 or 24 hours respectively without exceeding
the 4 or 24 hour MTTR.

Circumstances that can cause service outages to exceed the above limits
are man made and natural disasters such as destruction of facilities or
cabling. Facility access restrictions or customer directed delays could
also cause service outages to exceed the above limits.

######### Availability

Service availability is measured over the period of one year (8,760
hours). A failure is defined as an event that results in a packet loss
greater than 5 percent within NISN's WAN. Service availability excludes
scheduled preventative maintenance or upgrades. NISN's approach to
measuring availability includes the customer's Service Access Point
(SAP) as well as the availability of the shared resources within the
network, i.e., the backbone.

######### Round-Trip-Time

Round Trip Time is measured by utilizing the Internet Control Message
Protocol (ICMP) utility of Packet Inter-Network Groper (PING). Since
PING utilizes TCP protocol 1; it has the lowest priority during transit
across the network. This means that all other traffic receives a higher
priority during queuing within the router on a network link. Because of
this, an average is calculated to ensure that anomalies shall not skew
the data. For the purpose of latency measurements NISN uses an average
of 100 packets each sent with a 36 byte payload.

### Service Maintenance

Routed Data Services are maintained by NISN and are provisioned as part
of the service.

## NASA Internet Protocol (IP) Address Space

NASA IP address space includes any IP address assigned to the NASA OrgID
with the American Registry of Internet Names (ARIN). NISN may assign
NASA IP address space for customer use for the life of approved NASA
projects. NISN retains management authority over the assignment of this
address space assigned to Customers. Customers may not delegate the use
of this address space to third parties. Customers must cease to use this
address space upon the completion of the project it was intended to
support, subject to memorandum of agreement (MOA) to be executed upon
assignment of the address space to the Customer

## Dedicated Mission Voice and Data

### Dedicated Mission Voice Services

#### General Service Description

Dedicated Mission Voice Service encompasses a wide range of services and
service complexity. At its simplest, this service can be a dedicated
point-to-point "shout down" circuit with no signaling. However, the
majority of these services consist of a system of highly reliable,
dedicated voice circuits working in conjunction with a switching and
conferencing system to create voice loops. These voice loops
interconnect the different voice distribution systems that support the
diverse mission control centers within the Agency.

Conferencing is a distributed capability. The NISN Dedicated Voice
service works as a system with the various NASA Center/customer voice
distribution systems. The service, in combination with the NASA Center
systems, is scalable to meet all current and future mission critical
loop distribution requirements.

Dedicated Mission Voice services are currently available at 8 kilobits
per second (kbps) compressed and 64 kbps uncompressed rates and two
levels of performance criticalities, Real-time Mission Critical and
Mission Critical

######### Real-time Mission Critical

This level of service provides the highest reliability with no single
points of failure. Diversely routed infrastructure is provided and has
the highest priority for service repair.

######### Mission Critical

This level of service provides high reliability with redundant support
hardware, but depending upon the requirement, may not include diversely
routed infrastructure.

#### Service Operations

If a problem occurs with Dedicated Voice Service, contact the NISN
Communications Managers (Comm Manager) at 301-286-6141. The Comm Manager
is available 24-hours a day, 7 days a week, 365 days a year. The Comm
Manager will work with the appropriate support organizations to resolve
the problem.

#### Service Performance

Current service performance parameters are listed in table 2-5

[]{#__RefHeading___Toc185737172 .anchor}Table 2-5 Performance Standards
for Dedicated Mission Voice (by Service Category)

+-----------+-------+-------+------------+--------------+------------+
| Service   | Av    | Res   | Coverage   | Analog       | Latency    |
|           | ailab | toral | Period     | Channel      | (Round     |
| Category  | ility | Time  |            | Parameters   | Trip       |
|           | [^16] | [^17] |            |              | Time)[^18] |
|           |       |       |            |              |            |
|           | **(   |       |            |              |            |
|           | Perce |       |            |              |            |
|           | nt)** |       |            |              |            |
+===========+=======+=======+============+==============+============+
| **        | 99.98 | \< 5  | 24X7       | 300 to 3400  | \<500 ms   |
| Real-time |       | min   |            | Hz           |            |
| C         |       | [^19] |            | (+/-0.5dB)   |            |
| ritical** |       |       |            |              |            |
|           |       |       |            | \<1% total   |            |
|           |       |       |            | harmonic     |            |
+-----------+-------+-------+------------+--------------+------------+
| **Mission | 99.95 | 2     | 24X7       | distortion   | \<500 ms   |
| C         |       | hr^^ |            |              |            |
| ritical** |       |       |            | \<-40dBmO    |            |
|           |       |       |            | noise level  |            |
+-----------+-------+-------+------------+--------------+------------+

#### Service Maintenance

Dedicated Mission Voice Services are maintained by NISN and are
provisioned as part of the service.

### Dedicated Mission Data

#### General Service Description

Dedicated Mission Data Service is used to supplement NISN Mission Routed
Data services or it may constitute part of a total network solution
provided to a specific customer. Each dedicated mission data service is
a customized assessment for an individual customer requirement. The
current infrastructures used to support the Dedicated Mission data
service are the Network Service Assurance Plan (NSAP) network and the
NISN NASCOM Network.

Dedicated Mission Data service is primarily used for space flight
mission critical applications and is currently available at rates from
as low as 9.6 kbps up to multiples of 1.5 megabits per second (Mbps).
The most common rates are 56kpbs and 1.5 Mbps. There are two levels of
performance criticalities, Real-time Mission Critical and Mission
Critical.

######### Real-time Mission Critical

This level of service provides the highest reliability with no single
points of failure. Diversely routed infrastructure is provided and has
the fastest repair service.

######### Mission Critical

This level of service provides high reliability with redundant support
hardware, but depending upon the requirement, may not include diversely
routed infrastructure.

#### Service Operations

If a problem occurs with Dedicated Voice Service, contact the NISN
Communications Managers (Comm Manager) at 301-286-6141. The Comm Manager
is available 24-hours a day, 7 days a week, 365 days a year. The Comm
Manager will work with the appropriate support organizations to resolve
the problem.

#### Service Performance

Current service performance parameters are listed in table 2-6

[]{#__RefHeading___Toc185737173 .anchor}Table 2-6 Performance Standards
for Dedicated Mission Data (by Service Category)

+------------------+-------------+-------------+----------------------+
| Service          | Availa      | Restoral    | Coverage Period      |
|                  | bility[^20] | Time        |                      |
| Category         |             |             |                      |
|                  | **          |             |                      |
|                  | (Percent)** |             |                      |
+==================+=============+=============+======================+
| **Real-time      | 99.98       | \< 1        | 24X7                 |
| Critical**       |             | min[^21]    |                      |
+------------------+-------------+-------------+----------------------+
| **Mission        | 99.95       | \<2 hr^^   | 24X7                 |
| Critical**       |             |             |                      |
+------------------+-------------+-------------+----------------------+

#### Service Maintenance

Dedicated Mission Voice Services are maintained by NISN and are
provisioned as part of the service.

## High Rate Data/Video Services (HRDVS)

### General Service Description

The High Rate Data and video Service (HRDVS) is a one-way, simplex,
multi-mode/multi-channel system designed for operation over a full
C-band 36 Megahertz (MHz) domestic communications satellite transponder.
Specifically, it is used to provide the communications path between the
White Sands Complex (WSC) and the user at Johnson Space Center (JSC).
Additionally, a technical monitoring capability exists within the GSFC
technical control facility. This service provides a medium for transport
of a Tracking and Data Relay Satellite System user's digital baseband
return link when the rates are two Mbps or higher. The system has an
upper limit for the user's data of 48 Mbps. The satellite transponder
utilized for HRDS services is also configurable to provide video
transmission from WSC to JSC and GSFC or from Kennedy Space Center (KSC)
to JSC, MSFC, and GSFC.

### Service Operations

If a problem occurs with High Rate Data/Video Service, contact the NISN
Communications Managers (Comm Manager) at 301-286-6141. The Comm Manager
is available 24-hours a day, 7 days a week, 365 days a year. The Comm
Manager will work with the appropriate support organizations to resolve
the problem.

### Service Performance

Current service performance parameters are listed in table 2-7.

[]{#__RefHeading___Toc185737174 .anchor}Table 2-7 Performance Standards
for High Rate Data/Video Services

+--------------+----------+----------+-----------------+--------------+
| Service      | A        | Restoral | Coverage Period | Latency      |
|              | vailabil | Time     |                 | (Round Trip  |
| Category     | ity[^22] |          |                 | Time)        |
|              |          |          |                 |              |
|              | **(Pe    |          |                 |              |
|              | rcent)** |          |                 |              |
+==============+==========+==========+=================+==============+
| **HRDVS**    | 99.95%   | \< 2     | 24X7            | \<540 ms     |
|              |          | hr[^23]  |                 |              |
+--------------+----------+----------+-----------------+--------------+

### Service Maintenance

High Rate Data/Video Services are maintained by NISN and are provisioned
as part of the service.

## Data Center Network and Security Services (DCNSS)

### General Service Description

DCNSS provides a secure, highly available data center (centralized or
distributed) networking infrastructure for computing systems and
services that requires a redundant infrastructure managed at an Agency
level. Customers are able to tailor their services based on a grouping
of service options and levels that meet their projects/programs
requirements.

a.  LAN connectivity for Agency wide Server applications

```{=html}
<!-- -->
```
1.  Switch ports (10,100,1000Mbps)

2.  IP address assignment

3.  Domain Name Service

4.  Server network-based load balancing

```{=html}
<!-- -->
```
b.  Network Security Services

```{=html}
<!-- -->
```
1.  Firewall support

2.  Proxy server support

3.  Intrusion Detection

```{=html}
<!-- -->
```
c.  WAN connectivity

```{=html}
<!-- -->
```
1.  Direct connection to NISN PIP and SIP services

2.  Network-to-Network Virtual Private Network (VPN) [is provided by the
    Corporate VPN (CVPN) service to other centers and partners. CVPN
    provides an encrypted tunnel between two networks. NISN's CVPN
    supports the Triple Data Encryption Standard (3DES). The devices
    used are Federal Information Processing Standard (FIPS) 140-2
    compliant]{.underline}.

3.  Client-to-Network VPN tunnels for system administrator access to
    server resources

As an extension to traditional NISN WAN services, DCNSS extends the
network support to NASA Data Centers by providing the following three
distinct networks

a.  Private Network -- supports Data Center servers for Agency wide
    services not requiring Internet access

b.  Public Network -- supports Data Center servers for Agency wide
    services intended to support services that extend beyond NASA to the
    Public Internet

c.  Demilitarized Zone (DMZ) Network -- Provides a secure path for
    traffic flowing between the Private and Public networks and to the
    NISN WAN

### Service Operations

If a problem occurs with the DCNSS Service, contact the NASA Information
Support Center (NISC) at 1.800.424.9920 or submit a trouble ticket at
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a 24-hours a
day, 7 days a week, 365 days a year organization. Help Desk Analysts
create a trouble ticket and dispatch it to the NASA Customer Advocates
for resolution.

### Service Performance

Current service performance parameters are shown in Table 2-8

[]{#__RefHeading___Toc185737175 .anchor}Table 2-8 Current Service
Performance Parameters

  -----------------------------------------------------------------------------------------------------------
  Service Options/    Connectivity   Firewall     Sys Admin VPN CVPN          Intrusion   Domain    Proxy
  Service Metrics     to PIP/SIP     Management   Connections   Connections   Detection   Name      Service
  (per Service Level) Network                                                             Service   
  ------------------- -------------- ------------ ------------- ------------- ----------- --------- ---------
  **Premium**[^24]                                                                                  

  Availability        99.50          99.50        99.50         99.5          99.50                 99.50

  Restoral            \< 4 hrs.      \< 4 hrs.    \< 4 hrs.     \< 4 hrs.     \< 4 hrs.             \< 4 hrs.
  Time[^25]MTTR                                                                                     

  Acceptable Packet   \< 1.0         \< 1.0       \< 1.0        \< 1.0                              
  Loss (%)                                                                                          

  **Standard**                                                                                      

  Availability        99.50          99.50        99.50         99.50         99.50                 99.50

  Restoral            \< 24 hrs.     \< 24 hrs.   \< 24 hrs.    \<24 hrs.     \< 24 hrs.            \< 24
  Time^^MTTR                                                                                       hrs.

  Acceptable Packet   1.0            1.0          1.0           1.0                                 
  Loss (%)                                                                                          

  **Custom**                                                                                        

  Availability        TBD            TBD          TBD           TBD                                 

  Restoral            TBD            TBD          TBD           TBD                                 
  Time^^MTTR                                                                                       

  Acceptable Packet   TBD            TBD          TBD           TBD                                 
  Loss (%)                                                                                          

  **All Levels**                                                                                    

  **Change Request    N/A            \< 24 hrs.   \< 24 hrs.    TBD           \< 24 hrs.  \< 24     \< 24
  Completion**[^26]                                                                       hrs.      hrs.

  **Port Activation   \< 24 hrs.                                                                    
  Request**                                                                                         
  -----------------------------------------------------------------------------------------------------------

### Service Maintenance

DCNSS is maintained by NISN and is 100% Customer funded. Overall service
costs are evaluated annually. The operations, refresh (5-year technology
refresh model is used), and maintenance costs of the shared
infrastructure components are distributed across customers based on
"port count".

##  Directory Services (X.500)

### General Service Description

The NASA Directory Service is based upon the international X.500
standard for the organization and presentation of a hierarchical
directory service infrastructure. The NISN organization provides an
infrastructure consisting of an Agency level system and centralized
support of center level systems for maintaining the disbursed hardware
and software systems.

The X.500 was primarily established to assist in the standardization of
the various NASA electronic mail addressing and look-up functions. The
use of the directory Services has expanded to include Fax number, pager
number, building and room, telephone number, a unique identifier, and
address look-up information.

A summary of service supported by the X.500 service includes;

a.  Provide the interconnections to each center manager X.500 system to
    provide an overall agency service

b.  Provide Certificate Revocation List replication to each center
    managed X.500 to support the operation of the Agency's Public Key
    Infrastructure

c.  Provide Mail Relay services to center, program and project offices

d.  Provide a web based interface to provide users email address, phone
    number, building and room number to facilitate communications

e.  Provide system administration, configuration management, and
    security services for the Agency X.500 primary and backup server
    located at MSFC

```{=html}
<!-- -->
```
1.  Create, review, and maintain documentation such as plans, procedures
    and work instructions

2.  Provide white page directory lookup services on the
    http://directory.nasa.gov website

3.  Monitor statistics of server health including CPU usage on the
    servers

4.  Monitor message queues

5.  24x7 on-call support

### Service Operations

If a problem occurs with the X.500 Service, contact the NASA Information
Support Center (NISC) at 1.800.424.9920 or submit a trouble ticket at
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a 24-housr a
day, 7 days a week, 365 days a year organization. Help Desk Analysts
create a trouble ticket and dispatch it to the NASA Customer Advocates
for resolution.

### Service Performance

There are no performance metrics for this service.

### Service Maintenance

The X.500 Services are maintained by NISN and are provisioned as part of
the service.

## Domain Name Service (DNS)

### General Service Description

NISN Agency Domain Name Service (DNS) provides NASA, NASA affiliates
(such as educational institutions), and the public Internet with domain
name resolution services. The Agency DNS group serves as the Agency's
primary authorized interface with the American Registry for Internet
Numbers (ARIN) and other registration authorities in the registration
and maintenance of IP address space and public domain names that are
assigned to the NASA Agency.

NISN registers NASA.GOV domain names and administers the NASA.GOV
Internet domain naming policies and conventions. Sub-domain management
is conducted by the appropriate NASA centers/organizations. DNS
activities supported include additions, removals, and changes to the DNS
database. The Agency DNS group also provides secondary DNS services for
NASA Centers, projects and affiliates on an as needed basis.

NISN maintains and supports a high-availability, distributed network
configuration of several DNS services. DNS is offered through both the
PIP and SIP services.

Creation of new domain names shall require the approval of NISN
management in accordance with Agency policies.

### Service Operations

If a problem occurs with the DNS Service, contact the NASA Information
Support Center (NISC) at 1.800.424.9920 or submit a trouble ticket at
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a 24-hours a
day, 7 days a week, 365 days a year organization. Help Desk Analysts
create a trouble ticket and dispatch it to the NASA Customer Advocates
for resolution.

### Service Performance

There are no performance metrics for this service. Note that there are
three DNS servers, one at each of the major network peering points. Any
one of the three is capable of providing the entire Agency DNS queries.

### Service Maintenance

The DNS Services are maintained by NISN and are provisioned as part of
the service.

## International Services

### General Service Description

The International data distribution services are provided to many of
NASA's International Partners and agencies through cooperative
arrangements. Rather than purchase dedicated circuits for each
requirement, cooperative consolidation and integration of various
requirements into an economical infrastructure provide the basic
connectivity for programmatic requirements for the transport of data,
voice, facsimile, electronic mail, and video.

#### Mission

NISN provides Mission International Services between the U.S. and
various international locations to meet special Mission-Critical
requirements. The vast majority of Mission International Services are
dedicated, point-to-point interfaces provided by commercial
communication carriers. Mission Support International Services are also
available via digital backbone satellite and terrestrial/undersea cable
circuits between NASA and various International locations.

#### Mission Support

Expansion of the Mission Support International Services network is
accomplished using one or more of the following approaches:

a.  Sharing NISN's backbone circuit extensions with International
    Partner Agency networks

b.  Providing NISN tail circuit extensions from a NASA site to an
    International Partner Agency location

c.  Establishing research network or general internet peering
    arrangements

    New users or services must complete a [NASA IT Security
    Checklist](#nasa-integrated-services-network-nisn-it-security-check-lists.)
    to connect to the NISN IP networks.

### Service Operations

If a problem occurs with a non-mission critical service, contact the
NASA Information Support Center (NISC) at 1-800-424-9920 or submit a
trouble ticket at <https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC
is a 24-hours a day, 7 days a week, 365 days a year organization. Help
Desk Analysts create a trouble ticket and dispatch it to the NASA
Customer Advocates for resolution.

If a problem occurs with a mission critical service, contact the NISN
Communications Managers (Comm Manger) at 301 286 6141 or via dedicated
Mission Voice Loops. The Comm Manager is available 24-hours a day, 7
days a week, 365 days a year. The Comm Manager will work with the
appropriate support organizations to resolve service performance
concerns

### Service Performance

International service's performance is tailored to a specific set of
customer requirements and is subject to the performance levels offered
by vendors.

### Service Maintenance

The International Services are maintained by NISN and are provisioned as
part of the service.

## Russian Services

### General Service Description

Russian Services provides a variety of support to NASA projects working
in association with the Russian Federation. The service supports
numerous flight projects and the interchange of data and information
between NASA's and Russia's science communities.

The current infrastructure in Russia consists of telecommunications and
end user Automated Data Processing (ADP) services capable of supporting
mission operations as well as voice, data and video services required to
sustain and synchronize International Space Station (ISS) activities in
Russia and Houston. The locations receiving services in the Moscow area
for ISS support include: the Volga Apartments, Khrunichev State Research
and Production Facility, Moscow Mission Control Center, the Russia Space
Corporation - Energia, Gagarin Cosmonaut Training Center, U.S. Embassy
in Moscow and the Institute for Biomedical Problems.

### Service Operations

If a problem occurs with Secure Communications, users will obtain
service help by calling the phone number provided to them for this
purpose. All other problems should be reported to the NASA Information
Support Center (NISC) at 1-800-424-9920 or submit a trouble ticket at
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a 24-hours a
day, 7 days a week, 365 days a year organization, and will dispatch the
problem to the Russian Services Group.

### Service Performance

Current service performance parameters for Russia IT Services are shown
in Table 2-9

[]{#__RefHeading___Toc185737176 .anchor}Table 2-9 Russia IT Services and
Performance Standards

+----------------+-------+-------+-------+----------------------------+
| Service        | Av    | MTTR  | Lat   | Other                      |
|                | ailab |       | ency\ |                            |
|                | ility |       | (     |                            |
|                |       |       | Round |                            |
|                | (Per  |       | Trip) |                            |
|                | cent) |       |       |                            |
+----------------+-------+-------+-------+----------------------------+
| Mission        | 99.98 | \< 5  | \<    | \< 1 percent Harmonic      |
| Critical Voice |       | Mi    | 700   | distortion                 |
|                |       | nutes | ms    |                            |
|                |       |       |       | \<-40dBM0 noise level      |
|                |       |       |       |                            |
|                |       |       |       | Capability to immediately  |
|                |       |       |       | switch to alternate path.  |
+----------------+-------+-------+-------+----------------------------+
| Mission        | 99.95 | \< 2  | \<    | \< 1 percent Harmonic      |
| Non-Critical   |       | Hours | 700   | distortion                 |
| Voice          |       |       | ms    |                            |
|                |       |       |       | \< -40dBM0 noise level     |
+----------------+-------+-------+-------+----------------------------+
| Admin          | 99.95 | \< 4  | \<    | P3 Grade of Service        |
| Voice/Fax      |       | Hours | 300   |                            |
|                |       |       | ms    |                            |
+----------------+-------+-------+-------+----------------------------+
| Mission        | 99.98 | \< 1  | \<    | Capability to immediately  |
| Critical Data  |       | M     | 300   | switch to alternate data   |
|                |       | inute | ms    | path.                      |
|                |       |       |       |                            |
|                |       |       |       | \<. 001 percent Packet     |
|                |       |       |       | Loss                       |
+----------------+-------+-------+-------+----------------------------+
| Mission        | 99.95 | \< 2  | \<    | \<. 001 percent packet     |
| Non-Critical   |       | Hours | 300   | loss                       |
| Data           |       |       | ms    |                            |
+----------------+-------+-------+-------+----------------------------+
| Admin Data     | 99.95 | \< 4  | \<    | \< 1 percent packet loss   |
|                |       | Hours | 300   |                            |
|                |       |       | ms    |                            |
+----------------+-------+-------+-------+----------------------------+
| Mission/Admin  | 99.95 | \< 4  | \<    |                            |
| Video          |       | Hours | 300   |                            |
|                |       |       | ms    |                            |
+----------------+-------+-------+-------+----------------------------+
| Admin Video    | 99.95 | \< 4  | \<    |                            |
|                |       | Hours | 300   |                            |
|                |       |       | ms    |                            |
+----------------+-------+-------+-------+----------------------------+

### Service Maintenance

The Russian Services are maintained by NISN and are provisioned as part
of the service.

## Network Modeling Services

### General Service Description

The NISN Network Modeling Service provides the validation of networks
and evaluates the implementation of new technologies. The NISN Network
Modeling Service uses virtual computer simulation techniques. The
service also provides:

a.  Provision of the NISN WAN test bed to evaluate future space
    operations technology and systems.

b.  Modeling and simulation techniques to determine changing
    requirements impacts on the NISN networks, utilizing system
    engineering methodologies.

c.  Investigation of operational impacts such as cost, technology,
    support and performance, of new products and services prior to
    implementation on the WAN.

d.  Supports collaboration with engineers, laboratories, and other
    Federal Networks with like interests, as well as represent NASA at
    conference and working groups to development an understanding of the
    trends and changes in evolving network technologies.

### Service Operations

The standard operating hours for the laboratory support is 8 am to 5 pm,
Monday-Friday. Off hours can be scheduled in advance. Laboratory support
is prioritized as follows: 1) Production service impacts, 2) Emerging
standards and technology, and 3) Policy guidance (ex. IPv6).

If a problem occurs with the Network Modeling Service, contact the NASA
Information Support Center (NISC) at 1-800-424-9920 or submit a trouble
ticket at <https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a
24-hours a day, 7 days a week, 365 days a year organization. Help Desk
Analysts create a trouble ticket and dispatch it to the NASA Customer
Advocates for resolution.

### Service Performance

There is no standard performance metrics for this service. Each instance
of use is tailored to the project specific requirements.

### Service Maintenance

Network Modeling Services are maintained by NISN and are provisioned as
part of the service; however, some services will require customer
funding.

## Custom Services 

### General Service Description

Custom telecommunication and networking services are specifically
designed and engineered to meet unique NASA programmatic requirements.
Each program determines the unique attributes of the data distribution
services in such terms as security, availability, redundancy, and
features that provide the optimum trade-off between cost and program
success.

Custom Services may be used both for space flight mission critical
applications and for general administrative support requirements
possessing unique attributes.

### Service Operations

If a problem occurs with Mission or Mission Critical Custom Service
contact the GSFC Communication Manager at 301-286-6141. The GSFC
Communications Manager is a 24-hour a day, 7 day a week, 365 day a year
trouble reporting center.

If a problem occurs with the Mission Support Custom Service, contact the
NASA Information Support Center (NISC) at 1-800-424-9920 or submit a
trouble ticket at <https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC
is a 24-hours a day, 7 days a week, 365 days a year organization. Help
Desk Analysts create a trouble ticket and dispatch it to the NASA
Customer Advocates for resolution.

### Service Performance

There are no standard performance metrics for custom services.
Performance metrics for custom services are dependent on the type of
service requested and the ability of NISN and its providers to meet
those requirements. The best possible Service Level Agreements (SLA)
guarantees are provided to the customer when all dependencies have been
identified.

### Service Maintenance

Custom Services are maintained by NISN and are provisioned as part of
the service.

## Intrusion Detection Services (IDS)

### General Service Description

The Intrusion Detection Services provide NASA a monitoring capability to
detect and respond to network intrusions, or unauthorized access/use of
NASA networking resources. Each center on NISN is monitored via an
Intrusion Detection Sensor, as well as each of the Internet peering
locations.

The NISN Security Operations Center (NSOC), which is a 24x7x365 Tier-1
support desk, is located at Marshall Space Flight Center. The NSOC
monitors all of the sensors across the network and contacts the affected
center if an intrusion is detected. Daily reports are generated and
delivered to each center IT Security Manager with a summary of all
attacks detected.

### Service Operations

If a problem occurs with the IDS Service, contact the NASA Information
Support Center (NISC) at 1-800-424-9920 or submit a trouble ticket via
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a 24-hours a
day, 7 days a week, 365 days a year organization. Help Desk Analysts
create a trouble ticket and dispatch it to the NSOC for resolution.

### Service Performance

[]{#__RefHeading___Toc185737177 .anchor}Table 2-10 IDS Service
Performance

+------------------+-------+-------+----------------------------------+
| Service          | Av    | MTTR  | Other                            |
|                  | ailab |       |                                  |
|                  | ility |       |                                  |
|                  |       |       |                                  |
|                  | (Per  |       |                                  |
|                  | cent) |       |                                  |
+------------------+-------+-------+----------------------------------+
| Intrusion        | 99    | \< 12 |                                  |
| Detection Sensor |       | Hours |                                  |
| (IDS)            |       |       |                                  |
+------------------+-------+-------+----------------------------------+
| Incident         | 99    | \< 2  | \< 2 Hours to notify appropriate |
| De               |       | Hours | personnel and generate High      |
| tection/Response |       |       | Priority Event                   |
+------------------+-------+-------+----------------------------------+

### Service Maintenance

The IDS Services are maintained by NISN and are provisioned as part of
the service.

## Network Timing Protocol (NTP) Service

### General Service Description

The Network Time Protocol (NTP) is an Internet Protocol that is used to
synchronize a computer's clock to a reference time source. The NISN NTP
Service provides NASA with a stratum time reference source. This
supplies a distribution service to Center and Project lower stratum
level distribution servers. The NISN NTP service consists of servers
located on both PIP and SIP at Marshall Space Flight Center, Goddard
Space Flight Center, and Ames Research Center

### Service Operations

If a problem occurs with the NTP Service, contact the NASA Information
Support Center (NISC) at 1-800-424-9920 or submit a trouble ticket at
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is a 24-hours a
day, 7 days a week, 365 days a year organization. Help Desk Analysts
create a trouble ticket and dispatch it to the ENMC for resolution.

### Service Performance

There are no performance metrics for this service.

### Service Maintenance

The NISN NTP Services are maintained by NISN and are provisioned as part
of the service.

## Layer 2 Virtual Private Network (L2VPN) Service

### General Service Description

The L2VPN Service utilizes a backbone infrastructure that includes both
a Resilient Packet Ring (RPR) Core and a NISN-managed MPLS backbone
service. A LAN extension to the customer network is required. The L2VPN
service is appropriate when the Customer requires transparent extension
of LAN services between two physical locations. Unlike Corporate VPN
service (under DCNSS), L2VPN does not provide data encryption. Use of
L2VPN as a solution will be the decision of NISN based on established
NISN and Agency policy. L2VPN service is offered only at established
NISN backbone services locations.

#### Service Demarcation Points

The service demarcation point for the NISN L2VPN Service shall be the
Local Area Network (LAN) interface of the NISN L2VPN equipment. The LAN
interfaces available include 10 Base T, 100 Base-TX, 100 Base FX,
Gigabit (SX, LH, and ZX) Ethernet and 10 Gigabit Ethernet.

#### L2VPN Category Descriptions

Two service performance categories for L2VPN services have been defined:
(1) Premium and (2) Standard. NISN expects that the definitions of these
performance categories shall evolve as they are mapped against the
existing and planned needs of our customers. Note that requirements not
satisfied by these performance categories may be supportable under a
custom service.

#### Premium L2VPN Service

This service provides a premium level of data networking connectivity
using the IP suite. PIP service is differentiated from Standard Internet
Protocol (SIP) service in that it provides a higher performance level,
higher priority for problem resolution, and is not directly connected to
the general Internet.

PIP service is most appropriate for internal Agency networking
requirements where the Agency\'s operations should be isolated from the
general Internet and is used as a project specific resource.

#### Standard L2VPN Service

This service provides for basic data networking connectivity using the
IP suite. SIP service is the commodity Internet service that provides
the Agency's link to the Internet in general. It provides basic
universal Internet connectivity with lower performance guarantees or
restrictions on acceptable use.

SIP service is open to the public to enable access to publicly available
NASA information sources such as World Wide Web services.

#### L2VPN - Security

By definition, L2VPN services are restricted to defined source and
destination parameters to limit access to certain sub-networks as
indicated by customer or IT Security (ITS) requirements. It is important
to note that NISN views security as a responsibility that is shared with
the customer. NISN works with the customer to identify potential threats
and solutions for satisfying customer needs.

New users or services must complete a [NASA IT Security
Checklist](#nasa-integrated-services-network-nisn-it-security-check-lists.)
to connect to the network.

### Service Operations

If a problem occurs with an L2VPN service, contact the NASA Information
Support Center (NISC) at 1-800-424-9920 or submit a trouble ticket at
<https://arsweb.msfc.nasa.gov/ttsubmit.asp>. The NISC is operated
24-hours a day, 7 days a week, 365 days a year. Help Desk Analysts
create a trouble ticket and dispatch it to NASA Customer Advocates for
resolution.

### Service Performance

The performance specifications in Table 2-11 are stated from
NISN-location to NISN-location, e.g., Center-to-Center, and these
specifications apply to Continental United Stated (CONUS) connections
only. The customer is also advised that NISN cannot guarantee
performance beyond NISN's connections to the Internet.

[]{#__RefHeading___Toc185737178 .anchor}Table 2-[11]{.underline}
Performance Standards for L2VPN (by Service Category)

+--------------+---------+---------+-----------------+----------------+
| Service      | Ava     | R       | Coverage Period | Round Trip     |
|              | ilabili | estoral |                 | Time[^28]      |
| Category     | ty[^27] | Time^^ |                 |                |
|              |         |         |                 |                |
|              | **(Per  |         |                 |                |
|              | cent)** |         |                 |                |
+==============+=========+=========+=================+================+
| **Premium**  | 99.50   | 4       | 24X7            | \<100 ms       |
|              |         | hr[^29] |                 |                |
+--------------+---------+---------+-----------------+----------------+
| **Standard** | 99.50   | \<24    | 6 a.m. Eastern  | \<250 ms       |
|              |         | hr^^[  | Monday to 6     |                |
|              |         | ^30]^,^ | p.m. Pacific,   |                |
|              |         |         | Friday          |                |
+--------------+---------+---------+-----------------+----------------+

######### Availability

Service availability is measured over the period of one year (8,760
hours). A failure is defined as an event that results in a loss of
connectivity in excess of 5 seconds. Service availability excludes
scheduled preventative maintenance or upgrades. NISN's approach to
measuring availability includes the customer's Service Demarcation Point
(SDP) as well as the availability of the shared resources within the
network, i.e., the backbone.

######### Restoral Time 

NISN shall make every effort through its contractors and carriers to
restore interrupted service in a timely manner. A requirement has been
levied by NISN on itself, its contractors and its carriers to return
NISN services to an operational state as indicated in Table 2-11.

Restoral time is based on a calculated mean. Mean-Time-To-Restore (MTTR)
for L2VPN services is calculated on outage data gathered in the
proceeding 90 days and is based on the time NISN receives an outage
notification to the time the service is restored. A mean time
calculation can result in individual L2VPN service outages that exceed 4
or 24 hours respectively without exceeding the 4- or 24- hour MTTR.

Circumstances that can cause service outages to exceed the above limits
are man made and natural disasters such as destruction of facilities or
cabling. Facility access restrictions or customer-directed delays could
also cause service outages to exceed the above limits.

######### Round-Trip-Time

Round Trip Time is measured by utilizing the Internet Control Message
Protocol (ICMP) utility of Packet Inter-Network Groper (PING). Since
PING utilizes TCP protocol 1, it has the lowest priority during transit
across the network. This means that all other traffic receives a higher
priority during queueing within the router on a network link. Because of
this, an average is calculated to ensure that anomalies shall not skew
the data. For the purpose of latency measurements, NISN uses an average
of 100 packets each sent with a 36-byte payload.

### Service Maintenance

L2VPN services are maintained by NISN and are provisioned as part of the
service.

# How to Request Services

## General

Customers can request NISN services either by contacting the
Center/Program representative or a Customer Service Representative
(CSR). This process is initiated through a NISN Service Request (NSR)
via the NISN Integrated Information System (NIIS)/NISN Service Request
System (NSRS).

Requests for NISN services shall be submitted to NISN regardless of
whether the requirement already appears in a higher level document such
as a human space flight Program Requirements Document (PRD), Mission
Requirements Request (MRR), and Detailed Mission Requirements (DMR)
documents used for non-human flight Mission requirements or Project
Service Level Agreement (PSLA) used for Mission and Mission Support
requirements.

## The Requirements Process

### Customer Actions

Customers initiate contact with NISN by one of the following methods to
make known any new service requirements:

a.  Contact your NISN Center/Program representative or the Customer
    Service Representative (CSR) (see [Appendix
    C](#nasa-integrated-services-network-nisn-point-of-contact-poc) for
    a list of NISN representatives). This person can do one of two
    things on your behalf: (1) provide you with complete POC information
    for dealing directly with the UNITES/NISN/Customer Service
    Representative (CSR) staff person who shall be managing the
    processing and implementation of your requirement or (2) submit an
    NSR form directly to the UNITES/NISN/CSR staff person on your
    behalf. In either event you shall need to provide all the
    information necessary for completion of the NSR form.

```{=html}
<!-- -->
```
a.  ROM Costs and/or Detailed Cost Estimates can be requested via
    telephone and/or E-mail to your CSR. The points of contact for
    requesting circuit Rough Order of Magnitude (ROM) Costs and Detailed
    Cost Estimates are provided in [Appendix
    C](#nasa-integrated-services-network-nisn-point-of-contact-poc). The
    CSR will generate a NSR for the requested ROM or Cost Estimate.

b.  WAN service requests associated with Mission requirements shall be
    coordinated directly with NISN Service Manager (NSM) (see [Appendix
    C](#nasa-integrated-services-network-nisn-point-of-contact-poc) for
    the name and phone number of the NSM responsible for your
    requirement) or the assigned NISN UNITeS Customer Service
    Representative (CSR). The NISN CSR will initiate the required NSR
    process and track the requirement from its receipt to its
    implementation.

c.  Designated personnel representing existing DCNSS customers may
    request adds, modifications, and changes to existing services via
    the DCNSS Service Request System (SRS). Services other than routine
    requests support by the DCNSS SRS web site must be submitted via the
    standard NSR process

### NASA Integrated Services Network (NISN) Actions

Once a service request has been received by the CIG, the NSR is entered
into the NIIS/NSRS and undergoes an in-house evaluation, to determine
the level of service being requested. Part of this
[validation](#validation) process includes ascertaining the
requirement's validity and that customer funding will be provided for
the requested service, if required. When these evaluation steps are
completed, the CIG obtains any additional information that may be needed
to implement the service.

## Rough Order of Magnitude (ROM) Costs and Detailed Cost Estimates 

Customers frequently need estimates of what their new communications
service requirements are going to cost. Sometimes a very general, rough
order of magnitude number may satisfy this need. At other times, the
need may be for a fairly accurate estimate of all the costs associated
with a set of requirements. NISN shall provide ROM costs and Cost
Estimates upon request.

### Detailed Cost Estimate Vs Rough Order of Magnitude (ROM) Cost 

The distinctions between a ROM Cost and a Cost Estimates are described
in the following paragraphs:

### Rough Order of Magnitude (ROM) Cost

A ROM Cost is a general approximation of the cost of providing a stated
service. It is based on experience, costs of similar services, or on a
cursory examination of other vendor's rates. A ROM Cost is usually
provided to a customer who is seeking general information. ROM Costs do
not include engineering analyses, references to configuration databases,
or the development of alternative solutions to generally stated
communications requirements. ROM Cost information can normally be
provided within 5 working days.

### Detailed Cost Estimate

A Detailed Cost Estimate provides a more detailed and comprehensive
response than a ROM Cost does. Detailed Cost Estimates are based on the
costs associated with a specific solution to a generally stated
requirement. Detailed Cost Estimates generally result in dollar figures
that include all known cost elements, i.e., labor, additional equipment,
overhead, carrier recurring and non-recurring costs, travel (if
required), etc. Given the variability of the factors associated with
developing Detailed Cost Estimates, NISN cannot set a general standard
that would be applicable to all requests. Often, detailed information is
required from sources outside NISN and may only be gained by the
issuance of a formal Request for Information (RFI) to industry. However,
NISN shall provide the requester with status information and with such
cost information (e.g., for those elements of the solution, which have
been priced) within 15 working days of receipt of a Request for a
Detailed Cost Estimate.

# Fiscal Year 2008 (FY08) Pricing

## Pricing Overview

Customers will fund the following for FY08:

-   Any unforecasted/Non-Budgeted services

    -   Requirement not included in prior year NISN budget submittal

-   Mission and Mission Support Services

    -   Any unforecasted requirements if additional bandwidth is
        required

    -   Any additional equipment, hardware, and labor to implement all
        requirements

-   All Outside Continental United States (OCONUS), except:

    -   Space Network (SN)

    -   Deep Space Network (DSN)

    -   Ground Network (GN)

-   Switched Voice / Data Services

-   Mission Unique Transport Service

    -   All Circuits between non-NASA sites and anywhere else (Tail
        Circuits)

    -   All satellite communications, except NASA Select

-   ViTS Services

    -   All current and future ViTS utilization

    -   All new ViTS Service conference room systems including
        maintenance, with the exception of Center main ViTS rooms

-   VoTS Services

    -   All new VoTS conference room system requirements, including
        maintenance

-   All Custom Services

-   All DCNSS Services (annual usage fees apply)

## Budgeting Process

NISN shall interact with its customers to define budgets on an annual
basis and throughout the year as requirements change. The following is a
high-level description of the budgeting process:

a.  Customers define their requirements for NISN services and NISN
    provides price estimates for those requirements. Customers may
    refine requirements as necessary. Definition and modification of the
    customer's requirements are accomplished during the development,
    updating, and reconciliation of each Project's, Center's and Mission
    Directorate's Program/PSLA.

b.  NISN summarizes customer funded prices at the project, center, and
    Mission Directorate (or other funding sources for non-NASA
    customers) levels. Projects and Mission Directorates may refine
    their requirements to fit within their budgets.

c.  Requesting projects shall commit to a full year of funding for the
    finalized requirements. The funds will be transferred beginning in
    the first quarter of the fiscal year.

d.  NISN shall provide customers with planned versus actual reporting to
    keep customers informed as to the status of their funding. \[As
    required\]

[]{#__RefHeading___Toc185737179 .anchor}Table 4-1 General Annual PSLA
Requirements Validation

  -----------------------------------------------------------------------
  ***General Annual PSLA Requirements Validation***

  Issue call letter for projected requirements

  Distribute FY08 NISN details and document to community for review

  Review requirements with customers

  Obtain Technical approval signature for FY08 NISN requirements details

  Obtain Funding approval signature for FY08 NISN requirements details

  Mission Directorate customer requirement/funding review

  Requirements cutoff for POP
  -----------------------------------------------------------------------

######## Supported Interfaces and Protocols 

**A.1 General**

NISN supports the interfaces and protocols listed below. If your
particular requirement does not appear on this list, please contact your
NISN Service Manager in the Customer Interface Group or your center's
Customer Service Representative to determine if it can be satisfied by a
standard service offering or if it requires a custom solution (custom
solutions cost more than standard offerings).

A.2 Interfaces

  ----------------- ----------------- ----------------- ------------------
  Consultative      Differential      EIA RS-449        Stick and Click
  Committee for     Emitter Coupled                     Connector (SC),
  International     Logic (D-ECL)                       Stick and Twist
  Telephone and                                         Connector (ST),
  Telegraph (CCITT)                                     Optical
  V.35                                                  

  Digital           Electronic        EIA RS-530        Registered Jack
  Cross-Connect     Industries                          (RJ)-xx
  Level 1 (DSX-1)   Alliance                            
                    Recommended                         
                    Standard 232 (EIA                   
                    RS-232)                             

  DSX-3             EIA RS-422        High Speed Serial Bayonet
                                      Interface (HSSI)  Neill-Councilmen
                                                        (BNC)
  ----------------- ----------------- ----------------- ------------------

**A.3 Protocols**

Subject to waiver action, the use of IP is required for the transport of
data across the NISN. Refer to Applicable Documents
[1.4.1.b](#Applicable_Documents_141b) and
[1.4.1.c](#Applicable_Documents_141c) for specific protocol standard
information and waiver processing instructions.

  ----------------------- ----------------------- -----------------------
  User Data               Border Gateway Protocol Multi-cast Open
  Protocol/Internet       (BGP)                   Shortest Path First
  Protocol (UDP/IP)                               (MOSPF)

  Transmission Control    4800 Bit Block (4800    Multi-cast
  Protocol (TCP)/IP       BB)                     

  Multilink               Consultative Committee  Voice Over Internet
  Point-to-Point Protocol for Space Data Systems  Protocol (VoIP)
  (MPPP)                  (CCSDS)                 
  ----------------------- ----------------------- -----------------------

######## NISN Service Standard Intervals

**B.1 General**

Table B-1 is a "guide" to assist customers in the planning of NISN
Standard Services.

**B.2 Standard Interval Factors**

The NISN Service Standard Intervals can be affected by actions and tasks
performed by various entities involved in the process.  This can include
the Vendors, the Customer and the host center location. The customer's
approval of the design package and funding transfer process will affect
the NISN Service Standard Intervals. Certain NISN Services will require
tasks to be performed by the host location which include inside or
extended wiring, construction/facility modifications or electrical power
installations. In order to reduce the implementation timeframe, NISN
recommends that host center support is worked in parallel with NISN
activities

NISN IT security checklist must be approved prior to physical connection
of IT resources.

NOTE:

NISN is currently implementing an Indefinite Delivery Indefinite
Quantity (IDIQ) procurement process. This will lower NISN standard
intervals for services that require hardware procurement. Updates to the
NISN Service Standard Intervals will be published at a later date

NOTE:

Standard Intervals are based upon business days and new requirements
from customer.

[]{#__RefHeading___Toc185737180 .anchor}Table B- NISN Service Standard
Intervals

  ------------------------------- ---------- ------------ ------------------ -----------
  **Service**                     **Design   **Approval / **Implementation   **Total**
                                  Phase**    Funding      Phase**            
                                             Phase**                         

  **VIDEO**                                                                   

  **Custom VITS**                 69         15           116                200

  **VRA**                         25         15           57                 97

  **DVA**                         25         15           57                 97

  ** **                                                                       

  **VOICE**                                                                  

  **Custom VOTS**                 69         15           116                200

  **COTS VOTS**                   10         15           55                 80

  **Modified VOTS**               25         15           55                 95

  **Switched Voice Service**      6          5            42                 53

  **Toll Free Numbers**           0          0            14                 14

  **Calling Cards**               0          0            19                 19

  **Instant Meeting \< 50 ports** 0          0            3                  3

  **Instant Meeting \> 50 ports** 0          5            2                  7

  **Mission Dedicated Voice**     7          0            7                  14
  (NASA facility to NASA                                                     
  facility)                                                                  

  **Mission Dedicated Voice**     27         15           54                 96
  (NASA facility to customer                                                 
  location)                                                                  

  **Dedicated Data**                                                         

  **Mission Dedicated Data**      7          0            38                 45
  (NASA facility to NASA                                                     
  facility)                                                                  

  **Dedicated Data** (NASA        28         0            22                 50
  facility to NASA facility)                                                 

  **Mission Dedicated Data**      15         15           43                 73
  (NASA facility to customer                                                 
  location)                                                                  

  **Dedicated Data** (NASA        19         15           42                 76
  facility to customer location)                                             

  **Routed Data**                                                            

  **Mission Routed Data** (NASA   27         15           71                 113
  facility to NASA facility)                                                 

  **PIP/SIP Routed Data** (NASA   27         15           67                 109
  facility to NASA facility)                                                 

  **Mission Routed Data** (NASA   30         15           71                 116
  facility to customer location)                                             

  **PIP/SIP Routed Data (NASA     27         15           62                 104
  facility to customer                                                       
  location)**                                                                

  Procurement lead-times are                                                 
  estimated at 45 - 55 days.                                                 

  Host Center Support for local                                              
  circuit extension is estimated                                             
  at 30 days                                                                 

  Standard Intervals do not                                                  
  include any time for mandatory                                             
  10 day outage notification.                                                

  Standard Intervals do not                                                  
  include any time for IT                                                    
  security approval process.                                                 

  **Standard Intervals are based                                             
  upon business days and new                                                 
  requirements from customer.**                                              
  ------------------------------- ---------- ------------ ------------------ -----------

######## NASA Integrated Services Network (NISN) Point of Contact (POC)

**C.1 NASA Mission Directorate, Mission Support Office, Center or
Facility and Program Assignments**

CIG personnel are assigned responsibility for requirements processing
and implementation based upon the NASA mission directorate served by the
requirement, as well as on program/project and NASA Center or Facility
basis. NSM assignments, by Enterprise, are found at
<http://www.nisn.nasa.gov/DOCUMENTS1/POC_nisn_service_managers.html>.
Where resources permit, the CIG assigns both a primary and alternate
person to be the cognizant NSM for each NASA Center or Facility.

**C.2 NISN On-site Customer Support**

NISN provides Customer Service Representatives (CSR) who are co-located
with the customer and provide on-site support for NISN services, a
listing may be found on the [NISN
website](http://nisn.nasa.gov/DOCUMENTS1/POC_customer_service_representatives.html).

**C.3 NISN Organization**

The NISN organizational structure may be found at
<http://www.nisn.nasa.gov/DOCUMENTS1/NISN_OrganizationChart.ppt>

**C.4 About this Document**

Send your comments or questions pertaining to this document to the
following E-mail address: [mailto:
Kimberly.A.Wright@nasa.gov](mailto:Kim.Wright@nasa.gov) .

######## Key Personnel

**D.1 NISN Center/Program Representatives/Customer Commitment Managers**

Centers and Programs have identified personnel to act as liaison between
the Center/Program and NISN. A listing of these representatives and
their alternates may be found on the [NISN
website](http://nisn.nasa.gov/DOCUMENTS1/POC_ctr_program_representatives.html).

**D.3 NISN Service Owners**

The NISN Service Owners can be found at the following website:

<http://www.nisn.nasa.gov/DOCUMENTS1/POC_ServiceOwners.html>

######## Abbreviations and Acronyms 

3DES Triple Data Encryption Standard

ADP Automatic Data Processing

AOPNS Activity and Outage Posting and Notification System

ARIN American Registry for Internet Numbers

AS Autonomous System

ATM Asynchronous Transfer Mode

BGP Border Gateway Protocol

BMG Business Management Group

BRI Basic Rate Interface

CCB Configuration Control Board

CCM Customer Commitment Manager

CIG Customer Interface Group

CIO Chief Information Officer

CM Configuration Management

COMSEC Communications Security

CONUS Continental United States

COTS Commercial-off-the-shelf

CSR Customer Service Representative

CVPN Corporate Virtual Private Network

DCN Document Change Notice

DCNSS Data Center Network and Security Services

DMR Detailed Mission Requirements

DNS Domain Name Service

DMZ Demilitarized Zone

DSN Deep Space Network

DVA Desktop ViTS Appliance

DVD Digital Video Disk

EIGRP Enhanced Interior Gateway Routing Protocol

E-mail Electronic mail

FIPS Federal Information Processing Standard

FISMA Federal Information Security Management Act

FTS Federal Technology Service

FY Fiscal Year

Gbps Gigabits per second

GigE Gigabit Ethernet

GN Ground Network

GPS Global Positioning Satellite

GSA General Services Administration

GSFC Goddard Space Flight Center

HPREN High Performance Research Engineering Network

HQ Headquarters

HRDS High Rate Data System

HRDVS High Rate Data/Video System

HSF Human Space Flight

HSR Houston Support Room

ICMP Internet Control Message Protocol

IDS Intrusion Detection Service

IONet Internet Protocol Operational Network

IP Internet Protocol

ISDN Integrated Services Digital Network

ISP Internet Service Provider

ISS International Space Station

IT Information Technology

ITS Information Technology Security

ITU International Teleconferencing Union

JSC Johnson Space Center

Kbps kilobits per second

LAN Local Area Network

LD Long Distance

MAA Metropolitan Area Access

Mbps megabits per second

MCC-M Mission Control Center - Moscow

MCIP Mission Critical IP

MHz Megahertz

MOA Memorandum Of Agreement

MONS Mission Outage Notification System

MPLS Multi-Protocol Label Switching; Multi-Protocol Lambda Switching

MRR Mission Requirements Request

MSFC Marshall Space Flight Center

MTTR Mean-Time-to-Restore

NASA National Aeronautics and Space Administration

NIIS NISN Integrated Information System

NISC NASA Information Support Center

NISN NASA Integrated Services Network

NPD NASA Policy Directive

NPR NASA Procedure Requirement

NSAP Network Service Assurance Plan

NSD NISN Services Document

NSG Network Services Group

NSM NISN Service Manager

NSR NISN Services Request

NSRS NISN Services Request System

NTP Network Timing Protocol

NTR NSAP Technology Refresh

OC Optical Carrier

OCONUS Outside Continental United States

ORD Organization Responsibility Document

OSPF Open Shortest Path First

PBX Private Branch Exchange

PIP Premium IP

POC Point of Contact

PRD Program Requirements Document

PRI Primary Rate Interface

QoS Quality of Service

RCIP Real-time Critical IP

RIP Routing Information Protocol

ROM Rough Order of Magnitude

SAP Service Access Point

SCANS Space Communications And Navigation Systems

SDD Secure Data Devices

SIP Standard IP

SN Space Network

SOP Standard Operating Procedure

SRS Service Request System (for DCNSS)

SVS Switched Voice Service(s)

VBS Video Bridging Service

VCR Video Cassette Recorder

ViTS Video Teleconferencing System

VoIP Voice over Internet Protocol

VoTS Voice Teleconferencing System

VPN Virtual Private Network

VRA Video Roll-About

VTC Video Teleconferencing Center

WAN Wide Area Network

WSC White Sands Complex

######## Glossary

+-------------+--------------------------------------------------------+
| ATM         | Asynchronous transfer mode switched service -          |
|             | high-speed packet (cell) switching using fixed cell    |
|             | size for all media (voice, video, and data).           |
+-------------+--------------------------------------------------------+
| A           | A measure of equipment, system, or network             |
| vailability | performance, usually expressed in percent; the ratio   |
|             | of operating time to the sum of operating time plus    |
|             | downtime.                                              |
+-------------+--------------------------------------------------------+
| Bandwidth   | A quantified description of the information-carrying   |
|             | capacity of a communications path or link. It can      |
|             | apply to telephone or network wiring as well as system |
|             | buses, radio frequency signals, and monitors.          |
|             | Bandwidth is measured in (1) cycles per second, or Hz, |
|             | which is the difference between the lowest and highest |
|             | frequencies transmitted or (2) in terms of data bits   |
|             | or data bytes per second.                              |
+-------------+--------------------------------------------------------+
| Circu       | A voice or data oriented switched service arrangement  |
| it-switched | that initiates a switched connection on a message or   |
|             | voice call basis.                                      |
+-------------+--------------------------------------------------------+
| Closed      | There is neither access to nor from the Internet.      |
| network     | Communications are limited to a defined set of         |
|             | authorized addresses.                                  |
+-------------+--------------------------------------------------------+
| Core        | The service is centrally funded by the SCANS office of |
|             | NASA HQs.                                              |
+-------------+--------------------------------------------------------+
| Customer    | A customer is any organizational entity which          |
|             | validates a network requirement and either directly    |
|             | funds or arranges funding for the requirement.         |
|             | Examples of customers are officials in NASA Mission    |
|             | Directorates, Mission Support Offices, Program         |
|             | Offices, as well as, Directors of NASA Centers and     |
|             | Field Installations.                                   |
+-------------+--------------------------------------------------------+
| ATM         | Asynchronous transfer mode switched service -          |
|             | high-speed packet (cell) switching using fixed cell    |
|             | size for all media (voice, video, and data).           |
+-------------+--------------------------------------------------------+
| []{#A       | A measure of equipment, system, or network             |
| vailability | performance, usually expressed in percent; the ratio   |
| .anchor}A   | of operating time to the sum of operating time plus    |
| vailability | downtime.                                              |
+-------------+--------------------------------------------------------+
| Bandwidth   | A quantified description of the information-carrying   |
|             | capacity of a communications path or link. It can      |
|             | apply to telephone or network wiring as well as system |
|             | buses, radio frequency signals, and monitors.          |
|             | Bandwidth is measured in (1) cycles per second, or Hz, |
|             | which is the difference between the lowest and highest |
|             | frequencies transmitted or (2) in terms of data bits   |
|             | or data bytes per second.                              |
+-------------+--------------------------------------------------------+
| Circu       | A voice or data oriented switched service arrangement  |
| it-switched | that initiates a switched connection on a message or   |
|             | voice call basis.                                      |
+-------------+--------------------------------------------------------+
| Closed      | There is neither access to nor from the Internet.      |
| network     | Communications are limited to a defined set of         |
|             | authorized addresses.                                  |
+-------------+--------------------------------------------------------+
| Core        | The service is centrally funded by the SCANS office of |
|             | NASA HQs.                                              |
+-------------+--------------------------------------------------------+
| [           | A customer is any organizational entity which          |
| ]{#Customer | validates a network requirement and either directly    |
| .anch       | funds or arranges funding for the requirement.         |
| or}Customer | Examples of customers are officials in NASA Mission    |
|             | Directorates, Mission Support Offices, Program         |
|             | Offices, as well as, Directors of NASA Centers and     |
|             | Field Installations.                                   |
+-------------+--------------------------------------------------------+
| Dedicated   | Services in which communications resources are         |
| services    | permanently assigned to one user.                      |
+-------------+--------------------------------------------------------+
| Denial of   | When a conference cannot be accommodated at the        |
| service     | requested time with all requested participants at the  |
|             | originally requested time due to insufficient          |
|             | transmission or bridging capabilities.                 |
+-------------+--------------------------------------------------------+
| E-mail      | Basic e-mail service aimed at providing the most basic |
|             | end-to-end capabilities commercially available.        |
|             |                                                        |
|             | Enhanced electronic mail service has functionality     |
|             | beyond that provided under a basic E-mail offering     |
|             | (e.g., supports electronic commerce requirements,      |
|             | signature authentication, direct fax transfer, group   |
|             | ware support, security features).                      |
+-------------+--------------------------------------------------------+
| E-1         | 2.048 megabits per second                              |
+-------------+--------------------------------------------------------+
| Filtering   | The process of discarding packets that do not meet the |
|             | network's criteria for forwarding.                     |
+-------------+--------------------------------------------------------+
| Firewall    | A firewall is either the program or the computer it    |
|             | runs on, usually an Internet gateway server that       |
|             | protects the resources of one network from users from  |
|             | other networks. Typically, an enterprise with an       |
|             | intranet that allows its workers access to the wider   |
|             | Internet shall want a firewall to prevent outsiders    |
|             | from accessing its own private data resources. There   |
|             | are a number of firewall screening methods. A simple   |
|             | one is to screen requests to make sure they come from  |
|             | acceptable (previously identified) domain names and IP |
|             | addresses. Another is to not allow Telnet access into  |
|             | your network (although you may permit your own users   |
|             | to request Telnet connections outside your network).   |
+-------------+--------------------------------------------------------+
| Grade of    | The probability of a call being blocked or delayed     |
| Service     | more than a specified interval, expressed as a decimal |
|             | fraction. As an example, a P.03 grade of service means |
|             | there is a 3 percent probability of a call being       |
|             | blocked on the first attempt. The call may go through  |
|             | on any subsequent attempt.                             |
+-------------+--------------------------------------------------------+
| Hyperlink   | An element in an electronic document that links to     |
|             | another place in the same document or to an entirely   |
|             | different document. Typically, you click on the        |
|             | hyperlink to follow the link.                          |
+-------------+--------------------------------------------------------+
| Denial of   | When a conference cannot be accommodated at the        |
| service     | requested time with all requested participants at the  |
|             | originally requested time due to insufficient          |
|             | transmission or bridging capabilities.                 |
+-------------+--------------------------------------------------------+
| E-mail      | Basic e-mail service aimed at providing the most basic |
|             | end-to-end capabilities commercially available.        |
|             |                                                        |
|             | Enhanced electronic mail service has functionality     |
|             | beyond that provided under a basic E-mail offering     |
|             | (e.g., supports electronic commerce requirements,      |
|             | signature authentication, direct fax transfer, group   |
|             | ware support, security features).                      |
+-------------+--------------------------------------------------------+
| E-1         | 2.048 megabits per second                              |
+-------------+--------------------------------------------------------+
| []          | The process of discarding packets that do not meet the |
| {#filtering | network's criteria for forwarding.                     |
| .ancho      |                                                        |
| r}Filtering |                                                        |
+-------------+--------------------------------------------------------+
| Firewall    | A firewall is either the program or the computer it    |
|             | runs on, usually an Internet gateway server that       |
|             | protects the resources of one network from users from  |
|             | other networks. Typically, an enterprise with an       |
|             | intranet that allows its workers access to the wider   |
|             | Internet shall want a firewall to prevent outsiders    |
|             | from accessing its own private data resources. There   |
|             | are a number of firewall screening methods. A simple   |
|             | one is to screen requests to make sure they come from  |
|             | acceptable (previously identified) domain names and IP |
|             | addresses. Another is to not allow Telnet access into  |
|             | your network (although you may permit your own users   |
|             | to request Telnet connections outside your network).   |
+-------------+--------------------------------------------------------+
| Grade of    | The probability of a call being blocked or delayed     |
| Service     | more than a specified interval, expressed as a decimal |
|             | fraction. As an example, a P.03 grade of service means |
|             | there is a 3 percent probability of a call being       |
|             | blocked on the first attempt. The call may go through  |
|             | on any subsequent attempt.                             |
+-------------+--------------------------------------------------------+
| Hyperlink   | An element in an electronic document that links to     |
|             | another place in the same document or to an entirely   |
|             | different document. Typically, you click on the        |
|             | hyperlink to follow the link.                          |
+-------------+--------------------------------------------------------+
| [           | Any failure that denies a user one or more of the      |
| ]{#impacted | requested functionalities from the room or the network |
| .anch       |                                                        |
| or}Impacted |                                                        |
| conference  |                                                        |
+-------------+--------------------------------------------------------+
| []{#IDS     | Provides real-time monitoring of all IP traffic that   |
| .ancho      | traverses the perimeter of the network, both inbound   |
| r}Intrusion | and outbound. Inspects all services, protocols, and    |
| Detection   | packets looking for unique attack signatures and shall |
| System      | alert the proper personnel of an attempted intrusion,  |
|             | as well as blocking the IP address, port, and/or       |
|             | service of source system in question                   |
+-------------+--------------------------------------------------------+
| Latency     | The time it takes for a data packet to move across a   |
|             | network connection.                                    |
+-------------+--------------------------------------------------------+
| []{         | The liaison person who coordinates customer functions  |
| #NISNCTRREP | for a program or center with the NISN project.         |
| .           |                                                        |
| anchor}NISN |                                                        |
| Center/     |                                                        |
| Program     |                                                        |
| Rep         |                                                        |
| resentative |                                                        |
+-------------+--------------------------------------------------------+
| []{         | Access to the Internet is permitted but access from    |
| #restricted | the Internet is strictly controlled.                   |
| .anchor     |                                                        |
| }Restricted |                                                        |
| network     |                                                        |
+-------------+--------------------------------------------------------+
| Special     | Employees with expert skills in a narrowly defined     |
| Staff       | area, e.g., information technology security. Employees |
|             | assigned to special staff functions are made available |
|             | on an as-needed basis, performing duties in support of |
|             | other organizations when not engaged by NISN.          |
+-------------+--------------------------------------------------------+
| Switched    | Services in which communications resources are shared  |
|             | among many users using a switching device.             |
+-------------+--------------------------------------------------------+
| []{#Trojan  | A Trojan, also "Trojan Horse," is a program that does  |
| .an         | something undocumented that the programmer intended,   |
| chor}Trojan | but that some users would not approve of if they knew  |
|             | about it. Some consider that a virus is a particular   |
|             | case of a Trojan Horse, namely one that is able to     |
|             | spread to other programs (i.e., it turns them into     |
|             | Trojans too). Others consider that a virus that does   |
|             | not do any deliberate damage (other than merely        |
|             | replicating) is not a Trojan. Finally, many use the    |
|             | term "Trojan" to refer only to "non-replicating"       |
|             | malware, in which instance the set of Trojans and the  |
|             | set of viruses are disjointed.                         |
+-------------+--------------------------------------------------------+
| Tail        | The circuit extension between the NISN Backbone and    |
| Circuit     | the NISN service demarcation at the customer location. |
|             | A tail circuit is typically customer funded.           |
+-------------+--------------------------------------------------------+
| T-1         | 1.544 megabits per second                              |
+-------------+--------------------------------------------------------+
| Unit of     | The standard quantification, sometimes expressed in    |
| Service     | relation to time, in which a particular WAN service    |
|             | may be priced, ordered, and delivered. A significant   |
|             | deviation from these standard quantifications may      |
|             | result in a tailored (custom) WAN service requirement  |
|             | that in turn shall cause development of a SCANS WAN    |
|             | price quote.                                           |
+-------------+--------------------------------------------------------+
| []{#User    | The organizational element that is the direct          |
| .           | recipient of a NISN provided service, i.e., has one or |
| anchor}User | more physical interfaces used for terminating or       |
|             | originating a NISN telecommunications (see also        |
|             | "customer").                                           |
+-------------+--------------------------------------------------------+
| Validation  | The authentication and confirmation by NISN of a       |
|             | requirement to include an implicit promise of          |
|             | providing such funds as may be necessary to defray the |
|             | costs incurred in meeting the requirement.             |
+-------------+--------------------------------------------------------+
| Virus       | A computer virus is defined by Symantec as being a     |
|             | parasitic program written intentionally to enter a     |
|             | computer without the user's permission or knowledge.   |
|             | The word parasite is used because a virus attaches to  |
|             | files or boot sectors and replicates itself, thus      |
|             | continuing to spread. Though some viruses do little    |
|             | but replicate, others can cause serious damage or      |
|             | affect program and system performance. A virus should  |
|             | never be assumed harmless and left on a system.        |
+-------------+--------------------------------------------------------+
| Worm        | A computer worm is a self-contained program (or set of |
|             | programs) that is able to spread functional copies of  |
|             | itself or its segments to other computer systems       |
|             | (usually via network connections).                     |
+-------------+--------------------------------------------------------+

######## NASA Integrated Services Network (NISN) IT Security Check Lists.

**G1.** **Security Check Lists Overview**

New users or services must complete a NASA IT Security Checklist to
connect to the IP networks. The specific checklists are tailored to
reflect the risks but as a general rule, the following areas must be
addressed:

1\) Personnel - making sure they are trained and have a need for access

2\) Equipment - dealing with outages, physical security and firewalls

3\) Software - vulnerability scanning and software updates

4\) Threat response - processes for dealing with problems

5\) Renewal - typically on a three year cycle, it is subject to change

**G2. The Premium Internet Protocol (PIP)/Standard Internet Protocol
(SIP) Security Checklist**

The NISN PIP/SIP Security checklist can be found on the NISN website at
<http://www.nisn.nasa.gov/DOCUMENTS1/MsnSptSecChk.doc>.

**G3. The Real Time Critical IP (RCIP) and Mission Critical Internet
Protocol (MCIP) Security Checklist.**

The RCIP and MCIP security checklist can be found on the NISN website at
<http://www.nisn.nasa.gov/DOCUMENTS1/IONet_Security_Audit_Checklist_Rev3.doc>.

[^1]: The meaning of words underlined at their first appearance is found
    in the Glossary at the end of the document.

[^2]: ^^ The availability includes room systems, NISN provided
    transport and multiport control system.

[^3]: ^^ These restoral times represent the time to restore service to
    the user and assume immediate access to the user\'s facility to
    repair/replace equipment if necessary and are mean time to restore
    figures.

[^4]: ^^

[^5]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

    ^^ These restoral times represent the time to restore service to
    the user and assume immediate access to the user\'s facility to
    repair/replace equipment if necessary and are Mean Time To Restore
    (MTTR) figures.

[^6]: ^^

[^7]: ^^

[^8]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

    ^^ These restoral times represent the time to restore service to
    the user and assume immediate access to the user\'s facility to
    repair/replace equipment if necessary and are Mean Time To Restore
    (MTTR) figures.

    \* One day implementation depends on prior receipt of properly
    executed service request.

[^9]: ^^

[^10]: ^^

[^11]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

[^12]: ^^ Round Trip Time (latency) is specified for data flow between
    domestic WAN nodes controlled and operated by NISN. Latency is a
    function of distance and carrier capabilities. User applications
    that are sensitive to latency shall be engineered to account for the
    upper limit round trip times specified in the above table.

[^13]: ^^ A capability for immediately switching to an alternate data
    path shall exist.

[^14]: ^^ These restoral times represent the time to restore service to
    the user and assume immediate access to the user\'s facility to
    repair/replace equipment if necessary.

[^15]: ^^ The 24-hour restoral time results from the decreased priority
    given to standard service as compared to the other classes of
    service and from the fact that standard routed data service
    equipment is often a considerable distance from a NASA operating
    location.

[^16]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

[^17]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

[^18]: ^^ Round Trip Time (latency) is specified for connections
    between domestic WAN nodes controlled and operated by NISN. Latency
    is a function of distance and carrier capabilities.

[^19]: ^^ A capability for immediately switching to an alternate data
    path shall exist.

    ^^ This restoral time represents the time to restore service to the
    user and assumes immediate access to the user's facility to
    repair/replace equipment if necessary.

[^20]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

[^21]: ^^ A capability for immediately switching to an alternate data
    path shall exist.

    ^^ This restoral time represents the time to restore service to the
    user and assume immediate access to the user\'s facility to
    repair/replace equipment if necessary.

[^22]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

[^23]: ^^ A capability for immediately switching to an alternate data
    path shall exist.

    ^^ This restoral time represents the time to restore service to the
    user and assume immediate access to the user\'s facility to
    repair/replace equipment if necessary.

[^24]: ^^ A capability for immediately switching to an alternate data
    path or devise must exist

[^25]: ^^ These restoral times represent the time to restore service to
    the user and assume immediate access to the user's facility to
    repair/replace equipment if necessary. Premium and Standard time to
    restore is based on a calculated mean. Mean-Time-To-Restore (MTTR)
    for these services is calculated on outage data gathered in the
    proceeding 90 days and is based on the time NISN receives an outage
    notification to the time the service is restored. A mean time
    calculation can result in individual service outages that exceed 4
    or 24 hours respectively without exceeding the 4 or 24 hour MTTR.

[^26]: ^^ A request that requires a change to the technical
    architecture of the service implementation or the purchase of new
    hardware or software to complete the request

    Time is measured from initial creation of the NSR to service
    implementation, and assume a 10-day turnaround for funding transfers
    (which are required prior to hardware implementation)

[^27]: ^^ These values apply only for those parts of the WAN service
    supported by the NISN mission services backbone infrastructure.
    These values do **not** apply to tail circuits unless the
    circuits/services were specifically ordered and supplied with
    diverse routing end-to-end.

[^28]: ^^ Round Trip Time (latency) is specified for data flow between
    domestic WAN nodes controlled and operated by NISN. Latency is a
    function of distance and carrier capabilities. User applications
    that are sensitive to latency shall be engineered to account for the
    upper limit round trip times specified in the above table.

[^29]: ^^ These restoral times represent the time to restore service to
    the user and assume immediate access to the user\'s facility to
    repair/replace equipment if necessary.

[^30]: ^^ The 24-hour restoral time results from the decreased priority
    given to standard service as compared to the other classes of
    service and from the fact that standard routed data service
    equipment is often a considerable distance from a NASA operating
    location.