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

Compare with Current View Page History

« Previous Version 2 Next »

Back to Table of Contents

Back to SBC Network Deployment Scenarios

Back to Service Provider Deployment Scenarios

Back to Access (UNI) Scenarios

In this section:

Scenario

The 

Unable to show "metadata-from": No such page "_space_variables"
 supports encryption across the access and core networks.

Background Information

  • Refer to the background information in Basic Service Availability - DNS.
  • The
    Unable to show "metadata-from": No such page "_space_variables"
    supports various encryption protocols such as TLS, IPsec and SRTP.
  • Since the peers are trusted in the core network, encryption protocols may not be necessary on this side.

Description

Encryption support

  • IADs may use secure paths, such as TLS, IPsec and SRTP for encryption.
  • The
    Unable to show "metadata-from": No such page "_space_variables"
    performs scaling as each end point requires a separate connection/tunnel. With support for encryption protocols, the
    Unable to show "metadata-from": No such page "_space_variables"
    transmits the message to the core network.

DTLS Encryption

The following cipher suites are supported for DTLS encryption:

  • rsa-with-3des-ede-cbc-sha
  • rsa-with-aes-128-cbc-sha
  • rsa-with-aes-128-cbc-sha-256
  • rsa-with-aes-256-cbc-sha
  • rsa-with-aes-256-cbc-sha-256
  • rsa-with-null-sha
  • tls_ecdh_ecdsa_with_aes_256_cbc_sha384
  • tls_ecdh_ecdsa_with_aes_256_gcm_sha384
  • tls_ecdhe_rsa_with_aes_128_cbc_sha
  • tls_ecdhe_rsa_with_aes_256_cbc_sha384

SRTP Encryption

The crypto suite profile is supported with the following values for SRTP encryption:

  • AES-CM-128-HMAC-SHA1-32 
  • AES-CM-128-HMAC-SHA1-80 

 

  • No labels