IETF Logo Mail Archive

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

"Gould, James" <jgould@verisign.com> Wed, 02 January 2019 16:44 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 C65A9130EB8 for <regext@ietfa.amsl.com>; Wed, 2 Jan 2019 08:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] 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 Wiico5iIBT9W for <regext@ietfa.amsl.com>; Wed, 2 Jan 2019 08:44:42 -0800 (PST)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (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 6287D130EC5 for <regext@ietf.org>; Wed, 2 Jan 2019 08:44:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2652; q=dns/txt; s=VRSN; t=1546447483; h=from:to:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=IjlpsIDQq+RCltPs9suqZ52QJMBg6ccY0fJfsLdY2OM=; b=Vxf370+uRr903ilhxXfy0l2queH06NWCExJhiZ6qBa6kaDHquCg8tDx7 2wjpp6/aBwgr2oiQFE/R0zlSTe4BDCm7sYXAhT71o2JdDFtuZuwz0tYxt yaQfzw5EZqRS9EDeerG4pSHxuy5nLqgigAddyYDRadR70sRP15WlsGWPL ZCJ7bNHq6VN/vqxWAU04V/ugPPBb+chVjTwXO2R1/lALUaRsxOl3C0qKw cnJWx3FdWGS9G2uUGvJDZIb1Td1EMhRUQyEvyHhZerem4+467TkmXwg/w YYoBwHvpHnt1UYAKcoUIOvb8fm2dEZa+Xj7w5DQBYqVAR+M2V6lvCxNJ+ Q==;
X-IronPort-AV: E=Sophos;i="5.56,431,1539662400"; d="scan'208";a="6688461"
IronPort-PHdr: 9a23:2DhYkxa59B91TDSDMGndz/f/LSx+4OfEezUN459isYplN5qZrsqzbnLW6fgltlLVR4KTs6sC17KG9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQpFiCa+bL9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjmk8qxlSgLniD0fOjA57m/Zl9BwgqxYrhKvpRNwzY/Ub52aOvVxZa7dYcgVRW9dUspNTSFMAIWxZJYPAeobOuZYqpHwq1UPoxu5GAmsAP7gxidVjXHyx6I61vouERrI0Ac9GN8OsnvUrNLoNKcWTO+417fIwivZb/NXwjf96YfIchY7rf6QWrJwdNPcxE8yHA3LiVWQrJbqPzKT1ukVrWiU8fBgVeO0i24mpAFxpDmvxsEwhYXTmo0VzVXE+T14wIkrOd24RlR3Ydm+EJtfsSyRKoh4Qts6Tm11pCo20KAKtJy1cSQQ1ZgqxxDSZ+aIfoWL+h7vSfqdLS1liH9nZL6znQu+/Eejx+HmS8W5005GriRbndTPqnwA0hne5dKER/Z55Uis3DiC2x7O5exFJE07jq7WJp8jz7M1mJcev0bOETLwlU7rlqGZbF8k9fKt6+n/Z7XmoYKTOJFshwHlN6QuhtS/AeMlMggSR2Sb+fqz1Lnk/UDhXbhEkuU4nrTZv57CKsoUp7K1DxJP3oY99xm/CC2m0MwCkXYdMV1JYgyHj5LyO1HIOvz3EfC/g1G0nDdqwfDJIKHhD43QInTfirvtYLRw5kBGxAYuzd1S6YhYB74CLf7rX0/+rt3YDhs3MwyuxObnDc1w1oERWWKIH6+ZNL7dvESW5u0xOemMZZQVuDfyK/gj/fLhkXg5mVoFcamzwZQXcGy4HuhhI0iBY3rshdcBEWEOvgclUOzlkkCCUTFTZ3qoQ6084TQ7Apq8DYjfXoCtnKCB3CCjE51MeG9GBU6DEHj0d4ifWvcDdj6SIsF7njwDT7ihRNxp6Rb7/g39y7xjBvbd5yIY85nk0ZI9s+/UlRc23SB9EsudlWqKSjcw1ikSSjA7zLxXoEFhxBGEy6cyy6hCGNNe9+9hUwomO9jb1eMsWP7oXQeUNPiOVVKqBp2ECDQ8VZh5l90BZFt5F/28gwrCxCulBfkekLndV898yb7Vw3Wkf5U18H3BzqR011Q=
X-IPAS-Result: A2FzAADi6Sxc/zCZrQpgAx4BBgcGgVEJCwGBWoEPgSkKg3WZYI8MhH8UgSsXGA0MARgLC4N4RgIXggU0CQ0BAwEBAQEBAQIBAQKBBQyCOiIcMRwvCQEFAQEBAQEBJwEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQgCCAc1EgEaAgEDAQEhETobAgEIGgImAgICJQsVEAIEARKCcDIBghCmDIEvih2BC4tLgUE+gREnH4JMgx4BAYFJGBcKJoJBMYImAqFLAwYChxCKb4FgTYgFhzSJWYR7BosoAgQCBAUCFIFGYoEtcBU7KgGCQQmCR4M4hRSFP3INJIl2gR8BAQ
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, 2 Jan 2019 11:44:40 -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, 2 Jan 2019 11:44:40 -0500
From: "Gould, James" <jgould@verisign.com>
To: "johnl@taugh.com" <johnl@taugh.com>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] Privacy and HR considerations for draft-ietf-regext-verificationcode
Thread-Index: AQHUlxVqlYBPqhgCwUiJL3hXFpv+MKWGLv8AgABFogCAAtzsAIAHz/yAgAM6N4CAAJWVAIAHVWgA
Date: Wed, 02 Jan 2019 16:44:40 +0000
Message-ID: <01E9282A-0F48-4A39-837A-52CBB362571F@verisign.com>
References: <41f72627-faf2-1fd4-b356-065b3cb98e2b@cis-india.org> <20181228194511.1ACBC200C07CD3@ary.qy>
In-Reply-To: <20181228194511.1ACBC200C07CD3@ary.qy>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.3.181015
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8D1C4B8641910D409EBD636C3F2B073E@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/xbULaHywQHAtw8C6c4XX5ymvxD8>
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: Wed, 02 Jan 2019 16:44:46 -0000

John,

The 2119 words MUST and MAY are used to signify requirements; although that does imply interoperability as well.  This statement is associated with making the verification code functional, since the verification code represents a signed and typed verification pointer, it must point to something.  The VSP is required, by the normative MUST, to store the proof of verification and the generated verification code, and can optionally, by the normative MAY, store the verified data.  The "; and MAY store the verified data" can be removed, since the proof of verification is the only requirement for the verification code to be a functional pointer.  

Do you agree that the "; and MAY store the verified data" text should be removed?    The statement would then read:

"The VSP MUST store the proof of verification and the generated verification code."

Thanks,
  
—
 
JG



James Gould
Distinguished Engineer
jgould@Verisign.com

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

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

On 12/28/18, 2:45 PM, "regext on behalf of John Levine" <regext-bounces@ietf.org on behalf of johnl@taugh.com> wrote:

    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
    
    _______________________________________________
    regext mailing list
    regext@ietf.org
    https://www.ietf.org/mailman/listinfo/regext

v2.23.0 | Report a Bug | By Email