Web Payments Working Group

<Ian> Scribe: Ian

<nicktr> reminder that the agenda can be found at https://github.com/w3c/webpayments/wiki/Agenda-20180222

nicktr: Welcome all

<nicktr> draft spec https://w3c.github.io/webpayments/proposals/interledger/

AdrianHB: There has been a significant change to that piece of work
... there's an explainer doc as well

<AdrianHB> https://github.com/w3c/webpayments/tree/gh-pages/proposals/interledger

adrianhb: You pass in a pointer that can be used to resolve the account where you send money (to the merchant)
... we are working on a way to pass a request for a token that can be redeemed (
... quite a lot has changed regarding ILP overall
... mostly around the way the ecosystem is evolving...and focusing more on payment messages instead of clearing and settlement
... ILP operates at the authorization layer

<Zakim> nicktr, you wanted to ask if there are any example implementations or web app payment handlers

nicktr: Are there any example implementations or payment handlers?

adrianhb: Not yet...I had a working demo that was based on the older proposal; my plan is to have something for Singapore
... I'm holding off until we make some decisions around the tokenization payment model

<Zakim> Ian, you wanted to ask if there is a link to changes

adrianhb: Regarding a description of the changes to ILP, we are writing a blog post
... we are now on ILP "v4"
... in v1 payment was cleared at each node
... but we've bumped that up to authorization, which has some tradeoffs
... if you send an ILP packet to an intermediary, you are committing to pay them the value of that packet...they might only forward if you've already agreed out-of-band, or they might trust you
... this lets you make payments to entities you don't trust directly

<nicktr> registration https://www.w3.org/2002/09/wbs/83744/ftf-reg-201804/

FTF meeting

NickTR: Please register. If you can't join us in person, we have requests for remote access

IJ: Any venue updates AdrianHB?

AdrianHB: Working on the venue; not finalized

NickTR: Thanks to Ripple for hosting!
... We have received requests to have breakouts on both days
... for focused work.
... to help us plan for those, please propose breakout sessions to help build the agenda

<AdrianHB> Proposed venue: http://one15marina.com/browse-all-venues/nova-room.html

Charter update

<AdrianHB> Map: https://goo.gl/maps/6H3zx9sJu7T2

<nicktr> scribenick: nicktr

ian: Good news: positive review of the charter

<Ian> Revised charter

<Ian> Diff

ian: we did get some comments that led to changes
... from a process perspective, we have asked the director to approve
... all of the changes bar one are editorial except one
... the latter is a small question of scope

Ian reviews changes

ian: end date corrected back to end 2019
... in section 1.2, we have sharpened language to make sure it's clear that we're not inventing new encryption
... in s1.3, we have been more explicit about the various specifications
... we have added an expression of interest in working in trailing transactions (should we add an 's'?)
... we have made the case that this is the suggested new topics section and therefore it is ok for us to include this
... also in s1.3 we made editorial change to a description of enabling merchant validation
... all the other changes are editorial including an explicit reference to Secure Remote Commerce
... our charter expires 1 March
... there's a new feature to allow members to delay call for participation which one member has requested
... so we will issue the call for participation around 9th March

Next call

<Ian> planned for 8 march

<Ian> ...will get a tokenization task force update

<Ian> ..we will be working on FTF agenda over the next few weeks to ensure it's of value to participants

<Ian> ...we welcome suggestions, people volunteering to lead sessions, demonstrations