Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

UAS ROADMAP 2005
layer 4 protocol is in use, the receiving terminal’s transport layer may send acknowledgments of receipt
of packets. Two layer 4 protocols are recommended and both should be present on both the transmitting
and receiving platforms. The receiver should be able to determine which protocol the transmitting system
utilized by the information in the packet header.
� User datagram protocol (UDP), IETF Standard 6, IETF RFC 768. This is a mandated standard
identified in the DISR. UDP is used when transport layer delivery assurance of packets sent over the
data link is not required (e.g., in the transmission of video frames, a condition where tolerance of
errors and/or missing frames is high and low latency is important).
� Transport control protocol (TCP), IETF Standard 7, IETF RFC 793. This is a mandated standard
identified in the DISR. The TCP [RFC 761] provides a connection oriented reliable byte stream
service. TCP is a bi-directional protocol, which has no concept of messages. Any framing has to be
added at the application level. TCP contains an acknowledgement scheme which makes it reliable
(bytes are delivered correctly and in order) and which implements flow control.
The Network Layer (OSI Layer 3)
In the OSI reference model, the network layer (layer 3) provides a means for addressing messages and
translating logical addresses and names into physical addresses. It also provides a means for determining
the route from the source to the destination computer and manages traffic problems, such as switching,
routing, and controlling the congestion of data packets. The ubiquitous standard for layer 3 networking is
the Internet Protocol (IP). IP version 4 (IPv4) is currently in widespread usage. IP version 6 (IPv6) is an
emerging standard that is in development, and mandated for DoD usage with a transition completion goal
of 2008, per DoD-CIO memoranda dated 9 June 2003.
� IP, IETF Standard 5, IETF RFCs 791, 792, 950, 919, 922, 1112. This is a mandated standard
identified in the DISR.
INTERNET STANDARDS
� Hypertext transfer protocol (HTTP) Version 1.1, internet engineering task force (IETF) request for
comment (RFC) 2616. HTTP shall be the main protocol used for web browsing. This is a mandated
standard identified in the DISR.
� Hypertext markup language (HTML) 4.01, world wide web consortium (W3C) recommendation.
This is a mandated standard identified in paragraph 2.5.4.1 – as of volume I of the JTA.
� File transfer protocol (FTP), IETF Standard 9, IETF RFC 959. This is a mandated standard identified
in.the DISR
� Simple mail transfer protocol (SMTP), IETF RFCs 1870, 2821. This is a mandated standard
identified in.the DISR
� Multi-purpose internet mail extensions (MIME), IETF RFCs 2045-2049. This is a mandated standard
identified in.the DISR
� Uniform resource locator (URL), uniform resource identifier (URI), IETF RFCs 1738, 1808, 1866.
IETF RFC 1738 is mandated in.the DISR
� Unicode universal character set, international organization for standardization (ISO) 10646,
“universal multiple-octet coded character set (UCS)”, IETF RFC 2277 http://unicode.org. This is a
mandated standard identified in the DISR
INTERNETWORKING (ROUTER) STANDARDS
Routers are used to interconnect various sub networks and end-systems. Protocols necessary to provide
this service are specified below. IETF RFC 1812 is an umbrella standard that references other documents
and corrects errors in some of the referenced documents. The DISR mandates the following standards.
� ��IETF
RFC 1886, DNS Extensions to Support IPv6, December 1995.
� ��IETF
RFC 3152, Delegation of IP6.ARPA, August 2001.
APPENDIX E – INTEROPERABILITY STANDARDS
Page E-3