Re: [Id-event] SecEvent WG last calls

Dick Hardt <dick.hardt@gmail.com> Wed, 09 October 2019 14:46 UTC

Return-Path: <dick.hardt@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 F008212010E for <id-event@ietfa.amsl.com>; Wed, 9 Oct 2019 07:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 aK2nce2U8FXF for <id-event@ietfa.amsl.com>; Wed, 9 Oct 2019 07:46:26 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 C35471200E0 for <id-event@ietf.org>; Wed, 9 Oct 2019 07:46:25 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id b20so2789152ljj.5 for <id-event@ietf.org>; Wed, 09 Oct 2019 07:46:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5IdCjPHcY6Xm4GrpCYzEGj+lamIzGYiBcZd1HxQuHMU=; b=jaVEaqkh5owzhbcXfHhSUY7xZGrVOuVNIUD/Bcc9+e8eOO0sWrbXAR6laF2eeN8xSp QIgsPf3dFVr4fnZ+DYsiIgYK2dlgqlCu7L/Qypl7EQ+xLANNBdZBym7KbIz7NgoGQ7gw 4wrjOmqpqChQhKH3t7NFJsLTwAOYVUAPCLK/JgIlNhBv9NQ9jPLGizOUkBJvdFcLdAxE KmXcPpEyDbLCOjuSjC8uJ4dhQv59+sQoyXMqHsgeD8mxlBtW0GX7CF6RWsdo9C5HZ8cG avb1rZSIZ6bbmGJrcrmSaTGdYMHCbaUFXBSXFv8szDeB5SnJE9okRbOExxPtM2dRPx2b YY5w==
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=5IdCjPHcY6Xm4GrpCYzEGj+lamIzGYiBcZd1HxQuHMU=; b=VRobQEN+Re/PlS5sOZMMiuO6Q3yIjuJfkmoImcNfUCoRcRBLDP2c27BzpWU/rck4/V ECTBKefSumY7W2Q9bNUttnf6J4j9UPZAju/pF6f02b5blsPUD5uCu41kkRpzbfR6alDp 4c4yP7TcCNnNhgDDGOksSVRQviUV+zUnYtdFuyAzQ4urVwee4t380yVRx3YIgN9Tu4H+ 1eTLyVOk4GGH6HNLe81UCFIQJB5FGW2suZHLTNPERS0X7D5x3ljU8J+Lplq6ozftvY6M HB8NiTovM8JK4gDYQASyedf8wpcOCSrw0JHKOJ+7mAwFZCXOPyCxvy7ubTGogDBoCkYI OsiA==
X-Gm-Message-State: APjAAAWNsgCPL/5XXAoE5nS2s9mQ+9PR/HZ5246mkNt2IJRfUOBFSQI2 KSjRYhqwNXVSMDMiHY+wLkxzQD0Zl7JhihtdaUc=
X-Google-Smtp-Source: APXvYqz43mwa3uRE4c0yXzUebSCiHkt7QypcJlYfw6+GcQXlALQ6bZKdsB+SQon2fGm4FMBMkxZMcVG42cNTm0llunw=
X-Received: by 2002:a2e:658f:: with SMTP id e15mr2643253ljf.254.1570632383681; Wed, 09 Oct 2019 07:46:23 -0700 (PDT)
MIME-Version: 1.0
References: <LO2P265MB06394AFC2DCE83E2533DA44BA9BA0@LO2P265MB0639.GBRP265.PROD.OUTLOOK.COM> <CABpvcNuVeRSitfrVMw4DATJUF5aN0AsGGRL+SyU+Kd++M3tkRQ@mail.gmail.com> <284098F9-B975-439F-8037-6E41375AEDC6@amazon.com> <FD2A8D21-7B6D-4293-A9C4-9D10987679D9@gmail.com> <BYAPR00MB05673EFD0324BA5939DBFA75F59A0@BYAPR00MB0567.namprd00.prod.outlook.com> <CAOJhRMY9dNPBiAcuD1-TMWwXfqBtT2qYn+ma3wTE+Du2b54HgA@mail.gmail.com>
In-Reply-To: <CAOJhRMY9dNPBiAcuD1-TMWwXfqBtT2qYn+ma3wTE+Du2b54HgA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Wed, 09 Oct 2019 07:46:12 -0700
Message-ID: <CAD9ie-vFRprxBPg=aHW8iOSqTirPw+zhcB-3Wg03zWZUu1brzA@mail.gmail.com>
To: Adam Dawes <adawes=40google.com@dmarc.ietf.org>
Cc: Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org>, Yaron Sheffer <yaronf.ietf@gmail.com>, "Richard Backman, Annabelle" <richanna@amazon.com>, Marius Scurtescu <marius.scurtescu=40coinbase.com@dmarc.ietf.org>, "id-event@ietf.org" <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004d5a5405947b596c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/nvJZkDcqJzfZJlfojh58O32EAQ8>
Subject: Re: [Id-event] SecEvent WG last calls
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, 09 Oct 2019 14:46:30 -0000

