IETF Logo Mail Archive

RE: [TLS] Please discuss: draft-housley-evidence-extns-00 (resend)

Peter Williams <home_pw@msn.com> Wed, 20 December 2006 19:13 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx6sF-00045M-OJ; Wed, 20 Dec 2006 14:13:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx6sE-0003vu-0F for tls@ietf.org; Wed, 20 Dec 2006 14:13:06 -0500
Received: from bay0-omc1-s7.bay0.hotmail.com ([65.54.246.79]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx6pq-000571-Ss for tls@ietf.org; Wed, 20 Dec 2006 14:10:41 -0500
Received: from BAY103-W8 ([65.54.174.108]) by bay0-omc1-s7.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Wed, 20 Dec 2006 11:10:38 -0800
X-Originating-IP: [69.227.152.254]
X-Originating-Email: [home_pw@msn.com]
Message-ID: <BAY103-W823A3E509D2A0ACC868B892CF0@phx.gbl>
From: Peter Williams <home_pw@msn.com>
To: Mark Brown <mark@redphonesecurity.com>, tls@ietf.org
Subject: RE: [TLS] Please discuss: draft-housley-evidence-extns-00 (resend)
Date: Wed, 20 Dec 2006 11:10:38 -0800
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Dec 2006 19:10:38.0063 (UTC) FILETIME=[889F67F0:01C7246A]
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
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>
Content-Type: multipart/mixed; boundary="===============1877195145=="
Errors-To: tls-bounces@lists.ietf.org

Hmm. 
 
> http://www.navysbir.com/06_1/215.htm
a multi-level capable router, with layer 3 segregation based on KMI controlling the TLSConnections, with 
the protocol engine inside the N-TCB.
 
I.e. WAN router prevents IP-connectivity if the evidence does not satisfy centralized policy.
 
one should be able to repurpose alot of the multilevel layer 2 stack work done by cisco for LANs/MANs, with 
different STPs  for each VLAN (PVST+) - controlling compartmentalization across the trunks. i.e. 802.1q 
tagging for multilevel policy.
 
I assume that the testing criteria in the reseach is to do it all now with commodity TLS as the 
enforcement mechanism, and use CA graphs (with security labels in the certs) as the control 
mechanism for connectivity.?
 
_________________________________________________________________
Get the Live.com Holiday Page for recipes, gift-giving ideas, and more.
www.live.com/?addtemplate=holiday
_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls

v2.23.0 | Report a Bug | By Email