Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

IdentifierREQ-PKI-11
TitleBasic validation of the server certificate
RequirementService consumers shall do basic validation of the server certificate:
  • Verify Server Identity:
    • Clients shall validate the server's identity to ensure they are communicating with the intended server and not a malicious actor.
  • Trust Chain Verification:
    • Clients check if the server’s certificate is issued by a trusted Certificate Authority (CA) and verify the entire chain of trust up to a root CA.
  • Certificate Revocation Checks:
    • Clients may check for certificate revocation using Certificate Revocation Lists (CRLs) or the Online Certificate Status Protocol (OCSP).
  • Certificate Expiry and Validity:
    • Ensure the server’s certificate is within its valid date range and hasn’t expired.
  • Certificate Usage and Extensions:
    • Confirm that the server’s certificate is intended for server authentication.
Source

AF5 Information and System Requirements UNDER REVIEW

Guidance

NM 27.0 - NM B2B Reference Manual

Unable to render {include} The included page could not be found.

IdentifierFFICE-008
TitleSatisfying the ICAO IERs for the Filing Service (consumer side)
RequirementThe IERs specified in Appendix B and Appendix C of the ICAO FF-ICE/R1 Implementation Guidance Manual that are applicable to the Filed Flight Plan (eFPL), Flight Plan Update and Flight Cancellation messages SHALL be satisfied by the impacted Aus/AROs.
Source

AF5 Information and System Requirements UNDER REVIEW


Guidance

ICAO Doc 9965 Ed2 Vol II (d0.993)

  • Appendix C-4 (resp. C-9 and C-8) details the required and allowed data elements for the Filed Flight Plan message (resp. for the Flight Plan Update message and the Flight Cancellation message).

FIXM

NM 27.0 - NM B2B Reference Manual



IdentifierFFICE-009
TitleProvision of an expanded route if the submitted eFPL
Requirement

The desired route/trajectory of the submitted eFPL SHALL contain an expanded route, in line with the rules of the IFPS Users Manual. (*)

(*) NOT APPLICABLE to State Flights (incl. military flights) and to Mixed IFR/VFR operations.

Source

AF5 Information and System Requirements UNDER REVIEW

Information Exchange Requirements for FF-ICE/R1 UNDER REVIEW

Rationale

A Route/Trajectory is distinguished by the type of route provided, and the type of trajectory information provided. The FF-ICE/R1 Manual, Appendix E-3. Route/Trajectory, outlines five options for the level of details of the route/trajectory information in an eFPL, described as packages:
  - Package 1A = Route and no trajectory points
  - Package 1B = Route with selected trajectory points
  - Package 2A = Expanded Route and no trajectory points
  - Package 2B = Expanded Route with selected trajectory points
  - Package 2C = Expanded Route with complete trajectory

The exchange of 4D trajectory information is mandated by CP1,

Altogether, REQ-FFICE-009 (this requirement) and REQ-FFICE-010 require that at least Package 2B (Expanded Route with selected trajectory points) is supported in the submitted eFPL. The selection of trajectory points to be supported compulsorily is based on the minimum trajectory requirements specified in the NM IFPS User Manual R27.0.

State Flights and Mixed IFR/VFR operations are exempted from fulfilling this requirement in order to acknowledge that the information can be either sensitive or harder to originate and process.

The wording “in line with the rules of the IFPS Users Manual” is used in the requirements in order to acknowledge that the IPFS Users Manual might specify further rules on the expected route/trajectory content in some particular cases, for instance when the submitted eFPL contains en-route delay information (see e.g. chapter C-7 En-Route Delay).


Guidance

ICAO Doc 9965 Ed2 Vol II (d0.993)

  • Chapter 10 ROUTE AND TRAJECTORY INFORMATION
  • Appendix E-3. Route/Trajectory

FIXM




 FOR TEST - REQ-PKI-11 - Basic validation of the server certificate
IdentifierREQ-PKI-11
TitleBasic validation of the server certificate
RequirementService consumers shall do basic validation of the server certificate:
  • Verify Server Identity:
    • Clients shall validate the server's identity to ensure they are communicating with the intended server and not a malicious actor.
  • Trust Chain Verification:
    • Clients check if the server’s certificate is issued by a trusted Certificate Authority (CA) and verify the entire chain of trust up to a root CA.
  • Certificate Revocation Checks:
    • Clients may check for certificate revocation using Certificate Revocation Lists (CRLs) or the Online Certificate Status Protocol (OCSP).
  • Certificate Expiry and Validity:
    • Ensure the server’s certificate is within its valid date range and hasn’t expired.
  • Certificate Usage and Extensions:
    • Confirm that the server’s certificate is intended for server authentication.
Source

AF5 Information and System Requirements UNDER REVIEW

Guidance

NM 27.0 - NM B2B Reference Manual



















Unable to render {include} The included page could not be found.

  • No labels

Working Draft