What is the business rationale for this exception? Is there a specific customer that needs this RFE?
This impacts live migration for trunk ports (likely telco customers). Specifically NTT Communications has asked for the fix as they are planning for 17.1 FFU in early 2023

Are there any security concerns?
No

What other functions, teams, or DFGs are impacted by this feature?
None, Networking DFG only

What is the estimated time to have the upstream work complete and approved?
Already merged upstream and in rhos-17.1-trunk-patches

What is the time and resources required to test this issue? On what date will automated tests be written and ready to run and report results in Polarion?

Is there potential doc impact?
No, mostly release note cleanup 

Are there new packages needed that are not packaged in OSP or RHEL? Does it require newer versions of existing dependencies (dependency bumps)?
No new packages or dependencies.
What is the support level? Tech Preview or fully supported
Full support

How invasive is the code? From very invasive, a core change to very isolated, no risk to other components?
Mostly isolated to trunk ports (and live migartion scenario)

What is the impact to deployment/updates/upgrades/FFU; what are the test plans in these areas?
No impact