Document Deliverables

1
Document Deliverables

• An expository document discussing the problem of
  service identification and its perils on
  interoperability and correctness
• A P-Header allowing a trusted edge element to
  store the result of its analysis of a SIP
  message, which can be used by trusted elements in
  the trust domain
• A media feature tag registration for subtypes of
  the application type

2
Expository Document Contents 1/2

• What is service identification
• Examples of services that appear to be hard to
  differentiate
• IPTV vs. multimedia, voice in a game vs. voice
  with IM chat, messaging vs. config update
• What do people usually want to do with a service
  identification
• QoS, authorization, network server invocation,
  client dispatch, call routing, billing, etc.

3
Expository Document Contents 2/2

• Do-what-I-say must use information in the
  signaling that defines the behavior that
  fundamentally defines this service as different
  from others
• Examples of this for the three services in
  section 2
• Architectural perils of driving service
  definition off of extra data
• Fraud users lying to gain advantage extra
  QoS, unauthorized services, free service
• Interoperability Failures what if someone has a
  different definition of service than you
• Innovation Stifling needs agreement and
  standardization of services
• Examples demonstrating these perils happening for
  the three services in the examples section