-
Notifications
You must be signed in to change notification settings - Fork 9
BSL v1.0 Test Readiness Review
- Agenda
- Review Board
- Software Overview
- Requirements
- Improvements
- Defect Corrections
- Sustaining Activities
- Other
- Test Objectives
- Test Environment
- Key/New Test Cases
- Test Personnel
- Test Effort Rationale
- Test Constraint And Risks
- Action Item Status
- Deviations
| Review Board Chair | Jamie Seung Shin |
| MGSS Chief Engineer | Michele Vogt |
| MGSS Deputy Chief Engineer | Kyran Owen-Mankovich |
| MGSS Assurance Engineer | Eva Bokor, Korwin Anderson (Alternate) |
| MGSS Cybersecurity Engineer | Mike Pajevski |
| MGSS Customer Support Lead | Scott Markham |
| AMMOS Architect | Mike Pajevski |
| MGSS System Test lead | Dipak Achnnani |
| MGSS Schedulers | Kristin Drucker (Lead), RJ Mariano |
| MGSS Mission Assurance MGR | Patricia Lock (Invite DDRs only) |
| Task Manager | Chris Krupiarz |
| Task Cognizant Engineer | Brian Sipos |
| Other Stakeholders | N/A |
The BPSec Library (BSL) is a software library (v1.0) and an implementation of Bundle Protocol Security (BPSec), which is the standardized mechanism for BPv7 bundle-layer security as specified in the IETF RFC 9172. The BPv7 transport protocol was developed as part of an overall Delay-Tolerant Networking (DTN) architecture for data exchange in challenging communications environments. BPv7 has been baselined for use in a variety of NASA and other space agency missions such as NASA’s LunaNet and ESA’s Moonlight projects, and has been recommended for a variety of other IOAG and CCSDS space-networked architectures and functions.
The BPv7 protocol data unit is the Bundle, and bundles are comprised of multiple Blocks of information. An application that produces, processes, and/or delivers bundles in compliance with the BPv7 specification is called a Bundle Protocol Agent (BPA). BPSec defines special extension blocks that carry cryptographic information related to other blocks in the same bundle. All standards-compliant BPAs must be able to process BPSec blocks in a received bundle if required by the security policy of the BPA. This project will create a BPSec Library (BSL) that implements a general-purpose BPSec security block processor.
Release information for the software can be found in the BSL docs repository.
This section has no updates because this is the initial release, and there have been no changes from the baseline as of yet.
The following table is the sections of requirements and how many requirements per section.
| Area | Number of Requirements |
|---|---|
| GEN | 20 |
| SFF | 9 |
| ERR | 10 |
| BIN | 13 |
| CIN | 5 |
| PIN | 6 |
| TIN | 1 |
| LIN | 4 |
| SVC | 4 |
| CFG | 7 |
| PFR | 2 |
| SEC | 2 |
| ADP | 4 |
This section has no updates because this is the initial release, and there have been no changes from the baseline as of yet.
This section has no updates because this is the initial release, and there have been no changes from the baseline as of yet.
This section has no updates because this is the initial release and there have been no changes from the baseline as of yet.
| ID | Title | Status | Test Case ID(s) |
|---|---|---|---|
| N/A | N/A |
The BSL is a library and the objective of testing is to ensure the library performs its expected behaviors in accordance with the requirements.
The overall purpose is to make test results reproducible for the users. All testing happens as a single library instance on a single "mock BPA" node. There are no requirements or expectations about integrating with any particular real BPA or any multiple node test cases. Certain requirements for the overall environment are as follows:
- Must be RedHat Enterprise 9
- Must have FIPS 140 enabled at OS install
- Must have SE Linux enabled
- Since the BSL software will be configuration managed as rpm packages, the test executor must interact with tests via command prompt/terminal
Note that we describe in more detail the Test Environment in the Acceptance Test Plan.
OPTIONAL
| Person | Role | Assignment | Availability |
|---|---|---|---|
TODO: Assign each test some period of time and multiply it by some multiplier to get estimate for test effort amount.
Because the BSL is a library and its Mock BPA can operate in isolation, testing doesn't require external systems or resources. The lack of constraints means there are no risks to being able to execute the tests.
This is the initial release so there are no action items from previous release.
This is the initial release so there are no deviations from previous release. We are treating the need for an architecture description as being fulfilled by PDR presentation. Design specifications will be fulfilled by CDR.