[Openid-specs-authzen] meeting notes for July 22
gerry gebel
ggebel at gmail.com
Tue Jul 22 20:10:02 UTC 2025
and the recording:
https://zoom.us/rec/share/o5-CJbJyuwy2m3NMVNb1PKlg0JgMFtRMucYbCMWXaxA7zRYF14KeomN_e8_LByg2.HZ2oJTkiRLh-ASmS?pwd=DMzxLkYIoaPAD-4STwAAIAAAALMSiIWTZKFuJhi1cEXjkgbAfRrE7ctY2gVbg1MKVUJkZ0gAvdBHsL8brKaT-6piZDAwMDAwNA
Attendees
- Gerry Gebel
- Jeff Lombardo
- Michiel Trimpe
- Alex Babaenu
- Victor Lu
- Gert Drapers
- Vladi Berger
- Julio Auto De Medeiros
- Travis Farrell
- Roland Baum
<#Agenda>Agenda
- New time proposal for this meeting
- Issues updates
- 278: inconsistent use of reason and pagination. Alex B, timeline
for splitting this into two PRs?
- 268: security section needs details on client authN failure. Alex
B, timeline for updates to this?
- 46 and 47 Device ID and IP address
<#Notes>Notes
-
New time proposal: David Hyland suggests that we align this call with
5am Australia time. This will enable him to join regularly and also provide
more consistent times for other regions. One impact is that we will need to
move to Wednesday or Thursday so as not to collide with the SSF call on
Tuesday. Today's attendees prefer Thursday by a slight margin and we will
make a final decision shortly.
-
Issue 278: Alex is unable to split into 2 PRs, can we focus on the
content?
- Gert volunteerd to split the changes into separate PRs, 278 will
remain on the reason and a new PR will be created for pagination
- It was determined that the proposed structure introduces a lot of
semantics into the spec, which will require a lot of discussion before
reaching an agreement. Keeping in the spirit of avoiding incorporating
semantics into the spec, the reason section will only include
non-normative
examples. We can learn from early implementations on what is needed here
and this is another area where profiles can suggest recommended patterns
and practices.
-
Issue 268: Jeff has issued a PR for this change
-
Issue 46/47: Device id and ip address will be non-normative examples
-
PR 345: JSON-LD support
- Michiel wanted to discuss this PR so we can have a resolution. The
discussion pointed out that JSON-LD is also a semantic change
and it's also
a large topic that could delay our timeline for getting to version 1.0
- Michiel agreed to have a presentation for the next call to review
some of the context and reasoning for adding JSON-LD
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-authzen/attachments/20250722/3dbd4096/attachment.htm>
More information about the Openid-specs-authzen
mailing list