Re: [Emu] EAP-TLS 1.3 - Session-Id and extended EAP types
Alan DeKok <aland@deployingradius.com> Mon, 25 March 2019 08:26 UTC
Return-Path: <aland@deployingradius.com>
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 737BE120373 for <emu@ietfa.amsl.com>; Mon, 25 Mar 2019 01:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 GLgrLusV-yWJ for <emu@ietfa.amsl.com>; Mon, 25 Mar 2019 01:25:59 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) by ietfa.amsl.com (Postfix) with ESMTP id 28B85120370 for <emu@ietf.org>; Mon, 25 Mar 2019 01:25:58 -0700 (PDT)
Received: from [192.168.46.58] (198-84-237-221.cpe.teksavvy.com [198.84.237.221]) by mail.networkradius.com (Postfix) with ESMTPSA id 6B8D6713; Mon, 25 Mar 2019 08:25:57 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <CAE216A3-0359-4241-8FE1-5B99CA33D00B@ericsson.com>
Date: Mon, 25 Mar 2019 04:25:55 -0400
Cc: EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3466C871-C85B-4AD2-AD24-925B592E7063@deployingradius.com>
References: <CAE216A3-0359-4241-8FE1-5B99CA33D00B@ericsson.com>
To: John Mattsson <john.mattsson@ericsson.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/QYmpnaEwAKt3UoDGiMtr2bmoMdM>
Subject: Re: [Emu] EAP-TLS 1.3 - Session-Id and extended EAP types
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, 25 Mar 2019 08:26:01 -0000
On Mar 25, 2019, at 12:59 AM, John Mattsson <john.mattsson@ericsson.com> wrote: > > Noticed the following: > > draft-ietf-emu-eap-tls13-04 defines the key hierarchy as > > Type-Code = 0x0D > Key_Material = TLS-Exporter("EXPORTER_EAP_TLS_Key_Material", > Type-Code, 128) > IV = TLS-Exporter("EXPORTER_EAP_TLS_IV", > Type-Code, 64) > Method-Id = TLS-Exporter("EXPORTER_EAP_TLS_Method-Id", > Type-Code, 64) > Session-Id = Type-Code || Method-Id > > But section 1.4 of RFC 5247 defines Session-Id as > > Session-Id = Type-Code || Method-Id > > or > > Session-Id = 0xFE || Vendor-Id || Vendor-Type || Method-Id > > The definition in draft-ietf-emu-eap-tls13-04 does not seem compatible with extended EAP types. TBH, the simple approach is to extend the definition of Type-Code when extended types are used. Type-Code = 0x0d for types < 254 Type-Code = 0xFE || Vendor-Id || Vendor-Type for extended types And then use that definition for Key_Material, Method-Id, Session-Id, etc. Alan DeKok.
- [Emu] EAP-TLS 1.3 - Session-Id and extended EAP t… John Mattsson
- Re: [Emu] EAP-TLS 1.3 - Session-Id and extended E… Alan DeKok