Return-Path: 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 E82F03A0C5D for ; Sun, 8 Mar 2020 08:59:02 -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, 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 333YI_CZTqei for ; Sun, 8 Mar 2020 08:59:01 -0700 (PDT) Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 2FBD43A0C5C for ; Sun, 8 Mar 2020 08:59:01 -0700 (PDT) Received: by mail-ot1-x331.google.com with SMTP id f21so7151658otp.12 for ; Sun, 08 Mar 2020 08:59:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=reso-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=3sE/+019LyOr4cRn4thXUUOT2udslpJQ0X8ILtgIn10=; b=k1PES/dVZASP31UZhqwT4ZXQkzGI8znd7DHh2HmcnU9uXyOLC+7DBg4H77C+prVglh IVJty3GT2/lHhJN1GJiiuzgDj9nU6FplOJsIymgqSUpAqg8L5/9JtaoxsJ7pnW+SPzRS TcjGeqtOCml7U4wkJJ2hdgE20CMdyjdkERsXK9eFH9C9wELNCKfaElIj1QmrGcw+Pk7j ZBMahjsci2PTzuy6PMhsukuY8MgwAQfWxXR2QYOmFG4nKRLL6NwgJ6Gf/tJ6sdTZsSq8 gm4H7Yq5PrFdSz15pPTIkFhhzMcM+9p6ZebSFtaHiYLRrFogzj/+fdbmc3a98zAHa9RP v/dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=3sE/+019LyOr4cRn4thXUUOT2udslpJQ0X8ILtgIn10=; b=arXjGlUYGbKBiUFtkYl9VBhrXQG9xvoPM1CYAZN2DMShFOKjSMmBx9PkLm5vYPfEOC CeI/LPXa+CsYsaj1RO+qKXSw0kCs74SG09E9DLzaBGxxOJktwDh/jO4oizHu5hGRfQuK ogSxVCyTcQG5OVQPvjY4sO2W+DKubGhxju96ZOi1V+J7yY03hgs4z9N0uA4/VDpMWuJ/ qPH6xU+LtgI4o6HRVKbD/LbYhf6IH/1FN2AmNwEX/EiBAdpkKev11XhY6aEVerk7vXSM F3OJFZO6+VxguHY4PKar1Qdq+kmEz+KhB7/EY44+5L3Bzp2qaWcCieRkT330ln/2uBGJ pqsQ== X-Gm-Message-State: ANhLgQ0XYTNIh+b9CKU8cYR5apF8zxydWq7jGTkyCr1MSOyHCLXQtJzw fSsIMp+ArEjhizXXUDmU4Vs6MQmVoThcsJ/lBOUEv93OOVaETw== X-Google-Smtp-Source: =?utf-8?q?ADFU+vvha6fBX8bbQsQuKFVFczvWCIcKmL2UGnRIFNFY?= =?utf-8?q?mLF0v0mu3cYQFSVXHGItpTOzQrAfKvLWPSqv4VUsnI7UVk4=3D?= X-Received: by 2002:a05:6830:129a:: with SMTP id z26mr10328512otp.179.1583683140006; Sun, 08 Mar 2020 08:59:00 -0700 (PDT) MIME-Version: 1.0 From: Sam DeBord Date: Sun, 8 Mar 2020 08:58:24 -0700 Message-ID: To: urn@ietf.org Cc: Joshua Darnell Content-Type: multipart/alternative; boundary="000000000000ff6e6105a059f616" Archived-At: Subject: [urn] Namespace application v2: reso X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2020 15:59:03 -0000 --000000000000ff6e6105a059f616 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Please see resubmission of namespace application below. *Sam DeBord* CEO | RESO - Real Estate Standards Organization sam@reso.org | 206.658.3225 -- Namespace Identifier: reso Version: 0.1 Date: 2020-03-08 Registrant: Real Estate Standards Organization Sam DeBord, CEO sam@reso.org =E2=80=93 919.504.9898 Purpose: The Namespace Identifier (NID) "reso" for Uniform Resource Names (URNs) will be used to identify resources published by Real Estate Standards Organization: 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. Examples of proposed uses: Representation of Unique Licensee IDs: These will have the form of urn:reso:ulid:x, where x is a specific licensee identifier. Licensees can be people like Agents, photographers, appraisers, and others involved in the transaction. Recorder IDs: These are part of an event model proposal, in which the URN will take a form of urn:reso:recorder:org:x, where org is an organization id well-known to RESO and x is identifier of the recording entity in that organization. References to RESO Data Dictionary items: These are already established in our ecosystem. This link shows the "Property" resource, which consists of fields and enumerations. Each field has a RESO-generated RecordID associated with it (or LookupID in the case of enumerated values). For example, the PropertySubType field has a RecordID of 100222, and one of the allowed values for that field is Apartment, which is part of Lookup Field ID 302000 and has LookupID 302001. These would have URNs of the form: urn:reso:rid:100222, urn:reso:lfid:302000, and urn:reso:lid:302001, respectively. Syntax: The syntax of Namespace Specific Strings for the "reso" namespace is 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 . The RESO workgroups describe the , 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 --000000000000ff6e6105a059f616 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Please see resubmission=C2=A0of namespace application=C2= =A0below.
=C2=A0
Sam DeBord
CEO | RESO -=C2=A0Real Estate Standards Organization=C2=A0=C2=A0
= sam@reso.org | 206.658.3225=C2=A0
<= font color=3D"#000000" face=3D"arial, sans-serif">
--

