IETF Logo Mail Archive

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

Andrew Newton <andy@hxr.us> Tue, 18 December 2018 22:00 UTC

Return-Path: <andy@hxr.us>
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 E0C6F1312B8 for <regext@ietfa.amsl.com>; Tue, 18 Dec 2018 14:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20150623.gappssmtp.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 hRgPe6E4MJka for <regext@ietfa.amsl.com>; Tue, 18 Dec 2018 14:00:11 -0800 (PST)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2052131211 for <regext@ietf.org>; Tue, 18 Dec 2018 14:00:10 -0800 (PST)
Received: by mail-io1-xd30.google.com with SMTP id s22so14000145ioc.8 for <regext@ietf.org>; Tue, 18 Dec 2018 14:00:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=y/10AK9/pH3f27WfpRwdVPanG3z/T+Ti7qi/B6E7Mow=; b=pIU6n1Pjv+IaSDdx59o/KCQ9F8Gv1cqnQqdZCwF0cUI9LCvQSkau+6jGQFJwEElzNE vuBmaQZ29Ok7Cg4oi5WJ4IjCXVk621I+ZeQfnBRK2Wgat8gp1rUwnGPWy/clC/VPlwTS Z5t+IHVh7V6nqAm4vPgdAUaiwsnD9V3G9YaE9AsFsoeYEMX1y9KyHws9BeFWJVX3etG4 jBRi5pbXWHwurv1A08yjMv5S53IwVPBGeeEkR8eXY2b0W7NClFWWSsj9Bzm5wK/euV2g Jk8zYYV6oJA0nUrUPLKhoTnYyi/wJOz4aekC9l2rxJgu7ZELL91oQHhUPKws0lD1eeek f4fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y/10AK9/pH3f27WfpRwdVPanG3z/T+Ti7qi/B6E7Mow=; b=XoGqfJs+eoHk/wLbPyQl6ZQO26+bLioXZFMyYJN6ui8CG3mHOhqfTIrdWofX0m65kw ij+qDnIO6JWKpWbvRFiQwyZktGxFvJBQBJjQQumPX1QIgcXN6yB9VW8wWlLEkHi36P5/ +NF2VvghVhXGIVeBc4QEVnyHG9G0d+1AJUZmWo9SFRQOIYEGdDTzc2Tlv2x/LwHDYT71 OP02FUrswpj7fvAszmB1ctEmJsFQctSPT3Kls0Fp3LUtb5p10sqtL1e977w7/UB58pLy 84j8MhQk5KA2AC/KUocXK4lWm5XWlFOUnRhk6MJzIF4YuVi8NtTeCr4HkuF0dR7LOfDG iewg==
X-Gm-Message-State: AA+aEWbxZPC7r+thoPhPMgqD27Yjg7mDRxRVhPumUzSohv2jcoVh+99m saD2dTFl3csHtc5SLwRb0DUakas9PDnyJWDKcd6iDg==
X-Google-Smtp-Source: AFSGD/VSxJHwjWAE8IbmrjKArDUumm0b6sA0ihlDJwzeAkDlLpUrGPSfy49xMRpJHHOSEwnVjmz6rgXRU49+ZTeBWJw=
X-Received: by 2002:a6b:39c6:: with SMTP id g189mr15076842ioa.255.1545170409933; Tue, 18 Dec 2018 14:00:09 -0800 (PST)
MIME-Version: 1.0
References: <5f7d0b3e-c844-1700-c369-90bb41e8241e@cis-india.org> <CAAQiQReVnuwFBCA2vOwnwaUw8k+1TCK-5DO+KLsd=CWF3Lh8Cg@mail.gmail.com> <FD1E789E-8B3B-41D3-8DA3-57056DBC437E@verisign.com>
In-Reply-To: <FD1E789E-8B3B-41D3-8DA3-57056DBC437E@verisign.com>
From: Andrew Newton <andy@hxr.us>
Date: Tue, 18 Dec 2018 16:59:14 -0500
Message-ID: <CAAQiQRf-sq52ypDpyKQ9TUQiTiR0o5H-1RAaOyjf20YwphStyg@mail.gmail.com>
To: "Gould, James" <jgould@verisign.com>
Cc: gurshabad@cis-india.org, Registration Protocols Extensions <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/RlBs--1qnMN-ZMgcCY7ifG9MF28>
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: Tue, 18 Dec 2018 22:00:14 -0000

On Tue, Dec 18, 2018 at 4:20 PM Gould, James <jgould@verisign.com> wrote:
>
> Yes, draft-ietf-regext-verificationcode defines the structure of the verification code that is passed between the EPP client (registrar) to the EPP server (registry) to show that the verification occurred before the EPP transaction.
>

Thanks for the _verification_, James. :)

I think this means the premise for the privacy considerations is
nonexistent, and therefore the text given is not applicable.

-andy

v2.23.0 | Report a Bug | By Email