[MEXT] comments to draft-bernardos-mext-aero-nemo-ro-sol-analysis-01.txt

Hi Carlos and Marcelo,

Thanks for writing this document.
It summarizes the list of right questions to aviation industry.
Unfortunately, I don't have answers to any of them :-)

Some comments

In section 3.1,
    o  if a craft attached to an ANSP access network is communicating
       with a CN attached to the same ANSP, is it required for the NEMO
       RO solution to survive when the link of the ANSP to its gACSP  
goes
       down? or put in a different way, would it be OK for such a
       communication to be broken?  It should be noted that the default
       MRHA path used by the NEMO Basic Support protocol would likely
       fail in this scenario.

Are you sure we need to consider the scenario of gACSP failure?
gACSP failure seems very critical errors and MUST NOT be happened...

In section 3.2,
    entities belong to the same administrative domain.  However, this
    does not mean that this scenario is excluded from having trust
    issues, since a particular solution might require to inject routes  
in
    some parts of the network (e.g., RO entities owned by an airline and
    placed in networks not managed by the airline, anycast routing,
    etc.), and this could require additional trust relationships.

This additional trust relationships are not always required to be  
dynamic one.
It might be just business agreements, isn't it?

I think we need more information from aviation industry such as
- How many CNs does each MR communicates with?
- How many ANSPs does each MR communicate with?
- The least HOPs path is not always the shortest latency path.
   It depends on the topology (L1-L3) of gACSP and ANSPs.
   Since the aviation network is somehow closed network and designed  
by themselves,
   we need more detailed information of topology information.

regards,
ryuji

_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext