Re: Request for well-known URI: ashrae

Hi Dave,

Looks good. Do you mind if we omit the 'related information' in the registry entry?

Cheers, 

> On 19 Jan 2016, at 10:58 am, Dave Robin <dave@daverobin.com> 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) www.ashrae.org
> 
> Specification document(s):  http://www.bacnet.org/Addenda/Add-135-2012am-ppr3-draft-17_chair_approved.pdf
> 
> 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
> wellknown-uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/wellknown-uri-review

--
Mark Nottingham   https://www.mnot.net/