1. DTN Network Management CCSDS Green Book Approach Ed Birrane Edward.Birrane@jhuapl.edu 443-778-7423

2. 2 Topics  Purpose/Scope  Network Layers and Management Functions  Multi-tiered management models  Configuration, Performance Monitoring, Event Reaction  Architectures and Protocols  Computationally infeasible to re-create message with C < R chunks.  Concepts of Operation  Scenarios, Interfaces

3. 3 Purpose and Scope  Provide justification and mechanisms for:  Autonomous network agents  Fault protection/recovery and quality of service.  Describe format and utilities for:  Configuration, Monitoring, and Control.  Achieving necessary emergent behavior from these primitives.  Illustrate:  When different NM approaches are required based on link characteristic.  How to interface different NM approaches.  Scope:  Network Management at the application layer.

4. 4 Scope Focus is Management at the Application Layer

5. 5 Networking Layers Application Layer Segmented into Three “Tiers”

6. 6 Role of Network Management  Configuration  Synchronize Tier 1 and 2 configurations throughout the network  Tier-3 configurations are un-examined payloads passed as bundles.  Performance Monitoring  Provide “pull” mechanisms for data over low-latency links.  Provide “push” mechanisms for data over high-latency links.  Intelligent data push may change data sent based on circumstance.  Event Reaction  Network fault protection and self-configuration  Similar to safe modes on deep-space spacecraft  Superset of terrestrial network management

7. 7 Implementation Architectures  Protocol Interface  Protocol decoding  Payloads and Extension Headers  Data Ingest  Format, Test Scripts, Rollback  Databases  ADMs (MIBs) by function  Rules/Actions  Autonomy  Evaluates rules, applies actions  Telemetry Collection  ADM (Page) definition, versioning  Data conditioning/sampling  Aggregation  Protocol encoding

8. 8 Concepts of Operation Predicated on “Island” Model

9. 9 Security Models  Investigating Identity-Based Encryption (IBE)  Working with CCSDS Security WG (Howie)  Less reliance on central key authority and key exchange  Fewer Key queries. Avoid Challenge/response systems  Support authentication, integrity, and confidentiality.  Multiple-Group Model  Composite Keys {AssetID, GroupID}  {Lander1, NASA}, {Lander1, ESA}, {Lander1, MartianNetwork}  Group membership may be dynamic  Interfaces naturally with terrestrial PKI schemes. Non-chatty, low-maintenance key negotiation

10. 10 Policy Enforcement  Automated Policy Enforcement  Remote nodes support rule-based autonomy  Fault detection, enhanced reporting, maybe rate limiting  Manual Policy Enforcement  Fine-Grained security built into Tier 1 and 2 applications  Expansive group model. Can be extended to distinguish read and write.  Security authentication can be a significant policy enforcement method.  Support of modern crypto-suites enable cross-domain communication  Automated enhanced reporting greatly increases action time of operator  Less time to request more data over high-latency link. Tools Must Exist to Enforce Policy

11. 11 Configuration Scenarios  Pushing New Contact Graphs  Synchronizing data across Tier-2 applications  Demonstrates application of policy: who update whose contacts?  Updating ADM and aggregation definitions  New version of telemetry pages, how to build them, or when to send them.  Demonstrates handling versioning issues in the network.  Work prototyped in RMON extensions  Security Key and Group Changes  Add new group, keys in the network  Demonstrate security model, including group-based access (ACL)  Work prototyped in IBE code in ION (@APL)

12. 12 Performance Monitoring Scenarios  Tracking bundle status through the network  Cache/batch report-to addresses through the network  Demonstrates reportability of bundles without saturating network links.  SNMPv3 Gateways  Construct “pull” repositories populated by “push” data.  Demonstrates terrestrial NM interface to high-delay/distruption systems.  Prototype work completed by GRC (DTN2) and OU (ION).  Producing verbose telemetry on failure  Rule/Action configurations define verbose tlm pages on fault  Demonstrate ability to get information to operator faster

13. 13 Event Reaction Scenarios  Cancelling large file transfer  Multiple bundles form CFDP transfer  Demonstrate control of bundles at all nodes in the network.  Quality of Service Enforcement  Codified policy decisions on bandwidth, rate, or contact  Demonstrates ability to control traffic over links based on rule configurations at intermediate nodes.  Path Failure Reaction  Tier-2 application configuration in reaction to loss of node.  Likely update contact graph  Demonstrate ability to automate certain fault recovery.

14. 14 Next Steps  By next CCSDS meeting  Add NM green book to SIS-DTN charter  Construct development schedule  Synchronize outline  Assemble technical stakeholders  JHU/APL will collect, organize, edit information  OU and UCB – ION  GRC – DTN2 applied lessons learned, MIBs  JPL and GSFC – network implementations lessons learned.

15. 15 Thank you! Questions?