Yaron and I appreciate the value of the subject identifier work, but that
has not been reflected by the working group.

Only a small minority of those that attend the in-person WG meetings
responded to the subject identifiers draft WG LC, and none of those
responses provided feedback on the draft, which has us question how
carefully the WG reviewed the draft.

It is now October, and the WG LC was in August.

As Yaron stated previously, the chairs will work with the AD and the
authors to publish the draft outside of the WG given the lack of response
from the WG
ᐧ

On Tue, Oct 8, 2019 at 9:20 AM Adam Dawes <adawes=
40google.com@dmarc.ietf.org> wrote:

> +1
>
> Agree with Mike that subject identifier work is very important. Other
> specs like RISC need subject identifiers and it will be more useful to have
> these defined at IETF than having it defined as part of other specs.
>
> On Tue, Oct 8, 2019 at 8:39 AM Mike Jones <Michael.Jones=
> 40microsoft.com@dmarc.ietf.org> wrote:
>
>> Per my note on the WGLC thread, I would like to see the WG continue the
>> subject identifiers work until it is published as an RFC.  It’s an
>> important piece in making the SecEvents work broadly useful.  There was
>> additional interest in it expressed by those working on the new Continuous
>> Access Evaluation Protocol (CAEP) last week during IIW.  That will be a new
>> use case for the document.
>>
>>
>>
>> I would also advocate keeping the working group open until all the
>> working group drafts have been published as RFCs.
>>
>>
>>
>>                                                        -- Mike
>>
>>
>>
>> *From:* Id-event <id-event-bounces@ietf.org> *On Behalf Of *Yaron Sheffer
>> *Sent:* Sunday, October 6, 2019 8:22 AM
>> *To:* Richard Backman, Annabelle <richanna@amazon.com
>> <richanna@amazon..com>>; Marius Scurtescu <marius.scurtescu=
>> 40coinbase.com@dmarc.ietf.org>
>> *Cc:* id-event@ietf.org
>> *Subject:* Re: [Id-event] SecEvent WG last calls
>>
>>
>>
>> Hi Marius, Annabelle,
>>
>>
>>
>> Once we have published the Poll document, the WG would have achieved its
>> goal of standardizing a format and protocol(s) for event transmission. We
>> polled the group and there is no interest/energy in follow-up work, so
>> there’s no value in keeping the group open. Please note that the mailing
>> list will remain available, as is common at the IETF for closed working
>> groups.
>>
>>
>>
>> We are not closing the WG immediately. We are only proposing to wrap up
>> once the Poll document has been handed to the IESG. And personally I can be
>> convinced to delay closure until the docs have gone through IETF last call
>> and IESG review.
>>
>>
>>
>> Thanks,
>>
>>                 Yaron
>>
>>
>>
>> *From: *"Richard Backman, Annabelle" <richanna@amazon.com>
>> *Date: *Tuesday, 1 October 2019 at 19:00
>> *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>
>> *Subject: *Re: [Id-event] SecEvent WG last calls
>>
>>
>>
>> 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>
>> 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
>> https://www.ietf.org/mailman/listinfo/id-event
>> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fid-event&data=02%7C01%7CMichael.Jones%40microsoft.com%7Cde1c4971c1c54ec178a808d74a70fed6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C637059721485078910&sdata=foD7S5LUPas3lRJG2YZg%2F%2FZYHU%2F%2Bp1EHWdkZPRPy2oM%3D&reserved=0>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>