IETF Logo Mail Archive

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

Andrew Newton <andy@hxr.us> Wed, 19 December 2018 15:46 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 AB9A2130E1A for <regext@ietfa.amsl.com>; Wed, 19 Dec 2018 07:46:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 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] 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 JpM2590fPcbD for <regext@ietfa.amsl.com>; Wed, 19 Dec 2018 07:46:20 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 DF12C130E0C for <regext@ietf.org>; Wed, 19 Dec 2018 07:46:19 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id v10so15894149ios.13 for <regext@ietf.org>; Wed, 19 Dec 2018 07:46:19 -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:content-transfer-encoding; bh=LqypGh2cmQrEB/GCf2Hd86S8vxidlVWrb1EJK1uV7yw=; b=wubrYu8ulDrXX/EBWWLYYCi0ql6YL/AMeQcBXHwAa9Z7bh1+NWMTMtikIWxNYnN44J WMCTk6ng0DQBIMXJLYWY+zQgoETOdyyngQ/hIXv8zZouhTVF7aRot0DJIiEORWuMZCvw mNJupu2OALStmCJx1jjNg7TuqCD03jAa7lO5lACr4haGfZvqqmrrvOdM4KIsuP2Al50m 3MlInFR5/8u8vPOdzL8lWCmlDHTXpFhEWHl4TWGlk5r8YHHV/4+R7kUFkPU7ccPivWx+ SQEKQBE1qi5RBHqJaaXDUJOdGvRelw4KXWRBg1r9X2bDZi8oj1PI0Kzy+Q8Pa7H7CX/y PXTQ==
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:content-transfer-encoding; bh=LqypGh2cmQrEB/GCf2Hd86S8vxidlVWrb1EJK1uV7yw=; b=hKRVEeQAq2w58lYiFMmr6poexqzM7yfAr6NN71LGjVJ0OewEw5ZtPhexJlhMssfmz+ AG6EIPe8tFNuFV04ZdyxDDJ3gXtbmt+uWgnxOtbdpbAcQXp36LSz+5GJV8LEjwGTjYQQ BVHob9cCzkVjX383H32BPBN2U9KAV7swlx+0eI2wvwL0x6wQCAoFtQ8333bdMiLCs5Ea ahK1WaeU5Cg2lKy2xf/exXVeKIh7MnduQdnPZBCHzlU8n7NGvzTDILzSocOKmAQtz0o4 yGxxQM2je26Ganbq4NXFsUol7Kj1DKudIjqZyvNInE39TWEDkO7BtKYGwxq88kyraDS6 o5aQ==
X-Gm-Message-State: AA+aEWbDOxpGrp1VSBwnG/Oc7MYY15o9gR5RakqF3P+HQn+zNYTNMw33 6Ko7OZ3hzZZeUZC9deF2E3/yepz3NRe8JfqVBv6wbkZx
X-Google-Smtp-Source: AFSGD/VB601qtTK711t7FSdqp02lQVYoa76oQSMjunDxRep5jGaRvG0YCiyrvtqoDwjQzfmAnzopPNhpUmEQpw3Cz9E=
X-Received: by 2002:a6b:39c6:: with SMTP id g189mr17355945ioa.255.1545234379082; Wed, 19 Dec 2018 07:46:19 -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> <CAAQiQRf-sq52ypDpyKQ9TUQiTiR0o5H-1RAaOyjf20YwphStyg@mail.gmail.com> <bfaed3fe-6f3b-75c3-e343-297cbe7130f7@digitaldissidents.org> <CAAQiQRew=goq7CXfXjw+nEsnLpqmkCtPOtpcTerahb3YFrc1mA@mail.gmail.com> <7f0eb968-4caa-7a81-e3b1-81b52fe4edc8@digitaldissidents.org>
In-Reply-To: <7f0eb968-4caa-7a81-e3b1-81b52fe4edc8@digitaldissidents.org>
From: Andrew Newton <andy@hxr.us>
Date: Wed, 19 Dec 2018 10:45:23 -0500
Message-ID: <CAAQiQRfW7OJ5SgxzQfRP0fmfm_a7fBSHjSmbusrZZxB9_661uw@mail.gmail.com>
To: lists@digitaldissidents.org
Cc: Registration Protocols Extensions <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/ZnIZpd9SuLL5MLlydSazb0zaAzE>
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, 19 Dec 2018 15:46:22 -0000

On Wed, Dec 19, 2018 at 10:38 AM Niels ten Oever
<lists@digitaldissidents.org> wrote:
>
>
> Everything is possible without the IETF: the Internet has open standards. So IETF is never solely responsible for anything. But IETF is setting a norm and thus normalizing and enabling this behavior. I think this is made clear in the text, and even clearer in the new text proposed by Gurshabad.

Except that is not true. The IETF is not setting a norm. The norm
already exists. Any abusive authority that can force a registry to
obey verification codes already has the power to force a registry to
remove domain names.

-andy

v2.23.0 | Report a Bug | By Email