Re: [urn] Namespace application: reso

Sam DeBord <sam@reso.org> Wed, 30 October 2019 18:49 UTC

Return-Path: <sam@reso.org>
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 B1DEE120805 for <urn@ietfa.amsl.com>; Wed, 30 Oct 2019 11:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=reso-org.20150623.gappssmtp.com
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 4baEHxBfjqNE for <urn@ietfa.amsl.com>; Wed, 30 Oct 2019 11:49:35 -0700 (PDT)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E58B1120013 for <urn@ietf.org>; Wed, 30 Oct 2019 11:49:34 -0700 (PDT)
Received: by mail-oi1-x22d.google.com with SMTP id i185so2894984oif.9 for <urn@ietf.org>; Wed, 30 Oct 2019 11:49:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=reso-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=h/FmVD/SoJv3p1QeyCHzkiRtfVAiGTh1rXmZNsW8ix0=; b=xIXO8C6s7hwUQ9qLNN+wi6v11IpyICZrmhZ8mizDnXJBpAhJz97uNJO7Gqi8o2YZ7W /1A2x8cA/D5K3k5/IPFMjZ+A4Yq1xlIkUrOViDbAgvPz749dzHEU0xKGCktbd4mTNjwe 1DgV1fl3rerzHHb9kbxJEN6k+KYh6w0BZWE50fBmF7l+2fuDO7lM5dKpe+VSfqwK+Aus KuQ6mXR8/2wvAPQZO7onHkuX6sbalhyt/8sRsVxOpMNktf4FIFMRLQoOUpqytSDbMz3X o5BBTKhA8hoURfmJzZubwzMENHXQ8PzQ1MzX/vmDS+T3eYF6+ey8YUCH3FqJsxXrCjn1 KYPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=h/FmVD/SoJv3p1QeyCHzkiRtfVAiGTh1rXmZNsW8ix0=; b=HdXFGhXHE7gZ8rzJgs+BcHItPVjIpXqIubJ4/zg3V75Ga3DbyzXT617rAflPSsJ2fh kv1NEhWzumEluXeHIaE7yD0gfr2ifIVGbUWSe4Rd9jKn6E2NMawEV90jQ42b+QU7Duks nmwALYmrNeMhbTocIisT3+txHtBTZMxFwjKVKqdFrVdlQy2KWixisFxvr/BWh2H5+0M3 dmgX8oawCOuC4wnDiawO/gyA2PNAyBgroseZaIE3TtaqrHzcm8z1D/YfydZteO3ryXrI LPLX8RGJQvZGF1TJjHgIqnDfXL/nbFkntcku1HO6k/0Wo56t5wn/pEXOsYRw4J1zs2bY v+tA==
X-Gm-Message-State: APjAAAWERS90JeWggETfTBJW859SrSPeq0FrYBlinzR1/bagDxJD5F93 HB6c+P70UqG2ynU/UCEbyVODNsCCJauzqzTtKtysz+yjOTo=
X-Google-Smtp-Source: APXvYqx4M990MXEkau1v1XPRIygR/y1Px3aVBDIl/z5kRlV1hkFuAB7fgs/ZZTxjTTSoHNeocAhelVXWIESXko09rrw=
X-Received: by 2002:aca:4f51:: with SMTP id d78mr630342oib.40.1572461374129; Wed, 30 Oct 2019 11:49:34 -0700 (PDT)
MIME-Version: 1.0
References: <CAEKPRhkkPZ6Hyu-QQ=8k4CVkhTETBr8MdkYQ3VbWOXwZg=_AXA@mail.gmail.com> <d213cfb2-68b1-9339-4b8a-9ffffc662c38@it.aoyama.ac.jp>
In-Reply-To: <d213cfb2-68b1-9339-4b8a-9ffffc662c38@it.aoyama.ac.jp>
From: Sam DeBord <sam@reso.org>
Date: Wed, 30 Oct 2019 11:49:21 -0700
Message-ID: <CAEKPRh=pqqpdfaEaKnHZfooRiHxdAkHw9v+wHFtFh7SDmibA4g@mail.gmail.com>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>, urn@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a0d7b60596253145"
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/P4WdOZBIBlRCgDXGtNjhTCjfXAk>
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: Wed, 30 Oct 2019 18:49:38 -0000

