[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] Agenda: XDI TC Telecon Friday 09:00 - 10:30AM PT 2014-10-10
XDI TC Agenda
Following is the agenda for the unofficial telecon of the XDI TC at:
Date: Friday, 10 October 2014 USA
Time: 09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)THE LINK TO THIS AGENDA AND LIVE MEETING MINUTES IS:
https://docs.google.com/document/d/1t5Mx0ITqJdLwo8wM5GD9lcqehgbgnrhk-k2sERwc7J0/edit
THE WEBEX INSTRUCTIONS FOR THIS MEETING ARE:
1. Go to https://neustar.webex.com/neustar/j.php?ED=203186612&UID=1364257662&PW=NN2Y2NzAxZTVj&RT=MiMxMQ%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: 5474
4. Click "Join".
5. Follow the instructions that appear on your screen.
To view in other time zones or languages, please click the link:
IRC Channel: irc://irc.freenode.net:6667/xdi
AGENDA
NEWS & UPDATES
Vienna Deep Dive
Dan+André+Markus have been meeting in Vienna to discuss current issues around the XDI Policy and XDI Connection specs, as well as preparations for the upcoming IIW conference, e.g. the XDI Hackathon.
PRESENTATIONS/DISCUSSIONS
Report from XDI editors subcommittee
https://wiki.oasis-open.org/xdi/XdiOneSpecs
https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook
XDI Policy and Connections
Let’s continue to discuss XDI connection requests, connection invitations, link contracts, templates, community contracts, requester contracts, etc.
Update from Vienna Deep Dive:
Dan has uploaded a new version of XDI Policy, and the first version of XDI Connections
Dan has uploaded a working document about community link contracts
Discuss different ways for an RA to receive a copy of a new link contract instance
Insight: A link contract instance may be used by many authorities that can satisfy a policy _expression_ (e.g. groups, roles, organization membership)
Insight: Just like there can be a connection invitation, there can also be invitations for any other operation, e.g. $get
Challenge of correlating message requests and responses (see below)
Issue related to having multiple link contract instances based on one link contract template (how to algorithmically determine the address?)
Other topics:
Review what happens when a connection invitation is processed.
Template versioning - what if the Template Authority changes a template? How does this affect existing LC instances? Should versioning for LC templates be mandatory?
What do “deferred” connection requests look like, and how are they processed?
Collection of Documents:
XDI Policy draft spec:
https://www.oasis-open.org/committees/download.php/54276/XDIPolicyDraft%20v8.docx
XDI Connections draft spec:
https://www.oasis-open.org/committees/download.php/54279/XDI%20Connections%20V1.docx
Link Contract Instantiation:
https://www.oasis-open.org/committees/download.php/54205/LinkContractInstantiation25Sep2014.pdf
Community Link Contracts:
Berkeley Deep Dive notes:
https://www.oasis-open.org/committees/download.php/53986/xdi%20deep%20dive%202014-8-27.pdf
https://www.oasis-open.org/committees/download.php/53985/linkcontractExamples.pdf
Correlating message requests and responses
In the XDI Browser Binding, and in the case of “deferred” responses, how can a message request and response be correlated? Do responses need IDs that match the request?
This may have special relevance for XDI connection invitations and connection requests.
Will this be covered by the XDI Asynchronous Messaging spec?
Transactional integrity
We have discussed the topic of transactional integrity a number of times in the past without reaching a conclusion. This seems to now have new relevance in conjunction with link contract instantiation.
The following document has a section titled “XDI Message Transactional Integrity Notes”, let’s review and discuss:
https://www.oasis-open.org/committees/download.php/53921/LinkContractInstantiation17Aug2014.pdf
IIW Preparations
Let’s discuss what demos or other sessions we are planning for the upcoming Internet Identity Workshop.
NEXT CALL
The next call is next week at the regular time.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]