PROPOSED JOINT ACTIVITY ON A GENERIC PROTOCOL MECHANISM FOR E ND-TO-END QOS SERVICE CONTROL

[Bob Braden]

  *> From owner-issll at mercury.lcs.mit.edu  Wed May 30 14:59:58 2001
  *> From: "Roy, Radhika R, ALCTA" <rrroy at att.com>
  *> To: gratta at lucent.com, sob at harvard.edu, mankin at ISI.EDU
  *> Cc: diffserv at ietf.org, iptel at lists.bell-labs.com, issll at mercury.lcs.mit.edu,
  *>    megaco at fore.com, sip at lists.bell-labs.com, sipping at ietf.org, tsvwg at ietf.org,
  *>    Yukio Hiramatsu
  *>     <hiramatsu.yukio at lab.ntt.co.jp>, rbuhrke at lucent.com,
  *>    tsg11q8 at ties.itu.ch, tsg11q9 at ties.itu.ch, ITU-SG16 at mailbag.cps.INTEL.COM
  *> Subject: RE: PROPOSED JOINT ACTIVITY ON A GENERIC PROTOCOL MECHANISM FOR E
  *>    ND-TO-END QOS SERVICE CONTROL
  *> Date: Wed, 30 May 2001 17:21:14 -0400
  *> MIME-Version: 1.0
  *>
  *> Hi, Everyone:
  *>
  *> Question Q.F/16 of ITU-T SG16 is fully dedicated for developing standards
  *> for "End-to-End QOS for Multimedia Applications". Contributions are also
  *> being under discussion in the ITU-T SG16 Brazil May 28 - June 8, 2001
  *> meeting.

This is very confusing.   "End-to-End QOS for Multimedia Applications"
is an really important topic, but this topic must be a superset of
"End-to-End QOS signaling".  There are much harder problems than
signaling in providing E2E QoS.  Can you explain how signaling relates
to the title of this working party?

Thanks,

Bob Braden

  *>
  *> Applications like H.323, SIP, H.324, H.310, and others will also be able to
  *> use this Q.F/16's QOS signaling protocol. MEGACO/H.248 and BICC will also be
  *> able to use this when specs are fully developed and, TIPHON's QOS mechanisms
  *> can also be used as one of the mechanisms for implementations.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com