vendor registry lookup service

Marc Blanchet <> Mon, 27 July 2009 15:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6247A3A6BFB; Mon, 27 Jul 2009 08:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EFUjoSTJRU5P; Mon, 27 Jul 2009 08:05:01 -0700 (PDT)
Received: from ( [IPv6:2620:0:230:8000::2]) by (Postfix) with ESMTP id 0CC6D3A6B22; Mon, 27 Jul 2009 08:05:01 -0700 (PDT)
Received: by (Postfix, from userid 8) id 0C82A29E15E5; Mon, 27 Jul 2009 11:05:02 -0400 (EDT)
Received: from ( []) by (Postfix) with ESMTP id 63D9829E15E1; Mon, 27 Jul 2009 11:05:01 -0400 (EDT)
Message-ID: <>
Date: Mon, 27 Jul 2009 17:04:44 +0200
From: Marc Blanchet <>
User-Agent: Thunderbird (Macintosh/20090605)
MIME-Version: 1.0
Subject: vendor registry lookup service
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 27 Jul 2009 15:05:02 -0000

 there are some discussions about creating/extending a vendor name space
registry for applications protocols
(see as
presented at apps-area meeting this morning).

I made the point at the mike that we already have a vendor registry: the
private enterprise numbers (PEN), which contains 35K entries, on a first
come first serve manner, and automated by IANA. On the contrary, the
proposal is based on the acap registry which contains about a dozen entries.

why should we reinvent another registry with almost same data?

One comment was made about the fact that the PEN are made of digits,
therefore not user-friendly to be shown to the end-user. While I don't
think this is a real issue and can be managed differently, I'm proposing
a simple solution: a lookup service mapping PEN to vendor name, for user

Thereby, this mail announces a PEN lookup service to map the PEN to the
vendor name. This is implemented as a DNS TXT record under the domain name. It is available now.

For example:

dig TXT
... 86400 IN	TXT	"Viagenie inc."

dig TXT
... 86400 IN	TXT	"Cisco Systems"

Regards, Marc.

IPv6 book: Migrating to IPv6, Wiley.
Stun/Turn server for VoIP NAT-FW traversal:
DTN news service: