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

2. SIS_DTN 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. SIS_DTN 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 4 SIS-DTN: FORWARD PLANNING October 2013

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

6. SIS_DTN 6 SIS-DTN Forward Work 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 May 2010 Done Nearly Done In Framework Approved Not In Framework

7. SIS_DTN 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 (http://tools.ietf.org/html/rfc6257)http://tools.ietf.org/html/rfc6257 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) http://tools.ietf.org/html/draft-irtf-dtnrg-sbsp-00 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. SIS_DTN 8 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. SIS_DTN 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. SIS_DTN 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. SIS_DTN 11 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. SIS_DTN 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. SIS_DTN 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. SIS_DTN 14 October 2013

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

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