Hi John,

> I guess that it might be helpful to get some more insight into the expected 
> operating environment, since going by the draft as written it would appear 
> that celestial body based issuance would require deep space operators to 
> carry additional and distinctly non-aggregataable routes for all elements 
> served that have celestial-based allocations…    


That’s exactly backwards. The intent is to provide aggregation along celestial 
body lines.

The network operating environment is pretty spartan. Deep space communications 
are expensive, slow, and have major outages when physics precludes the 
connection.  Redundancy is luxury for the distant future. There will be relay 
nodes in place, and eventually many different surface networks that will be 
interconnected.  Those networks are deployed by a number of different space 
agencies, who are somewhat mutually cooperative, but need gudiance about 
network architecture. 

Now, according to current policies, each of these agencies will use part of 
their own address space allocations, presumably one prefix per network. As 
those allocations are from different RIRs and different blocks, all of those 
prefixes will result in explicit routes carried across interplanetary links.  

By doing allocation along celestial bodies, each agency will be able to get a 
prefix for their network from the common block for that specific body.  These 
can then be aggregated when they hit interplanetary links, resulting in minimal 
overhead.

Regards,
Tony


_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to