Re: [port-srv-reg] FW: Question regarding service name "panoply"

Joe Touch <touch@isi.edu> Fri, 15 April 2011 05:49 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 A010CE06F2 for <port-srv-reg@ietfc.amsl.com>; Thu, 14 Apr 2011 22:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.842
X-Spam-Level:
X-Spam-Status: No, score=-104.842 tagged_above=-999 required=5 tests=[AWL=1.757, BAYES_00=-2.599, 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 BGH9JNAqBhaW for <port-srv-reg@ietfc.amsl.com>; Thu, 14 Apr 2011 22:49:28 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfc.amsl.com (Postfix) with ESMTP id 5D462E065C for <port-srv-reg@ietf.org>; Thu, 14 Apr 2011 22:49:25 -0700 (PDT)
Received: from [10.133.205.207] (UAPublic-35.guest.arizona.edu [206.207.225.35]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p3F5mM3J024160 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 14 Apr 2011 22:48:31 -0700 (PDT)
Message-ID: <4DA7DC25.4030101@isi.edu>
Date: Thu, 14 Apr 2011 22:48:21 -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: <C9CB47C2.2EEA8%michelle.cotton@icann.org>
In-Reply-To: <C9CB47C2.2EEA8%michelle.cotton@icann.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
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: Question regarding service name "panoply"
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: Fri, 15 Apr 2011 05:49:29 -0000

AOK - then register the SRV name for both transports in this case.

Joe

On 4/13/2011 12:29 PM, Michelle Cotton wrote:
> FYI. Response from one of the contacts.
>
> --Michelle
>
> ------ Forwarded Message
> *From: *Natarajan Balasundara <rajan@ipanoramii.com>
> *Date: *Wed, 13 Apr 2011 11:52:23 -0700
> *To: *Michelle Cotton <michelle.cotton@icann.org>
> *Subject: *Re: Question regarding service name "panoply"
>
> Dear Michelle,
>
> The transports used will be TCP and
> UDP. Which of the either actually gets
> used in a particular case depends on
> the characteristics of the underlying
> Data Link/Physical layer.
>
> Essentially, we currently use it for/with
> Peer-to-Peer connectivity on iPad/iPhone for Bluetooth and WiFi. So,
> Stuart Cheshire himself might have more info on its internals.
>
> Hope that answers your question.
> If I can be of any help, please do not
> hesitate to contact me.
>
> With best regards,
>
> Nat
>
>
> On Apr 13, 2011, at 2:28 PM, Michelle Cotton <michelle.cotton@icann.org>
> wrote:
>
>     Dear Natarajan,
>
>     We are currently merging the service names registry (maintained by
>     Stuart Cheshire) and the ports registry (maintained by IANA)
>     according to
>     http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/
>     <http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/>
>
>     In the service names registry the following entry appears:
>
>     panoply Panoply multimedia composite transfer protocol
>     Natarajan Balasundara <rajan at ipanoramii.com <http://ipanoramii.com> >
>     Primary Transport Protocol: Proprietary
>     Defined TXT keys: None
>
>
>
>     In the new structure of the registry, a transport is identified.
>     Currently the records shows the transport protocol as proprietary.
>     Which transport do you intend to use for lookup (which we understand
>     may have nothing to do
>     with the transport actually used by the service)?
>
>     Thank you in advance.
>
>     Michelle Cotton
>     Manager, IETF Relations – IANA
>     ICANN
>
>
>
> ------ End of Forwarded Message
>
>
>
> _______________________________________________
> Port-srv-reg mailing list
> Port-srv-reg@ietf.org
> https://www.ietf.org/mailman/listinfo/port-srv-reg