Re: [port-srv-reg] "xmp" service type and the unified IANA Service Name and Port Number Registry

[Bobby Krupczak <[e-mail]>]

Hi!

>> From: Henric Bergh<[e-mail]>
>> Date: Wed, 24 Jan 2007 14:14:52 -0700

He has me beat by roughly 1.5 years :(

> A Google search for "srv type xmp" finds the DNS SRV Service Types list as the first hit:

Back in 2008, it did not return this when one searched for XMP or xmp.
>
> The additional factor here is that because Xperientia registered *only* a service name, they don't have an assigned port to go with it. Therefore, by definition they must be using the name, because that's all they have. Their servers bind to a dynamically-allocated port and their clients discover the dynamically-allocated port via DNS-SD queries, thereby conserving the limited remaining assigned port space, which is beneficial for the future of the Internet, and is virtuous behavior we'd like to encourage.

Good point.

> My personal view is that getservbyname() is a flawed API with very limited usefulness. It simply consults the local /etc/services table on Unix, and, in your case, should always return the fixed constant 5270. So calling getservbyname("xmp", "tcp") is just a less-efficient way of writing "htons(5270)".

Thanks for the networking API tutorial.

I appreciate the additional info.  I think it would have been helpful 
had you given this info in your original request; it might have come off 
less of an imposition.

I'm happy to change my service name as my software only needs the 
assigned port.

Let me think of something cute and we can switch to that.  Give me a 
couple of days to try to be creative with some sort of name.  What is 
the service name criteria?  How many letters/digits?

As a former participant in the IETF, I really do appreciate the work you 
guys do.

Thanks,

Bobby