FW: Application for port-number (more tech)

[Fred Baker <fred@cisco.com>]

FYI:

advise I am giving Michelle, which may come back to you.


> From: "IANA" <iana@iana.org>
> To: "Fred Baker" <fred@cisco.com>
> Subject: FW: Application for port-number (more tech)
> Date: Thu, 1 May 2003 12:09:14 -0700
> X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
> Importance: Normal
>
> Fred,
>
> I'm having trouble understanding exactly what
> this applicant wants.  Hi application is for
> a port number but it doesn't seem he is requesting
> one.  Any ideas or suggestions?
>
> Thanks,
>
> Michelle
> IANA
>
>
> -----Original Message-----
> From: Michael™ Hamel [mailto:mhamel@adi.co.nz]
> Sent: Monday, April 28, 2003 5:11 PM
> To: IANA
> Subject: Re: Application for port-number (more tech)
>
>
>
> On Tuesday, April 29, 2003, at 11:55  AM, IANA wrote:
>
> > We have reviewed your port number application.  We
> > are not sure if a port number is what you are requesting.
> > You mention in the description that you are seeking to
> > register a protocol name.  Is this correct?
>
> > Is this something that is needed for the Zeroconf
> > working group?  Please clarify.
>
> It is required by Zeroconf: I (and Apple) are under the impression that
> a protocol name was necessarily associated with a port number, so we
> had to apply for both. If they are seperate entities,  the protocol
> name is really what we want to have registered. See Apples Rendezvous
> FAQ at:
>
> http://developer.apple.com/macosx/rendezvous/faq.html
>
> - the relevant section is:
>
> > Q: What value should I pass for the "type" parameter when registering
> > a service?
> >
> > A: You must pass a string of the form
> > "_applicationprotocol._transportprotocol". Currently
> > "_transportprotocol" must be either "_tcp" or "_udp". Your
> > "_applicationprotocol" must be a protocol name registered with IANA
> > and appearing in the list of registered IANA protocol names and port
> > numbers. If your application protocol does not appear in this list, it
> > is a simple matter to fill out the IANA application for user
> > registered port number form. You will also be allocated a registered
> > port number for your protocol, but of course you don't actually need a
> > registered port number because you will be using DNS Service Discovery
> > SRV records which specify the port number, so the client can find you
> > no matter what port your server is running on today.
>
> I hope this clarifies what we are asking for...
>
> ---
> "Now, the objective of this expedition is to attempt to find some trace
> of last years expedition."
>
> Michael Hamel
> ADInstruments Ltd, Dunedin, NZ
> Reply-To: <mjhamel@adi.co.nz>
> From: <mjhamel@adi.co.nz>
> To: <iana@iana.org>,
>         <mjhamel@adi.co.nz>
> Subject: Application for port-number
> Date: Sun, 2 Mar 2003 19:11:18 -0700
> Message-ID: <200303030211.h232BIg14581@plata.icann.org>
> MIME-Version: 1.0
> Content-Type: text/plain;
>         charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
> X-Spam-Status: No, hits=0.4 required=5.0 
> tests=NO_REAL_NAME,SUPERLONG_LINE,AWL version=2.20
> X-Spam-Level:
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> X-Real-Host-From: 202.36.219.140
Application for User Registered Port Number

Name :
Michael Hamel

E-mail :
mjhamel@adi.co.nz

Protocol Number :
TCP

Message Formats :
message target <16-bit>
message sender <16-bit>
message length < 16-bit>
message type <16-bit>
data field <0..32750 bytes>

Message Types :
There are ~100 message types currently in use. The details of what each
message type does are proprietary. Please forward a non-disclosure
agreement.

Message opcodes :
Not applicable, messages do not contain sub-messages

Message Sequences :
Not applicable. Messages can be in any order

Protocol functions :
Control and data transfer between unreleased ADI data acquisition hardware
and applications running on PC hosts

Broadcast or Multicast used ?
no

How and what for Broadcast or Multicast is used (if used):


Description :
This port would be used exclusively for control and data transfer using TCP
over Ethernet between unreleased ADI data acquisition hardware and ADI
proprietary applications running on PC hosts.

We intend to use Zeroconf/Rendezvous multicast DNS to discover ADI hardware
on the local net and TCP to work with it via this port. As we will be using
Rendezvous we do not actually require a fixed port assignment, but we
understand one is necessary to register the protocol name for use with
Zeroconf.

Name of the port :
powerlab

Short name of the port :
powerlab