[dns-dir] DNS-EW: draft-vanderstok-core-bc-01.txt

DNS_EARLY_WARNING <ogud@ogud.com> Sun, 11 July 2010 18:39 UTC

Return-Path: <ogud@ogud.com>
X-Original-To: dns-dir@core3.amsl.com
Delivered-To: dns-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25D5E28C0DF for <dns-dir@core3.amsl.com>; Sun, 11 Jul 2010 11:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level:
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RJfQnlkZC1OB for <dns-dir@core3.amsl.com>; Sun, 11 Jul 2010 11:39:55 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id A593428C0CF for <dns-dir@ietf.org>; Sun, 11 Jul 2010 11:39:54 -0700 (PDT)
Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id o6BIe0r5022444 for <dns-dir@ietf.org>; Sun, 11 Jul 2010 14:40:00 -0400 (EDT) (envelope-from ogud@ogud.com)
To: dns-dir@ietf.org
From: DNS_EARLY_WARNING <ogud@ogud.com>
Date: Sun, 11 Jul 2010 14:40:00 -0400
X-Mailer: Perl script "early-2010.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox"
Message-ID: <20100711_184000_091671.ogud@ogud.com>
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Subject: [dns-dir] DNS-EW: draft-vanderstok-core-bc-01.txt
X-BeenThere: dns-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNS directorate discussion list <dns-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dns-dir>
List-Post: <mailto:dns-dir@ietf.org>
List-Help: <mailto:dns-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 18:39:59 -0000

Count:       28 


CoRE                                                     P. van der Stok
Internet-Draft                                          Philips Research
Intended status: Informational                                   K. Lynn
Expires: January 10, 2011                                     Consultant
                                                            July 9, 2010


                 CoAP Utilization for Building Control
                      draft-vanderstok-core-bc-01

 Abstract

   This I-D describes an example use of the RESTful CoAP protocol for
   building control applications such as HVAC and lighting.  A few basic
   design assumptions are stated first.  The URI structure is exploited
   to define multicast as well as unicast scopes.  RFC 3986 defines the
   URI components as (1) a scheme, (2) an authority, used here to locate
   the building, area, or node under control, (3) a path, used here to
   locate the resource under control, and (4) a query and fragment part,
   where fragments are not supported in CoAP.

   This proposal supports the view that (1) building control is likely
   to move in steps toward all-IP control networks based on the legacy
   efforts provided by DALI, LON, BACnet, ZigBee, and other standards,
   (2) service discovery is complimentary to resource discovery and
   facilitates control network scaling, and (3) the provision of a
   reliable group communication protocol is essential to support
   building control applications.