A GSS-API Mechanism for the Extensible Authentication Protocol
draft-ietf-abfab-gss-eap-06

The information below is for an old version of the document
Document Type Active Internet-Draft (abfab WG)
Last updated 2012-04-09
Replaces draft-howlett-eap-gss
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    S. Hartman, Ed.
Internet-Draft                                         Painless Security
Intended status: Standards Track                              J. Howlett
Expires: October 11, 2012                                          JANET
                                                           April 9, 2012

     A GSS-API Mechanism for the Extensible Authentication Protocol
                    draft-ietf-abfab-gss-eap-06.txt

Abstract

   This document defines protocols, procedures, and conventions to be
   employed by peers implementing the Generic Security Service
   Application Program Interface (GSS-API) when using the EAP mechanism.
   Through the GS2 family of mechanisms, these protocols also define how
   Simple Authentication and Security Layer (SASL, RFC 4422)
   applications use the Extensible Authentication Protocol.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on October 11, 2012.

Copyright Notice

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

   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

Hartman & Howlett       Expires October 11, 2012                [Page 1]
Internet-Draft                 EAP GSS-API                    April 2012

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Discovery  . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2.  Authentication . . . . . . . . . . . . . . . . . . . . . .  5
     1.3.  Secure Association Protocol  . . . . . . . . . . . . . . .  6
   2.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  8
   3.  EAP Channel Binding and Naming . . . . . . . . . . . . . . . .  9
     3.1.  Mechanism Name Format  . . . . . . . . . . . . . . . . . .  9
     3.2.  Internationalization of Names  . . . . . . . . . . . . . . 11
     3.3.  Exported Mechanism Names . . . . . . . . . . . . . . . . . 12
     3.4.  Acceptor Name RADIUS AVP . . . . . . . . . . . . . . . . . 12
     3.5.  Proxy Verification of Acceptor Name  . . . . . . . . . . . 13
   4.  Selection of EAP Method  . . . . . . . . . . . . . . . . . . . 15
   5.  Context Tokens . . . . . . . . . . . . . . . . . . . . . . . . 16
     5.1.  Mechanisms and Encryption Types  . . . . . . . . . . . . . 17
     5.2.  Processing received tokens . . . . . . . . . . . . . . . . 17
     5.3.  Error Subtokens  . . . . . . . . . . . . . . . . . . . . . 18
     5.4.  Initial State  . . . . . . . . . . . . . . . . . . . . . . 18
       5.4.1.  Vendor Subtoken  . . . . . . . . . . . . . . . . . . . 19
       5.4.2.  Acceptor Name Request  . . . . . . . . . . . . . . . . 19
       5.4.3.  Acceptor Name Response . . . . . . . . . . . . . . . . 19
     5.5.  Authenticate State . . . . . . . . . . . . . . . . . . . . 20
       5.5.1.  EAP Request Subtoken . . . . . . . . . . . . . . . . . 21
       5.5.2.  EAP Response Subtoken  . . . . . . . . . . . . . . . . 21
     5.6.  Extension State  . . . . . . . . . . . . . . . . . . . . . 21
       5.6.1.  Flags Subtoken . . . . . . . . . . . . . . . . . . . . 22
       5.6.2.  GSS Channel Bindings Subtoken  . . . . . . . . . . . . 22
       5.6.3.  MIC Subtoken . . . . . . . . . . . . . . . . . . . . . 23
     5.7.  Example Token  . . . . . . . . . . . . . . . . . . . . . . 24
     5.8.  Context Options  . . . . . . . . . . . . . . . . . . . . . 24
   6.  Acceptor Services  . . . . . . . . . . . . . . . . . . . . . . 26
     6.1.  GSS-API Channel Binding  . . . . . . . . . . . . . . . . . 26
     6.2.  Per-message security . . . . . . . . . . . . . . . . . . . 26
     6.3.  Pseudo Random Function . . . . . . . . . . . . . . . . . . 27
   7.  Iana Considerations  . . . . . . . . . . . . . . . . . . . . . 28
     7.1.  OID Registry . . . . . . . . . . . . . . . . . . . . . . . 28
Show full document text