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

Phil Hunt <phil.hunt@oracle.com> Mon, 25 February 2019 21:30 UTC

Return-Path: <phil.hunt@oracle.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 448E9131090 for <id-event@ietfa.amsl.com>; Mon, 25 Feb 2019 13:30:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=oracle.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 sXBXUjijhRHQ for <id-event@ietfa.amsl.com>; Mon, 25 Feb 2019 13:30:19 -0800 (PST)
Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82CB41279E6 for <id-event@ietf.org>; Mon, 25 Feb 2019 13:30:19 -0800 (PST)
Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x1PLOTAe118616; Mon, 25 Feb 2019 21:30:16 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=corp-2018-07-02; bh=P/49t6E5fPy9dw3RDTTBowFY4saM5JCwIebmpEFG2k0=; b=GDwQXx6ShP81PpLLKQt9fVOAvKuwXa9it1ipZ3TKfsM1itXC44Kf/p3BCoioDiy9lSyu Fhe9ZG815z/LTAyxP1I1SxAfZvbxnkuDrCzCt6QoYKKPGkVF6FQEQ6uUEmR5bnV+M/Ms T1kltcRTZmNdBi5jEFy9N1zQfJ1YFCh2AsgWgQThOZQiG1VWDL6Wr84C+Yvxr3bldc7b FPzpZ1C+C86ar+H2GaBQ3++e1IVbtNeDaDst8WT/6li7waOH1g6EPLF9ivJ50PpY+8H0 WDbFKou9ZjwcABB6k2DofFgPsEVOMUR8Do2XAUdBe7Scefh1qngs2V/kXhdkfF84ENn4 cw==
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp2130.oracle.com with ESMTP id 2qtupe0yyq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 25 Feb 2019 21:30:15 +0000
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id x1PLUEfw008661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 25 Feb 2019 21:30:14 GMT
Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id x1PLUCi9011717; Mon, 25 Feb 2019 21:30:12 GMT
Received: from dhcp-10-65-173-200.vpn.oracle.com (/10.65.173.200) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 25 Feb 2019 13:30:11 -0800
From: Phil Hunt <phil.hunt@oracle.com>
Message-Id: <EBEB0245-A4F0-448B-AB71-B4B3B962163D@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D2021FC4-E5ED-4454-992E-470EE1AB1D1F"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 25 Feb 2019 13:30:04 -0800
In-Reply-To: <41cdc155-6637-170b-e9f5-b31e624f7783@gmail.com>
Cc: "Richard Backman, Annabelle" <richanna@amazon.com>, SecEvent <id-event@ietf.org>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
References: <7cfedb70-a999-ad63-efd0-56a178adde97@gmail.com> <05D942B6-1F1C-4205-B0E9-5AF6B37D551B@amazon.com> <41cdc155-6637-170b-e9f5-b31e624f7783@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9178 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1902250152
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/C02agWVKhx0fy309AFK9VwiRcVE>
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 21:30:22 -0000

It might be time to look at current popular streaming systems such as Kafka. If the group wants to write a new spec, then identify what problem is to be solved that hasn’t already been addressed in the market.

Phil Hunt | Cloud Security and Identity Architect
Oracle Corporation, Oracle Cloud Infrastructure
@independentid
www.independentid.com
phil.hunt@oracle.com






> On Feb 25, 2019, at 12:24 PM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
> 
> 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
> 
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_id-2Devent&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=IhopAP-6tWoTdeVj-i6_kC7N053G_eaQJ7OEZGpoNmc&s=Nu5StUuDomBOpZIwbF7bpUS3djwgeBfySnVPbWZdNdE&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_id-2Devent&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=IhopAP-6tWoTdeVj-i6_kC7N053G_eaQJ7OEZGpoNmc&s=Nu5StUuDomBOpZIwbF7bpUS3djwgeBfySnVPbWZdNdE&e=>