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

[Roy, Radhika R, ALCTA]

Hi, Bob:

All applications (e.g., H.323, SIP) uses signaling messages among its
functional entities (e.g., terminal, agents, gatekeepers, proxies, gateways)
for communications.

The signaling messages that carry QOS parameters are treated as QOS
signaling messages. The applications like SIP and H.323 send signaling
messages end-to-end. H.323 uses H.225.0 RAS, Q.931, Annex G, and H.245
signaling protocols.  SIP also uses SDP as a part of the signaling messages.


The signaling messages that carry QOS related information can be treated as
"End-to-End QOS signaling" messages.

Kindly see the ongoing works of Q.F/16 of SG16. This will provide more
information related to your questions.

Hope this helps.

Best regards,
Radhika R. Roy

-----Original Message-----
From: Bob Braden [mailto:braden at ISI.EDU]
Sent: Wednesday, May 30, 2001 7:39 PM
To: gratta at lucent.com; sob at harvard.edu; mankin at ISI.EDU; Roy, Radhika R,
ALCTA
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; 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



  *> 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