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

"David Harrington" <ietfdbh@comcast.net> Wed, 13 April 2011 06:12 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 81506E0695 for <port-srv-reg@ietfc.amsl.com>; Tue, 12 Apr 2011 23:12:08 -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 p+-P+n2xR70E for <port-srv-reg@ietfc.amsl.com>; Tue, 12 Apr 2011 23:12:07 -0700 (PDT)
Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by ietfc.amsl.com (Postfix) with ESMTP id 33B35E065A for <port-srv-reg@ietf.org>; Tue, 12 Apr 2011 23:12:07 -0700 (PDT)
Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta13.emeryville.ca.mail.comcast.net with comcast id WtzA1g0021vN32cADuC68Y; Wed, 13 Apr 2011 06:12:06 +0000
Received: from davidPC ([188.20.103.10]) by omta22.emeryville.ca.mail.comcast.net with comcast id WuBl1g00B0DTzuc8iuBpjZ; Wed, 13 Apr 2011 06:12:04 +0000
From: David Harrington <ietfdbh@comcast.net>
To: 'Michelle Cotton' <michelle.cotton@icann.org>, 'Lars Eggert' <lars.eggert@nokia.com>, 'Joe Touch' <touch@isi.edu>
References: <C2E251E92B444F08A448D9BEAEAC598A@davidPC> <C9C9FCA6.2EDBC%michelle.cotton@icann.org>
In-Reply-To: <C9C9FCA6.2EDBC%michelle.cotton@icann.org>
Date: Wed, 13 Apr 2011 08:11:42 +0200
Message-ID: <398A15CFD40641018E20090AEBFDCD2D@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: Acv4sVPbQFnu7I0LRuGWpQiXD39SQAAOO4jQABhjPUIAAxc6YA==
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: Wed, 13 Apr 2011 06:12:08 -0000

Hi,

does anybody know if these protocols are actually in use? 
do we WANT to limit registration to the 4 ietf protocols?
can we reclaim these (by asking the companies to change their
registration/withdraw their registration?)
we don't have a registration date for these?

dbh

> -----Original Message-----
> From: Michelle Cotton [mailto:michelle.cotton@icann.org] 
> Sent: Tuesday, April 12, 2011 9:57 PM
> To: David Harrington; 'Lars Eggert'; 'Joe Touch'
> Cc: port-srv-reg@ietf.org
> Subject: Re: [port-srv-reg] FW: Merging Stuart's registry 
> with port-numbers
> 
> FYI...we believe these 2 (mentioned below) are the only 2
exceptions.
> How do you want to proceed?
> 
> --Michelle
> 
> 
> 
> On 4/12/11 1:18 AM, "David Harrington" <ietfdbh@comcast.net> wrote:
> 
> > +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
> >> 
> >> 
> > 
> > _______________________________________________
> > Port-srv-reg mailing list
> > Port-srv-reg@ietf.org
> > https://www.ietf.org/mailman/listinfo/port-srv-reg
> 
>