Re: Enforcing symmetric operation in the context of slow start fo r H. 323v4
Since the proposed procedure simply defines implementation details at application level and redifines the meaning of caps which already exist in H.323v2, there is nothing that would prevent an H.323v2 compliant endpoint to make use of this procedure for enforcing symmetric operation. Is it safe to recommend this procedure as the prefered approach for H.323v2 endpoints as well?
Danail Kirov Vertical Networks
-----Original Message----- From: mike.nilsson@bt.com [mailto:mike.nilsson@bt.com] Sent: Thursday, September 07, 2000 2:47 AM To: itu-sg16@mailbag.cps.intel.com; h323implementors@imtc.org Subject: Enforcing symmetric operation in the context of slow start for H. 323v4
At the Portland rapporteur's meeting of Q12-14, document APC-1881, 'Enforcing symmetric operation in the context of slow start for H.323v4', was discussed. The outcome of the discussion, as described in the meeting report, is:
This was accepted for the H.323 IG and also H.323 V4. It was agreed that this was meritorius, but that some further discussion was needed. See TD-47. The agreement is that APC-1881 is adopted for changes to H.323 V4, and TD-47 for H.245 V7, with the redefinition of the receiveAndTransmitt capability being the preferred approach. It was noted that the rejectReason needs to be mentioned in TD-47. Text will also be added to note that the procedures of TD-47 only apply if the slave has detected a conflict. All are urged to look very closely at this, and to consider if there are any issues with this. If any are found, we will make changes in November. The editor will post this discussion on the mailing list to ensure broad discussion.
The purpose of this mail is simply to do as the meeting report stated, and highlight the issue and to try to get broad agreement on the proposed solution. As far as H.245 is concerned the proposed solution is to include text from TD-47a that is labelled as 'Proposal for immediate action' and the first option (redefinition of the receiveAndTransmitt capability) from the section labelled 'Longer term options'.
The documents are available at:
ftp://standard.pictel.com/avc-site/0008_Por/APC-1881.zip ftp://standard.pictel.com/avc-site/0008_Por/TD-47a.zip
Best regards
Mike Nilsson
-------------------- Mike Nilsson Multimedia Applications B81 Room 102 pp14 BT Advanced Communications Technology Centre Adastral Park, Martlesham Heath, Ipswich, IP5 3RE, UK Tel: +44 1473 645413 Mobile: +44 7808 635412 Fax: +44 1473 646589 Email: mike.nilsson@bt.com
--------------------------------------------------------------------------- ------------------------------ Please send E-mail to contact@imtc.org mailto:contact@imtc.org to subscribe or unsubscribe from this list ------------------------------ ---------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
Danail,
Yes, it is safe. I mean, it can't be any worse than it already is, right? :-) H.323v1, v2, and v3 EPs _should_ support this new procedure. However--and this is important--they are still compliant even if they don't whereas v4 EPs would not be compliant. For example, our v3 EPs do not currently obey this procedure, but they are still compliant.
Paul Long Smith Micro Software, Inc.
-----Original Message----- From: Danail Kirov [mailto:DanailK@VERTICAL.COM] Sent: Friday, September 08, 2000 1:01 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Re: Enforcing symmetric operation in the context of slow start fo r H. 323v4
Since the proposed procedure simply defines implementation details at application level and redifines the meaning of caps which already exist in H.323v2, there is nothing that would prevent an H.323v2 compliant endpoint to make use of this procedure for enforcing symmetric operation. Is it safe to recommend this procedure as the prefered approach for H.323v2 endpoints as well?
Danail Kirov Vertical Networks
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com
participants (2)
-
Danail Kirov
-
Paul Long