X509v3 EAP Parameter Extension
draft-rieckers-eapparameterextension-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-01
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda emu at IETF-106
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        J. Rieckers
Internet-Draft                                                Uni Bremen
Intended status: Standards Track                       November 02, 2019
Expires: May 5, 2020

                     X509v3 EAP Parameter Extension
                draft-rieckers-eapparameterextension-00

Abstract

   This document specifies an extension to X509v3 certificates for EAP-
   TLS servers to mitigate some flaws in the specification to the use of
   TLS in EAP as specified in RFC5216.  The specified extension enables
   clients to decide whether to trust the certificate presented by the
   EAP-TLS server by including information implicitly defined by login
   credentials or communication context in the server certificate.

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 https://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 May 5, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Rieckers                   Expires May 5, 2020                  [Page 1]
Internet-Draft           EAP Parameter Extension           November 2019

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  EAP Parameter Types . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Realm Suffix types  . . . . . . . . . . . . . . . . . . .   4
       4.1.1.  Syntax  . . . . . . . . . . . . . . . . . . . . . . .   5
       4.1.2.  Validation  . . . . . . . . . . . . . . . . . . . . .   5
       4.1.3.  CA Requirements . . . . . . . . . . . . . . . . . . .   5
     4.2.  Identity  . . . . . . . . . . . . . . . . . . . . . . . .   5
       4.2.1.  Syntax  . . . . . . . . . . . . . . . . . . . . . . .   5
       4.2.2.  Validation  . . . . . . . . . . . . . . . . . . . . .   6
       4.2.3.  CA Requirements . . . . . . . . . . . . . . . . . . .   6
     4.3.  Login Medium  . . . . . . . . . . . . . . . . . . . . . .   6
       4.3.1.  Syntax  . . . . . . . . . . . . . . . . . . . . . . .   6
       4.3.2.  Validation  . . . . . . . . . . . . . . . . . . . . .   6
       4.3.3.  CA Requirements . . . . . . . . . . . . . . . . . . .   6
     4.4.  Handling of future EAP Parameter Types  . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  ASN.1 Modul  . . . . . . . . . . . . . . . . . . . .   9
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Logging in with EAP-TLS based methods is a widely used mechanism for
   password based login with protocols like RADIUS [RFC2865].  Two
   mechanisms used in WPA2-Enterprise areas are EAP-TTLSv0 and EAP-
   PEAPv0.  Unfortunately, the specification of EAP-TLS does not specify
   how the EAP-TLS peer can verify that the certificate presented by the
   server is valid apart from the Key Usage identifiers and user set
   configuration parameters.

   The configuration parameters include especially the information about
   the trust anchor and the expected domain.

   In contrast to the usage of X509v3 certificates in other contexts,
Show full document text