IETF Logo Mail Archive

Re: [regext] Privacy and HR considerations for draft-ietf-regext-verificationcode

"John Levine" <johnl@taugh.com> Fri, 28 December 2018 19:45 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB581310CC for <regext@ietfa.amsl.com>; Fri, 28 Dec 2018 11:45:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=cfRQl62e; dkim=pass (1536-bit key) header.d=taugh.com header.b=No4rjRGx
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 9tpin5r8fHXa for <regext@ietfa.amsl.com>; Fri, 28 Dec 2018 11:45:13 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 583FA12DD85 for <regext@ietf.org>; Fri, 28 Dec 2018 11:45:13 -0800 (PST)
Received: (qmail 21616 invoked from network); 28 Dec 2018 19:45:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=546e.5c267d47.k1812; bh=000t3SQGhtBlxzkCxw6qI0RxpEBkRw4hCnbQcwF+yNQ=; b=cfRQl62eeAvo5uK7z5aaOAPq1fVlD+7twC1rVZ+K2xxGWhXBK/9NjT5Ai3AqY63INCOSYfiTROh6iV0kE48/EypcTjUVj2v6t8cBs7DVkVL2IIZev0CYsJHvxG+4CAZemjKN/1OWX3Zygvywo2+cFerjExK7JsWn64GrHONeOMajYSY0QHQPk4IAxTYPLew4lvsOV30QEhJHb6ewwsbePBbR1GXY413oGW9o0rqQ6uW5hoEica9IcbtLJNSNgzlF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=546e.5c267d47.k1812; bh=000t3SQGhtBlxzkCxw6qI0RxpEBkRw4hCnbQcwF+yNQ=; b=No4rjRGxDzLe1tAkviG3dPmV906jggnBiJQjX5/GG8w/QowFAn/2g0c3JcqKOUnrYNZYVRWiq83UnosBZRWo9f6Sf/1t89R6zJoFvoR1DxgRmgduJXTuDo3oA6eu/xtsycTPke4m3yg27RrejR+ezXBYx7X1hGb3GCKkn7X2WG2VDCjD72T9o5+TmbE1j65Ttmf4o+ZuURz5AYuLjXHsfq6fYzh4qttiwJCNtqQ1HWB7dLJKQ3p0bAdFdtBDVb1F
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 28 Dec 2018 19:45:11 -0000
Received: by ary.qy (Postfix, from userid 501) id 1ACBC200C07CD3; Fri, 28 Dec 2018 14:45:10 -0500 (EST)
Date: Fri, 28 Dec 2018 14:45:10 -0500
Message-Id: <20181228194511.1ACBC200C07CD3@ary.qy>
From: John Levine <johnl@taugh.com>
To: regext@ietf.org
In-Reply-To: <41f72627-faf2-1fd4-b356-065b3cb98e2b@cis-india.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/wztTlq_qDITZh8oZh4vHnVeiVtA>
Subject: Re: [regext] Privacy and HR considerations for draft-ietf-regext-verificationcode
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Dec 2018 19:45:15 -0000

In article <41f72627-faf2-1fd4-b356-065b3cb98e2b@cis-india.org> you write:
>"The VSP MUST store the proof of verification and the generated
>verification code; and MAY store the verified data."

The 2119 words MUST and MAY are about interoperation.

Now that you point it out, this has nothing to do with interoperation
unless compliance somehow affects interop.

I would suggest removing that part, or at least making it
non-normative since business practices are generally way out of scope
for IETF specs.

R's,
John

v2.23.0 | Report a Bug | By Email