Re: Request for well-known URI: ashrae

Dave Robin <> Tue, 19 January 2016 06:39 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 569351AC41C for <>; Mon, 18 Jan 2016 22:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7RCV38yumI3R for <>; Mon, 18 Jan 2016 22:39:32 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 29CAD1AC41B for <>; Mon, 18 Jan 2016 22:39:32 -0800 (PST)
Received: by with SMTP id 77so539862409ioc.2 for <>; Mon, 18 Jan 2016 22:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=r5pI6bbldDm9nFzpvl4PGDwMzloey3DLaOTatvcs+qc=; b=S9dUaNURu5TJlt3rgqgCh/RmhfiXDE0V0aC7R2cItGHWG0Y2CO+5TvxDDWbgyV8+FV +XJq8FoIFJ6UQdvro5lSPQFt62c6bUieL39DQai7U+v+rzfykO6qbAotJ6bF4VeIp+mo yGVMJVOZ8jDk2CCCmBIUJcLvuoplOvs5qgZGymbgUCRLDeAmSacHxqTzts0QYlNmU3yC dsSNIGmTvIxBp86gjj2CC31MTKPg3QHWBF/YgMr0zGcZIHTnRiRnsBjG9dj8Y1CnCZjy ANMTiyfCK1YMTmBwZplkxxutFd4r1yfTq7JVSrG1MpPNavylPhwiHyldCd7Z7xAxazq9 gyUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=r5pI6bbldDm9nFzpvl4PGDwMzloey3DLaOTatvcs+qc=; b=Wdo+cRjODXY0l6089c5WrpdmhMd7bNQUbdDwoklxxth+fmAKYAIcFNGPOwPnU9+qdv 4ekG2NvfF05i7SCC0GoX/qh2OSSdfvdGWTAmogSY5eScP54f8UravlZg15Xm0oN7QlYZ cTg36d5X3vJ9KXIl4XoUNAMZj9plLbuq/FbR1RyqsLeYVQSCemQbma7PzluKPG1bMu95 GOHn7btlC+k9joTf/iaIk8OOFObcTabwWAvyrARtKw0TURqL7eEuMQq3dl+HJQERy3LV G5/QP7NoRCJk9uZzimWM5j17tLBlSGdLAS7NNBKgRPUgSYkZgmN1sgS1KEO++s4IcX1N xoTQ==
X-Gm-Message-State: ALoCoQkktDdWNgrdKnQtIFGweEgB/EW1XbpR0f0Xq13GzoWkEAGxw9UVMmwmhM6gKzC+1fF5b48rRAZ08Xdux8ErM+PQkG3LrA==
X-Received: by with SMTP id x18mr29756343iod.170.1453185571379; Mon, 18 Jan 2016 22:39:31 -0800 (PST)
Received: from ( []) by with ESMTPSA id j136sm10240543ioj.32.2016. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 18 Jan 2016 22:39:30 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_08B5F56F-30CE-4521-A3B7-165BFCA0FE7B"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Request for well-known URI: ashrae
From: Dave Robin <>
In-Reply-To: <>
Date: Tue, 19 Jan 2016 01:39:26 -0500
Message-Id: <>
References: <> <>
To: Mark Nottingham <>
X-Mailer: Apple Mail (2.2104)
Archived-At: <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Well-Known URI review list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 19 Jan 2016 06:39:34 -0000

On Jan 19, 2016, at 12:02 AM, Mark Nottingham <> wrote:
> Hi Dave,
> Looks good. Do you mind if we omit the 'related information' in the registry entry?

Not at all.  That was for your benefit. I didn't intend that to be part of the registry.  My mistake.

One issue... a bit of a chicken and egg, actually.  Since we are a overly-careful publicly-reviewed ANSI and ISO standard, some folks did not want to publish the standard until the postfix was registered, but if the registration contains a "Specification Document" that points to pre-publication public review version of our standard, they don't like that either!  dueling dependencies!

You see, that link I included is to <>, which is a kind of a staging area for what will eventually be published at 

So, the questions are: 
after registration...
1) what is the procedure to update the "Specification Document" when we get a fully published version?
2) can we list *two* specification documents?  (some folks might prefer to get the ISO standard rather then the ANSI/ASHRAE one).


> Cheers, 
>> On 19 Jan 2016, at 10:58 am, Dave Robin <> wrote:
>> Greetings, 
>> As part of our on-going development of standard protocols for building automation, we are requesting a /.well-known suffix. (We have already registered the needed Content-Types mentioned in the referenced document)
>> URI suffix:  "ashrae"
>> Change controller:  American Society of Heating, Refrigeration, and Air-conditioning Engineers (ASHRAE)
>> Specification document(s):
>> Related information:  The referenced document is a new version of BACnet/WS (Building Automation and Control network / Web Services). BACnet (ANSI/ASHRAE Standard 135 and ISO Standard 16484-5) is the dominant protocol for commercial, industrial, and institutional building automation and control.  The primary protocol is based on binary encoded ASN.1 data structures.  This is a RESTful JSON and XML versions of that, plus numerous web-services-only features.  Initially, we need a way to discover URI prefixes for the resources on a given BACnet/WS server.  However, this /.well-known is being requested for "ashrae", rather than just "bacnet", so that other uses by the ASHRAE engineering society can be defined in the future.
>> Thank you for your consideration,
>> Dave Robin
>> Editor, BACnet Web Services
>> _______________________________________________
>> wellknown-uri-review mailing list
> --
> Mark Nottingham