Re: [port-srv-reg] Inconsistent terminology regarding "Administrative Contact" and "Technical Contact"

Joe Touch <touch@isi.edu> Tue, 14 September 2010 21:50 UTC

Return-Path: <touch@isi.edu>
X-Original-To: port-srv-reg@core3.amsl.com
Delivered-To: port-srv-reg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BECC3A6B3D for <port-srv-reg@core3.amsl.com>; Tue, 14 Sep 2010 14:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level:
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IyR6HDVm0TQB for <port-srv-reg@core3.amsl.com>; Tue, 14 Sep 2010 14:50:23 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id C4D503A6B34 for <port-srv-reg@ietf.org>; Tue, 14 Sep 2010 14:50:22 -0700 (PDT)
Received: from [128.9.176.34] (c1-vpn4.isi.edu [128.9.176.34]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id o8ELnF3A019373 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 14 Sep 2010 14:49:16 -0700 (PDT)
Message-ID: <4C8FEDDB.9060205@isi.edu>
Date: Tue, 14 Sep 2010 14:49:15 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: Michelle Cotton <michelle.cotton@icann.org>
References: <C8B538C0.28902%michelle.cotton@icann.org>
In-Reply-To: <C8B538C0.28902%michelle.cotton@icann.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [port-srv-reg] Inconsistent terminology regarding "Administrative Contact" and "Technical Contact"
X-BeenThere: port-srv-reg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of updates to service name and transport protocol port registry <port-srv-reg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/port-srv-reg>
List-Post: <mailto:port-srv-reg@ietf.org>
List-Help: <mailto:port-srv-reg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 21:50:32 -0000

Hi, Michelle,

The problem is that they're both contacts, and there's a problem staying 
that the contact is authorized to make changes for the registrant if you 
don't also say who wins when there's conflict (i.e., what happens when 
they disagree).

IMO:

	registrant	name of the party controlling the registration

	tech contact	name of the party to whom tech questions are
			referred, but who can't modify the record

In the DNS, FWIW, these are called:

	registrant		party to whom registration is granted

	billing contact		not applicable here

	administrative contact	other managing party

	technical contact	tech questions

The precedence, AFAICT, is as follows, for the DNS:

	registrant > admin > tech/billing

In our situation, we have only two, which correspondingly would be:

	registrant

	technical contact

Where registrant > tech if any conflict arises. AFAICT, the tech contact 
also ought not be able to change the name of the service, but might be 
able to ask for the corresponding other transport protocol assignments.

Joe



On 9/14/2010 2:35 PM, Michelle Cotton wrote:
> This is why we suggested the following terminology:
>
> o Registrant: Name and email address of the Registrant. This is
> REQUIRED. The Registrant is the Organization or Company responsible for
> the initial registration. For registrations done through IETF-published
> RFCs, the Registrant will be the IESG.
>
> o Contact: Name and email address of the Contact person for the
> registration. This is REQUIRED. The Contact person is the responsible
> person for the Internet community to send questions to. This person
> would also be authorized to submit changes on behalf of the Registrant.
> Additional address information MAY be provided. For registrations done
> through IETF-published RFCs, the Contact will be the IESG.
>
> This also fits well with other registries where we will be applying the
> same concept.
> If there is a better word for “registrant” I’m open for suggestions.
>
> Michelle
>
>
> On 9/14/10 2:28 PM, "Stuart Cheshire" <cheshire@apple.com> wrote:
>
>     On 9 Sep, 2010, at 08:32, Joe Touch wrote:
>
>     >  FWIW, I'm a bit confused by the current terms. I think we all
>     >  understand the goal - a tech contact and an owner.
>
>     Except it's not an "owner", because we have, in previous versions of
>     the draft, taken pains to stress that no one except IANA "owns" a
>     port or service name:
>
>     It is important to note that ownership of registered port numbers
>     and
>     service names remains with IANA.
>
>     Can we get some agreement on the terminology and concepts here?
>
>     Stuart Cheshire <cheshire@apple.com>
>     * Wizard Without Portfolio, Apple Inc.
>     * www.stuartcheshire.org
>
>     _______________________________________________
>     Port-srv-reg mailing list
>     Port-srv-reg@ietf.org
>     https://www.ietf.org/mailman/listinfo/port-srv-reg
>