IETF Logo Mail Archive

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

Mike Jones <Michael.Jones@microsoft.com> Mon, 25 February 2019 20:21 UTC

Return-Path: <Michael.Jones@microsoft.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 35D9C130F85 for <id-event@ietfa.amsl.com>; Mon, 25 Feb 2019 12:21:03 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 KjcbazxplEDa for <id-event@ietfa.amsl.com>; Mon, 25 Feb 2019 12:21:00 -0800 (PST)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650107.outbound.protection.outlook.com [40.107.65.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24ECD130F8B for <id-event@ietf.org>; Mon, 25 Feb 2019 12:20:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4iWfXTnfNfkKfJYZXgv9yZpoIPZnBId1I1e5pd5xXdg=; b=dQZkQuwXS08RvAWP0kXZCcbvxAYMboXfFCCJcDtM10Zk2nYt1AVh95mjEOTJc/YAaqoj1mKFYeXiVWa69BWhC5GuoKfJNZIVgEqsB+Qhronq2svf7SM1z28iPZoZU+0CiZMuI+EWDwSx0en97dy17N9wiopa93TpTYJGsdYDL7M=
Received: from BL0PR00MB0292.namprd00.prod.outlook.com (52.132.19.158) by BL0PR00MB0338.namprd00.prod.outlook.com (52.132.20.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1699.0; Mon, 25 Feb 2019 20:20:57 +0000
Received: from BL0PR00MB0292.namprd00.prod.outlook.com ([fe80::d4e5:d345:a6ac:ab9b]) by BL0PR00MB0292.namprd00.prod.outlook.com ([fe80::d4e5:d345:a6ac:ab9b%5]) with mapi id 15.20.1697.000; Mon, 25 Feb 2019 20:20:57 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Richard Backman, Annabelle" <richanna=40amazon.com@dmarc.ietf.org>, Yaron Sheffer <yaronf.ietf@gmail.com>, SecEvent <id-event@ietf.org>
Thread-Topic: [Id-event] Push draft: conclusion of WGLC
Thread-Index: AQHUxs8bqHR71Euy40us3VTFa48mAqXw7UsAgAATwaA=
Date: Mon, 25 Feb 2019 20:20:57 +0000
Message-ID: <BL0PR00MB0292981A3127F5C890DFFF7EF57A0@BL0PR00MB0292.namprd00.prod.outlook.com>
References: <7cfedb70-a999-ad63-efd0-56a178adde97@gmail.com> <05D942B6-1F1C-4205-B0E9-5AF6B37D551B@amazon.com>
In-Reply-To: <05D942B6-1F1C-4205-B0E9-5AF6B37D551B@amazon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=mbj@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-02-25T20:20:55.4448813Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=67bd96a0-398e-4c77-ab67-02874ddc242f; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic
x-originating-ip: [2001:4898:80e8:1:48fd:c7b5:1d51:1bfd]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f07a2e56-012e-496b-518c-08d69b5ec073
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600126)(711020)(4605104)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BL0PR00MB0338;
x-ms-traffictypediagnostic: BL0PR00MB0338:
x-microsoft-antispam-prvs: <BL0PR00MB0338A716B057F6990511E637F57A0@BL0PR00MB0338.namprd00.prod.outlook.com>
x-forefront-prvs: 095972DF2F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(376002)(396003)(346002)(366004)(199004)(189003)(6246003)(186003)(14444005)(72206003)(5660300002)(86612001)(14454004)(74316002)(6436002)(46003)(68736007)(8676002)(86362001)(256004)(6506007)(53546011)(316002)(478600001)(790700001)(71200400001)(8990500004)(52536013)(2906002)(71190400001)(6116002)(33656002)(99286004)(102836004)(54896002)(6306002)(236005)(9686003)(81156014)(76176011)(55016002)(229853002)(7736002)(6346003)(110136005)(10090500001)(7696005)(476003)(22452003)(97736004)(53936002)(25786009)(105586002)(486006)(446003)(8936002)(11346002)(10290500003)(81166006)(106356001); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR00MB0338; H:BL0PR00MB0292.namprd00.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5UC3Iyr1DjqLvFVww+TMh3XGyRhzf4DnQ9xUFuJss+mb0H6to6vT1Cp8Q0IBkWsYjSjhWh7eiglyqn7Q9FbW+j7eX4xBVRLQdve/zJuvmIEIs4nE9YSQEkwMMUYAanv2J5kX2Elq0VpUPpAs8o5lDnqWd4nbzN+/a+TNrLYEizI/VMZS9095mTxV5KCEpU3+myfKCQOsrWnjRb09CUWvZoHAdZzuouA+CHtPOsYn3cxeLao2LSZ2rbuscbyG3zHyLrKq8Qt6X+E52XedwN98YWnRIvSTNnU5V1lCrV4EaqHUd1qnh33XuEbOdVttA6Ppv8NlIeXzG0uknZ2bmbASTxgjNnHqfj7sKQBvUC+RmnZ4KVtEkjYfBUdi90RXuwA0zXn95Qtllrgy2K3kpUetlXQBep40M21sL2xJWNUlEl0=
Content-Type: multipart/alternative; boundary="_000_BL0PR00MB0292981A3127F5C890DFFF7EF57A0BL0PR00MB0292namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f07a2e56-012e-496b-518c-08d69b5ec073
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Feb 2019 20:20:57.5339 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR00MB0338
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/B-PhOJCsSTU5zhJrqsCuqddDhIA>
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:21:03 -0000

It’s my hope that this will serve as a wake-up call to the working group that they need to participate if they want this and the poll spec to become standards.  Indeed, I hope that many additional reviews are forthcoming before our meeting in Prague and the decision to not proceed can be reversed on that basis.

Note that this is problematic for the poll spec as well, given its normative dependencies on the push spec.

                                                                -- Mike

From: Id-event <id-event-bounces@ietf.org> On Behalf Of Richard Backman, Annabelle
Sent: Monday, February 25, 2019 11:08 AM
To: Yaron Sheffer <yaronf.ietf@gmail.com>; SecEvent <id-event@ietf.org>
Subject: Re: [Id-event] Push draft: conclusion of WGLC

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<mailto:id-event-bounces@ietf.org>> on behalf of Yaron Sheffer <yaronf.ietf@gmail.com<mailto:yaronf.ietf@gmail.com>>
Date: Sunday, February 17, 2019 at 6:43 AM
To: SecEvent <id-event@ietf.org<mailto: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

v2.23.0 | Report a Bug | By Email