Re: [port-srv-reg] Inconsistent terminology regarding "Administrative Contact" and "Technical Contact"
Joe Touch <touch@isi.edu> Thu, 09 September 2010 15:33 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 73C013A6891 for <port-srv-reg@core3.amsl.com>;
Thu, 9 Sep 2010 08:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.655
X-Spam-Level:
X-Spam-Status: No,
score=-102.655 tagged_above=-999 required=5 tests=[AWL=-0.056, 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 I+AqA1l8emGD for
<port-srv-reg@core3.amsl.com>; Thu, 9 Sep 2010 08:33:30 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com
(Postfix) with ESMTP id BE1023A68B3 for <port-srv-reg@ietf.org>;
Thu, 9 Sep 2010 08:33:29 -0700 (PDT)
Received: from [75.217.58.205] (205.sub-75-217-58.myvzw.com [75.217.58.205])
(authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id
o89FWjRJ009144 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);
Thu, 9 Sep 2010 08:32:55 -0700 (PDT)
Message-ID: <4C88FE1D.1050609@isi.edu>
Date: Thu, 09 Sep 2010 08:32:45 -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: Mark Mcfadden <mark.mcfadden@icann.org>
References: <11ED4B07-AABE-4F4F-BED0-41BBDBF2ABE8@apple.com>
<05B243F724B2284986522B6ACD0504D7D34108316E@EXVPMBX100-1.exc.icann.org>
In-Reply-To: <05B243F724B2284986522B6ACD0504D7D34108316E@EXVPMBX100-1.exc.icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 09 Sep 2010 15:33:39 -0000
FWIW, I'm a bit confused by the current terms. I think we all understand the goal - a tech contact and an owner. However, both require contact info, so both are 'contacts'. Further, the doc needs to be clear about aspects of a registration each contact is permitted to change. AFAICT (subject to IANA approval): tech POC - can change to anything EXCEPT tech POC and owner POC owner POC - can change anything When tech POC and owner POC disagree, owner POC wins. The key question is whether the tech POC can really change things at all without owner POC confirmation. Joe On 9/9/2010 7:42 AM, Mark Mcfadden wrote: > I need to go through and change the rest of the document so that it is consistent. > Let me do that later today. > > mark > > Mark McFadden > mark.mcfadden@icann.org > IANA Resource Specialist > ________________________________________ > From: Stuart Cheshire [cheshire@apple.com] > Sent: Wednesday, September 08, 2010 8:54 PM > To: port-srv-reg@ietf.org > Cc: Mark Mcfadden > Subject: Inconsistent terminology regarding "Administrative Contact" and "Technical Contact" > > I see that Mark Mcfadden's checkin yesterday changed: > > @@ -874,8 +878,8 @@ > <t> > Service Name (REQUIRED)<vspace /> > Transport Protocol(s) (REQUIRED)<vspace /> > - Registration Administrative Contact (REQUIRED)<vspace /> > - Registration Technical Contact (REQUIRED)<vspace /> > + Registrant (REQUIRED)<vspace /> > + Contact (REQUIRED)<vspace /> > Description (REQUIRED)<vspace /> > Reference (REQUIRED)<vspace /> > Port Number (OPTIONAL)<vspace /> > > However, other places in the document still refer to "Administrative > Contact" and "Technical Contact", which no longer make sense. > > Why was this changed? Do we need to reverse this change, or change > the rest of the document to be consistent? > > 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
- [port-srv-reg] Inconsistent terminology regarding… Stuart Cheshire
- Re: [port-srv-reg] Inconsistent terminology regar… Mark Mcfadden
- Re: [port-srv-reg] Inconsistent terminology regar… Joe Touch
- Re: [port-srv-reg] Inconsistent terminology regar… Stuart Cheshire
- Re: [port-srv-reg] Inconsistent terminology regar… Michelle Cotton
- Re: [port-srv-reg] Inconsistent terminology regar… Joe Touch
- Re: [port-srv-reg] Inconsistent terminology regar… Joe Touch
- Re: [port-srv-reg] Inconsistent terminology regar… Michelle Cotton