IETF Logo Mail Archive

Re: [Id-event] Push draft: conclusion of WGLC

Marius Scurtescu <marius.scurtescu@coinbase.com> Mon, 25 February 2019 00:52 UTC

Return-Path: <marius.scurtescu@coinbase.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8138130E7F for <id-event@ietfa.amsl.com>; Sun, 24 Feb 2019 16:52:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=coinbase.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 BRkHQWPiI_bg for <id-event@ietfa.amsl.com>; Sun, 24 Feb 2019 16:52:19 -0800 (PST)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (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 3183B12DD85 for <id-event@ietf.org>; Sun, 24 Feb 2019 16:52:19 -0800 (PST)
Received: by mail-pg1-x52f.google.com with SMTP id h11so3665286pgl.0 for <id-event@ietf.org>; Sun, 24 Feb 2019 16:52:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coinbase.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zEcQkCmU0YRvpFYSz7v5sApbp6NIbqiKu/ihkwkySkU=; b=XyBRQjdLoUmFm762OC/OajjLKtPBjXMPtRfxTnPoY9RzRWeOqPRM+WqNburyIAYoSZ GFZfeeL3gdUcXa2lPJsvV5J541F1yrcP0pro+w6INkAVXTYeF4/gigBsMCAoHthzMyxk BHfVPtKb49nKNncnkQ8K2UhMLxn3iMr/mIMDE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zEcQkCmU0YRvpFYSz7v5sApbp6NIbqiKu/ihkwkySkU=; b=qphcrJZcNWQZ5Yj0gD+9MSTXkMtWGqtLdcwnzv6FzTqsoAKAXL3e2ZQIKkDMJK/Dsc OQj2Gz+PwofmE7WsmPO5kAI4dDU9yxwuwIuid/VpkfUO1uw8UCR1dH2ieMLXUPjGpID5 JdcQfrBxXz7DMBiu5Umv/bKC4gCzywWUiCe3HO3pgf58u7+FXMeYYq3OMWJdksvpUJyW BOT8fhlFdatpG6fqgbtMwWqhIVVu6FfTulWt65DEvigfgZ53QF6a44U8TIhYrhA4V7v2 kqM2ZmKfe3oQqfMPuoxwWaS3Pw64P2TODWeAmQPvOXEYpxg+/lGve3c9ZU2c0mlGcH4P jWEA==
X-Gm-Message-State: AHQUAubuDSGINhtrqSZePNtCazPheyCwpmRfntWLrmGicoL+JugGE2GE GaTou5lOxc6PsMT9btZ9Tgg5oBUYXUZBO25xqc168w==
X-Google-Smtp-Source: AHgI3IbgriFRIzaEhJzmdDS/qUOI1U8ppWlApBadSU8esO9Txy2Ifva8imMKX2LCmW8WNGbkXr+5HNYQNMn4XkNliak=
X-Received: by 2002:a63:541:: with SMTP id 62mr16313756pgf.172.1551055938378; Sun, 24 Feb 2019 16:52:18 -0800 (PST)
MIME-Version: 1.0
References: <7cfedb70-a999-ad63-efd0-56a178adde97@gmail.com>
In-Reply-To: <7cfedb70-a999-ad63-efd0-56a178adde97@gmail.com>
From: Marius Scurtescu <marius.scurtescu@coinbase.com>
Date: Sun, 24 Feb 2019 16:52:07 -0800
Message-ID: <CABpvcNs69NZeqXmNui6poP79R6q40WgEAT7jRkvb_vTL_Y8x=A@mail.gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Cc: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003c08c70582ad5a52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/aO2lAIY3-iE6yG9gMiuVMARtm_0>
Subject: Re: [Id-event] Push draft: conclusion of WGLC
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2019 00:52:22 -0000

Regrettable indeed :-(

Were the recent official launches by Adobe and Google taken into
consideration?

Is it possible to consult the AD for options?

Did we consider the implications for the whole working group?

While the group is indeed at a low point of activity, a lot of work went
into this draft and it is central for real life implementations.




On Sun, Feb 17, 2019 at 6:43 AM Yaron Sheffer <yaronf.ietf@gmail.com> wrote:

> Dear working group,
>
> We issued a 2-week second last call for draft-ietf-secevent-http-push-04
> on Jan. 24, and extended it by a further week, which expired on Friday. We
> had to issue a second last call because of lack of response to the first
> last call which took place in November/December.
>
> The results were better in the second try (2 non-authors in support, and 1
> not clearly supporting publication) but not enough in our mind to push the
> document forward.
>
> This means that we will not be publishing the Push protocol as a working
> group document. The authors are welcome to publish it through other
> channels, as an AD-sposored RFC or through the ISE.
>
> We regret that we have reached this impasse, but clearly there is too
> little energy within the working group. We thank the authors for the
> significant effort that they put into this document, and thank the working
> group members who reviewed it.
>
> Regards,
>
>     Dick and Yaron
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>

v2.23.0 | Report a Bug | By Email