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

Michelle Cotton <michelle.cotton@icann.org> Wed, 13 April 2011 19:30 UTC

Return-Path: <michelle.cotton@icann.org>
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 BF27BE07CB for <port-srv-reg@ietfc.amsl.com>; Wed, 13 Apr 2011 12:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.206
X-Spam-Level:
X-Spam-Status: No, score=-106.206 tagged_above=-999 required=5 tests=[AWL=0.392, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 Xt40JVeXQNJL for <port-srv-reg@ietfc.amsl.com>; Wed, 13 Apr 2011 12:29:59 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfc.amsl.com (Postfix) with ESMTP id 2ABFEE065C for <port-srv-reg@ietf.org>; Wed, 13 Apr 2011 12:29:59 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Wed, 13 Apr 2011 12:29:58 -0700
From: Michelle Cotton <michelle.cotton@icann.org>
To: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Date: Wed, 13 Apr 2011 12:29:54 -0700
Thread-Topic: Question regarding service name "panoply"
Thread-Index: Acv6C/yJZmg1j/F4RjCzMGYj9wfYqwABS2wS
Message-ID: <C9CB47C2.2EEA8%michelle.cotton@icann.org>
In-Reply-To: <29E60FFA-BA19-4A8C-B1BA-4DBF5D9D61CE@ipanoramii.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.8.0.101117
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C9CB47C22EEA8michellecottonicannorg_"
MIME-Version: 1.0
Subject: [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: Wed, 13 Apr 2011 19:30:00 -0000

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