At one level this document is ready for publication subject to a few relatively minor comments which I include below. However, considering that this is a safety of flight system and as such a prime target for hostile state and non-state actors of many kinds, I was surprised at the brevity of the security considerations. I also wonder if greater security would have been obtained through the use of a non-native- IP overlay such as MPLS and or through a directed path technology such as one of the SR variants.

Comments:

The draft references RFC6347 which is obsoleted by RFC9147 is this intended?

=====
2.  Terminology
SB> An early forward reference to terminology would help in reading the Introduction

=====
   packet matches a black-hole route without matching an MNP/SNP, the
   c-ASBR should drop the packet and may also generate an ICMPv6

SB> The should looks as if they should be expressed as RFC 2119 SHOULD. 
======

   The number of aircraft in operation at a given time worldwide is
   likely to be significantly less than 1M, but we will assume this
   number for a worst-case analysis.  

SB> 1M is undoubtedly true for the register of full sized human piloted aircraft, but I wonder if it holds true when UAVs (drones) are added into the mix and hence whether the obvious move towards an integrated control system for human in cockpit, remote piloted and autonomous aircraft would stress this assumption.