This is a security directorate review; editors should treat these
comments as any other last call comments.

Sorry that the review is late.  I read the draft, prepared my comments
and failed to send them out.

This draft describes requirements from the air and space communities
for nemo route optimization for aircraft and spacecraft.

Within that scope, I have no additional security concerns.

However it is important to make sure that everyone involved
understands meeting these requirements alone without more general
security requirements would not produce an acceptable solution.  If
the intent of this draft is to state all the requirements that mext
needs to consider in developing a solution that meets IETF standards
and that meets the needs of the air/space community, then it falls
significantly short.  I don't think that is the intent though; I think
this is simply intended to be one stakeholder's input.  Presumably,
even if we are only targeting deployment in air/space enviroments, we
will look at more general security and management requirements
necessary to make the technology deployable on the internet.  If we're
all on the same page on that point, then this draft is fine.

I think the stated requirements seem reasonable.  However, I'm not
actually sure that a solution exists as an extension to current basic
nemo.  In particular, requirements about minimizing or avoiding custom
software may rule out nemo.  However, perhaps I'm missing something.