payment for services in sip draft-jennings-sipping-pay cullen jennings gyuchang jun jason fischl...
TRANSCRIPT
![Page 1: Payment for Services in SIP draft-jennings-sipping-pay Cullen Jennings Gyuchang Jun Jason Fischl Hannes Tschofenig](https://reader036.vdocuments.us/reader036/viewer/2022082506/5697c0081a28abf838cc6ba1/html5/thumbnails/1.jpg)
Payment for Services in SIPdraft-jennings-sipping-pay
Cullen JenningsGyuchang JunJason Fischl
Hannes Tschofenig
![Page 2: Payment for Services in SIP draft-jennings-sipping-pay Cullen Jennings Gyuchang Jun Jason Fischl Hannes Tschofenig](https://reader036.vdocuments.us/reader036/viewer/2022082506/5697c0081a28abf838cc6ba1/html5/thumbnails/2.jpg)
sipping-pay draft
• Postage stamps for SIP
• One approach to combating SPIT
• Revised to use SAML– Relies heavily on draft-tschofenig-sip-saml– Payment Request and Receipt are now SAML
documents– Can use SAML Artifacts or Assertions
![Page 3: Payment for Services in SIP draft-jennings-sipping-pay Cullen Jennings Gyuchang Jun Jason Fischl Hannes Tschofenig](https://reader036.vdocuments.us/reader036/viewer/2022082506/5697c0081a28abf838cc6ba1/html5/thumbnails/3.jpg)
New Examples
• Added example where Merchant Proxy acts on behalf of Merchant
• Added example where Customer Proxy acts on behalf of Customer
![Page 4: Payment for Services in SIP draft-jennings-sipping-pay Cullen Jennings Gyuchang Jun Jason Fischl Hannes Tschofenig](https://reader036.vdocuments.us/reader036/viewer/2022082506/5697c0081a28abf838cc6ba1/html5/thumbnails/4.jpg)
Merchant Proxy Example
![Page 5: Payment for Services in SIP draft-jennings-sipping-pay Cullen Jennings Gyuchang Jun Jason Fischl Hannes Tschofenig](https://reader036.vdocuments.us/reader036/viewer/2022082506/5697c0081a28abf838cc6ba1/html5/thumbnails/5.jpg)
SAML Receipt<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Body> <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ID="abe567de6" InResponseTo="example-ncname" Version="2.0" IssueInstant="2005-01-31T12:00:00Z" Destination="http://psp.example.com" Consent="http://www.example.com/">
<samlp:Status> <samlp:StatusCode Value="samlp:Success"/> <samlp:StatusMessage>Success</samlp:StatusMessage> <samlp:StatusDetail/> </samlp:Status>
<!-- SAML ASSERTION AND STATEMENTS --> <saml:Assertion xmlns:saml=" urn:oasis:names:tc:SAML:2.0:assertion "Version="2.0" IssueInstant="2005-01-31T12:00:00Z"> <saml:Issuer> www.payment-provider.com </saml:Issuer> <saml:Subject> <saml:NameID Format=" urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress"> [email protected]</saml:NameID> </saml:Subject>
<saml:Conditions NotBefore="2005-01-31T12:00:00Z" NotOnOrAfter="2005-01-31T12:00:00Z"/> <saml:AuthnStatement AuthnInstant="2005-01-31T12:00:00Z" SessionIndex="67775277772"> <saml:AuthnContext> <saml:AuthnContextClassRef> urn:oasis:names:tc:SAML:2.0:ac:\ classes:PasswordProtectedTransport </saml:AuthnContextClassRef> </saml:AuthnContext> </saml:AuthnStatement>
<saml:Statement xsi:type="PaymentReceipt"> <merchantBits> MDE1Mw== </merchantBits> <merchantId> 15 </merchantId> <serviceUrl> https://psp.example.com/paymentService </serviceUrl> <currencyDivisor> 1000 </currencyDivisor> <currency>
USD </currency> <amount> 300 </amount> </saml:Statement> </saml:Assertion> </samlp:Response> </env:Body> </env:Envelope>
![Page 6: Payment for Services in SIP draft-jennings-sipping-pay Cullen Jennings Gyuchang Jun Jason Fischl Hannes Tschofenig](https://reader036.vdocuments.us/reader036/viewer/2022082506/5697c0081a28abf838cc6ba1/html5/thumbnails/6.jpg)
SAML Issues
• SAML artifacts add additional complexity which translates to cost for the merchants and payment providers
• SAML documents may cause MTU issues
![Page 7: Payment for Services in SIP draft-jennings-sipping-pay Cullen Jennings Gyuchang Jun Jason Fischl Hannes Tschofenig](https://reader036.vdocuments.us/reader036/viewer/2022082506/5697c0081a28abf838cc6ba1/html5/thumbnails/7.jpg)
Questions
• Do we want to use SAML?