[regext] draft-ietf-regext-verificationcode Feedback by Gurshabad Grover at REGEXT Meeting

"Gould, James" <jgould@verisign.com> Wed, 07 November 2018 06:00 UTC

Return-Path: <jgould@verisign.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 104CB128C65 for <regext@ietfa.amsl.com>; Tue, 6 Nov 2018 22:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level:
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.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 9vTQAR9FGIC1 for <regext@ietfa.amsl.com>; Tue, 6 Nov 2018 22:00:11 -0800 (PST)
Received: from mail4.verisign.com (mail4.verisign.com [69.58.187.30]) (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 70CC112785F for <regext@ietf.org>; Tue, 6 Nov 2018 22:00:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=22828; q=dns/txt; s=VRSN; t=1541570412; h=from:to:subject:date:message-id:mime-version; bh=N5D+KcJFiSp1F5wAZzI7g6XXsMd60JfJV4kC4+4QhRA=; b=beOfTrg6h+EjZts5gYk9wrwED3UJyuCsn2ZlxWyuhJOt13HnrRoRrtm+ kjaeD+qhNF39xPonyJ/WqFsJYNKn3Ubkmhzv3hPLC9X726ThBXG3gHiDE 5H/8gWflr2KdGUJjPTiS5lje/qw3iBteULIn8eoHavg7LRUQ9M6PeK1gS o0uM4Gh+7zYVNa6vKRkBdIALrH3uKJf///PgbzcozY4zBaJ4CGioyfo7R KGGVfLZ38PkDDVAXR6hmm1pHUYRYZoqL0rREv3N18gn7DmpYjlndpZelg Xt20lcpYWczlkYKj5k0TCS1Uz1eAvRqFCoQps/X7J/ijOtNo4x6U9AVhV w==;
X-IronPort-AV: E=Sophos;i="5.54,474,1534824000"; d="png'150?scan'150,208,217,150";a="6295741"
IronPort-PHdr: 9a23:YB2g3xLnzuZHhEl5tdmcpTZWNBhigK39O0sv0rFitYgeIvTxwZ3uMQTl6Ol3ixeRBMOHs60C07KempujcFRI2YyGvnEGfc4EfD4+ouJSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgppPOT1HZPZg9iq2+yo9JDffwdFiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLdQgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QLYpUjqg8qhrUgflhicZOTAk7GHZhM9+g6xaoB29qBNy2JTUbJ2QNPdkYq/QZ9EXSGxcVchRTSxBBYa8YpMBA+QAOuZYso39qEYWoRCjAQejHubvxSFThnP4wKY31OYhEQ7B3Aw9G9IBrW/ZrMvrO6cIUOC116jIzTrFb/9MxTj9743IfwknrPqRU7xwds/RxlMuFwPDlliQt5LqPymU1uQWsmib4OxgWfizhG4grgF9uiavydk2ionInYIVy1/E9SN4wIYzOdK0UlJ0YdmhEJZWqiqUNJN2T9s/T210oio2178LtJChcCQXyJkqyQTTZvOEfoSQ/x7vSPydLSp6iX55Yr6zmhm//Eu6xuHhVcS4yFhKoTRGn9XQs30A0gbc58uDR/Rm+0qs1yiD2B3S5+xBOk85kavWJpwkz7M+mJces1nMEynrk0vslqCWbF8r+u2w5uTiZbXpu4GTOpdvigH7LqQugsu/AfkkMgQWX2iU5+C81Lr78EDkXLtEluA6nanBvp7VJMsXurO1DxVL0ok/7Ba/FS+m3M4CknYaNl5FZgiHj5PvO13UPP/4CvK/j0ytkDdt2f/GIqXsDojRInTZjbvsf7hw51RBxAczw91T/Z1ZB7IZLPL2QEDxtdjYDhEjMwyzxubqENd91owZWWKSBq+WLbjfsUGW6eI1IumMf44VuDn7K/Q/+/Huino5lUcHfaa1xZsXdGy4HvN+LkWDf3XsjckOEGgWvgclTezllkGCUTBJa3a1RaI86WJzNIXzR53OSY29nJSA0Tu1WJpMaSoOXkqBHnr4a62FVusCLiWILZkyvCYDUO3rZIg80R3q/C3zzrd8ZKKA+CIfqJbv/MZ4/ezIlB40szdzCpLOgCm2U2hokzZQFHcN16dlrBklxw==
X-IPAS-Result: A2E8AABtfuJb/zCZrQphAx0BAQUBBwUBgVEIAQsBgQ2BXIEpCoNuiBiNf4MpjzWEd4E/OwgBAwETDA+EPhmDZDQNDQEDAQEBAQEBAgEBAoEFAQuCNiISSy8JATIBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEIAggHRwElAR0CCAFdAQYfAQEBIgIEBRABDgwnBBIBBgiDEwGPNJtQgS6FPIRgD4wPgUI+gREnDBOHNC0KJoI9MYImAo5nih+BZYRTAwYChggBZIo7giKORIdkhTGKJAIEAgQFAhSBQ4IOcBU7KgGCQQmCHhcSgziKUnINJIttgR8BAQ
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Wed, 7 Nov 2018 01:00:09 -0500
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d]) by BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d%5]) with mapi id 15.01.1531.003; Wed, 7 Nov 2018 01:00:09 -0500
From: "Gould, James" <jgould@verisign.com>
To: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: draft-ietf-regext-verificationcode Feedback by Gurshabad Grover at REGEXT Meeting
Thread-Index: AQHUdl8jwCzz3jWAiUqbItLyWUrohA==
Date: Wed, 07 Nov 2018 06:00:09 +0000
Message-ID: <95290846-8A56-4BB2-ACCD-6D754C46830E@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.f.0.180709
x-originating-ip: [10.170.148.18]
Content-Type: multipart/related; boundary="_004_952908468A564BB2ACCD6D754C46830Everisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/wc7m3_4OTK_IBUj1yoxK6CFF1-8>
Subject: [regext] draft-ietf-regext-verificationcode Feedback by Gurshabad Grover at REGEXT Meeting
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: Wed, 07 Nov 2018 06:00:14 -0000

There were 3 draft-ietf-regext-verificationcode items brought up by Gurshabad Grover that I captured from the REGEXT Meeting:


  1.  Clarifying that it’s up to server policy to define the server action taken when the verification code grace period expires
     *   I re-reviewed draft-ietf-regext-verificationcode, and it does not include any language related to the action taken by the server when the verification code grace period expires.  I believe this can be addressed by adding the following sentence in the Verification Profile section (section 2.2) of the draft:

                                                              i.      “…the grace period by which the verification code types MUST be set.  It is up to server policy what action to take if the verification code type is not set by the grace period.”

  1.  Ensure that the VSP does not modify the data verified after the verification code is generated
     *   I’m still not clear what the issue is here, since the role of the VSP is to perform the verification and to generate the verification code when the verification has been successfully completed.  The draft-ietf-regext-verificationcode does not define the interface used by the VSP and does not define the policies of how the verification is performed.
     *   Gurshabad, can you share your issue on the list to help clarify how the draft would address it?
  2.  Include a HRPC section in draft-ietf-regext-verificationcode
     *   This is being discussed actively on the list, but at present I believe that we can address the feedback without adding a new section to the document.  If the IESG changes the default structure of the document to add a new section, then it can certainly be added.

Let me know if I missed anything and share your feedback on the list for the items above.

Thanks,

—

JG

[cid:image001.png@01D255E2.EB933A30]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com<http://verisigninc.com/>