Re: [port-srv-reg] SHORT name (14 CHARACTER MAXIMUM)

Joe Touch <touch@isi.edu> Tue, 30 August 2011 21:23 UTC

Return-Path: <touch@isi.edu>
X-Original-To: port-srv-reg@ietfa.amsl.com
Delivered-To: port-srv-reg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8028F21F8F4A for <port-srv-reg@ietfa.amsl.com>; Tue, 30 Aug 2011 14:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXMnGgoRzpiI for <port-srv-reg@ietfa.amsl.com>; Tue, 30 Aug 2011 14:23:34 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 92BD321F8F2E for <port-srv-reg@ietf.org>; Tue, 30 Aug 2011 14:23:34 -0700 (PDT)
Received: from [198.123.60.219] ([198.123.60.219]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p7ULOcqP028021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Aug 2011 14:24:41 -0700 (PDT)
Message-ID: <4E5D5515.8030203@isi.edu>
Date: Tue, 30 Aug 2011 14:24:37 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Stuart Cheshire <cheshire@apple.com>
References: <429E7E1A-3FE1-4796-B269-C04477CDB62F@apple.com> <4E590422.5050201@isi.edu> <83E929D8-B0AB-49A7-B3D3-47841D3AA194@apple.com>
In-Reply-To: <83E929D8-B0AB-49A7-B3D3-47841D3AA194@apple.com>
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
Subject: Re: [port-srv-reg] SHORT name (14 CHARACTER MAXIMUM)
X-BeenThere: port-srv-reg@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 30 Aug 2011 21:23:35 -0000

Hi, Stuart,

Yes - the form that's up right now is incorrect. I am hoping we can fix 
that very soon, and don't know why we haven't already posted the new 
form (which we do send to applicants after they apply). I'm not sure 
what we can do other than wait for that change and encourage it to 
happen soon.

Some suggestions below...

On 8/29/2011 8:30 PM, Stuart Cheshire wrote:
> On 27 Aug 2011, at 7:50, Joe Touch wrote:
>
>> FWIW, this form has not been updated to the new template. IANA is sending applicants the new template by email right now.
>>
>> (I'm not sure if this is because the RFC hasn't been published, or just them catching up on updates)
>
> I have updated the<http://www.dns-sd.org/ServiceTypes.html>  to say:
>
>> This temporary registry of DNS SRV (RFC 2782) Service Names is now closed to new entries.
>>
>> This temporary registry operated from 2003 to 2010, because during that time the IANA assignment procedures did not allow for registration of a service name without an associated port number.
>>
>> The IANA assignment procedures have now been updated to allow registration of a service name without an associated port number. For more information see draft-ietf-tsvwg-iana-ports, soon-to-be RFC 6335.
>>
>> If you already sent a Service Name registration request that does not appear in this list, it has been forwarded to IANA for inclusion in the new Unified Service Name and Port Number Registry. Please be patient while IANA processes the backlog and records these new entries.
>>
>> If you have a new Service Name you wish to register, you can now do this directly through IANA.
>>
>> <http://www.iana.org/cgi-bin/usr-port-number.pl>
>
> However, right now, that link is not terribly helpful. When a
> developer goes to the wrong page to register their service type, I
> redirect them to the wrong form to register their service type. For now
> should the<http://www.dns-sd.org/ServiceTypes.html> page be saying
> something different, until the IANA pages are updated?

You might point out that the current pages are being updated and that 
additional information is already requested after the initial form is 
completed.

> In July and August (prior to me updating the page) we received 25
> new registration requests, so we seem to be averaging about three
> new requests per week. I don't want to be giving confusing guidance
> to too many developers.

Agreed and appreciated! The note above might help until the form is changed.

Joe