Re: [Nea] RFC 6876 on A Posture Transport Protocol over TLS (PT-TLS)
Stephen Hanna <shanna@juniper.net> Mon, 04 March 2013 14:32 UTC
Return-Path: <shanna@juniper.net>
X-Original-To: nea@ietfa.amsl.com
Delivered-To: nea@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E94B21F8A53 for <nea@ietfa.amsl.com>; Mon, 4 Mar 2013 06:32:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.867
X-Spam-Level:
X-Spam-Status: No, score=-102.867 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O3yWWYXDzaYV for <nea@ietfa.amsl.com>; Mon, 4 Mar 2013 06:32:06 -0800 (PST)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 3E85D21F8A00 for <nea@ietf.org>; Mon, 4 Mar 2013 06:32:04 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUTSwZEfdAdqCXjk/jFrOLLf8nSWqJ3rn@postini.com; Mon, 04 Mar 2013 06:32:04 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 4 Mar 2013 06:29:58 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Mon, 4 Mar 2013 06:29:58 -0800
Received: from va3outboundpool.messaging.microsoft.com (216.32.180.11) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 4 Mar 2013 06:39:16 -0800
Received: from mail241-va3-R.bigfish.com (10.7.14.244) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 14.1.225.23; Mon, 4 Mar 2013 14:29:47 +0000
Received: from mail241-va3 (localhost [127.0.0.1]) by mail241-va3-R.bigfish.com (Postfix) with ESMTP id 1100C10031C for <nea@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Mon, 4 Mar 2013 14:29:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.234.117; KIP:(null); UIP:(null); (null); H:SN2PRD0510HT005.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -26
X-BigFish: PS-26(zzbb0bI9371I542I1432I1528I4015Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1155h)
Received: from mail241-va3 (localhost.localdomain [127.0.0.1]) by mail241-va3 (MessageSwitch) id 1362407383897000_3161; Mon, 4 Mar 2013 14:29:43 +0000 (UTC)
Received: from VA3EHSMHS040.bigfish.com (unknown [10.7.14.238]) by mail241-va3.bigfish.com (Postfix) with ESMTP id D7C652009F for <nea@ietf.org>; Mon, 4 Mar 2013 14:29:43 +0000 (UTC)
Received: from SN2PRD0510HT005.namprd05.prod.outlook.com (157.56.234.117) by VA3EHSMHS040.bigfish.com (10.7.99.50) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 4 Mar 2013 14:29:43 +0000
Received: from SN2PRD0510MB372.namprd05.prod.outlook.com ([169.254.9.72]) by SN2PRD0510HT005.namprd05.prod.outlook.com ([10.255.116.40]) with mapi id 14.16.0275.006; Mon, 4 Mar 2013 14:29:42 +0000
From: Stephen Hanna <shanna@juniper.net>
To: "nea@ietf.org" <nea@ietf.org>
Thread-Topic: [Nea] RFC 6876 on A Posture Transport Protocol over TLS (PT-TLS)
Thread-Index: AQHOFSHK844ni1s9p0ulKnga4pfck5iVnC/g
Date: Mon, 04 Mar 2013 14:29:41 +0000
Message-ID: <F1DFC16DCAA7D3468651A5A776D5796E15B5B3E3@SN2PRD0510MB372.namprd05.prod.outlook.com>
References: <20130227193501.632B772E168@rfc-editor.org>
In-Reply-To: <20130227193501.632B772E168@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: Re: [Nea] RFC 6876 on A Posture Transport Protocol over TLS (PT-TLS)
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 14:32:10 -0000
Congratulations to the nea working group on the successful completion of this significant milestone! Thanks to all those who have helped over the years. Now we have a complete top-to-bottom set of IETF RFCs for endpoint assessment, all approved as standards. As noted in this blog post, Trusted Computing Group has approved identical documents as TCG Specifications: http://www.trustedcomputinggroup.org/community/2013/02/ietf_approves_tcg_networking_standards I'm delighted to see everyone converging on one set of standards for endpoint assessment. That was the goal of the nea working group when it was chartered and now we are almost done. We just have to get PT-EAP to RFC status, which is expected by the end of 2013. Even without having PT-EAP as an RFC, implementers are starting to implement PT-TLS, PB-TNC, and PA-TNC for endpoint assessment. Together, these standards help establish the security and trustworthiness of network endpoints. And since most attacks today focus on compromising the endpoints, the NEA standards will play an essential role in combating the threats of the future. With the NEA standards, infected machines can be detected, quarantined, and remediated using open standards. Thanks, Steve > -----Original Message----- > From: nea-bounces@ietf.org [mailto:nea-bounces@ietf.org] On Behalf Of > rfc-editor@rfc-editor.org > Sent: Wednesday, February 27, 2013 2:35 PM > To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org > Cc: nea@ietf.org; rfc-editor@rfc-editor.org > Subject: [Nea] RFC 6876 on A Posture Transport Protocol over TLS (PT- > TLS) > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 6876 > > Title: A Posture Transport Protocol over > TLS (PT-TLS) > Author: P. Sangster, N. Cam-Winget, > J. Salowey > Status: Standards Track > Stream: IETF > Date: February 2013 > Mailbox: paul_sangster@symantec.com, > ncamwing@cisco.com, > jsalowey@cisco.com > Pages: 44 > Characters: 109852 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-nea-pt-tls-08.txt > > URL: http://www.rfc-editor.org/rfc/rfc6876.txt > > This document specifies PT-TLS, a TLS-based Posture Transport (PT) > protocol. The PT-TLS protocol carries the Network Endpoint > Assessment (NEA) message exchange under the protection of a > Transport Layer Security (TLS) secured tunnel. > > This document is a product of the Network Endpoint Assessment Working > Group of the IETF. > > This is now a Proposed Standard. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and > suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc- > editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > Nea mailing list > Nea@ietf.org > https://www.ietf.org/mailman/listinfo/nea
- [Nea] RFC 6876 on A Posture Transport Protocol ov… rfc-editor
- Re: [Nea] RFC 6876 on A Posture Transport Protoco… Stephen Hanna