Re: [quicwg/base-drafts] Allow provisional registrations for all registries (#3170)

hardie <notifications@github.com> Wed, 30 October 2019 16:52 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC80312082F for <quic-issues@ietfa.amsl.com>; Wed, 30 Oct 2019 09:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 VvB-FR8baTRY for <quic-issues@ietfa.amsl.com>; Wed, 30 Oct 2019 09:52:56 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA316120024 for <quic-issues@ietf.org>; Wed, 30 Oct 2019 09:52:55 -0700 (PDT)
Date: Wed, 30 Oct 2019 09:52:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572454375; bh=4wprGizNgReKFurZtH73TUxLemN2d/V6DkbAN4fxJyE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z/tXOmHEhYI5ishtQpVLyhiwcT7aJZMhng3K7U5MVj/2iThADrYOPOGLerue0YO4I KkwZNZq/6wCpKZJ9vjh713U63j8fefI6inZKi3zSby7dyNcws90VzyXjCGWDq07Wud Aw54KhfIpbFzw3xloc3x7qKavkf+iJp/U68xmhKc=
From: hardie <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZ34WHCEF2AAOP4IIF3Y3ZGNEVBNHHB5KNIHE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3170/c548005590@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3170@github.com>
References: <quicwg/base-drafts/pull/3170@github.com>
Subject: Re: [quicwg/base-drafts] Allow provisional registrations for all registries (#3170)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db9bfe6eb152_3cb93fa6e32cd96c3541c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: hardie
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/cks3eUgjxrn7vmDJS_OpTb1UC8w>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2019 16:52:58 -0000

On Wed, Oct 30, 2019 at 12:31 AM MikkelFJ <notifications@github.com> wrote:

> Could contact information be replaced with a domain name. There is much
> abuse of contact information and domain names can have private contact
> information?
>
You can specify this so that IANA collects the information and thus can
follow up if needed, but where the registry does not display this
information.   I understand that the authors of RFC 8126 are working on a
bis that will make this much more common, if not the default.

> Also, maintaining an email address is harder over time. I realize the
> field contact field doesn't say email, but that is sort of implied.
>
You can also split the contact information from the change controller, if
you want to have, say Joe be the contact but Example Corp be the change
controller.  There's also a presumption that if the change controller is
gone that the change controller for the entire registry (usually the IESG)
can make a determination of what to do in the case that a change is needed.
For many registries this amounts to "do nothing" since there is no scarcity
of code points.  In the case of scarcity, that's how you get re-use when
the change controllers are gone.

Ted



> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/pull/3170?email_source=notifications&email_token=AAKVXZGW4DLXVXEZDME5SHLQREZ5BA5CNFSM4JGUI6W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECTFPAI#issuecomment-547772289>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAKVXZDFDTCYMGMTNCEWAPDQREZ5BANCNFSM4JGUI6WQ>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3170#issuecomment-548005590