SomeoneElse’sNET

IONET Big I

MCCGO

White Sands

TDRSS

Tracking#1

Tracking#2

Multicast Registration

Routers Proxy Multicast Registration

For Spacecraft

Multicast ProtocolPares Extra Links

SomeoneElse’sNET

IONET Big I

MCCGO

White Sands

TDRSS

Tracking#1

Tracking#2

On Launch Pad1. Radios turned ON at Ground Operations and White Sands

2. RF connectivity established

3. MCC sends command using Multicast

SomeoneElse’sNET

IONET Big I

MCCGO

White Sands

TDRSS

Tracking#1

Tracking#2

Launch to Orbit1. Radios turned ON at Ground Operations and White Sands

2. RF connectivity established

3. MCC sends command using Multicast

SomeoneElse’sNET

IONET Big I

MCCGO

White Sands

TDRSS

Tracking#1

Tracking#2

On Orbit1. Radios turned ON at Ground Operations and White Sands

2. RF connectivity established

3. MCC sends command using Multicast

SomeoneElse’sNET

IONET Big I

MCCGO

White Sands

TDRSS

Tracking#1

Tracking#2

Some Possibilities(These May or MAY NOT be good ideas.)

FlightComputer

UnicastCommand

IPsec MulticastCommand

UnicastCommand

Conclusions base on Experience. Deployments and Observations

• When it is all said and done you WILL implement multiple mechanisms to get to the vehicle. 

• Mobile-NETWORKING (nemo) is a protocol that may be useful – particularly for LEO. 

• Limited strategic deployment of static routing is useful.• Default routes are useful.  • Dynamic routing may be useful. • Mobile Ad Hoc Networking (manet) may be useful. • While on the pad or in testing at the factory is the most

simplistic network of all and easy to solve as there is no real time-sensitive mobility.

• Launch and Reentry are the hardest to solve and communications is most critical at this point in the mission.  

Launch / Reentry Requirements• No loss of contact with the vehicle if at all possible• For the must part, any practical route convergence time

is associated with dynamic routing is unacceptable• For the most part, any route time-outs as a result of

mobile-ip or dynamic routing are unacceptable • Bandwidth is at a minimum during launch and re-entry.

Additional bandwidth is not available to allow routing protocols to run with reduced timers –- particularly since it still will probably not get me the convergence time I want. 

• Use of static routes is problematic and should be avoided. – To easy to misconfigure– Difficult to trouble-shoot– Predictive static routing is really a new routing protocol.