Re: [T2TRG] [core] OCF Observe on special interfaces, design question, RFC requirements?

Michael Koster <michaeljohnkoster@gmail.com> Wed, 10 July 2019 06:10 UTC

Return-Path: <michaeljohnkoster@gmail.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B01F12010E for <t2trg@ietfa.amsl.com>; Tue, 9 Jul 2019 23:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level:
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XJEmMoScJO42 for <t2trg@ietfa.amsl.com>; Tue, 9 Jul 2019 23:10:51 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E6771200DB for <t2trg@irtf.org>; Tue, 9 Jul 2019 23:10:51 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id l21so691080pgm.3 for <t2trg@irtf.org>; Tue, 09 Jul 2019 23:10:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QGYAbE5CPM3fRDX0VOKJAPv0S1wSDLfzD96qyqsnY2s=; b=MCal0yL5CzCXN2kLa+NdbQXGWT8yEqKZHfWc6e0KKSfsSyq7nywrB7P2vNc9ZChp60 vWbVEuTXTn7yPagmgVvzxdYascYBHk+ghtxsDMkehgzuR+y3FcOeyF1YuAGSAC9k9ybr 0mdQwLrofRa1oWI3kwoOq9Bm5KqkUBpJah7QkPHF8n3AhLvcYmic0oXV9fc/e5ofRxPU c+6dntrXEiR+upRmLvhLbFRKKe/Hdzu1tIHIa/ks342IZTIf4p3vRVC5x2iwvKe9wWtc /4UsFv+O4zkJhLmh1U2IKZF0o7BY5yk2Psuel8v2Ff1BCg0aApA9Qvm8aox8ipPHk2HH hnqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QGYAbE5CPM3fRDX0VOKJAPv0S1wSDLfzD96qyqsnY2s=; b=U+gbom9EmJw8x2xFZzow/I0+gZWp/VuzDaFBGHGBSGMdx7m+oJpDCnLQf1L7AD4U94 mqYp0c3kc1P9s+D8w/ChO0zhTDVWyFx0DRSFy9d84OjRlf3Wykgbom7ugzW1Rs49SlJf Flyw7FwojAH+0i5M3IUNQAPfV5nkLFHw8OqOARTCs9fPuIELLhu4c8fdh2l9wR7dnd0P VLbxGPOv8/JP2QQZtxyceeBXJHEBe5wQulxoSDa84u4XXz1uH9G6qKGEQUt5r56Mifzp F+IBlG8WWkIiNCHYjab4EkB9WzkTjWlazk5jVswt0tl3qePjKSQ4uz5Sl1TRgDq2gTBw hJog==
X-Gm-Message-State: APjAAAUonUz+J8D4Frak2kSuMUgTfvop8+o+cHACtJCmh9AuJeDzN71G T68A+q4gb+cioiP0r0xPeno=
X-Google-Smtp-Source: APXvYqx0OqSC5mkiWrocM483rPbW6RpSB4imzzsbIY+VZsq3R5K5q0iYnW/l0DmO7/JwLTm+jwzXZA==
X-Received: by 2002:a17:90a:28e4:: with SMTP id f91mr4661677pjd.99.1562739050840; Tue, 09 Jul 2019 23:10:50 -0700 (PDT)
Received: from [172.16.0.7] (c-71-202-145-92.hsd1.ca.comcast.net. [71.202.145.92]) by smtp.gmail.com with ESMTPSA id j1sm928275pfe.101.2019.07.09.23.10.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jul 2019 23:10:50 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Michael Koster <michaeljohnkoster@gmail.com>
In-Reply-To: <683B27F7-F738-4B80-A27E-B65B75EFCDA6@tzi.org>
Date: Tue, 09 Jul 2019 23:10:47 -0700
Cc: Klaus Hartke <hartke@projectcool.de>, Michael Koster <michael.koster=40smartthings.com@dmarc.ietf.org>, "t2trg@irtf.org" <t2trg@irtf.org>, core <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <571F4900-C0C7-438B-A707-562A611581CF@gmail.com>
References: <166B0435-8C96-4B83-98CB-A1D6F0838335@smartthings.com> <CAAzbHvYGVtNiw5taGMaVVRe4RuN9s2y4Y6RkJxR06Nk=w3CiTQ@mail.gmail.com> <683B27F7-F738-4B80-A27E-B65B75EFCDA6@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/1buepAXQFUhZwvHCo3YebUg8nUc>
Subject: Re: [T2TRG] [core] OCF Observe on special interfaces, design question, RFC requirements?
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2019 06:10:53 -0000

Hi Carsten,

Yes, as is, this is not guaranteed to deliver all of the updates. 

Best regards,

Michael

PS We were thinking along similar lines as STP, with the idea of subscriber queues in Pub/Sub, where each subscriber would have its own queue and cursor. Of course, one could combine the storage for elements that are common across more than one subscriber, and recover storage for items that have been consumed by all subscribers.

> On Jul 9, 2019, at 10:52 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> There is, of course, nothing wrong with observing a resource that is the “last change” of another resource.  This just doesn’t give you a reliable sequence of all changes; that requires something like the “Series Transfer Pattern”, https://tools.ietf.org/html/draft-bormann-t2trg-stp
> 
> Grüße, Carsten
> 
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg