RE: vendor registry lookup service

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 27 July 2009 17:10 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F08E728C333; Mon, 27 Jul 2009 10:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.323
X-Spam-Level:
X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpize7v9Wyuu; Mon, 27 Jul 2009 10:10:44 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 8C23928C2F6; Mon, 27 Jul 2009 10:10:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,277,1246852800"; d="scan'208";a="178131564"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 27 Jul 2009 13:10:32 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 27 Jul 2009 13:10:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: vendor registry lookup service
Date: Mon, 27 Jul 2009 19:10:09 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04018CFA35@307622ANEX5.global.avaya.com>
In-Reply-To: <4A6DC20C.8040608@viagenie.ca>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: vendor registry lookup service
thread-index: AcoOy6JXe0Xa6LJuSEyu8LfY/YgMdgAESjDw
References: <4A6DC20C.8040608@viagenie.ca>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Marc Blanchet" <marc.blanchet@viagenie.ca>, <apps-discuss@ietf.org>, <vcarddav@ietf.org>
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 17:10:46 -0000

Marc,

The name that is associated with a PEN is the name on the form submitted
to IANA at the moment of the request. Nothing less, nothing more. 

Dan
 

> -----Original Message-----
> From: apps-discuss-bounces@ietf.org 
> [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Marc Blanchet
> Sent: Monday, July 27, 2009 6:05 PM
> To: apps-discuss@ietf.org; vcarddav@ietf.org
> Subject: vendor registry lookup service
> 
> Hi,
>  there are some discussions about creating/extending a vendor 
> name space registry for applications protocols (see 
> http://www3.ietf.org/proceedings/75/slides/apparea-3.pdf 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 display.
> 
> 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 enterprise-numbers.org domain name. It is 
> available now.
> 
> For example:
> 
> dig 31474.enterprise-numbers.org TXT
> ...
> 31474.enterprise-numbers.org. 86400 IN	TXT	"Viagenie inc."
> 
> 
> dig 5842.enterprise-numbers.org TXT
> ...
> 5842.enterprise-numbers.org. 86400 IN	TXT	"Cisco Systems"
> 
> Regards, Marc.
> 
> --
> =========
> IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca 
> Stun/Turn server for VoIP NAT-FW traversal: 
> http://numb.viagenie.ca DTN news service: http://reeves.viagenie.ca
> 
> _______________________________________________
> Apps-Discuss mailing list
> Apps-Discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>