RE: [AVT] The Secure Real-time Transport Protocol : Padding/Bandw idth.
"Waterhouse, Richard" <Richard.Waterhouse@GDC4S.Com> Tue, 24 June 2003 16:43 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23103 for <avt-archive@odin.ietf.org>; Tue, 24 Jun 2003 12:43:29 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OGh2W10021 for avt-archive@odin.ietf.org; Tue, 24 Jun 2003 12:43:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Uqsn-0002aq-OM; Tue, 24 Jun 2003 12:43:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UqsB-0002aC-6C for avt@optimus.ietf.org; Tue, 24 Jun 2003 12:42:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23058 for <avt@ietf.org>; Tue, 24 Jun 2003 12:42:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Uqru-0004B5-00 for avt@ietf.org; Tue, 24 Jun 2003 12:42:06 -0400
Received: from ns4.gdgsc.com ([192.160.62.68] helo=newman.gdgsc.com) by ietf-mx with esmtp (Exim 4.12) id 19Uqrj-0004Am-00 for avt@ietf.org; Tue, 24 Jun 2003 12:41:55 -0400
Received: from gscex01.gsc.gte.com ("port 1932"@gscex01.gsc.gte.com [155.95.162.170]) by newman.gdgsc.com (PMDF V6.2 #30756) with ESMTP id <0HGZ00LJ2VMGBS@newman.gdgsc.com> for avt@ietf.org; Tue, 24 Jun 2003 12:39:52 -0400 (EDT)
Received: by gscex01.gsc.gte.com with Internet Mail Service (5.5.2653.19) id <MSYJGMFJ>; Tue, 24 Jun 2003 12:40:34 -0400
Content-return: allowed
Date: Tue, 24 Jun 2003 12:40:25 -0400
From: "Waterhouse, Richard" <Richard.Waterhouse@GDC4S.Com>
Subject: RE: [AVT] The Secure Real-time Transport Protocol : Padding/Bandw idth.
To: norbert.rossello@mindspeed.com
Cc: avt@ietf.org
Message-id: <085B0B78E426244B9C29A160098DAFF5019B4EA9@ndhmex02.ndhm.gd-ns.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
We don't use SRTP, but we do use AES. We use Counter Mode. This mode doesn't have "error extension". Thus after we have encrypted the 48 bytes we can proceed to throw away 8 of them. When it comes time to decrypt the receiver can just add 8 bytes of padding on the black side, decrypt, and then throw away the padding bits on the red side. The problem you are pointing out is not inherent to AES, it's inherent to the mode you are using with AES. > ---------- > From: > norbert.rossello@mindspeed.com[SMTP:norbert.rossello@mindspeed.com] > Sent: Tuesday, June 24, 2003 12:08 PM > To: mbaugher@cisco.com; rolf.blom@era.ericsson.se; > elisabetta.carrara@era.ericsson.se; mcgrew@cisco.com; > mats.naslund@era.ericsson.se; karl.norrman@era.ericsson.se; > oran@cisco.com; avt@ietf.org > Subject: [AVT] The Secure Real-time Transport Protocol : > Padding/Bandwidth. > > > Madam and Sirs, > > I am responsible for Cipher/VoIP implementation at Mindspeed (ex > Conexant). > > I would like to draw your attention about padding: > draft-ietf-avt-srtp-05.txt - 4.1.1 : > <<Each of the three terms in the XOR-sum above is padded with as many > leading zeros as needed to make the operation well-defined..>> > > By implementing block cipher (as AES), as you experts know already, > we have been facing the padding method consequence (RFC1423, NIST,..) > leading to increase bandwidth. > > Example: > G.711 at 5ms generates a payload of 40 bytes. > AES blocks are made of 128 bits = 16 bytes. > 40 / 16 = 2.5: AES will require 3 blocks increasing the encrypted payload > up to 16 x 3 =48 bytes. > Hence, AES encryption has impacted the original bandwidth consumption by > +20%. > This drawback applies to others codec G.729,...which have been designed to > save bandwidth. > This bandwidth increase is not acceptable for many Gtw manufacturers. > > Mindspeed would like to submit to you a new scheme that allows encrypting > packets which size is not a multiple of AES block size without impacting > bandwidth > complying with existing modes ECB, CBC,... > > Please, let me know if this new scheme could contribute to SRTP, > so I will send you related documents. > > Dr Norbert Rossello. > Group Leader MindSpeed Cipher Development > norbert.rossello@mindspeed.com > > Mindspeed Technologies > BP 161 > 06903 Sophia Antipolis Cedex - France > www.mindspeed.com > > > > > _______________________________________________ > Audio/Video Transport Working Group > avt@ietf.org > https://www1.ietf.org/mailman/listinfo/avt > _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- RE: [AVT] The Secure Real-time Transport Protocol… Waterhouse, Richard
- RE: [AVT] The Secure Real-time Transport Protocol… Euchner Martin