[Openid-specs-fapi] Updated invitation with note: FAPI WG Call (Atlantic) @ Wed 2020-09-02 11pm - Thu 2020-09-03 12am (JST) (openid-specs-fapi at lists.openid.net)

[Nat Sakimura]

No. Not dedicated. Just as one item, obviously.
Finishing FAPI 1 is the priority right now.
Also, we need to wait a bit till other parties like AU and FDX coming in
before making critical decisions for FAPI 2.0.

On Wed, Sep 2, 2020 at 8:45 PM Torsten Lodderstedt <torsten at lodderstedt.net>
wrote:

> Hi,
>
> as far as I remember we had agreed last time to dedicated this call (or
> parts of it) for discussing and deciding message signing as this is the
> last topic blocking FAPI 2 advanced profile draft publication.
>
> Here is the ticket:
> https://bitbucket.org/openid/fapi/issues/309/decision-on-message-signing-for-fapi-2
>
> best regards,
> Torsten.
>
> > On 2. Sep 2020, at 11:18, sakimura--- via Openid-specs-fapi <
> openid-specs-fapi at lists.openid.net> wrote:
> >
> > This event has been changed with this note:
> > "Updated the Agenda. "
> > FAPI WG Call (Atlantic)
> > When
> > Wed 2020-09-02 11pm – Thu 2020-09-03 12am Japan Standard Time
> > Where
> > https://global.gotomeeting.com/join/321819862 (map)
> > Calendar
> > openid-specs-fapi at lists.openid.net
> > Who
> > •
> > Nat Sakimura - creator
> > •
> > Dave Tonge
> > •
> > tonynad at microsoft.com
> > •
> > openid-specs-fapi at lists.openid.net
> >  more details »
> > Changed: OIDF FAPI WG Atlantic Call.
> >
> > Agenda
> > ------------------
> > * For agenda, see
> https://bitbucket.org/openid/fapi/wiki/FAPI_Meeting_Notes_2020-09-02_Atlantic
> >
> >
> > 1.   Roll Call
> > 2.   Adoption of Agenda (Nat)
> > 3.   Events
> > 4.   External Organizations
> > 4.1.   Australia (Dima/Stuart)
> > 4.2.   Berlin Group (Francis)
> > 4.3.   European Commission (Mark/Torsten)
> > 4.4.   ETSI (Ralph)
> > 4.5.   FDX (Anoop)
> > 4.6.   UK (Chris/Ralph)
> > 5.   Issues (Anoop)
> > 6.   PRs for 1.0 (Dave)
> > 6.1.   PR 189 FAPI-RW: Require PKCE when using PAR (Stuart)
> > 6.2.   PR 182 Add non-normative examples of various objects
> > 6.3.   PR 187 Privacy Considerations
> > 7.   AOB
> >
> > Call in Information
> > -----------------------------
> > 1. Please join my meeting.
> > https://global.gotomeeting.com/join/321819862
> >
> > 2. Use your microphone and speakers (VoIP) - a headset is recommended.
> Or, call in using your telephone.
> >
> > United States: +1 (224) 501-3316
> > United Kingdom: +44 (0) 20 3713 5011
> >
> > Access Code: 321-819-862
> > Audio PIN: Shown after joining the meeting
> >
> > Meeting ID: 321-819-862
> >
> > GoToMeeting®
> > Online Meetings Made Easy®
> >
> > Not at your computer? Click the link to join this meeting from your
> iPhone®, iPad®, Android® or Windows Phone® device via the GoToMeeting app.
> > Going (openid-specs-fapi at lists.openid.net)?   Yes - Maybe - No    more
> options »
> > Invitation from Google Calendar
> >
> > You are receiving this courtesy email at the account
> openid-specs-fapi at lists.openid.net because you are an attendee of this
> event.
> >
> > To stop receiving future updates for this event, decline this event.
> Alternatively you can sign up for a Google account at
> https://www.google.com/calendar/ and control your notification settings
> for your entire calendar.
> >
> > Forwarding this invitation could allow any recipient to send a response
> to the organizer and be added to the guest list, or invite others
> regardless of their own invitation status, or to modify your RSVP. Learn
> More.
> >
> > <Mail
> Attachment.ics><invite.ics>_______________________________________________
> > Openid-specs-fapi mailing list
> > Openid-specs-fapi at lists.openid.net
> > http://lists.openid.net/mailman/listinfo/openid-specs-fapi
>
>

-- 
Nat Sakimura
NAT.Consulting LLC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20200904/1f2cb557/attachment.html>