CCSDS Toulouse November 2004 Cislunar WG CCSDS Toulouse November 2004

Cislunar Goals Create a top-level architecture and operations concept for communicating effectively over the whole range of cislunar distances. Review current and emerging CCSDS standards and recommend any updates required to keep them current. Examine the spectrum of new Internet development activities that are proceeding, and identify where they may be applicable to cislunar Recommend standards for cislunar communications. Define architecture that handles: Voice/video (realtime and non-realtime) Data (realtime and non-realtime) Between Earth and Moon (RTT ~2.5s) Extensible to Mars (RTT ~ 8--40 minutes)

Cislunar Activities Green book describing Interface with C3I activity Architecture Operations Concept Interface with C3I activity Paper describing candidate protocols Review of applicable CCSDS Protocols SCPS-TP Updates

Starting from… Treat CCSDS channel access services as interfaces to IP

And recognizing ongoing work in the IETF… The Stream Control Transmission Protocol SCTP. The Datagram Congestion Control Protocol (DCCP). Voice Over IP (VOIP). Disruption Tolerant Networking (DTN). LEMONADE enhancements to Internet email to support diverse service environments. Internet over Digital Broadcast Video Networks.

IP-Based Communications Architecture Single packet-switched network carrying: Voice (over IP) data HDTV Quality of Service Protect life-critical and mission-critical data from congestion QoS options (not mutually exclusive) Manually set up class-based queueing classes Integrated Services Differentiated Services Standard IP TOS

“Draft Green Book” More a compendium of tools with some rationale for why they’re needed Needs Architecture Use cases / scenarios to beat the architecture against

Review current and emerging CCSDS standards A number of vendors are selling SCPS-TP-based Performance Enhancing Proxies (PEPs) SIS-SCPS-INTEREST mailing list started to get vendor inputs All the major SCPS vendors that I know of are on the list Active discussion of SCPS-TP Clarifications to improve interoperability Possible extensions to address specific needs