Agenda 20161020

• Should there be a default user agent behavior for PMIs that are not URLs and not recognized short strings? (E.g., just used for matching.)
• Detecting if payment app is available from Mahesh
  • What exactly are the requirements? "Some app available?" "Specific app available?" Is the requirement that a given merchant be able to query payment apps with whom they have an existing relationship?
• Push payment discussion update (Roy). See pull request
• Update on Q1 2017 FTF meeting schedule
  • Proposal 1: 27-28 February 2017 in Capetown, South Africa, hosted by Ripple. (Great weather! There are other interesting events around then in the region as well)
  • Proposal 2: 23-24 March in Chicago, USA, (no host identified yet). IETF 98 is the following week in Chicago.
  • Should we have a July/August meeting?
  • TPAC 2017: 6-10 Nov near San Francisco
• Check in on priorities:
  • PR API issues
  • Payment app spec reviews
  • Push payment proposal
  • Test suite
• Upcoming meeting schedule
  • NOTE: 3 November call will be 1 hour earlier for many people (e.g., Europeans) due to end of DST.
  • We plan to meet weekly through the year except for 24 Nov, 22 Dec, 29 Dec.
  • First meeting of 2017 will be 5 Jan.

Possibly:

• ISO 20022 data type alignment for basic card terms (cf Matt Saxon and ISO PaymentCard value types)