[Ecrit] Generalizing draft-george-ecrit-lamp-post

Richard Barnes <rbarnes@bbn.com> Mon, 19 April 2010 21:07 UTC

Return-Path: <rbarnes@bbn.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC9673A68D4 for <ecrit@core3.amsl.com>; Mon, 19 Apr 2010 14:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.179
X-Spam-Level:
X-Spam-Status: No, score=-1.179 tagged_above=-999 required=5 tests=[AWL=-1.180, BAYES_50=0.001]
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 AXNkIydC2xoL for <ecrit@core3.amsl.com>; Mon, 19 Apr 2010 14:07:39 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id DBB0F3A67BD for <ecrit@ietf.org>; Mon, 19 Apr 2010 14:07:39 -0700 (PDT)
Received: from [192.1.255.202] (port=62399 helo=col-dhcp-192-1-255-202.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1O3yBm-0001Jp-It; Mon, 19 Apr 2010 17:07:30 -0400
Message-Id: <94C75AEE-279A-4E1E-AB21-91FEEAE4EC7E@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: draft-george-ecrit-lamp-post@tools.ietf.org
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 19 Apr 2010 17:07:29 -0400
X-Mailer: Apple Mail (2.936)
Cc: ecrit@ietf.org
Subject: [Ecrit] Generalizing draft-george-ecrit-lamp-post
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2010 21:07:41 -0000

It seems like this draft is a little specific to a particular use- 
case.  As several people mentioned in Anaheim, there are lots of  
things around that have numbers on them -- from lamp-posts, mile- 
posts, utility poles, bridges, etc.  If you were going to be  
inclusive, you might include all the QR codes that Google has been  
putting up as well.

So to avoid having to define new CAtypes for every "numbered thing  
that can be a location indicator", could I suggest that we make the  
following generalization?

1. Add a single "place number" ("PLN"?) CAtype with two child nodes:
1.1. A "type" to indicate what type of numbered object is being  
referred to
1.2. The number of the referenced object

2. Add a first-come-first-served registry of type values