IETF Logo Mail Archive

Re: [Emu] RFC 7170 (TEAP) errata

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 23 July 2019 15:09 UTC

Return-Path: <mcr@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 043681200E0 for <emu@ietfa.amsl.com>; Tue, 23 Jul 2019 08:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 9l5gP8WrUyUL for <emu@ietfa.amsl.com>; Tue, 23 Jul 2019 08:09:44 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C46CF1200B5 for <emu@ietf.org>; Tue, 23 Jul 2019 08:09:44 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-939f.meeting.ietf.org [31.133.147.159]) by relay.sandelman.ca (Postfix) with ESMTPS id 84BB81F44B; Tue, 23 Jul 2019 15:09:43 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 657AB1BBF; Tue, 23 Jul 2019 11:10:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alan DeKok <aland@deployingradius.com>
cc: Joseph Salowey <joe@salowey.net>, emu@ietf.org
In-reply-to: <F0527F34-CD94-405C-9863-F06AAD181060@deployingradius.com>
References: <CANe27jLO9eDA867X8hCHv_WRADN_txSp4xpRTxn2RpwS=yaquA@mail.gmail.com> <CAOgPGoBXrm0kGk4xsSen9ihCKRhVYgzPQR-H0C5AFtY9wChxqQ@mail.gmail.com> <F0527F34-CD94-405C-9863-F06AAD181060@deployingradius.com>
Comments: In-reply-to Alan DeKok <aland@deployingradius.com> message dated "Mon, 22 Jul 2019 15:47:02 -0400."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 23 Jul 2019 11:10:04 -0400
Message-ID: <3383.1563894604@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/t0zM7otPAB5hT5HQYiBUUNYXApY>
Subject: Re: [Emu] RFC 7170 (TEAP) errata
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: Tue, 23 Jul 2019 15:09:48 -0000

Alan DeKok <aland@deployingradius.com> wrote:
    >   TBH, I haven't seen an implementation.

    >   I suspect that the lack of implementations is why these questions are
    > only coming up now.

    >> My feeling is that it would be better to make the TLV length variable
    >> with the hash length.  However, I do not see why truncating would work
    >> as well.

    >   My $0.02 is to allow a variable TLV length.

    >   I think it's OK to leave these as errata now.  I'm not sure that any
    > existing EMU document would be appropriate for these changes.

Apparently there will soon be a mechanism deployed which will let people
see the documents with the errata *applied* on the rfc-editor.org site, so
it's a good idea to formally accept the errata, make a decision and then you
can generate a diff.

It seems like having the TLV length be variable is the right answer.
(I don't have a TEAP implementation.... yet)

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

v2.23.0 | Report a Bug | By Email