Thank you, Martin. We will include an expansion of RESO to Real Estate
Standards Organization. Are there other areas of feedback from the group
before we re-submit?

*Sam DeBord*
CEO | Real Estate Standards Organization
sam@reso.org | 206.658.3225


On Mon, Oct 21, 2019 at 6:38 PM Martin J. Dürst <duerst@it.aoyama.ac.jp>
wrote:

> Hello Sam,
>
> Just some quick comment: The template should contain at least one
> expansion of "RESO". If it weren't for your signature, I wouldn't have
> had a clue that it's standing for "Real Estate Standards Organization".
> Also, it looks like this organization is limited to the US (which is
> okay), maybe there should be a word or two mentioning that.
>
> Regards,   Martin.
>
>
> On 2019/10/22 03:39, Sam DeBord wrote:
> > Hello,
> >
> > Please see the template attached for a reso namespace. Please advise us
> of
> > next steps.
> > Thank you.
> >
> > *Sam DeBord*
> > CEO | Real Estate Standards Organization
> > sam@reso.org | 206.658.3225
> >
> > --
> >
> > Namespace Identifier:
> >
> >     reso
> >
> > Version:
> >
> >     0.1
> >
> > Date:
> >
> >     2019-10-21
> >
> > Registrant:
> >
> >     <RESO Contact Information here...>
> >
> > Purpose:
> >
> > The Namespace Identifier (NID) "reso" for Uniform Resource Names
> > (URNs) will be used to identify resources published by RESO.
> > These might include published standards or protocols that RESO
> > defines and that make use of URNs.  These namespaces are globally
> > unique.  The URN namespace will be used in public networks by
> > clients to configure and manage resources in the network.  Servers
> > will enforce the uniqueness of the namespaces by using the
> > namespace and the XPath associated with the managed node in the
> > network when accessing a resource.
> >
> > Syntax:
> >
> >     The syntax of Namespace Specific Strings for the "reso" namespace
> >     is <NSS> in Uniform Resource Names (URNs) [RFC8141].
> >
> > The entire URN is case-insensitive.
> >
> > Assignment:
> >
> >     RESO will maintain the list of registered resources that use the
> >     "reso" NID in the "RESO URN Namespace" standards at
> >     <https://www.reso.org/>.
> >
> >     The RESO workgroups describe the <NSS>, how namespaces will be
> > allocated, and how experimental namespaces can
> >     be used within the allocated URN.
> >
> >     RESO will manage resource classes using the "reso" NID and will be
> >     the authority for managing resources and associated subsequent
> >     strings.  RESO will guarantee the uniqueness of the strings by
> >     validating them against the existing content of the standards.
> >     RESO may also permit secondary responsibility for certain defined
> >     resources.  Once a subtree assignment is made, it cannot be
> >     deleted or reassigned.
> >
> >     RESO may allow use of experimental type values in specific
> >     subtrees for testing purposes only.  Note that using experimental
> >     types may create collision as multiple users may use the same
> >     values for different resources and specific strings.  All
> >     experimentation must follow the guidance set forth in "A Uniform
> >     Resource Name (URN) Namespace for Examples" [RFC6963].
> >
> > Security and Privacy:
> >
> >     There are no additional security considerations other than those
> >     normally associated with the use and resolution of URNs in general.
> >
> > Interoperability:
> >
> >     There are no known interoperability issues at this time.
> >
> > Resolution:
> >
> >     It is not foreseen that URNs within this namespace will undergo
> >     resolution.
> >
> > Documentation:
> >
> >     Documentation can be found at
> >     <https://www.reso.org>
> >
> >
> > _______________________________________________
> > urn mailing list
> > urn@ietf.org
> > https://www.ietf.org/mailman/listinfo/urn
> >
>