[Nea] RFC 7171 on PT-EAP: Posture Transport (PT) Protocol for Extensible Authentication Protocol (EAP) Tunnel Methods

rfc-editor@rfc-editor.org Thu, 08 May 2014 06:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: nea@ietfa.amsl.com
Delivered-To: nea@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4ABC1A022F; Wed, 7 May 2014 23:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89K2E2Uujo1Q; Wed, 7 May 2014 23:16:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id C6F611A04B9; Wed, 7 May 2014 23:16:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 81DEC180095; Wed, 7 May 2014 23:15:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140508061524.81DEC180095@rfc-editor.org>
Date: Wed, 07 May 2014 23:15:24 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/nea/nbqJHEA2Dtw3xLUYfUvW8N8tG5E
Cc: drafts-update-ref@iana.org, nea@ietf.org, rfc-editor@rfc-editor.org
Subject: [Nea] RFC 7171 on PT-EAP: Posture Transport (PT) Protocol for Extensible Authentication Protocol (EAP) Tunnel Methods
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 08 May 2014 06:16:09 -0000

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

        
        RFC 7171

        Title:      PT-EAP: Posture Transport (PT) Protocol 
                    for Extensible Authentication Protocol (EAP) Tunnel 
                    Methods 
        Author:     N. Cam-Winget, P. Sangster
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2014
        Mailbox:    ncamwing@cisco.com, 
                    paul_sangster@symantec.com
        Pages:      19
        Characters: 45604
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nea-pt-eap-09.txt

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

This document specifies PT-EAP, a Posture Transport (PT) protocol
based on the Extensible Authentication Protocol (EAP) and designed to
be used only inside an EAP tunnel method protected by Transport Layer
Security (TLS).  The document also describes the intended
applicability of PT-EAP.

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/search
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