Kantara FI-WG Teleconference

...

1. Roll call (QV group participation agreement) 
1. Quorum achieved
2. Agenda bash
3. Approval of 8/21 meeting minutes: https://kantarainitiative.org/confluence/x/fwbnBg 
1. Judith moved to accept
2. Keith seconds
3. Minutes approved
4. SAML2int formatting edits
   AIs for
   1. 1. Walter
   , Alan and EricWalter
   2. 1. completed all on last week’s call except for one where there was a question to the list. 2.1 flattening not done AI: All/Walter
      2. Eric’s not done. AI: Eric [DONE]
      3. Alan’s stuff - status update? [DONE]
   1. AIs for Walter, Alan and Eric
   3. Disposition column on the feedback page: https://kantarainitiative.org/confluence/x/6IDJBg
   Homework to all from last time to review this content and see if we can agree that it’s complete
   4. 1. Any concerns about the disposition column?
      1. No concerns
   5. Additionally, what to do with Rainer’s feedback
   6. 1. Discovery issue
      1. SP-23 is the only statement about discovery in the doc, not even a MUST.
      2. We’re going to make things worse by adding more language.
      3. This has always been the problem area of the doc. Maybe we should remove SP-23.
      4. Striking SP-23 not a good idea.
      5. To the extent you can define it, you want an inline discovery, rather than out-of-band via a URL.Example of a way to split the implementations, which is why Scott is getting uncomfortable having this in the doc. It’s not a deployment concern, it’s implementation.
      6. AI: Scott try to come up with something. Scott will send something to the list. Judith offers to help bounce ideas around.
   1. Homework to all from last time to review this content and see if we can agree that it’s complete
   2. Additionally, what to do with Rainer’s feedback
   7. Review of outstanding issues in Github
   1. 130 is done, closed
   2. 134 AI: Scott - entity or role level - indentation - [DONE]
   3. 135: Scope at entity or role level - text explicitly says it’s allowed to be at either level. Could do indentation. Vlad was reading into the indentation. AI: Scott will look into this. - [DONE]

...

1. 25: Not sure this is still relevant.
1. Any further work needed on feedback received so far

AI: Eric will review for consistency

1. Should the abstract or introduction mention that this document supersedes saml2int, since the title has changed with this version?
2. Proposed that we remove the subsection numbers, but otherwise keep the content unchanged.
3. Alan suggests making them section headings instead of numbers
   1. Just remove subheadings from 2.1. AI Alan wrote PR.
4. This working group could say that this supersedes the prior version, provided the Kantara leadership doesn’t disagree.
5. REFEDS uses the original document and probably can’t use the new version
6. Path of least resistance is to leave as-is rather than try to explain why
7. Decision: leave this as-is
8. What about saml2int.org?  Do nothing now
9. In section 2.1 all four requirements have their own subsections. This seems a bit inconsistent with later sections.

AI: Walter merge(d) the existing pull request (DONE)

1. There is still an asciidoctor artifact that is causing the "Contributors" headings to be red. I/we should probably figure that out, although I guess it looks fine as is.

AI: Alan wants to beat on this for a while to try to make it match the implementation profile (DONE)

1. Walter - reading through the whole document - the requirements seem like they have received considerable word-smithing, but the introduction and another section could use some touch-up.  AI: Walter will send improved wording to the list for review
2. Nick’s AI to update the disposition column on the feedback page: https://kantarainitiative.org/confluence/x/6IDJBg
1. Scott completed revisions to items 5 and 6. Any further work needed on this page?
2. Homework assignment for everyone - review the disposition column.  Is there anything else to be done for these items? Issue 6 may need improvement.
Rainer provided clarification on his feedback on SDP-SP23 in an email to the list dated 27 July. Any action to be taken?“Responding to item 4 (SDP-SP23/IDP-disco): I agree that [IdPDisco] does not prescribe the caching solution. However, it fails to point out that best practice is to have a centralized caching solution but decentralized UI
1. .
At least I think that this is best practice, because it reduces the IDP-disco process, and in certain use cases (users always starting with an intranet portal that will provision IDP-disco cookies upfront) it can almost eliminate it. The RA21-document that I mentioned describes this approach.”
1. Related to homework item above.
2. Here is Rainer’s clarification:
3. Scott disagrees that centralized discovery is a best practice
4. Scott - our document should be silent about this.  Eric agrees.
5. We (Shib project?) tried to separate the discovery from the SP so that changes to discovery don’t require changes to the SP software.
6. Deep linking matters
3. Review of outstanding issues in Github
4. Any further work needed on feedback received so far

...

Next Meeting

• Date: Weds, Sep 418, 2019
• Time: 16:30 EDT
• Code: https://global.gotomeeting.com/join/110596309

• You can also dial in using your phone.
  
  

  United States: +1 (669) 224-3318

  
  

  Access Code: 110-596-309

  
  

  More phone numbers
  
  

  Australia: +61 2 8355 1038
  
  

  Austria: +43 1 2530 22500
  
  

  Belgium: +32 28 93 7002
  
  

  Canada: +1 (647) 497-9380
  
  

  Denmark: +45 32 72 03 69
  
  

  Finland: +358 923 17 0556
  
  

  France: +33 170 950 590
  
  

  Germany: +49 692 5736 7300
  
  

  Ireland: +353 15 360 756
  
  

  Italy: +39 0 230 57 81 80
  
  

  Netherlands: +31 207 941 375
  
  

  New Zealand: +64 9 282 9510
  
  

  Norway: +47 21 93 37 37
  
  

  Spain: +34 932 75 1230
  
  

  Sweden: +46 853 527 818
  
  

  Switzerland: +41 225 4599 60
  
  

  United Kingdom: +44 330 221 0097

...