IETF Logo Mail Archive

[Emu] Chennal binding

Sam Hartman <hartmans-ietf@mit.edu> Wed, 22 August 2007 11:48 UTC

Return-path: <emu-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1INohU-0004kG-25; Wed, 22 Aug 2007 07:48:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1INohS-0004k9-Nc for emu@ietf.org; Wed, 22 Aug 2007 07:48:38 -0400
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INohS-0007BE-EU for emu@ietf.org; Wed, 22 Aug 2007 07:48:38 -0400
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3384448C3; Wed, 22 Aug 2007 07:48:37 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Lakshminath Dondeti <ldondeti@qualcomm.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE5044ECE60@xmb-sjc-225.amer.cisco.com> <tslmywku5d0.fsf@mit.edu> <46CBBDC3.50300@deployingradius.com> <46CBBF61.8070207@qualcomm.com>
Date: Wed, 22 Aug 2007 07:48:37 -0400
In-Reply-To: <46CBBF61.8070207@qualcomm.com> (Lakshminath Dondeti's message of "Tue, 21 Aug 2007 21:45:21 -0700")
Message-ID: <tsld4xfokmi.fsf_-_@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: emu@ietf.org
Subject: [Emu] Chennal binding
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
Errors-To: emu-bounces@ietf.org

>>>>> "Lakshminath" == Lakshminath Dondeti <ldondeti@qualcomm.com> writes:

    Lakshminath> I would like to see the crypto-binding stuff (not
    Lakshminath> compound binding -- as others have noted, we don't
    Lakshminath> have consensus on that topic) and extensibility (how
    Lakshminath> to add new attributes) specified.


I'd really appreciate it if someone would think hard about the
interactions of draft-housley-aaa-key-mgmt and channel binding.  I'd
like to understand whether we can meet all the requirements of that
BCP without channel binding and if not, what we need to do about it.


_______________________________________________
Emu mailing list
Emu@ietf.org
https://www1.ietf.org/mailman/listinfo/emu

v2.23.0 | Report a Bug | By Email