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

Yaron Sheffer <yaronf.ietf@gmail.com> Mon, 25 February 2019 20:24 UTC

Return-Path: <yaronf.ietf@gmail.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 6C955130FBF for <id-event@ietfa.amsl.com>; Mon, 25 Feb 2019 12:24:37 -0800 (PST)
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_PASS=-0.001, URIBL_BLOCKED=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 5SosVteSpV-M for <id-event@ietfa.amsl.com>; Mon, 25 Feb 2019 12:24:35 -0800 (PST)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 613D2130FB8 for <id-event@ietf.org>; Mon, 25 Feb 2019 12:24:35 -0800 (PST)
Received: by mail-wr1-x42c.google.com with SMTP id d17so11383421wre.10 for <id-event@ietf.org>; Mon, 25 Feb 2019 12:24:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=5DVGe2aP9V8LO04s4+PbcTUYeSJB0EghtNh3blsANxw=; b=aw6Fw65gYp0yIshdSjdvHDq+RN6ctwN9O97asUYXhCBv10J2p9R8IQySijqfdDRsxb 0lUnzPGaJzdL2dEl1KkXPXNlmyQrhk0NdTq0+hS0GwwtBkAVHqFeobheN8ugx1LYbV8c oMlIGIWZhF+wIXwF5XvJDOzLqtZd1UeTCmk2jBTPN2ma2DAJ7ypiOGw/ZeGJDagb0WUY 4+pldFTSsQZb4xcee4VTy7JhSAAEzPiS84KiB62Zo7cr3cP8x26uajGFPo+7yw3JV9N9 rdxhajppKHdPrbujXzxD2YHyvLELwMelwSi7sLIJmxceNtLuL5RI1xPgJ2BvEF5aWE50 l7IQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=5DVGe2aP9V8LO04s4+PbcTUYeSJB0EghtNh3blsANxw=; b=oIxVhgm/9ZZ1glDxSblQszCk6W8CUMaoXgsS9zonhbhgHvLdLIAKgdezB/tbo4T5aT tsy2uNCnt9itktbHM5nSTBFn5tkMbIFwApMkd4APnHX3NmKxpx+MJ/KVsz1pHiZ9S6at hJ8KU41N2YU9a0VuN6JKVRdW0/9pmLbp8PM0rrQGdDUPx3O4V4xxyY/3VLQQ/H1QaZ4q naHpqnlFBQriEdjoNgL88ovR62/qjnwQa/eIHIYof85wKZy/DPiTuuIufeV3Iqqt+6AA UWfyF42UD4KCGZMmOsprlmK75xpyMKd2qK+WjULuHvGCIcf6hk4mIoT8eimLHJGpMmbp i9Og==
X-Gm-Message-State: AHQUAua1s2stOO+JyM/my3J6sTV4EcYR8oLy6NLdjAjqHfH5YWaKJ0ux 32Wgv0QkDr/uguKTN4RpSgnizsCv
X-Google-Smtp-Source: AHgI3IYMtPAQPzSoJimN3y1fU8BYrau4gpbJ8rgFHOgmEmzHi5xS97P9VcG9xVUijHIsImGT9+cxdw==
X-Received: by 2002:a5d:55c5:: with SMTP id i5mr15080823wrw.245.1551126273594; Mon, 25 Feb 2019 12:24:33 -0800 (PST)
Received: from [10.0.0.151] (bzq-109-65-41-191.red.bezeqint.net. [109.65.41.191]) by smtp.gmail.com with ESMTPSA id w4sm17267516wrk.85.2019.02.25.12.24.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Feb 2019 12:24:32 -0800 (PST)
To: "Richard Backman, Annabelle" <richanna@amazon.com>, SecEvent <id-event@ietf.org>
References: <7cfedb70-a999-ad63-efd0-56a178adde97@gmail.com> <05D942B6-1F1C-4205-B0E9-5AF6B37D551B@amazon.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <41cdc155-6637-170b-e9f5-b31e624f7783@gmail.com>
Date: Mon, 25 Feb 2019 22:24:29 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <05D942B6-1F1C-4205-B0E9-5AF6B37D551B@amazon.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/voLnQSB7A7h3qpHFm8Pthjhn25w>
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 20:24:37 -0000

The latter: the working group is dropping HTTP Push as a topic.

Thanks,
	Yaron

On 25/02/2019 21:08, Richard Backman, Annabelle wrote:
> Yaron,
> 
> Forgive my unfamiliarity with IETF process, but could you explain what 
> this decision by the chairs means? Does this mean the document will not 
> be advanced along the standards track, but will remain as a WG draft? Or 
> does this mean the secevent WG is effectively dropping HTTP push 
> delivery as a topic that it is working on?
> 
> -- 
> 
> Annabelle Richard Backman
> 
> AWS Identity
> 
> *From: *Id-event <id-event-bounces@ietf.org> on behalf of Yaron Sheffer 
> <yaronf.ietf@gmail.com>
> *Date: *Sunday, February 17, 2019 at 6:43 AM
> *To: *SecEvent <id-event@ietf.org>
> *Subject: *[Id-event] Push draft: conclusion of WGLC
> 
> 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
>