[core] Observe Cancellation: The outcome

Carsten Bormann <cabo@tzi.org> Fri, 07 March 2014 17:08 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 459ED1A02DA for <core@ietfa.amsl.com>; Fri, 7 Mar 2014 09:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.348
X-Spam-Level:
X-Spam-Status: No, score=0.348 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 sXb6ILiiCjNq for <core@ietfa.amsl.com>; Fri, 7 Mar 2014 09:08:38 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 360E41A02D9 for <core@ietf.org>; Fri, 7 Mar 2014 09:08:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s27H8WOO024994 for <core@ietf.org>; Fri, 7 Mar 2014 18:08:32 +0100 (CET)
Received: from [10.109.74.208] (unknown [62.232.113.211]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id DD5FAF75; Fri, 7 Mar 2014 18:08:31 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Carsten Bormann <cabo@tzi.org>
Date: Fri, 07 Mar 2014 17:08:30 +0000
X-Mao-Original-Outgoing-Id: 415904910.721969-a047ab492b68ef03b7dcf8e8d1450e67
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A8F12CD-25B5-4915-A298-0AB0F6FA47F7@tzi.org>
To: "core@ietf.org WG" <core@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/core/IYAmAN7_Gd_McK5Ie8NP8BB4XeY
Subject: [core] Observe Cancellation: The outcome
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Fri, 07 Mar 2014 17:08:39 -0000

After extensive discussion both in person at IETF89 and on the mailing list the CoRE WG today met to close the issue.
Two solutions emerged as the winners in their respective class:
1) a GET that looks like an Observation renewal (i.e., carries the options and the token of the ongoing request), but has a (TBD) value of the Observe option ≠ 0, cancels the Observation relationship instead.
2) a new code (0.31 possibly was the most favored one) indicates a cancel message; the ongoing request identified by the token in the cancel message is canceled.

After some more discussion, we first checked whether there was anyone that couldn’t live with one of the solutions.
Nobody showed their hands for either solution.
(Thomas indicated that he was unhappy with both, but that wouldn’t have helped with deciding.)

So we went to a hum.  There was a strong, but not unanimous consensus for solution 1.

With respect to the value of TBD, the most basic value that is different from 0 (the vale of an empty Observe option, which we use for setting up and renewing Observation relationships) is 1.
Actually, any bits beyond the low order bit of the uint in the option should be ignored just in case we want to extend the (elective) request option later.

The successful cancellation is indicated by a GET response without an Observe option.
Any need to suppress the normal response of the GET will need to be handled by additional mechanisms such as the No-response Option.

As usual, we have to validate this result on the mailing list.  Please indicate on the mailing list any serious problems you see with this result until

	2014-03-14, 24:00 UTC

We will ship -observe-13 to the IESG on that date unless there is a major issue; that will be submitted in the next couple of days.

Grüße, Carsten