< draft-ietf-raw-ldacs-02.txt		draft-ietf-raw-ldacs-03.txt >
	RAW N. Maeurer, Ed.		RAW N. Maeurer, Ed.
	Internet-Draft T. Graeupl, Ed.		Internet-Draft T. Graeupl, Ed.
	Intended status: Informational German Aerospace Center (DLR)		Intended status: Informational German Aerospace Center (DLR)
	Expires: 28 April 2021 C. Schmitt, Ed.		Expires: 30 April 2021 C. Schmitt, Ed.
	Research Institute CODE, UniBwM		Research Institute CODE, UniBwM
	25 October 2020		27 October 2020
	L-band Digital Aeronautical Communications System (LDACS)		L-band Digital Aeronautical Communications System (LDACS)
	draft-ietf-raw-ldacs-02		draft-ietf-raw-ldacs-03
	Abstract		Abstract
	This document provides an overview of the architecture of the L-band		This document provides an overview of the architecture of the L-band
	Digital Aeronautical Communications System (LDACS), which provides a		Digital Aeronautical Communications System (LDACS), which provides a
	secure, scalable and spectrum efficient terrestrial data link for		secure, scalable and spectrum efficient terrestrial data link for
	civil aviation. LDACS is a scheduled, reliable multi-application		civil aviation. LDACS is a scheduled, reliable multi-application
	cellular broadband system with support for IPv6. LDACS shall provide		cellular broadband system with support for IPv6. LDACS shall provide
	a data link for IP network-based aircraft guidance. High reliability		a data link for IP network-based aircraft guidance. High reliability
	and availability for IP connectivity over LDACS are therefore		and availability for IP connectivity over LDACS are therefore
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on 28 April 2021.		This Internet-Draft will expire on 30 April 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 32, line 4 ¶		skipping to change at page 32, line 4 ¶
	CPDLC Controller Pilot Data Link Communication		CPDLC Controller Pilot Data Link Communication
	DT Nominal Time value for RSP		DT Nominal Time value for RSP
	ET Operational Time value for RCP		ET Operational Time value for RCP
	FH Flight Hour		FH Flight Hour
	MA Monitoring and Alerting criteria		MA Monitoring and Alerting criteria
	OT Operational Time value for RSP		OT Operational Time value for RSP
	RCP Required Communication Performance		RCP Required Communication Performance
	RSP Required Surveillance Performance		RSP Required Surveillance Performance
	TT Nominal Time value for RCP		TT Nominal Time value for RCP
	+--------------+---------------+		+========================+=============+=============+
	| | ECP 130 |		| | ECP 130 | ECP 130 |
	+--------------+-------+-------+		+========================+=============+=============+
	| Parameter | ET | TT95% |		| Parameter | ET | TT95% |
	+--------------+-------+-------+		+------------------------+-------------+-------------+
	| Transaction | 130 | 67 |		| Transaction Time (sec) | 130 | 67 |
	| Time (sec) | | |		+------------------------+-------------+-------------+
	+--------------+-------+-------+		| Continuity | 0.999 | 0.95 |
	| Continuity | 0.999 | 0.95 |		+------------------------+-------------+-------------+
	+--------------+-------+-------+		| Availability | 0.989 | 0.989 |
	| Availability | 0.989 |		+------------------------+-------------+-------------+
	+--------------+---------------+		| Integrity | 1E-5 per FH | 1E-5 per FH |
	| Integrity | 1E-5 per FH |		+------------------------+-------------+-------------+
	+--------------+---------------+
	Figure 5: CPDLC Requirements for ECP		Table 1: CPDLC Requirements for ECP
	+--------------+--------------------+---------------+		+==============+==========+==============+=========+=========+
	| | RCP 240 | RCP 400 |		| | RCP 240 | RCP 240 | RCP 400 | RCP 400 |
	+--------------+----------+---------+-------+-------+		+==============+==========+==============+=========+=========+
	| Parameter | ET | TT95% | ET | TT95% |		| Parameter | ET | TT95% | ET | TT95% |
	+--------------+----------+---------+-------+-------+		+--------------+----------+--------------+---------+---------+
	| Transaction | 240 | 210 | 400 | 350 |		| Transaction | 240 | 210 | 400 | 350 |
	| Time (sec) | | | | |		| Time (sec) | | | | |
	+--------------+----------+---------+-------+-------+		+--------------+----------+--------------+---------+---------+
	| Continuity | 0.999 | 0.95 | 0.999 | 0.95 |		| Continuity | 0.999 | 0.95 | 0.999 | 0.95 |
	+--------------+----------+---------+-------+-------+		+--------------+----------+--------------+---------+---------+
	| Availability | 0.989 (safety) | 0.989 |		| Availability | 0.989 | 0.989 | 0.989 | 0.989 |
	| | 0.9899 (efficiency)| |		| | (safety) | (efficiency) | | |
	+--------------+--------------------+---------------+		+--------------+----------+--------------+---------+---------+
	| Integrity | 1E-5 per FH | 1E-5 per FH |		| Integrity | 1E-5 per | 1E-5 per FH | 1E-5 | 1E-5 |
	+--------------+--------------------+---------------+		| | FH | | per FH | per FH |
			+--------------+----------+--------------+---------+---------+
	Figure 6: CPDLC Requirements for RCP		Table 2: CPDLC Requirements for RCP
	RCP Monitoring and Alerting Criteria in case of CPDLC:		RCP Monitoring and Alerting Criteria in case of CPDLC:
	- MA-1: The system shall be capable of detecting failures and		- MA-1: The system shall be capable of detecting failures and
	configuration changes that would cause the communication service		configuration changes that would cause the communication service
	no longer meet the RCP specification for the intended use.		no longer meet the RCP specification for the intended use.
	- MA-2: When the communication service can no longer meet the RCP		- MA-2: When the communication service can no longer meet the RCP
	specification for the intended function, the flight crew and/or		specification for the intended function, the flight crew and/or
	the controller shall take appropriate action.		the controller shall take appropriate action.
	+------------+---------------+--------------------+---------------+		+==============+=====+=====+==========+==============+======+=======+
	| | RSP 160 | RSP 180 | RSP 400 |		| | RSP | RSP | RSP 180 | RSP 180 | RSP |RSP 400|
	+------------+-------+-------+----------+---------+-------+-------+		| | 160 | 160 | | | 400 | |
	| Parameter | OT | DT95% | OT | DT95% | OT | DT95% |		+==============+=====+=====+==========+==============+======+=======+
	+------------+-------+-------+----------+---------+-------+-------+		| Parameter | OT |DT95%| OT | DT95% | OT | DT95% |
	| Trans- | | | | | | |		+--------------+-----+-----+----------+--------------+------+-------+
	| action | 160 | 90 | 180 | 90 | 400 | 300 |		| Transaction | 160 | 90 | 180 | 90 | 400 | 300 |
	| Time (sec) | | | | | | |		| Time (sec) | | | | | | |
	+------------+-------+-------+----------+---------+-------+-------+		+--------------+-----+-----+----------+--------------+------+-------+
	| Continuity | 0.999 | 0.95 | 0.999 | 0.95 | 0.999 | 0.95 |		| Continuity |0.999| 0.95| 0.999 | 0.95 |0.999 | 0.95 |
	+------------+-------+-------+----------+---------+-------+-------+		+--------------+-----+-----+----------+--------------+------+-------+
	| Avail- | 0.989 | 0.989 (safety) | 0.989 |		| Availability |0.989|0.989| 0.989 | 0.989 |0.989 | 0.989 |
	| ability | | 0.9899 (efficiency)| |		| | | | (safety) | (efficiency) | | |
	+------------+---------------+--------------------+---------------+		+--------------+-----+-----+----------+--------------+------+-------+
	| Integrity | 1E-5 per FH | 1E-5 per FH | 1E-5 per FH |		| Integrity | 1E-5| 1E-5| 1E-5 per | 1E-5 per FH | 1E-5 | 1E-5 |
	+------------+---------------+--------------------+---------------+		| | per | per | FH | |per FH| per FH|
			| | FH | FH | | | | |
			+--------------+-----+-----+----------+--------------+------+-------+
	Figure 7: ADS-C Requirements		Table 3: ADS-C Requirements
	RCP Monitoring and Alerting Criteria:		RCP Monitoring and Alerting Criteria:
	- MA-1: The system shall be capable of detecting failures and		- MA-1: The system shall be capable of detecting failures and
	configuration changes that would cause the ADS-C service no longer		configuration changes that would cause the ADS-C service no longer
	meet the RSP specification for the intended function.		meet the RSP specification for the intended function.
	- MA-2: When the ADS-C service can no longer meet the RSP		- MA-2: When the ADS-C service can no longer meet the RSP
	specification for the intended function, the flight crew and/or		specification for the intended function, the flight crew and/or
	the controller shall take appropriate action.		the controller shall take appropriate action.
End of changes. 10 change blocks.
	52 lines changed or deleted		54 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/