PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods
draft-ietf-nea-pt-eap-00

The information below is for an old version of the document
Document Type Active Internet-Draft (nea WG)
Last updated 2011-08-30
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       P. Sangster
Internet Draft                                     Symantec Corporation
Intended status: Proposed Standard                        N. Cam-Winget
Expires: February 2012                                    Cisco Systems

                                                         August 30, 2011

      PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods
                       draft-ietf-nea-pt-eap-00.txt

Abstract

   This document specifies PT-EAP, a Posture Broker Protocol compatible
   with the Trusted Computing Group's IF-T Protocol Bindings for
   Tunneled EAP Methods (also known as EAP-TNC). The document then
   evaluates PT-EAP against the requirements defined in the NEA
   Requirements and PB-TNC specifications.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on February 30, 2010.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors. All rights reserved.

Sangster et al.       Expires February 30, 2012                [Page 1]
Internet-Draft                  PT-EAP                      August 2011

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction...................................................3
      1.1. Prerequisites.............................................4
      1.2. Message Diagram Conventions...............................4
      1.3. Terminology...............................................5
      1.4. Conventions used in this document.........................5
   2. Use of EAP-TNC.................................................5
   3. Definition of EAP-TNC..........................................5
      3.1. Protocol Overview.........................................6
      3.2. Version Negotiation.......................................6
      3.3. Fragmentation.............................................7
      3.4. EAP-TNC Message Format....................................8
      3.5. Preventing MITM Attacks with Channel Bindings............10
   4. Security Considerations.......................................11
      4.1. Trust Relationships......................................11
         4.1.1. Posture Transport Client............................11
         4.1.2. Posture Transport Server............................12
      4.2. Security Threats and Countermeasures.....................13
         4.2.1. Message Theft.......................................14
         4.2.2. Message Fabrication.................................14
         4.2.3. Message Modification................................15
         4.2.4. Denial of Service...................................15
         4.2.5. NEA Asokan Attacks..................................16
      4.3. Requirements for EAP Tunnel Methods......................16
      4.4. Candidate EAP Tunnel Method Protections..................17
      4.5. Security Claims for EAP-TNC as per RFC3748...............18
   5. Privacy Considerations........................................18
   6. IANA Considerations...........................................19
      6.1. Registry for EAP-TNC Versions............................19
   7. References....................................................20
      7.1. Normative References.....................................20
      7.2. Informative References...................................20
   8. Acknowledgments...............................................21
   Appendix A. Evaluation Against NEA Requirements..................23
Show full document text