IETF Logo Mail Archive

Re: [core] Review of draft-ietf-core-coap-pubsub-06

Carsten Bormann <cabo@tzi.org> Wed, 23 January 2019 12:53 UTC

Return-Path: <cabo@tzi.org>
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 1879612DF71; Wed, 23 Jan 2019 04:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 vP8JhajK0E-e; Wed, 23 Jan 2019 04:53:13 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AAEC1228B7; Wed, 23 Jan 2019 04:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x0NCr1UY027303; Wed, 23 Jan 2019 13:53:06 +0100 (CET)
Received: from [192.168.217.106] (p54A6CC50.dip0.t-ipconnect.de [84.166.204.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 43l4vd1LBpz1Br6; Wed, 23 Jan 2019 13:53:01 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <011001d4a87a$76f82f40$64e88dc0$@augustcellars.com>
Date: Wed, 23 Jan 2019 13:53:00 +0100
Cc: draft-ietf-core-coap-pubsub@ietf.org, core@ietf.org
X-Mao-Original-Outgoing-Id: 569940778.420697-c5c321750e5e0698819a657a5a7852f6
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AB0F836-C3A1-4522-A3A8-81DE9943F3A9@tzi.org>
References: <011001d4a87a$76f82f40$64e88dc0$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/adXsazhnxJnGlp0NuEjuBRgjpKk>
Subject: Re: [core] Review of draft-ietf-core-coap-pubsub-06
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Jan 2019 12:53:15 -0000

On Jan 10, 2019, at 01:21, Jim Schaad <ietf@augustcellars.com> wrote:
> 
> 11. Section 4.3 - Am I correct in assuming that max-age defaults to 60
> seconds for a publish operation?  There is a different default value
> specified for CREATE but not here.  Another possible default value would
> have been the topic lifetime.

The default value for Max-Age is defined in RFC 7252 and cannot be altered here.

E.g., the sentence

   Broker SHOULD retain a
   topic indefinitely if the Max-Age option is elided or is set to zero
   upon topic creation. 

is broken as, if the option is elided, its value is 60.  Or, in other words, every CoAP message has a max-age, which is 60 (seconds) unless specified explicitly.

Also, using zero as indefinite value is very odd.  (Zero usually means “don’t cache”.)

Thank you for the review, Jim!

See you all in three hours (and, yes, the chairs are hammering together an agenda as I speak…)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email