Re: [dispatch] Potential incoming work: web push for IMAP, CalDAV and CardDAV

Michael Toomim <toomim@gmail.com> Wed, 23 October 2019 21:22 UTC

Return-Path: <toomim@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CC81200EF for <dispatch@ietfa.amsl.com>; Wed, 23 Oct 2019 14:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 KBrMTtJ_uH27 for <dispatch@ietfa.amsl.com>; Wed, 23 Oct 2019 14:22:21 -0700 (PDT)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 55CEE1200A4 for <dispatch@ietf.org>; Wed, 23 Oct 2019 14:22:21 -0700 (PDT)
Received: by mail-pf1-x42a.google.com with SMTP id b128so13729681pfa.1 for <dispatch@ietf.org>; Wed, 23 Oct 2019 14:22:21 -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=9OG4QRNlPvvosjPfFmyDd8uYPQ5ZeO/0PeaGtOxl2po=; b=OASBqhzdCeiPxcu/HmKatG3XeKSPVtWm2P/Q/Fr/lkMYRndwLc3sWeTmNHYXUSrNuB kC5gPP0pDVhi9O5GWz3NGhEtrGDXqbQvvruAy++QDqUK0tZRaz0jUqdk7IDBNT4oEUi7 ctSZJwR14BlPPqO1JA0dZTXG37sA5h2yed6zfDfdJYZout5wv8ZG2q4MOdeqPJtfxIsU oDjuwWfsRi48zBYpeQ5yb8m1oDokb3o8RJ4ukUE/zNiOBBQB2QgXkF2z1EjKifR2uYl+ U9HDBGJCxXzdLqXWF85t5GUXz3n2N/wKqktlbZr/BXWwRu4zeXer8A8NZA+82ArdsavA G67w==
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=9OG4QRNlPvvosjPfFmyDd8uYPQ5ZeO/0PeaGtOxl2po=; b=K+ro8wgKWrmdrHaWkZI4tV6pxxr9jF6T/2nASWJGmOnoxD9SLMj/tznTmp6zC8XVxl CtikCncTfgABSCH9a5bV6gu1FRZdWayKWUxU/3f0x5P/kcddjEVRgQZt6O/ixsUT+BPw bpixyENgCzwuSqf9IkY+YG66Owo/L7TI7FNsf9p0743MgLHMCLtI7VaL1GXG5PdOejtq nc1SkinUDOAFFEEovyEE5pxZtksvGDiBPKrjqXVgLjrEUaAh0IJ826z6n78YHoWG0nSE cvg2bgsmuD3V+yMrLlB9eG4b+zxJxQVyahTgW2z4n115wvtuHBRX5nv2OJEkCXu96+Hw EB2A==
X-Gm-Message-State: APjAAAXX1IaXiHF8xDGAPtLyE8VwWj61JxXCs32n8fc5AZT+kGKrky5Z TCLR61NPuFZiC+sqhAI72OE=
X-Google-Smtp-Source: APXvYqxV2NAmV/Pl6u1Maw8CTy3PpFuZtF/n06HcH38PokdGN7MpaRlA1o2JapvQzw4IM/V8nq8gmQ==
X-Received: by 2002:a63:68c8:: with SMTP id d191mr12016505pgc.197.1571865740750; Wed, 23 Oct 2019 14:22:20 -0700 (PDT)
Received: from [192.168.42.3] (135-180-2-130.static.sonic.net. [135.180.2.130]) by smtp.gmail.com with ESMTPSA id r30sm25093116pfl.42.2019.10.23.14.22.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 23 Oct 2019 14:22:20 -0700 (PDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Michael Toomim <toomim@gmail.com>
In-Reply-To: <839ea4e5-db2d-8220-6058-93869a29c185@gmx.de>
Date: Wed, 23 Oct 2019 14:22:19 -0700
Cc: Bron Gondwana <brong@fastmailteam.com>, dispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <82F33D05-D8BC-4F69-A198-677773F3427C@gmail.com>
References: <290514e7-79ce-4852-bf05-a684e2e8d045@beta.fastmail.com> <DFC3797D-DA12-4470-9CBE-D7BD981DB6CE@gmail.com> <839ea4e5-db2d-8220-6058-93869a29c185@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/CPxLDt0sKOJowlKcA544xuMuCzs>
Subject: Re: [dispatch] Potential incoming work: web push for IMAP, CalDAV and CardDAV
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2019 21:22:23 -0000

Julian:
> Mike:
>> The current design allows clients to specify a "Subscribe" header in the
>> GET request, which tells the server to keep the connection open and
>> stream all updates to the resource, as they happen.
> 
> Why would you need a new header field for that?

The header is just one way to do it.  What we *need* is some way for the client to signal to the server that it wants to subscribe to changes.  Right now, a header on GET seems to be the most elegant way to signal that.