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

Henning Schulzrinne <hgs@cs.columbia.edu> Mon, 19 April 2010 21:28 UTC

Return-Path: <hgs@cs.columbia.edu>
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 38C4D3A68BA for <ecrit@core3.amsl.com>; Mon, 19 Apr 2010 14:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level:
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
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 nzjBRLjf-G7q for <ecrit@core3.amsl.com>; Mon, 19 Apr 2010 14:28:11 -0700 (PDT)
Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by core3.amsl.com (Postfix) with ESMTP id 583763A67BD for <ecrit@ietf.org>; Mon, 19 Apr 2010 14:28:11 -0700 (PDT)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o3JLRxR2000996 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 19 Apr 2010 17:27:59 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <94C75AEE-279A-4E1E-AB21-91FEEAE4EC7E@bbn.com>
Date: Mon, 19 Apr 2010 17:27:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3CD3ACB-84EB-41FD-84C1-0E1A0915F594@cs.columbia.edu>
References: <94C75AEE-279A-4E1E-AB21-91FEEAE4EC7E@bbn.com>
To: Richard Barnes <rbarnes@bbn.com>
X-Mailer: Apple Mail (2.1078)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: draft-george-ecrit-lamp-post@tools.ietf.org, ecrit@ietf.org
Subject: Re: [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:28:12 -0000

I think there's little advantage of sub-spacing; we have no shortage of CA numbers and each time you do that, you then have to face the issue of whether a new element belongs in one bin or the other.

Henning

On Apr 19, 2010, at 5:07 PM, Richard Barnes wrote:

> 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
> 
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
>