[core] draft-ietf-core-coap-pubsub-00

Jim Schaad <ietf@augustcellars.com> Mon, 12 December 2016 08:18 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 921A0126579 for <core@ietfa.amsl.com>; Mon, 12 Dec 2016 00:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.797
X-Spam-Level:
X-Spam-Status: No, score=-4.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 xoqBtVhuH5AQ for <core@ietfa.amsl.com>; Mon, 12 Dec 2016 00:18:56 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9935D127078 for <core@ietf.org>; Mon, 12 Dec 2016 00:18:55 -0800 (PST)
Received: from hebrews (24.21.96.37) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 12 Dec 2016 00:38:26 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: draft-ietf-core-coap-pubsub@tools.ietf.org
Date: Mon, 12 Dec 2016 00:18:42 -0800
Message-ID: <0d0901d25450$5b138b10$113aa130$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdJUPCxvBes3tabDSouiE7QbNuhEDw==
Content-Language: en-us
X-Originating-IP: [24.21.96.37]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ypaFeeT-wU-O7xFm0RbOeU-3Mys>
Cc: core@ietf.org
Subject: [core] draft-ietf-core-coap-pubsub-00
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 12 Dec 2016 08:18:57 -0000

I have some questions on this draft.

1.  I do not understand the correct use of the Max-Age option during the
CREATE operation.  
     * Is a CREATE considered to be equivalent to a publish operation?
     * Is the first publish all that is needed or is this related to the
time since the last publish?
     * The last sentence in the first paragraph is really causing me
problems because it seems to imply that the time is both reset on "publish"
and has interesting properties as it only talks about create and not about
publishing in the tree.

2.  For CREATE - is the URI-Reference in the link value restricted in any
way or is the full set of values from RFC 6690 allowed?  Use of a full URI
would be bad news, however would "<mainTopic/subtopic>" be permitted.

3. For PUBLISH - if no content-type was specified on creation, can one be
specified at the time of publish or must it be absent?

4. For REMOVE - What is the correct behavior if a node with children is
removed?  Is this recursive or is it a failure?

5. For DISCOVER - Should the link relation rt="core.ps" be used only for the
root of the pubsub tree or for all nodes which allow a create to be done?

Jim