Re: [urn] Namespace application: reso
worley@ariadne.com (Dale R. Worley) Sun, 03 November 2019 14:10 UTC
Return-Path: <worley@alum.mit.edu>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D86B120089 for <urn@ietfa.amsl.com>; Sun, 3 Nov 2019 06:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Level:
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CeW2zII8lrJx for <urn@ietfa.amsl.com>; Sun, 3 Nov 2019 06:10:43 -0800 (PST)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D74D120033 for <urn@ietf.org>; Sun, 3 Nov 2019 06:10:43 -0800 (PST)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id RGPAirkntkltDRGaYidhFA; Sun, 03 Nov 2019 14:10:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1572790242; bh=4dCdg9m2eVjJBLsxQJxXzsFMoBqTNgFRvIppURDJ8Xw=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=dUc4X1tPtMVckqLQqpMdxLoVTHZB2Le+X0MCsZZ487teEyFjNO2a3QJluD/aMPLgg bWZ3Cup8Usolib+iDFKRgJReIhD5GLK3hx4oK7+DII2JnA3oW4siLGiiymtXh5wYuC JFcGIQA4/NhkK4DROsUfBH0ezU8smSJahSTGnXyRpo+UYOFW/Vk9bvlrp4Xvk4yxGW LtbVWPyuP8xNfuMPyXL6hNCpifQmRdDzWgyqihJa/2AgsG9ID8OFd3vAsp60zKbU0c tZnBd0e58MENposL72U7RazTJDx5jJ5JExwsSc0QjLZGqkzHXYVCzxq+lOqfP37IAr dGBmYU/eqT9fA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-06v.sys.comcast.net with ESMTPA id RGaWiabazcvPrRGaXixhQR; Sun, 03 Nov 2019 14:10:42 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id xA3EB6Vu019263; Sun, 3 Nov 2019 09:11:06 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id xA3EB5LN019256; Sun, 3 Nov 2019 09:11:05 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Sam DeBord <sam@reso.org>
Cc: duerst@it.aoyama.ac.jp, urn@ietf.org
In-Reply-To: <CAEKPRh=pqqpdfaEaKnHZfooRiHxdAkHw9v+wHFtFh7SDmibA4g@mail.gmail.com> (sam@reso.org)
Sender: worley@ariadne.com
Date: Sun, 03 Nov 2019 09:11:05 -0500
Message-ID: <87k18h9hja.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/EIyxWu3Dk6Yqa-8NOxl-UAb24oE>
Subject: Re: [urn] Namespace application: reso
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Nov 2019 14:10:46 -0000
It may be that I read this document too quickly, but I got the impression that it is completely *valid*, but it doesn't tell me anything, as far as I can tell, as to what these URNs will really be used for. Even to the point that I've never heard of the "Real Estate Standards Organization" or what it does. Does it produce a series of standards that are used in the real world? Where in those standards would these URNs be used? Simimlarly, the proposed syntax is just that the URNs have to be valid URNs. It doesn't hint that you've got any detailed plan in mind. Dale
- [urn] Namespace application: reso Sam DeBord
- Re: [urn] Namespace application: reso Sam DeBord
- Re: [urn] Namespace application: reso Dale R. Worley
- Re: [urn] Namespace application: reso Hakala, Juha E
- Re: [urn] Namespace application: reso Sam DeBord