[Openid-specs-risc] FW: [Id-event] subject-identifers WG interest (Was: Closing the SecEvent working group)
Stan Bounev
stanb at vericlouds.com
Thu Jul 30 18:04:53 UTC 2020
Annabelle, I need to create a pull request against Atul’s branch (or fork after he forks, per your request). In this case, is the best practice to fork or branch Atul’s repo - https://bitbucket.org/openid/risc/branch/Atul-Tulshibagwale/first-draft-of-sse-profile-spec-1593802798993?
Stan
From: Openid-specs-risc <openid-specs-risc-bounces at lists.openid.net> on behalf of "Richard Backman, Annabelle via Openid-specs-risc" <openid-specs-risc at lists.openid.net>
Reply-To: "Richard Backman, Annabelle" <richanna at amazon.com>
Date: Tuesday, July 21, 2020 at 11:23 AM
To: Atul Tulshibagwale <atultulshi at google.com>
Cc: "openid-specs-risc at lists.openid.net" <openid-specs-risc at lists.openid.net>
Subject: Re: [Openid-specs-risc] FW: [Id-event] subject-identifers WG interest (Was: Closing the SecEvent working group)
Looks like you’re trying to create the pull request from my repo. You need to create your own fork of the repo and create a pull request from there.
–
Annabelle Backman (she/her)
AWS Identity
https://aws.amazon.com/identity/
From: Atul Tulshibagwale <atultulshi at google.com>
Date: Sunday, July 12, 2020 at 5:54 PM
To: "Richard Backman, Annabelle" <richanna at amazon.com>
Cc: Mike Jones <Michael.Jones at microsoft.com>, Openid-specs-risc <openid-specs-risc at lists.openid.net>
Subject: RE: [EXTERNAL] FW: [Id-event] subject-identifers WG interest (Was: Closing the SecEvent working group)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Hi Annabelle,
Can you please give me (username: atultulshi) permission to create the pull request? I'm ready with the changes, but cannot create the pull request because it gives me the error:
remote: Permission to richanna/secevent.git denied to atultulshi.
fatal: unable to access 'https://github.com/richanna/secevent.git/': The requested URL returned error: 403
Thanks,
Atul
On Mon, Jul 6, 2020 at 3:36 PM Richard Backman, Annabelle <richanna at amazon.com<mailto:richanna at amazon.com>> wrote:
Yes, that is the correct repository. I’d like to have some discussion within the secevent WG (presuming it continues to exist) on the “category” property, as it’s not clear to me what it is intended to represent or what problem it is trying to solve.
–
Annabelle Backman (she/her)
AWS Identity
https://aws.amazon.com/identity/
From: Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>>
Date: Monday, July 6, 2020 at 1:54 PM
To: Atul Tulshibagwale <atultulshi at google.com<mailto:atultulshi at google.com>>, "Richard Backman, Annabelle" <richanna at amazon.com<mailto:richanna at amazon.com>>
Cc: Openid-specs-risc <openid-specs-risc at lists.openid.net<mailto:openid-specs-risc at lists.openid.net>>
Subject: RE: [EXTERNAL] FW: [Id-event] subject-identifers WG interest (Was: Closing the SecEvent working group)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Hi Atul,
You can create a pull request against the current sources at https://github.com/richanna/secevent. (Am I right about the current source location, Annabelle?) I’d do that. Then be sure to send a note about your review (which can contain a link to your PR) to the id-event at ietf.org<mailto:id-event at ietf.org> mailing so the chairs see it.
-- Mike
From: Atul Tulshibagwale <atultulshi at google.com<mailto:atultulshi at google.com>>
Sent: Monday, July 6, 2020 1:45 PM
To: Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>>
Cc: openid-specs-risc at lists.openid.net<mailto:openid-specs-risc at lists.openid.net>
Subject: Re: FW: [Id-event] subject-identifers WG interest (Was: Closing the SecEvent working group)
Hi all,
Thanks for highlighting the urgency on this.
Is it possible for me to create an updated version of the spec, given the voluminous nature of the changes? This corresponds to sections 4-6 of this SSE draft (still being reviewed in the WG and not ready for general commentary):
Atul
On Mon, Jul 6, 2020 at 12:49 PM Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>> wrote:
If you want to see the Subject Identifiers spec finish, please send a review of the spec to the id-event at ietf.org<mailto:id-event at ietf.org>. Both say what you like and what you’d like to see change. Please try to do it this week so that we’re not taking this down to the wire.
Many of you should really want this work to finish, since RISC and I think CAEP have dependencies on it!
BTW, some of you might be thinking “Why don’t we just do this in the SSE working group?” The problem is that the spec establishes an IANA registry, which requires an RFC. So we have to do this work in the IETF.
Please help make that happen!
-- Mike
From: Id-event <id-event-bounces at ietf.org<mailto:id-event-bounces at ietf.org>> On Behalf Of Dick Hardt
Sent: Monday, July 6, 2020 10:00 AM
To: Atul Tulshibagwale <atultulshi=40google.com at dmarc.ietf.org<mailto:40google.com at dmarc.ietf.org>>
Cc: Bjorn Hjelm <bjorn.hjelm at verizonwireless.com<mailto:bjorn.hjelm at verizonwireless.com>>; Yaron Sheffer <yaronf.ietf at gmail.com<mailto:yaronf.ietf at gmail.com>>; id-event at ietf.org<mailto:id-event at ietf.org>; Richard Backman, Annabelle <richanna=40amazon.com at dmarc.ietf.org<mailto:40amazon.com at dmarc.ietf.org>>
Subject: [EXTERNAL] Re: [Id-event] subject-identifers WG interest (Was: Closing the SecEvent working group)
Yaron and I have discussed keeping the WG going to work on the subject-identifiers draft. We were both disappointed in the previous feedback from the WG in the two WGLCs we had for the document.
With more people chiming in at this time, we have decided to check if there is renewed WG interest in subject-identifiers. To gauge the interest, we would like to see substantive feedback on the latest draft[1] from numerous people in the next two weeks. The cutoff will be July 20, 18:00 PDT. If we do not see substantial feedback, we will close the WG and assist Annabelle in publishing with the ISE.
Dick and Yaron
[1] https://tools.ietf.org/html/draft-ietf-secevent-subject-identifiers-05
Note this draft has expired, but still suits our purpose of gauging interest.
On Fri, Jul 3, 2020 at 10:07 AM Atul Tulshibagwale <atultulshi=40google.com at dmarc.ietf.org<mailto:40google.com at dmarc.ietf.org>> wrote:
I would also like this work to be completed. We're working on subject-type changes in the SSE spec, so those can be incorporated into this spec.
I'm happy to do this work within the SecEvents group.
Thanks,
Atul
On Fri, Jul 3, 2020 at 2:47 AM Yaron Sheffer <yaronf.ietf at gmail.com<mailto:yaronf.ietf at gmail.com>> wrote:
Sorry folks. We decided that this draft does not have WG support back in August, because it clearly did not have such support. Yes there are obviously people who want to see it published as an RFC. But not enough for any meaningful discussion during the WG last call (or even a positive response before the WGLC expired, we had exactly one). Nor any discussion since then. Nor a new draft version published since late July 2019.
Let me remind the group that the IETF offers two alternatives for publication, either AD-sponsored or through the ISE.
Thanks,
Yaron
From: Bjorn Hjelm <bjorn.hjelm at verizonwireless.com<mailto:bjorn.hjelm at verizonwireless.com>>
Date: Friday, July 3, 2020 at 05:29
To: "Richard Backman, Annabelle" <richanna=40amazon.com at dmarc.ietf.org<mailto:40amazon.com at dmarc.ietf.org>>
Cc: Yaron Sheffer <yaronf.ietf at gmail.com<mailto:yaronf.ietf at gmail.com>>, "id-event at ietf.org<mailto:id-event at ietf.org>" <id-event at ietf.org<mailto:id-event at ietf.org>>
Subject: Re: [E] Re: [Id-event] Closing the SecEvent working group
Annabelle,
I would like to see this work being completed.
BR,
Bjorn
On Jul 2, 2020, at 3:59 PM, Richard Backman, Annabelle <richanna=40amazon.com at dmarc.ietf.org<mailto:40amazon.com at dmarc.ietf.org>> wrote:
I’d like to hear from the working group on whether or not there is interest in completing the Subject Identifiers draft within secevents. This work has more or less been put on hiatus given the chairs’ previous decision not to continue with it within the working group, but it remains a dependency for other work, and a number of people within the working group have expressed interest and support for it previously. If there is support within the working group for resuming and completing Subject Identifiers, then it would seem reasonable to me to do so within secevents.
–
Annabelle Backman (she/her)
AWS Identity
https://aws.amazon.com/identity/<https://urldefense.proofpoint.com/v2/url?u=https-3A__aws..amazon.com_identity_&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=JdLD0MPKiH-cnYaRWq00dc9RaqFuwKAR2s9Y6qctmCY&s=sg2xiXxfFuwR2T2OCtgdsW708HRdK2DeOSvVtx3HhKo&e=>
From: Id-event <id-event-bounces at ietf.org<mailto:id-event-bounces at ietf.org>> on behalf of Yaron Sheffer <yaronf.ietf at gmail.com<mailto:yaronf.ietf at gmail.com>>
Date: Tuesday, June 30, 2020 at 2:06 AM
To: "id-event at ietf.org<mailto:id-event at ietf.org>" <id-event at ietf..org<mailto:id-event at ietf.org>>
Subject: [EXTERNAL] [Id-event] Closing the SecEvent working group
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Dear WG participants,
As you’ve all seen, our last two deliverables, the SET HTTP delivery specs, have both been approved for publication as RFCs.
Since the group has now completed its mission, we propose to close it down. Unless there are objections (accompanied by credible work items) within a week, we will ask the AD to do just that.. Even with the WG shut down, the mailing list will remain open for relevant discussions.
We would like to thank the authors of the Push and Poll soon-to-be RFCs, Annabelle, Mike, Marius, Morteza and Anthony. Many thanks also to the many other working group members who contributed to these quality documents.
Regards,
Dick and Yaron
_______________________________________________
Id-event mailing list
Id-event at ietf.org<mailto:Id-event at ietf..org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_id-2Devent&d=DwICAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=JdLD0MPKiH-cnYaRWq00dc9RaqFuwKAR2s9Y6qctmCY&s=ruzxNhwgDEh8N2N1ayOzTrCx8t1W3gLrz39-Jny_mhc&e=
_______________________________________________
Id-event mailing list
Id-event at ietf.org<mailto:Id-event at ietf.org>
https://www.ietf.org/mailman/listinfo/id-event
_______________________________________________
Id-event mailing list
Id-event at ietf.org<mailto:Id-event at ietf.org>
https://www.ietf.org/mailman/listinfo/id-event
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200730/fd098562/attachment-0001.html>
More information about the Openid-specs-risc
mailing list