[kitten] draft-melnikov-scram-2fa is adopted (with stipulations)

Robbie Harwood <rharwood@redhat.com> Fri, 07 January 2022 18:51 UTC

Return-Path: <rharwood@redhat.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E933A1195 for <kitten@ietfa.amsl.com>; Fri, 7 Jan 2022 10:51:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level:
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 MP3rgDiWUHOn for <kitten@ietfa.amsl.com>; Fri, 7 Jan 2022 10:51:54 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 669CF3A1194 for <kitten@ietf.org>; Fri, 7 Jan 2022 10:51:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1641581513; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=ciuLiAtfSwkGCO4UY4aSbAfoOIKUH2iSIENCnAIlq9Q=; b=d9X7lnaIu8XH9KBqNStk+2FdKfRNo1TePAzClHEGpyhAydPUpxpUKWY5x7XW7FNCISimL/ bNTRcewpwztpaQHCfRVaeCBIZ2EL2itcHWODsyEMTZhQf6NnFRjTKwJhaysg7DW1Qlsal0 f9PNs/4M66xaxDPeQ6hVPH/USlfbeh4=
Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-352-LMom_NrSNwaI3yaJDANjsQ-1; Fri, 07 Jan 2022 13:51:51 -0500
X-MC-Unique: LMom_NrSNwaI3yaJDANjsQ-1
Received: by mail-qv1-f72.google.com with SMTP id jn6-20020ad45de6000000b004146a2f1f97so4143068qvb.19 for <kitten@ietf.org>; Fri, 07 Jan 2022 10:51:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=ciuLiAtfSwkGCO4UY4aSbAfoOIKUH2iSIENCnAIlq9Q=; b=ofKfBzDmzmy08gNBuKbEfxsX4NnqAXV1TLThvofuQsyAjsc/TUd+J5phIURjWHB6s5 TZRpx6LS/XH1b6S7Nqe3FpA1gDM1HtQTR9MlxzZnjDboTd3XiboBXDndUNRhGr8NMFEm 0mrqaS5ly+s++Dym0uRMURox9eCgfLJe27Aw4JWKXN7wz/AYXj+BhGmOthAoEkuj/M1O bQsPeTaR9uRnNPFJSIBUoy5H37U4GMANHppxfGKRHpeymG64IgkU6r8fCfxzQkDxNbl0 tk5VDoNHEGNC+JvOa1N14aHzG9b4HR8ebiJ2NE6RMSlIxDqs1E2MHkPC1krt7jhX/i4q ICyA==
X-Gm-Message-State: AOAM532//C4L6P69POSyznrpm4uvxVhKX2Kt/474o4+aMr2nol/qTdLw mChQJ+etUSb2ud+fkWfRbnw0m2g3yNNToh4UHV5UN7ZCLjPtIOBQ/SO3zDGxRTZ9haUaxFj5kU7 OR0GX+0b3KpI2CyPNJGhOUSWbTOPadzzG9Qym4ilbv+CcccPwu/LNF6doLhw=
X-Received: by 2002:a05:620a:121c:: with SMTP id u28mr46198979qkj.12.1641581510255; Fri, 07 Jan 2022 10:51:50 -0800 (PST)
X-Google-Smtp-Source: ABdhPJzToz06eim/AiY97i8r9yHPPygalg9sy3fr7wHUQSjDcAm40S7SZ8grpoA4JwoTyExstmXKuQ==
X-Received: by 2002:a05:620a:121c:: with SMTP id u28mr46198929qkj.12.1641581509147; Fri, 07 Jan 2022 10:51:49 -0800 (PST)
Received: from localhost ([2601:184:4181:74c0:862e:5809:ed9e:e10e]) by smtp.gmail.com with ESMTPSA id f4sm3928312qkp.14.2022.01.07.10.51.48 for <kitten@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 07 Jan 2022 10:51:48 -0800 (PST)
From: Robbie Harwood <rharwood@redhat.com>
To: kitten@ietf.org
Date: Fri, 07 Jan 2022 13:51:45 -0500
Message-ID: <jlga6g72xby.fsf@redhat.com>
MIME-Version: 1.0
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=rharwood@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/zeDTCwjXcRcFd6X89HGrFr3yzN4>
Subject: [kitten] draft-melnikov-scram-2fa is adopted (with stipulations)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2022 18:51:58 -0000

Hi kitten,

Based on the feedback in "Requesting WG adoption of several SCRAM
related documents", I believe we have consensus to adopt the SCRAM 2FA
extension, with the understanding that to address concerns raised,
kitten needs to consider the problem of re-authentication/resumption.
(This could be something like draft-cridland-kitten-clientkey or
draft-schmaus-kitten-sasl-ht, or something not yet written - that will
need to be decided.)

Discussion suggests that there is support for SCRAM-SHA512 and
SCRAM-SHA3 work, but they are not adopted at this time.  (They were not
part of Alexey's final proposal.  Additionally, there was not clear
consensus about concerns raised and how/whether to address them, though
there does appear to be WG interest.)

Be well,
--Robbie