1. IP Addressing & Routing - Down Downlink addressing –Normal addressing to any ground destination with normal ground routing –Packets addressed to another spacecraft would probably go to its home agent and either forwarded or discarded Should packets ever be held for later forwarding ??? Is this only done for a few special type packets ??? –Common addresses to common ground services (e.g. store & forward file server, time server, ) Non-routable (10.0.0.1,2,3) addresses Multicast to one or more systems like redundant file servers Anycast addressing ??? Need addresses for common services onboard spacecraft (file store&forward and time services provided by spacecraft) Option to query (known or broadcast address) for range of services available

2. IP Addressing & Routing - Up Uplink addressing –How does the ground network know where to send data for uplink to a spacecraft –Manual static tunnel (blind commanding) –Mobile IP To a single address at spacecraft level For each instrument on spacecraft (e.g. Express Pallet with multiple but completely separate experiments on it) –Mobile Routing to support onboard LAN –DHCP for spacecraft to pick up new address per ground station (NOT recommended)

3. IP Addressing & Routing - Onboard Onboard addressing –Private address space with NAT to ground (IPSEC issues, but could terminate IPSEC at a router and NAT on other side) –Satellite LAN with mobile routing to ground –Addresses from ground subnet (e.g. control center) Defined space address space (who administers it) –Divided up into groups, each with its home agent (billing and security issues) What can IPv6 do for us (S/C MAC address combined with other addresses Intra-spacecraft routing –Direct between different spacecraft –Down to ground, around, and back up Express pallet –Multiple independent systems owned by different groups

4. Random IP Addressing Thoughts Routing based on predicted orbit/ground station knowledge Ground backbone relative to space nodes and routing table maintenance (OSPF, BGP, EGP, IS-IS, MOSPF, AODV, DSR, MANET) How do multiple levels of security interact with routing knowledge Are link establishment issues (e.g. MAC addresses, link negotiation, transmit/rcv status) separate ???

5. More Random Thoughts Knowing addresses of other spacecraft (name/address mapping) –simple hosts file –DNS –DDNS Very Secure agents to help sort out routing and network status (probably at application layer to allow for better authentication) Mobile IP triangular routing issues VLAN on board spacecraft and bridge traffic to it (bad) Does ARP exist in any of these scenarios ??? Fault tolerance and automatic failover issues with respect to addressing and routing

6. Network Management SNMP for monitoring and managing –Ground based –Onboard based –What about over the space link (SNMP probably not very efficient bitwise) XML Industrial solutions Troubleshooting use (why am I not getting my data) –How do IP addresses allocation schemes help or hinder this –Who controls the routers (IONET, mission, spacecraft)

7. Initial Simple Scenario LAN RF/ Optic Code Mod Crypt Cmd & Data Handling Router/ Bridge Router Ethernet Hub/Switch AB12xLANHDLC RF/ Optic Mod Code Crypt Mass Store C Transmitter/ Receiver EtherHDLC Mass Store Network Time NTP Store S&Fwd Time Server Transmitter/ Receiver Bit Store Mass Store User End User 1553 Mass Store IP addressable interface

8. Advanced Operational Scenario LAN RF/ Optic Code Mod Crypt Cmd & Data Handling Router/ Bridge Router Ethernet Hub/Switch AB12xLANHDLC RF/ Optic Mod Code Crypt Mass Store C Transmitter/ Receiver EtherHDLC Mass Store Network Time NTP Store S&Fwd Time Server Transmitter/ Receiver Bit Store Mass Store User End User 1553 Mass Store Ethernet Hub/Switch Ether Mass Store Time NTP Store S&Fwd Time Server HDLC IP addressable interface

9. Future Complex Scenario LAN RF/ Optic Code Mod Crypt Cmd & Data Handling Router/ Bridge Router Ethernet Hub/Switch AB12xLANHDLC RF/ Optic Mod Code Crypt Mass Store C Transmitter/ Receiver EtherHDLC Mass Store Network Time NTP Store S&Fwd Time Server Transmitter/ Receiver Bit Store Mass Store User End User 1553 Mass Store Space Routier Node One-to-many or Many-to-many Ethernet Hub/Switch Ether Mass Store Time NTP Store S&Fwd Time Server HDLC Mass Store IP addressable interface