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

Joe Touch <touch@isi.edu> Mon, 11 April 2011 22:36 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 23888E06CA for <port-srv-reg@ietfc.amsl.com>; Mon, 11 Apr 2011 15:36:26 -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=[AWL=0.000, BAYES_00=-2.599, 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 FUw7+W1bdy4I for <port-srv-reg@ietfc.amsl.com>; Mon, 11 Apr 2011 15:36:23 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfc.amsl.com (Postfix) with ESMTP id EE637E06AD for <port-srv-reg@ietf.org>; Mon, 11 Apr 2011 15:36:14 -0700 (PDT)
Received: from [192.168.1.93] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p3BMZ8Jd023065 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 11 Apr 2011 15:35:19 -0700 (PDT)
Message-ID: <4DA3821C.8090805@isi.edu>
Date: Mon, 11 Apr 2011 15:35:08 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Michelle Cotton <michelle.cotton@icann.org>
References: <C9C8B06D.2ECE0%michelle.cotton@icann.org>
In-Reply-To: <C9C8B06D.2ECE0%michelle.cotton@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] 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: Mon, 11 Apr 2011 22:36:26 -0000

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