IETF Logo Mail Archive

Re: [Id-event] SecEvent WG last calls

"Richard Backman, Annabelle" <richanna@amazon.com> Tue, 01 October 2019 16:00 UTC

Return-Path: <prvs=170d1d95b=richanna@amazon.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 95DF9120A4D for <id-event@ietfa.amsl.com>; Tue, 1 Oct 2019 09:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.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 86thudPGUT1s for <id-event@ietfa.amsl.com>; Tue, 1 Oct 2019 09:00:44 -0700 (PDT)
Received: from smtp-fw-9102.amazon.com (smtp-fw-9102.amazon.com [207.171.184.29]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FD68120A18 for <id-event@ietf.org>; Tue, 1 Oct 2019 09:00:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1569945644; x=1601481644; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3o5QwCabvaAdxU5C431TGvvHRTdqyyyUjCiZxgNsAyU=; b=ZbGZ2hDe9HziTSzCNfKITU3X53lxuoT+eaAAxtPGvVU5eX3q2tBtx1Ny 13uliELnP8e0cnVhGSTzKXplNIJjW2kJKCguzu+8kg6F3vuxdpuAVX9FA 839AZlzP8lMRtijP/9OOvykxYydaUCg0zZLX56tGZ157sAlkLLWgIJvMB Q=;
X-IronPort-AV: E=Sophos;i="5.64,571,1559520000"; d="scan'208,217";a="705908054"
Received: from sea3-co-svc-lb6-vlan3.sea.amazon.com (HELO email-inbound-relay-2a-c5104f52.us-west-2.amazon.com) ([10.47.22.38]) by smtp-border-fw-out-9102.sea19.amazon.com with ESMTP; 01 Oct 2019 15:59:21 +0000
Received: from EX13MTAUWC001.ant.amazon.com (pdx4-ws-svc-p6-lb7-vlan3.pdx.amazon.com [10.170.41.166]) by email-inbound-relay-2a-c5104f52.us-west-2.amazon.com (Postfix) with ESMTPS id ED3ECA1D5A; Tue, 1 Oct 2019 15:59:05 +0000 (UTC)
Received: from EX13D11UWC004.ant.amazon.com (10.43.162.101) by EX13MTAUWC001.ant.amazon.com (10.43.162.135) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 1 Oct 2019 15:59:05 +0000
Received: from EX13D11UWC004.ant.amazon.com (10.43.162.101) by EX13D11UWC004.ant.amazon.com (10.43.162.101) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 1 Oct 2019 15:59:05 +0000
Received: from EX13D11UWC004.ant.amazon.com ([10.43.162.101]) by EX13D11UWC004.ant.amazon.com ([10.43.162.101]) with mapi id 15.00.1367.000; Tue, 1 Oct 2019 15:59:05 +0000
From: "Richard Backman, Annabelle" <richanna@amazon.com>
To: Marius Scurtescu <marius.scurtescu=40coinbase.com@dmarc.ietf.org>, Yaron Sheffer <yaronf.ietf@gmail.com>
CC: "id-event@ietf.org" <id-event@ietf.org>
Thread-Topic: [Id-event] SecEvent WG last calls
Thread-Index: AQHVZLTWMbnmjseLTUqI0Zz8VZtuN6ce0lwAgCbRLQA=
Date: Tue, 01 Oct 2019 15:59:05 +0000
Message-ID: <284098F9-B975-439F-8037-6E41375AEDC6@amazon.com>
References: <LO2P265MB06394AFC2DCE83E2533DA44BA9BA0@LO2P265MB0639.GBRP265.PROD.OUTLOOK.COM> <CABpvcNuVeRSitfrVMw4DATJUF5aN0AsGGRL+SyU+Kd++M3tkRQ@mail.gmail.com>
In-Reply-To: <CABpvcNuVeRSitfrVMw4DATJUF5aN0AsGGRL+SyU+Kd++M3tkRQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1b.0.190715
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.161.16]
Content-Type: multipart/alternative; boundary="_000_284098F9B975439F80376E41375AEDC6amazoncom_"
MIME-Version: 1.0
Precedence: Bulk
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/K_Wnh0sKLWoZ_KA6Bl_IRBfDI9E>
Subject: Re: [Id-event] SecEvent WG last calls
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Oct 2019 16:00:52 -0000

I would similarly like to understand this decision considering there are multiple documents still in flight.

--
Annabelle Richard Backman
AWS Identity


From: Id-event <id-event-bounces@ietf.org> on behalf of Marius Scurtescu <marius.scurtescu=40coinbase.com@dmarc.ietf.org>
Date: Friday, September 6, 2019 at 9:14 AM
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Cc: "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] SecEvent WG last calls

Why is the WG wrapping up?

Anything we can still do to keep Subject ID in the WG?

On Fri, Sep 6, 2019 at 6:13 AM Yaron Sheffer <yaronf.ietf@gmail.com<mailto:yaronf.ietf@gmail.com>> wrote:
We concluded last call for the Poll and the Subject ID drafts.

The working group supported publication of the Poll draft. Authors, please address the comments that were raised in the last call, republish and we will request publication.

There was insufficient support for the Subject ID draft. We are planning to wrap up the WG as soon as we push the Poll draft to the IESG, and so the chairs will work with the authors of the Subject ID draft and with the AD to publish the draft outside of the WG.

Thanks,
                Yaron

_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event

v2.23.0 | Report a Bug | By Email