1. SIS-DTN Forward Planning
San Antonio
Fall 2013
October 2013 1 1

2. Tues PM Registered Attendees
Scott Burleigh
Patrick Gelard
Alan Hylton
Richard McGinnis
Lee Pitts
Adam Schlesinger
Keith Scott
Jason Soloff
Kiyohisa Suzuki
Peng Wan
October 2013

3. Generic File Transfer BoF
Generic File Transfer BoF (in the library)
I’d like to try to politely dissuade them from using ‘file transfer’ as part of a multi-hop (end-to-end) data delivery mechanism.
May 2010

4. SIS-DTN: Forward Planning
October 2013

5. SSI-Related CCSDS Documents
IOAG
Recommendations on a Strategy for Space Internetworking
Operations Concept for a Solar System Internetwork (SSI)
Rationale, Scenarios, and Requirements for DTN in Space
Solar System Internetwork (SSI) Architecture
CCSDS
LTP Mgmt
IETF
Contact Mgmt
SSI Network Management
Contact Graph Routing
Licklider Transmission Protocol for CCSDS
Space Communications Cross Support Architecture Description Document
RFC5050
(BP)
Multicast Routing
Bundle Protocol for CCSDS
Multi-Domain Routing
RFC5326 (LTP)
RFC5327 (LTPSec)
Space Communications Cross Support Architecture Requirements Document
SSI Coordination Procedures
Bundle Security Protocol for CCSDS
RFCXXXX TBD
Simplified Bundle Security Protocol

6. SIS-DTN Forward Work
Done
Rationale, Scenarios, and Requirements for DTN in Space (Green)
Licklider Transmission Protocol for CCSDS
Bundle Protocol for CCSDS
Solar System Internetwork Architecture
CFDP-over-BP Pink Sheet
Single-Agency Network Management Requirements for BP
Single-Agency BP Network Management [Protocol]
Bundle Security Protocol for CCSDS
Contact Graph Routing for CCSDS
Erasure Coding for LTP
Bundle Streaming Service
Multicast (tree formation and maintenance)
Modifications to support high-rate BP
Nearly Done
In Framework
Approved
Not In Framework
May 2010

7. Forward Work: Security
Need:
Multiple agencies on ISS all flowing data through one shared infrastructure
Need for interoperability
Certainly both ends need to agree on how to secure data; needed if you ever WANT to send data between agencies securely
There is currently an Internet Research Task Force RFC for bundle security (
It conflates routing and security
It imposes ciphersuite requirements that quickly become out-of-date
It allows for complex (Byzantine) nesting / overlapping security that makes implementation extremely difficult
Internet Research Task Force is currently working a ‘Streamlined Bundle Security Protocol’ (SBSP)
Decouples routing from security
Strongly separates ciphersuites
Support
NASA can work the document and interface with IRTF dtnrg
NASA can probably get two implementations (ION, DTN2) via some combination of NASA, other US participants
NEED: second agency support (at least monitor the book)
NEED: semi-formal collaboration with SEA-Security WG
October 2013

8. Who could contribute to CCSDS DTN Security protocol recommendation?
Security Discussion
Is this high priority for the WG? (i.e. is there something else we should do first?)
Who could contribute to CCSDS DTN Security protocol recommendation?
October 2013

9. Forward Work: Network Management
Need:
Network monitor and control
Need for interoperability:
Visibility / transparency for cross-agency network data transfer (what are YOU doing with MY data)
Probably NOT cross-agency control
Support
NASA can work the document (and interface with IRTF dtnrg if necessary)
Can probably get two implementations (ION, DTN2) via some combination of NASA, other US participants
NEED: Second agency support (at least monitor the book)
NEED: Use cases / scenarios / requirements
October 2013

10. Network Management Discussion
Is this high priority for the WG? (i.e. is there something else we should do first?)
Who could contribute to CCSDS DTN Network Management protocol recommendation?
October 2013

11. Need for interoperability:
Forward Work: Routing
Need:
BP provides a possibly multi-hop end-to-end service, need routing
Need for interoperability:
Need consistent set of rules for routing / forwarding bundles so that they don’t go in circles
Support
NEED: Someone to be book captain
NEED: Second agency support (at least monitor the book)
NEED: Use cases / scenarios / requirements
October 2013

12. Routing Discussion
Is this high priority for the WG? (i.e. is there something else we should do first?)
Who could support?
October 2013

13. Forward Work: Erasure Coding for LTP
Need
Improve LTP performance
Need for interoperability:
Would significantly change the bits on the wire for LTP
Support
DLR has an implementation (that Tomaso will talk about tomorrow AM)
Not clear if NASA has support here
Propose to continue discussion on Wednesday after Tomoso’s presentation
October 2013

14. October 2013

15. SSI-Related CCSDS Documents
IOAG
Recommendations on a Strategy for Space Internetworking
Operations Concept for a Solar System Internetwork (SSI)
Rationale, Scenarios, and Requirements for DTN in Space
Solar System Internetwork (SSI) Architecture
CCSDS
LTP Mgmt
IETF
Contact Mgmt
SSI Network Management
Contact Graph Routing
Licklider Transmission Protocol for CCSDS
Space Communications Cross Support Architecture Description Document
RFC5050
(BP)
Multicast Routing
Bundle Protocol for CCSDS
Multi-Domain Routing
RFC5326 (LTP)
RFC5327 (LTPSec)
Space Communications Cross Support Architecture Requirements Document
SSI Coordination Procedures
Bundle Security Protocol for CCSDS
RFCXXXX TBD
Simplified Bundle Security Protocol

16. SSI Networking Components
CGR
Multicast
Routing Information Base
Network Management
Applications (file transfer, telemetry, AAE, CFS, …)
Routing Protocol
Time Synchronization
Security Key Management
Multi-Domain Routing (Route Manager)
Forwarding Information Base (Routing Table)
User
End-to-End Security (BSP)
Signaling
System
Bundle Streaming Service (BSS)
End-to-End Networking (BP)
‘TCP-like’ services (DTPC)
Reliable Transport
Unreliable Transport
Support for high-rate BP
ACS
QoS (ECOS)
Naming (ipn scheme)
Network Management Support
Naming: BP imposes only very loose naming convention; efficient, space-centric naming system (e.g. ipn naming scheme) needed.
Reliable Data Link (LTP)
Link (e.g. CCSDS TC/TM)
Link (e.g. CCSDS Prox-1)
Link (e.g. X.25)
Adapted from:
May 2010