IETF Logo Mail Archive

Re: [Emu] EAP and Transport Protocol

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 01 April 2019 16:24 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03AB812038C for <emu@ietfa.amsl.com>; Mon, 1 Apr 2019 09:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 9qMy5Fxq_jxk for <emu@ietfa.amsl.com>; Mon, 1 Apr 2019 09:24:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94369120390 for <emu@ietf.org>; Mon, 1 Apr 2019 09:24:24 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 7B5803808A; Mon, 1 Apr 2019 12:23:37 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id BCB68FF4; Mon, 1 Apr 2019 12:24:22 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B6F2626; Mon, 1 Apr 2019 12:24:22 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Dr. Pala" <director@openca.org>, EMU WG <emu@ietf.org>
In-Reply-To: <5DF500CA-4D6F-4A03-A5E0-6F410D67370B@deployingradius.com>
References: <33af57b3-950b-20e2-7aae-7fea8d07b283@openca.org> <5DF500CA-4D6F-4A03-A5E0-6F410D67370B@deployingradius.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 01 Apr 2019 12:24:22 -0400
Message-ID: <32738.1554135862@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/0XeCcjQICj9ZQmFfsAknb3Rpmms>
Subject: Re: [Emu] EAP and Transport Protocol
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 16:24:27 -0000

Alan DeKok <aland@deployingradius.com> wrote:
    >> being fairly new to the EAP world, I noticed that in some environment,
    >> EAP is layered on top of other protocols - in particular RADIUS and
    >> DIAMETER.

    > EAP was originally over PPP.  Now it's mostly RADIUS.  There may be
    > increasing use in the Diameter space.

I would say it differently, because radius and PPP are not equivalent.

EAP was originally over-PPP connected to over-Radius.
EAP is now more commonly over-802.1x connected over-Radius.
With Diameter replacing Radius in some environments.
EAP is "end-to-end" supplicant to Authentication Server.

(I know you (Alan) know this, but others might not)

    > For TTLS, it can be:

    > * Ethernet
    > * IP
    > * UDP
    > * RADIUS
    > * EAP
    > * EAP-TTLS
    > *  TLS
    > *  EAP
    > *  EAP-MSCHAPv2
    > *  MSCHAPv2 credentials

    > Yes, it's complicated.

:-)

    > Open Source implementations of EAP are few and far between.  On the
    > server side, it's only hostap and FreeRADIUS.  On the client side, it's
    > hostap.

    > There used to be "xsupplicant" and "open1x" on the client side, but
    > those have been dead for 10 years.


    >> In particular, the use of the

    > Early truncation?

lack of fragmentation :-)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email