IETF Logo Mail Archive

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

Marius Scurtescu <marius.scurtescu@coinbase.com> Wed, 27 February 2019 22:42 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 36E3F1311AE for <id-event@ietfa.amsl.com>; Wed, 27 Feb 2019 14:42:50 -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 nVKzv6519VB5 for <id-event@ietfa.amsl.com>; Wed, 27 Feb 2019 14:42:46 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 15EE21311AF for <id-event@ietf.org>; Wed, 27 Feb 2019 14:42:43 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id i130so8675044pgd.1 for <id-event@ietf.org>; Wed, 27 Feb 2019 14:42:43 -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=t6DMgBa+IQ+p59SKzN+rTklHoK+UZVfX3X5eQ5mjgSU=; b=fBWlitvYBTLGsFOWqjt3uL7MpmhYL1Yqemy1ppCKjY3MuDWQAwTC9u+81goDuw8Ruh AR4oX/4GL341TyDCWa1rvKAss6G41cP3WR20D+DfbK9VZKO6f+Pz8KorrNu6j4lETwdA h7tQvf6DjWXfZrUsgX2VhLRMBPfjj7eV7tMnM=
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=t6DMgBa+IQ+p59SKzN+rTklHoK+UZVfX3X5eQ5mjgSU=; b=YPSE7h0NgUM/34DHmOnr+SnCM54yiJShHX4a69pfyK8RpPZSi/J2HqNmJ4wzWgTmLD 5R4HIFzRNoen9X6xCjpXNvf/5ZjARK8L7iWGFmLcUGAC41bmDFU4LRvNCMVAgdR4sirB vqRpfluKdUlFCTRAdkC6DfiIpOjnU3bPMFzFSR3t62ZzHrqllFrz9lzbK8ThSwvIyaFC oBLig05t93oIxzex+upnKk87AmTwJafoLOcskND18/4YSL48n1hFDnOkCFWAep28/Qs1 2IsFSS+PSRW8+hYXDphjZ9u0OJAiRMmK1BRd35DQqEX1QC2ad3H5MpvPWCat2yemh/AE TEGA==
X-Gm-Message-State: AHQUAubfaSB44/9mTw1ysOKsH9ReB3he0SVbUoHav9hko9cHU+CLT6x6 ZL2FmZUaIcmSnrsQ7ac2fEltaL1E9Nh9m+0M+9Y5SQ==
X-Google-Smtp-Source: AHgI3IanZm5rqjN65J1uGxpzVvbmbyWz4oZtsMwtg4iMIiwnJwCGmyLUwdYgCPoroQ2tlqqHFr57Ot/B95N5RG543vs=
X-Received: by 2002:a65:51ca:: with SMTP id i10mr5172796pgq.371.1551307363294; Wed, 27 Feb 2019 14:42:43 -0800 (PST)
MIME-Version: 1.0
References: <7cfedb70-a999-ad63-efd0-56a178adde97@gmail.com> <CABpvcNs69NZeqXmNui6poP79R6q40WgEAT7jRkvb_vTL_Y8x=A@mail.gmail.com>
In-Reply-To: <CABpvcNs69NZeqXmNui6poP79R6q40WgEAT7jRkvb_vTL_Y8x=A@mail.gmail.com>
From: Marius Scurtescu <marius.scurtescu@coinbase.com>
Date: Wed, 27 Feb 2019 14:42:32 -0800
Message-ID: <CABpvcNuZEvjwcsZjJP9gDtReRBAmeFM41b1O7uXzD=UCSasEZw@mail.gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Cc: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000053d2510582e7e419"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/gM1FgP3-Khv0C31Rj6VXJm_UGxs>
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: Wed, 27 Feb 2019 22:42:50 -0000

Any chance for an answer from the chairs to the 3 questions below?

On Sun, Feb 24, 2019 at 4:52 PM Marius Scurtescu <
marius.scurtescu@coinbase.com> wrote:

> 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