Namespace Identifier:

=C2=A0 =C2=A0reso

Version:

=C2=A0 =C2=A00.1

Date:

=C2=A0 =C2=A02020-03-08

Registrant:

Real Estate Standards Organization

Sam DeBord, CEO

sam@reso.org =E2=80=93 919.504.9898

Purpose:

The Namespace Identifier (NID) "reso" for Uniform Resource Names<= br> (URNs) will be used to identify resources published by Real Estate Standard= s Organization: RESO <ht= tps://reso.org>.


These might include published standards or protocols that RESO
defines and that make use of URNs.=C2=A0 These namespaces are globally uniq= ue.=C2=A0 The URN namespace will be used in public networks by clients to c= onfigure and manage resources in the network.=C2=A0 Servers will enforce th= e uniqueness of the namespaces by using the namespace and the XPath associa= ted with the managed node in the=C2=A0network when accessing a resource.

=C2=A0

Examples of proposed use= s:


=C2=A0

Representation of Unique= Licensee IDs: These will have the form of urn:reso:ulid:x, where x is a specific licensee identifier. Licensees can b= e people like Agents, photographers, appraisers, and others involved in the transaction.

=C2=A0

Recorder IDs: These are = part of an event model proposal, in which the URN will take a form of urn:reso:recorder:org:x, where org is an organization id well-known to RESO and x is identifier of the recording ent= ity in that organization.

=C2=A0

References to RESO Data = Dictionary items: These are already established in our ecosystem. This link shows the "Property" resource, which consists of fields and enumerations. Each field has a RESO-generated RecordID associated with it (or LookupID in the case of enumerated values). For example, the PropertySubType field has a RecordID o= f 100222, and one of the allowed values for that field is Apartment, which is part of Lookup Field ID 302000 and has LookupID 302001. These would have URNs of th= e form: urn:reso:rid:100222, urn:reso:lfid:302000, and urn:reso:lid:302001, respectively.

Syntax:

=C2=A0 =C2=A0The syntax of Namespace Specific Strings for the "reso&qu= ot; namespace
=C2=A0 =C2=A0is <NSS> in Uniform Resource Names (URNs) [RFC8141].

The entire URN is case-insensitive.

Assignment:

=C2=A0 =C2=A0RESO will maintain the list of registered resources that use t= he
=C2=A0 =C2=A0"reso" NID in the "RESO URN Namespace" standards at
=C2=A0 =C2=A0<https://www.reso.org/<= /span>>.

=C2=A0 =C2=A0The RESO workgroups describe the <NSS>, how namespaces w= ill be allocated, and how experimental namespaces can
=C2=A0 =C2=A0be used within the allocated URN.

=C2=A0 =C2=A0RESO will manage resource classes using the "reso" N= ID and will be
=C2=A0 =C2=A0the authority for managing resources and associated subsequent=
=C2=A0 =C2=A0strings.=C2=A0 RESO will guarantee the uniqueness of the strin= gs by
=C2=A0 =C2=A0validating them against the existing content of the standards.=
=C2=A0 =C2=A0RESO may also permit secondary responsibility for certain defi= ned
=C2=A0 =C2=A0resources.=C2=A0 Once a subtree assignment is made, it cannot = be
=C2=A0 =C2=A0deleted or reassigned.

=C2=A0 =C2=A0RESO may allow use of experimental type values in specific
=C2=A0 =C2=A0subtrees for testing purposes only.=C2=A0 Note that using experimental
=C2=A0 =C2=A0types may create collision as multiple users may use the same<= br> =C2=A0 =C2=A0values for different resources and specific strings.=C2=A0 All=
=C2=A0 =C2=A0experimentation must follow the guidance set forth in "A Uniform
=C2=A0 =C2=A0Resource Name (URN) Namespace for Examples" [RFC6963].
Security and Privacy:

=C2=A0 =C2=A0There are no additional security considerations other than tho= se
=C2=A0 =C2=A0normally associated with the use and resolution of URNs in gen= eral.

Interoperability:

=C2=A0 =C2=A0There are no known interoperability issues at this time.

Resolution:

=C2=A0 =C2=A0It is not foreseen that URNs within this namespace will underg= o
=C2=A0 =C2=A0resolution.

Documentation:

=C2=A0 =C2=A0Documentation can be found at
=C2=A0 =C2=A0<https://www.reso.org>

=C2=A0

<= /div>
--000000000000ff6e6105a059f616--