| rfc9372v2.txt | rfc9372.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) N. Mäurer, Ed. | Internet Engineering Task Force (IETF) N. Mäurer, Ed. | |||
| Request for Comments: 9372 T. Gräupl, Ed. | Request for Comments: 9372 T. Gräupl, Ed. | |||
| Category: Informational German Aerospace Center (DLR) | Category: Informational German Aerospace Center (DLR) | |||
| ISSN: 2070-1721 C. Schmitt, Ed. | ISSN: 2070-1721 C. Schmitt, Ed. | |||
| Research Institute CODE, UniBwM | Research Institute CODE, UniBwM | |||
| February 2023 | March 2023 | |||
| L-Band Digital Aeronautical Communications System (LDACS) | L-Band Digital Aeronautical Communications System (LDACS) | |||
| Abstract | Abstract | |||
| This document gives an overview of the L-band Digital Aeronautical | This document gives an overview of the L-band Digital Aeronautical | |||
| Communications System (LDACS) architecture, which provides a secure, | Communications System (LDACS) architecture, which provides a secure, | |||
| scalable, and spectrum-efficient terrestrial data link for civil | scalable, and spectrum-efficient terrestrial data link for civil | |||
| aviation. LDACS is a scheduled and reliable multi-application | aviation. LDACS is a scheduled and reliable multi-application | |||
| cellular broadband system with support for IPv6. It is part of a | cellular broadband system with support for IPv6. It is part of a | |||
| skipping to change at line 182 ¶ | skipping to change at line 182 ¶ | |||
| reasons since a previous architecture based on ISO/OSI protocols (the | reasons since a previous architecture based on ISO/OSI protocols (the | |||
| ATN/OSI) failed in the marketplace. | ATN/OSI) failed in the marketplace. | |||
| In the context of safety-related communications, LDACS will play a | In the context of safety-related communications, LDACS will play a | |||
| major role in future ATM. ATN/IPS data links will provide | major role in future ATM. ATN/IPS data links will provide | |||
| diversified terrestrial and space-based connectivity in a multilink | diversified terrestrial and space-based connectivity in a multilink | |||
| concept called the Future Communications Infrastructure (FCI) | concept called the Future Communications Infrastructure (FCI) | |||
| [VIR2021]. From a technical point of view, the FCI will realize | [VIR2021]. From a technical point of view, the FCI will realize | |||
| airborne and multihomed IPv6 networks connected to a global ground | airborne and multihomed IPv6 networks connected to a global ground | |||
| network via at least two independent communication technologies. | network via at least two independent communication technologies. | |||
| This is considered in more detail in related IETF Internet-Drafts | This is considered in more detail in related IETF documents | |||
| [LISP-GB-ATN] [RTGWG-ATN-BGP]. As such, ICAO has actively sought out | [LISP-GB-ATN] [RTGWG-ATN-BGP]. As such, ICAO has actively sought out | |||
| the support of IETF to define a mobility solution for step (2), which | the support of IETF to define a mobility solution for step (2), which | |||
| is currently the Locator/ID Separation Protocol (LISP). | is currently the Locator/ID Separation Protocol (LISP). | |||
| In the context of the Reliable and Available Wireless (RAW) Working | In the context of the Reliable and Available Wireless (RAW) Working | |||
| Group, developing options, such as intelligent switching between data | Group, developing options, such as intelligent switching between data | |||
| links, for reliably delivering content from and to endpoints is | links, for reliably delivering content from and to endpoints is | |||
| foreseen. As LDACS is part of such a concept, the work of RAW is | foreseen. As LDACS is part of such a concept, the work of RAW is | |||
| immediately applicable. In general, with the aeronautical | immediately applicable. In general, with the aeronautical | |||
| communications system transitioning to ATN/IPS and data being | communications system transitioning to ATN/IPS and data being | |||
| skipping to change at line 1617 ¶ | skipping to change at line 1617 ¶ | |||
| Thubert, P., Ed., Cavalcanti, D., Vilajosana, X., Schmitt, | Thubert, P., Ed., Cavalcanti, D., Vilajosana, X., Schmitt, | |||
| C., and J. Farkas, "Reliable and Available Wireless | C., and J. Farkas, "Reliable and Available Wireless | |||
| Technologies", Work in Progress, Internet-Draft, draft- | Technologies", Work in Progress, Internet-Draft, draft- | |||
| ietf-raw-technologies-06, 30 November 2022, | ietf-raw-technologies-06, 30 November 2022, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-raw- | <https://datatracker.ietf.org/doc/html/draft-ietf-raw- | |||
| technologies-06>. | technologies-06>. | |||
| [RAW-USE-CASES] | [RAW-USE-CASES] | |||
| Bernardos, C. J., Ed., Papadopoulos, G. Z., Thubert, P., | Bernardos, C. J., Ed., Papadopoulos, G. Z., Thubert, P., | |||
| and F. Theoleyre, "RAW Use-Cases", Work in Progress, | and F. Theoleyre, "RAW Use-Cases", Work in Progress, | |||
| Internet-Draft, draft-ietf-raw-use-cases-08, 22 October | Internet-Draft, draft-ietf-raw-use-cases-09, 13 March | |||
| 2022, <https://datatracker.ietf.org/doc/html/draft-ietf- | 2023, <https://datatracker.ietf.org/doc/html/draft-ietf- | |||
| raw-use-cases-08>. | raw-use-cases-08>. | |||
| [RFC4301] Kent, S. and K. Seo, "Security Architecture for the | [RFC4301] Kent, S. and K. Seo, "Security Architecture for the | |||
| Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, | Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, | |||
| December 2005, <https://www.rfc-editor.org/info/rfc4301>. | December 2005, <https://www.rfc-editor.org/info/rfc4301>. | |||
| [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, | [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, | |||
| "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, | "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, | |||
| DOI 10.17487/RFC4861, September 2007, | DOI 10.17487/RFC4861, September 2007, | |||
| <https://www.rfc-editor.org/info/rfc4861>. | <https://www.rfc-editor.org/info/rfc4861>. | |||
| skipping to change at line 1698 ¶ | skipping to change at line 1698 ¶ | |||
| [RTCA2019] Radio Technical Commission for Aeronautics (RTCA), | [RTCA2019] Radio Technical Commission for Aeronautics (RTCA), | |||
| "Internet Protocol Suite Profiles", RTCA DO-379, September | "Internet Protocol Suite Profiles", RTCA DO-379, September | |||
| 2019, <https://standards.globalspec.com/std/14224450/rtca- | 2019, <https://standards.globalspec.com/std/14224450/rtca- | |||
| do-379>. | do-379>. | |||
| [RTGWG-ATN-BGP] | [RTGWG-ATN-BGP] | |||
| Templin, F., Ed., Saccone, G., Dawra, G., Lindem, A., and | Templin, F., Ed., Saccone, G., Dawra, G., Lindem, A., and | |||
| V. Moreno, "A Simple BGP-based Mobile Routing System for | V. Moreno, "A Simple BGP-based Mobile Routing System for | |||
| the Aeronautical Telecommunications Network", Work in | the Aeronautical Telecommunications Network", Work in | |||
| Progress, Internet-Draft, draft-ietf-rtgwg-atn-bgp-19, 6 | Progress, Internet-Draft, draft-ietf-rtgwg-atn-bgp-19, 7 | |||
| November 2022, <https://datatracker.ietf.org/doc/html/ | November 2022, <https://datatracker.ietf.org/doc/html/ | |||
| draft-ietf-rtgwg-atn-bgp-19>. | draft-ietf-rtgwg-atn-bgp-19>. | |||
| [SAJ2014] Haindl, B., Meser, J., Sajatovic, M., Müller, S., | [SAJ2014] Haindl, B., Meser, J., Sajatovic, M., Müller, S., | |||
| Arthaber, H., Faseth, T., and M. Zaisberger, "LDACS1 | Arthaber, H., Faseth, T., and M. Zaisberger, "LDACS1 | |||
| conformance and compatibility assessment", IEEE/AIAA 33rd | conformance and compatibility assessment", IEEE/AIAA 33rd | |||
| Digital Avionics Systems Conference (DASC), pp. 1-11, | Digital Avionics Systems Conference (DASC), pp. 1-11, | |||
| DOI 10.1109/DASC.2014.6979447, October 2014, | DOI 10.1109/DASC.2014.6979447, October 2014, | |||
| <https://doi.org/10.1109/DASC.2014.6979447>. | <https://doi.org/10.1109/DASC.2014.6979447>. | |||
| End of changes. 4 change blocks. | ||||
| 5 lines changed or deleted | 5 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||