IETF Logo Mail Archive

Re: [TLS] Please discuss: draft-housley-evidence-extns-00<

Mike <mike-list@pobox.com> Fri, 12 January 2007 00:31 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5AK5-0006YS-07; Thu, 11 Jan 2007 19:31:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5AK3-0006Xh-Nd for tls@ietf.org; Thu, 11 Jan 2007 19:31:07 -0500
Received: from rune.pobox.com ([208.210.124.79]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5AK2-0007Mu-Ho for tls@ietf.org; Thu, 11 Jan 2007 19:31:07 -0500
Received: from rune (localhost [127.0.0.1]) by rune.pobox.com (Postfix) with ESMTP id 46AA5A819B for <tls@ietf.org>; Thu, 11 Jan 2007 19:31:24 -0500 (EST)
Received: from [192.168.1.8] (wsip-24-234-114-35.lv.lv.cox.net [24.234.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by rune.sasl.smtp.pobox.com (Postfix) with ESMTP id 0F32AA8191 for <tls@ietf.org>; Thu, 11 Jan 2007 19:31:23 -0500 (EST)
Message-ID: <45A6D700.4010203@pobox.com>
Date: Thu, 11 Jan 2007 16:32:00 -0800
From: Mike <mike-list@pobox.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: tls@ietf.org
Subject: Re: [TLS] Please discuss: draft-housley-evidence-extns-00<
References: <A15AC0FBACD3464E95961F7C0BCD1FF01D6E0EAA@EA-EXMSG-C307.europe.corp.microsoft.com>from "Stefan Santesson" at Jan 11, 7 06:33:08 pm<200701112043.VAA02623@uw1048.wdf.sap.corp> <A15AC0FBACD3464E95961F7C0BCD1FF01D6E0EE8@EA-EXMSG-C307.europe.corp.microsoft.com> <BAY126-DAV1531A9C0FA9A9E384EDBF092B00@phx.gbl>
In-Reply-To: <BAY126-DAV1531A9C0FA9A9E384EDBF092B00@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc:
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org

I've been trying to follow this discussion, since I may
have to implement this feature someday, yet I don't have
a clue what it would be used for.  Can someone please
lay out a scenario where "evidence" collection at the
TLS layer is the appropriate solution to a real problem?

Thanks,

Mike

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls

v2.29.0 | Report a Bug | By Email | System Status