IETF Logo Mail Archive

RE: [ipcdn] FW: DISCUSS: draft-ietf-ipcdn-bpiplus-mib-14

"Jean-Francois Mule" <jf.mule@cablelabs.com> Thu, 07 October 2004 21:57 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02197 for <ipcdn-archive@ietf.org>; Thu, 7 Oct 2004 17:57:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFgQ0-0007Tf-P3 for ipcdn-archive@ietf.org; Thu, 07 Oct 2004 18:07:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFg84-0007Ag-UL; Thu, 07 Oct 2004 17:48:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFfop-0008KV-B1 for ipcdn@megatron.ietf.org; Thu, 07 Oct 2004 17:29:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29344 for <ipcdn@ietf.org>; Thu, 7 Oct 2004 17:28:56 -0400 (EDT)
Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFfyb-0005pS-MH for ipcdn@ietf.org; Thu, 07 Oct 2004 17:39:06 -0400
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id i97LSOkH023954; Thu, 7 Oct 2004 15:28:24 -0600 (MDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ipcdn] FW: DISCUSS: draft-ietf-ipcdn-bpiplus-mib-14
Date: Thu, 07 Oct 2004 15:28:23 -0600
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D8480406A3C3@srvxchg.cablelabs.com>
Thread-Topic: [ipcdn] FW: DISCUSS: draft-ietf-ipcdn-bpiplus-mib-14
Thread-Index: AcSr/CARucdzLV0YRuuYOnQUxCyfsgAtrivA
From: Jean-Francois Mule <jf.mule@cablelabs.com>
To: Russ Housley <housley@vigilsec.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: quoted-printable
Cc: ipcdn@ietf.org, bwijnen@lucent.com, Eduardo Cardona <e.cardona@cablelabs.com>, Greg White <g.white@cablelabs.com>, Oscar Marcia <o.marcia@cablelabs.com>, "Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>, Eric Rosenfeld <e.rosenfeld@cablelabs.com>, "Steven M. Bellovin" <smb@research.att.com>
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=subscribe>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable

Russ wrote:
> I seriously doubt that t3DES128EdeMode is useful in this 
> context.  ECB had 
            ^^^ 
you mean EDE here
> some properties that are probably bad in this environment.

Okay, we can remove it, no pb.
Just fyi, 3DES EDE was also proposed because it is already used in the
BPI+ spec for the traffic encryption key (TEK). See page 21 of BPI+ at
http://www.cablemodem.com/downloads/specs/BPI+_I11-040407.pdf :
"The traffic encryption key (TEK) in the Key Reply is triple DES
(encrypt-decrypt-encrypt or EDE mode) encrypted, using a two-key, triple
DES key encryption key (KEK) derived from the Authorization Key."

This should close the threads on your comment - thank you again for the
review. 
Jean-Francois

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

v2.23.0 | Report a Bug | By Email