Re: [port-srv-reg] FW: Merging Stuart's registry with port-numbers

Joe Touch <touch@isi.edu> Tue, 12 April 2011 01:38 UTC

Return-Path: <touch@isi.edu>
X-Original-To: port-srv-reg@ietfc.amsl.com
Delivered-To: port-srv-reg@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 961F3E066A for <port-srv-reg@ietfc.amsl.com>; Mon, 11 Apr 2011 18:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.901
X-Spam-Level:
X-Spam-Status: No, score=-103.901 tagged_above=-999 required=5 tests=[AWL=1.302, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JgQRzvTZTZ4w for <port-srv-reg@ietfc.amsl.com>; Mon, 11 Apr 2011 18:38:04 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfc.amsl.com (Postfix) with ESMTP id 94DA4E0668 for <port-srv-reg@ietf.org>; Mon, 11 Apr 2011 18:38:04 -0700 (PDT)
Received: from [192.168.1.94] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p3C1b8Ru004963 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 11 Apr 2011 18:37:19 -0700 (PDT)
References: <C9C8B06D.2ECE0%michelle.cotton@icann.org> <4DA3821C.8090805@isi.edu> <DC6BAA95-7039-4D51-A96D-EA8204EEB8EC@nokia.com>
In-Reply-To: <DC6BAA95-7039-4D51-A96D-EA8204EEB8EC@nokia.com>
Mime-Version: 1.0 (iPhone Mail 8G4)
Content-Type: text/plain; charset="us-ascii"
Message-Id: <1805A615-F363-4DF6-85C1-0B262F9C4E4D@isi.edu>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (8G4)
From: Joe Touch <touch@isi.edu>
Date: Mon, 11 Apr 2011 18:37:05 -0700
To: Lars Eggert <lars.eggert@nokia.com>
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] FW: Merging Stuart's registry with port-numbers
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, 12 Apr 2011 01:38:06 -0000

One question - how does proprietary even use an srv record? Or is this just name grabbing?

On Apr 11, 2011, at 6:30 PM, Lars Eggert <lars.eggert@nokia.com> wrote:

> Hi,
> 
> if there are more cases like this, or more otherwise special cases, we may want to make edits during AUTH48. For example, allow "other" as a transport protocol tag in cases like this.
> 
> How far along with the merging are you?
> 
> Lars
> 
> On 2011-4-12, at 6:35, Joe Touch wrote:
>> That's a good question. I had argued that service names were independent of the transport protocol, but given the current text they aren't, so not clear how to handle it.
>> 
>> Maybe "other" or "proprietary" as the transport and leave it at that informally in the registry?
>> 
>> Joe
>> 
>> On 4/11/2011 1:19 PM, Michelle Cotton wrote:
>>> All:
>>> 
>>> We are in the process of officially combining the ports/service name
>>> registries.
>>> 
>>> Stuart's registry (http://www.dns-sd.org/ServiceTypes.html) contains
>>> these two entries:
>>> 
>>> panoply         Panoply multimedia composite transfer protocol
>>>                Natarajan Balasundara<rajan at ipanoramii.com>
>>>                Primary Transport Protocol: Proprietary
>>>                Defined TXT keys: None
>>> 
>>> parabay-p2p     Parabay P2P protocol
>>>                Vishnu Varadaraj<vishnuv at parabay.com>
>>>                Primary Transport Protocol: Proprietary
>>>                Defined TXT keys: None
>>> 
>>> There is a problem with the "Proprietary" transport protocol. The new
>>> port-numbers registry accepts only UDP, TCP, SCTP, or DCCP as transport
>>> protocol (according to draft-ietf-tsvwg-iana-ports-10 section 8.1.1).
>>> 
>>> How do we deal with this one?
>>> 
>>> Thanks,
>>> 
>>> --Michelle
>>> 
>>> _______________________________________________
>>> Port-srv-reg mailing list
>>> Port-srv-reg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/port-srv-reg
>> _______________________________________________
>> Port-srv-reg mailing list
>> Port-srv-reg@ietf.org
>> https://www.ietf.org/mailman/listinfo/port-srv-reg
>