RFC 5793 on PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)

rfc-editor@rfc-editor.org Wed, 10 March 2010 00:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D28D53A6A93; Tue, 9 Mar 2010 16:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.207
X-Spam-Level:
X-Spam-Status: No, score=-2.207 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UmnXhqPjME0w; Tue, 9 Mar 2010 16:36:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 1A5FE3A6AE7; Tue, 9 Mar 2010 16:36:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 20CAAE074C; Tue, 9 Mar 2010 16:36:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5793 on PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)
From: rfc-editor@rfc-editor.org
Message-Id: <20100310003643.20CAAE074C@rfc-editor.org>
Date: Tue, 9 Mar 2010 16:36:43 -0800 (PST)
Cc: nea@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 00:36:38 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5793

        Title:      PB-TNC: A Posture Broker (PB) 
                    Protocol Compatible with Trusted Network Connect 
                    (TNC) 
        Author:     R. Sahita, S. Hanna,
                    R. Hurst, K. Narayan
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    Ravi.Sahita@intel.com, 
                    shanna@juniper.net, 
                    Ryan.Hurst@microsoft.com,  kaushik@cisco.com
        Pages:      76
        Characters: 169140
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nea-pb-tnc-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5793.txt

This document specifies PB-TNC, a Posture Broker protocol identical
to the Trusted Computing Group's IF-TNCCS 2.0 protocol.  The document
then evaluates PB-TNC against the requirements defined in the NEA
Requirements specification.  [STANDARDS TRACK]

This document is a product of the Network Endpoint Assessment Working Group of the IETF.

This is now a Proposed Standard Protocol.

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