Re: [DNSOP] Agenda for IETF100

tjw ietf <tjw.ietf@gmail.com> Sat, 11 November 2017 07:11 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0817C129411 for <dnsop@ietfa.amsl.com>; Fri, 10 Nov 2017 23:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Fi3DMpEGKYDS for <dnsop@ietfa.amsl.com>; Fri, 10 Nov 2017 23:11:09 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 A676612948F for <dnsop@ietf.org>; Fri, 10 Nov 2017 23:11:08 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id r68so6353549wmr.1 for <dnsop@ietf.org>; Fri, 10 Nov 2017 23:11:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=q3YQQ+UQEIyXbvbHCkLM/EVUorwEJB+CETGmvCD3COI=; b=Lh54nlm/Iclv+tU8c1Yx7Epl4+zN9ss1j7ll0VlkhgPwvJh1g+XnMK3P75z0TgLaPD uQomOwWMivv3BDLASk9VR4z/3tWPFkCJ9+5602JzMFx78Z26U2kt+XF7dpAX+ND2N06C 5VVNfuzKxth6LUOEFCewebTxnNGQ5cfCRRdMKRBhpW9pykkZpCX7iqTfmra/o+rjhRID Iv9jDfPUAXxT9n9huTcQNH9iNwbRPEGtEGhH7ukscpN1EDlxyHvnhWes6xCSU5E+dUzz dSrseTj7rTiSrjn0BsmHfNq8KhrQduI7aNHUu4JoAcgUaZhzUcg0SeGXysGGucQrzmlh ilWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=q3YQQ+UQEIyXbvbHCkLM/EVUorwEJB+CETGmvCD3COI=; b=JBvsstdNHPbZGRc6yenLf/iYOgXcyTdlnojFETThi+MunzEAs1KoVZUTbYvi1Uy9Qo SZHCInvM88rp284hf4eGUJ6GOIGyUs+zrrxqHiBubk3uAuedci+K6TUSdlPplVahaKGc wrysER9ToovB0KPQTUI1Tbg7AnkzvGkGWVlZdIu9nE6rqX2UNcupkdcIT3/KL0cB5Ndq QdJfIgv1Jgd4Lsgwi9e0nv5TYyCewM5fWETOgCnAMCkuJed5xrhThL6FZPSjKo8hRYgd QrQBWxOS3NGP3lKBvcMm5utEeYghNo8a9N5NrZrBAh9L2Z6Hk8ZaXT0VnIfI+a94kaon v8PA==
X-Gm-Message-State: AJaThX6joM6o5dLlr/k3tmpAKJ+JoFNF2v6hX+p01XgQB9Px0L1h0URX ziHbUEcY9E0w3+Wj6zSWhZlfmvEbR7DtL4q1WqI=
X-Google-Smtp-Source: AGs4zMYZS0cP2IGEeucZPlz7XKUm141R2w7gMQhJ8b1EO3NI+UgO10ptob90yfQM9wErEG4+8je+cUBnG9KvrFpDNNQ=
X-Received: by 10.28.73.196 with SMTP id w187mr1899128wma.17.1510384267255; Fri, 10 Nov 2017 23:11:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.196.169 with HTTP; Fri, 10 Nov 2017 23:11:06 -0800 (PST)
In-Reply-To: <809562de-bbde-4548-a701-fe7fbfef6b5e@Spark>
References: <CADyWQ+HJyM5aUe4UpmU3vuzjaqOkzvC1+_bpvYd=dv93yzAewg@mail.gmail.com> <20171110121600.GA2749@laperouse.bortzmeyer.org> <EC0E4D2D-E9B1-4A1A-B3D5-24AD672DAFC0@nohats.ca> <20171110142508.GA4062@laperouse.bortzmeyer.org> <A85950D8-499F-4A83-A4C0-56B035AA8E37@nohats.ca> <809562de-bbde-4548-a701-fe7fbfef6b5e@Spark>
From: tjw ietf <tjw.ietf@gmail.com>
Date: Sat, 11 Nov 2017 15:11:06 +0800
Message-ID: <CADyWQ+GJLbThBwscMx6eaJpjBD8TTOQtMY__V8m2rDZmC1_Pog@mail.gmail.com>
To: David Conrad <drc@virtualized.org>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Paul Wouters <paul@nohats.ca>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b3092b9655a055dafbd6e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-9zBqWpvNBlekGotR211s1mf6tM>
Subject: Re: [DNSOP] Agenda for IETF100
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Nov 2017 07:11:11 -0000

Great question Paul and thanks for getting that on record.

On Sat, Nov 11, 2017 at 2:59 AM, David Conrad <drc@virtualized.org> wrote:

> Can confirm, as can anyone willing to go to an Adobe Connect archive. For
> the curious:
>
> https://participate.icann.org/p6u03rimy92/?launcher=false&
> fcsContent=true&pbMode=normal
>
> The discussion on Ethereum by Leonard Tan, an Ethereum developer, starts
> at 00:31:00. Paul’s question is at 00:42:16. From the transcript:
>
> >> PAUL:  PAUL, IETF.  LET'S SAY IETF GETS THE DOMAINS IETF IN THIS NAMING
> SYSTEM AND WE PAY OUR FEES FOR A COUPLE OF YEARS.  EVERYBODY USES THE
> SITE.  AND THEN AT SOME POINT WE FORGET TO PAY AND THE DOMAIN FALLS BACK
> INTO THE POOL AND SOMEBODY ELSE REGISTERS IT AND WE DON'T KNOW WHERE THEY
> ARE OR WHO THEY ARE.  NOW I GO TO A COURT SYSTEM.  I GET SOME LEGAL OPINION
> SAYING I OWN THIS TRADEMARK AND NOW I WANT TO GET THIS DOMAIN BACK.  IS
> THERE ANY WAY FOR ME TO GET THIS DOMAIN BACK?
> >>LEONARD TAN:  SO RIGHT NOW, THE ENS INDUSTRY, YOU CAN CHANGE IT BECAUSE
> IT REQUIRES FOUR OUT OF SEVEN PEOPLE.  MOST OF THEM ARE ETHEREUM
> DEVELOPERS.  AND IT IS A CONSENSUS OF THEM TO MAKE ANY CHANGES.  SO IT IS
> POSSIBLE, BUT IT IS GOING TO BE A VERY DIFFICULT THING TO DO.
>
> Regards,
> -drc
>
> On Nov 10, 2017, 10:47 PM +0800, Paul Wouters <paul@nohats.ca>, wrote:
>
> The ENS developer said so in response to my question.
>
> Sent from my iPhone
>
> On Nov 10, 2017, at 19:55, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>
> On Fri, Nov 10, 2017 at 05:58:13PM +0530,
> Paul Wouters <paul@nohats.ca> wrote
> a message of 29 lines which said:
>
> It takes 4 out of 7 geeks to bypass the blockchain in case of
> emergency, court orders or kneecaps.
>
> According to the presentation held at ICANN60
>
>
> Well, if someone at ICANN said so, someone is wrong (or, at the
> minimum, over-simplificator).
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>