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

"David Harrington" <ietfdbh@comcast.net> Tue, 12 April 2011 08:19 UTC

Return-Path: <ietfdbh@comcast.net>
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 528EEE06CB for <port-srv-reg@ietfc.amsl.com>; Tue, 12 Apr 2011 01:19:23 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hQJYvHakp0Ur for <port-srv-reg@ietfc.amsl.com>; Tue, 12 Apr 2011 01:19:22 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfc.amsl.com (Postfix) with ESMTP id 5AD64E0613 for <port-srv-reg@ietf.org>; Tue, 12 Apr 2011 01:19:22 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta13.westchester.pa.mail.comcast.net with comcast id WYKN1g0011vXlb85DYKNXB; Tue, 12 Apr 2011 08:19:22 +0000
Received: from davidPC ([85.124.176.130]) by omta17.westchester.pa.mail.comcast.net with comcast id WYK91g0062pAwk53dYKCH4; Tue, 12 Apr 2011 08:19:20 +0000
From: David Harrington <ietfdbh@comcast.net>
To: 'Lars Eggert' <lars.eggert@nokia.com>, 'Joe Touch' <touch@isi.edu>
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>
Date: Tue, 12 Apr 2011 10:18:58 +0200
Message-ID: <C2E251E92B444F08A448D9BEAEAC598A@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16543
Thread-Index: Acv4sVPbQFnu7I0LRuGWpQiXD39SQAAOO4jQ
Cc: 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 08:19:23 -0000

+1

dbh 

> -----Original Message-----
> From: port-srv-reg-bounces@ietf.org 
> [mailto:port-srv-reg-bounces@ietf.org] On Behalf Of Lars Eggert
> Sent: Tuesday, April 12, 2011 3:31 AM
> To: Joe Touch
> Cc: port-srv-reg@ietf.org
> Subject: Re: [port-srv-reg] FW: Merging Stuart's registry 
> with port-numbers
> 
> 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
> 
>