IETF Logo Mail Archive

Re: [core] Subscribe/Notify for CoAP

Peter Saint-Andre <stpeter@stpeter.im> Thu, 03 June 2010 16:54 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E368B3A69E7 for <core@core3.amsl.com>; Thu, 3 Jun 2010 09:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.984
X-Spam-Level:
X-Spam-Status: No, score=-1.984 tagged_above=-999 required=5 tests=[AWL=0.615, 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 Vn44-aP9dS0z for <core@core3.amsl.com>; Thu, 3 Jun 2010 09:54:38 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id D38953A63C9 for <core@ietf.org>; Thu, 3 Jun 2010 09:54:37 -0700 (PDT)
Received: from dhcp-64-101-72-121.cisco.com (dhcp-64-101-72-121.cisco.com [64.101.72.121]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8439E40E14 for <core@ietf.org>; Thu, 3 Jun 2010 10:54:24 -0600 (MDT)
Message-ID: <4C07DE3F.6000802@stpeter.im>
Date: Thu, 03 Jun 2010 10:54:23 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: core@ietf.org
References: <0D212BD466921646B58854FB79092CEC021F4E91@XMB-AMS-106.cisco.com> <OF54E90C1C.C8997A73-ONC1257731.003EAAE3-C1257731.004127C6@schneider-electric.com> <0D212BD466921646B58854FB79092CEC021F4EF2@XMB-AMS-106.cisco.com> <6A9FCAC7-E2FA-482D-ABFF-DB6B111A9EA2@sensinode.com><001501cb021b$e5d364c0$b17a2e40$@moritz@uni-rostock.de><4C06F48D.1020600@cisco.com><87vda0u9ry.fsf@kelsey-ws.hq.ember.com> <DE269E16-0F99-493B-A19D-6AAD50B140FE@sensinode.com> <05C6A38D732F1144A8C4016BA4416BFE02E4A8DC@SPO-EXVS-02.itron.com><4C07D108.3040509@sensinode.com> <4C07DA41.8030202@stpeter.im> <05C6A38D732F1144A8C4016BA4416BFE02E4A976@SPO-EXVS-02.itron.com> <4C07DC00.1030002@stpeter.im>
In-Reply-To: <4C07DC00.1030002@stpeter.im>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms070201080105060509050008"
Subject: Re: [core] Subscribe/Notify for CoAP
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 16:54:39 -0000

On 6/3/10 10:44 AM, Peter Saint-Andre wrote:
> On 6/3/10 10:41 AM, Stuber, Michael wrote:
>> CoAp specific.  My point is that a single CoAp specific method could
>> be mapped to wide variety of HTTP mechanisms if desired. 
> 
> So, to clarify, will we use:
> 
> 1. CoAp-specific methods for everything.
> 
> Or:
> 
> 2. CoAp-specific methods only for sub/notify, and HTTP for everything else.

Never mind, I hadn't revisited draft-shelby-core-coap in a while and
forgot that we were doing CoAp-specific methods for everything.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

v2.23.0 | Report a Bug | By Email