D.6. Communication and Network Services Standards

ID:Purpose Standard Guidance
1:Basic connectivity between technical services. Internet Protocol (IETF Standard 5, September 1981. RFCs 791/950/919/922/792/1112)

Transmission Control Protocol (IETF Standard 7, RFC 793:1981 updated by 3168:2001)

Internet Protocol, Version 6 (IPv6) (IETF RFC 2460:1998)

Domain Name System (IETF Standard 13, RFC 1034/RFC 1035:1987)

IP networking. Accommodate both IPv4 and IPv6 addressing and Network Address Translation. Utilize Quality of Service capabilities of the network.
2:Connectivity between AMN Core network and TCN networks IEEE 802.3z Gigabit Ethernet (GbE)

Border Gateway Protocol V4 (IET RFC 1771, March 1995)

BGP Communities Attribute (IETF RFC 1997, August 1996)

Multicast Source Discovery Protocol (MSDP) (IETF RFC 3618, October 2003)

Protocol Independent Multicast - Sparse Mode (PIM-SM) (IETF RFC 4601, August 2006)

Detailed Interface Control Document for "Connection Between CISAF network and TCN networks" (Thales Doc: F0057/62543313/558/-/I/EN), dated 24 Feb 2012
3:Service transport protocol Hypertext Transfer Protocol - HTTP 1.1 (RFC 2616:1999) HTTP shall be used as the transport protocol for information without 'need-to-know' caveats between all service providers and consumers.

HTTPS shall be used as the transport protocol between all service providers and consumers to ensure confidentiality requirements.

4:Provide communications security over the network above the Transport Layer Mandatory: Transport Layer Security (TLS) Protocol Version 1.2 (RFC 5246:2008)

Fading (until Dec 2011): Transport Layer Security (TLS) Protocol Version 1.0 (RFC 2246:1999)

Retired: Secure Sockets Layer (SSL) Protocol, Version 3.0, 18 Nov 1996

 
5:Voice communication VoIP: SIP RFC 3261

- Audio data compression Codec ITU-T Recommendation G.729 (01/07) - The use of G.729 may require a license fee and/or royalty fee - DiffServ,PHB and DSCP defined by IETF RFC 2474

- ITU-T G.Imp729 (11/09)

- Interval between Voice packets 40ms

- RTP protocol ports 16384 and/or 16385

- Detailed Interface Control Document for "Voice over Secure IP (VoSIP) Network Service" (Thales Doc: F0057/61935771/558/ICD VOSIP/A/EN; NATO RESTRICTED)

6:Secure Network management Simple Network Management Protocol Version 3 (SNMPv3)  
7:Facilitate the access and authorization between AMN users Directory service: LDAPv3, RFC 4510

Authentication: Kerberos version 5, RFC 1510

The AMN OPT has identified three options available to a nation when joining their national network extension to the AMN:
  1. Join the ISAF SECRET AD forest on AMN Core

  2. Join the AD forest of an existing AMN TCN

  3. Create own AD forest for the new AMN TCN

(Option 1 and 2 should be considered before option 3. Ref: AMN Systems engineering CONOPS dated 29 April 10).

Whilst LDAP is a vendor independent standard, in practice Active Directory (AD) is the product providing directory services on the AMN. AD provides additional services aside from LDAP like functionality.

8:Time synchronisation on the AMN Mandatory: Network Time Protocol version 3 (NTPv3), dated March 1992. RFC 1305 The W32Time service on all Windows DCs on the AMN Core is synchronizing time through the Domain hierarchy (NT5DS type).

POC: NCIA / Pierre Calvez

9:Video Collaboration Mandatory: Signalling - H.323, Audio - G.722.1c and Video - H.263 AMN VTC over IP is based on a QoS-Enabled Network Infrastructure(QENI) using Diffserve. AMN Wide allowed interconnections are A) Peer to Peer, B) Peer to MCU and C) Peer to MCU to MCU to Peer

POC: NCIA / Pierre Calvez

Table D.4. Communication and Network Services Standards