draft-beck-sipping-svc-charging- req-01 Wolfgang Beck - - PowerPoint PPT Presentation

draft beck sipping svc charging req 01
SMART_READER_LITE
LIVE PREVIEW

draft-beck-sipping-svc-charging- req-01 Wolfgang Beck - - PowerPoint PPT Presentation

draft-beck-sipping-svc-charging- req-01 Wolfgang Beck (beckw@t-systems.com) Deutsche Telekom 56. IETF San Francisco, CA Problem UASs sometimes want to charge for call duration (media server applications, hotlines etc). users want


slide-1
SLIDE 1

draft-beck-sipping-svc-charging- req-01

Wolfgang Beck (beckw@t-systems.com) Deutsche Telekom

  • 56. IETF – San Francisco, CA
slide-2
SLIDE 2

Problem

  • UASs sometimes want to charge for call duration (media server

applications, hotlines etc).

  • users want to minimize the number of their accounts (= trust

relationships)

  • a Trusted Third Party (TTP) could help here
slide-3
SLIDE 3

How to prove that a session is still active?

  • make sure that UAs use an accounting proxy and are not able

to send SIP messages directly to each other

  • get signed and time-stamped tokens from a TTP and include

them into INVITE and periodic UPDATE messages; Called party can use the tokens as evidence. – let a proxy insert these tokens? – get tokens elsewhere (as in OSP)?

  • trade-off between accuracy and load.
  • should pricing information be carried in SIP messages?
slide-4
SLIDE 4
  • ther TTPs in SIP
  • PKI (S/MIME, TLS)
  • network asserted identity (RfC 3325)
  • authorization service (J. Peterson’s draft)
  • P-OSP-Auth-Token header (draft-johnston-sip-osp-token-04)
slide-5
SLIDE 5

next steps

  • Should this become a WG item?
  • Or could this be an extension of NAI / Authorization Service

work?