November 2001 - sg16-avd - lists.packetizer.com

AW: [Mobility] Resending the email with H.235 Annex G added to th e agenda of ITU-T SG16 WP2 Q.2/Q.5/Q.G Conference Call meetings informat i on
by Klaghofer Karl ICN EN HC ID 14 30 Nov '01

30 Nov '01

Hi Paul, I do not see the H.22x standard being listed as document within the scope of these upcoming Q.5 conference calls. Who (which Question) will drive the H.22x standard ? How can H.MMS.1 for example be completed by February if the actual protocol that would be used for mobility management (H.22x) is out of the scope of these Q.5 discussions ? Thanks, Karl Klaghofer, Siemens -----Ursprungliche Nachricht----- Von: Reddy, Paul K [mailto:paul.k.reddy@INTEL.COM] Gesendet: Mittwoch, 28. November 2001 23:01 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: Re: [Mobility] Resending the email with H.235 Annex G added to th e agenda of ITU-T SG16 WP2 Q.2/Q.5/Q.G Conference Call meetings informati on Dear ITU-T SG16 WP2 Colleagues and Mobility Experts, Sorry for the delay in sending this email to the reflector and also due the outages of the SG16 reflector last week the last sent email could not be posted on this reflector. Please accept our apologies. As Rapporteur of Question_5/SG16 (Mobility for Multimedia Systems and Services) agreed in Dublin, Ireland Rapporteur's meeting to organize 3 two hours conference call meetings during Nov, Dec and January months before ITU-T SG16 face to face meeting during February, 2002 in Geneva, Switzerland. The goal of following conference call meetings are to make progress on the following recommendations: 1. H.MMS.0: User/Service Mobility Management for H.323 Multimedia Systems. 2. H.MMS.1: Terminal Mobility Management for H.323 Multimedia Systems. 3. H.MMS.2: Inter-working and Interoperability between Mobility Management for Multimedia systems and Cellular PLMNs. 4. H.MMS.3: Presence and Instant Messaging Services for mobile and non-mobile Multimedia systems. 5. H.MMS.4: Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems 6. H.235 Annex-G: Security for Multimedia Mobility (User, Terminal, Service) services. For the status of the above recommendations and related documents, please see the enclosed Dublin's Q.5 Rapporteur's meeting report. Also, please go to URL <http://standard.pictel.com/ftp/avc-site/0110_Dub> http://standard.pictel.com/ftp/avc-site/0110_Dub for Q.5/16 documents. Guidelines for contributing and participating in the following Conference calls: 1. Companies and individual experts are welcome to contribute by uploading the contributions to ftp site: ftp://standard.pictel.com/avc-site/Incoming/Q5conf/ By due dates of each conference call meetings Contributions submission due dates: * For November 30, 2001 conference call is midnight (Pacific standard time) of Nov 28, 2001 * For December 18, 2001 conference call is midnight (Pacific standard time) of Dec 14, 2001 * For January 25, 2002 conference call is midnight (Pacific standard time) of Jan 18, 2001 2. Reply to this email to <mailto:paul.k.reddy@intel.com> paul.k.reddy(a)intel.com and get confirmation of your attendance on each of the conference call meetings in order to reserve the bridge port for a guarantee access during the conference call meetings. 3. Agenda for each Conference call meeting: * Introduction * Review contributions in the following order(Note: continue where we left off in one conference call meeting to another) i. H.MMS.1 (Terminal Mobility for H.323 MM systems) and H.22x.x (Mobility Management protocol and procedures) contributions. This recommendation is targeted for approval during Feb, 2002 SG16 meeting in Geneva. ii. H.MMS.0 (User Mobility, Service Mobility for Multimedia systems) contributions. This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iii. H.MMS.3 (Presence and IM services for mobile and non-mobile Multimedia Systems (e.g., H.323 systems)). This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iv. H.MMS.4 (Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems). This recommendation is targeted for approval during Feb, 2003 SG16 meeting in Geneva. v. H.MMS.2 (Inter-working and Interoperability between Mobility Management for MM systems and Cellular PLMNs). This recommendation is targeted for approval during October, 2003 SG16 meeting in Geneva. vi. H.235 Annex G (Security for Multimedia Mobility Services). This recommendation with Security for Terminal mobility service is targeted for approval during Feb, 2002 SG16 meeting in Geneva. If you have any questions, please email Q.5/16 Rapporteur (Mr. Paul K. Reddy) at <mailto:paul.k.reddy@intel.com> paul.k.reddy(a)intel.com Conference call Bridge information: Conference call Meeting 1: Start: Nov 30, 2001 07:00 Pacific Standard Time End: Nov 30, 2001 09:00 Pacific Standard Time Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 9899887 --------------------------------------------------- Conference Call Meeting 2: Start: Dec 18, 2001 07:00 Pacific Standard Time End: Dec 18, 2001 09:00 Pacific Standard Time User Instructions: Date: Tuesday, December 18, 2001 Lines: 10 Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 6449818 ----------------------------------------------------- Conference Call Meeting 3: Start: Jan 25, 2002 07:00 Pacific Time End: Jan 25, 2002 09:00 Pacific Time Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 3708752 ----------------------------------------------------- regards, Paul BM__MailAutoSigPaul K. Reddy Rapporteur of Q.5/16 ITU-T SG16 Working Party 2 Intel Labs, 2111 N.E. 25th Avenue, mailstop: JF3-377 Hillsboro, OR-97124, USA Tel: +1 (503)-264-9896 E-mail: paul.k.reddy(a)intel.com

1 0

Re: [Mobility] Resending the email with H.235 Annex G added to th e agenda of ITU-T SG16 WP2 Q.2/Q.5/Q.G Conference Call meetings informati on
by Reddy, Paul K 28 Nov '01

28 Nov '01

Dear ITU-T SG16 WP2 Colleagues and Mobility Experts, Sorry for the delay in sending this email to the reflector and also due the outages of the SG16 reflector last week the last sent email could not be posted on this reflector. Please accept our apologies. As Rapporteur of Question_5/SG16 (Mobility for Multimedia Systems and Services) agreed in Dublin, Ireland Rapporteur's meeting to organize 3 two hours conference call meetings during Nov, Dec and January months before ITU-T SG16 face to face meeting during February, 2002 in Geneva, Switzerland. The goal of following conference call meetings are to make progress on the following recommendations: 1. H.MMS.0: User/Service Mobility Management for H.323 Multimedia Systems. 2. H.MMS.1: Terminal Mobility Management for H.323 Multimedia Systems. 3. H.MMS.2: Inter-working and Interoperability between Mobility Management for Multimedia systems and Cellular PLMNs. 4. H.MMS.3: Presence and Instant Messaging Services for mobile and non-mobile Multimedia systems. 5. H.MMS.4: Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems 6. H.235 Annex-G: Security for Multimedia Mobility (User, Terminal, Service) services. For the status of the above recommendations and related documents, please see the enclosed Dublin's Q.5 Rapporteur's meeting report. Also, please go to URL http://standard.pictel.com/ftp/avc-site/0110_Dub <http://standard.pictel.com/ftp/avc-site/0110_Dub> for Q.5/16 documents. Guidelines for contributing and participating in the following Conference calls: 1. Companies and individual experts are welcome to contribute by uploading the contributions to ftp site: ftp://standard.pictel.com/avc-site/Incoming/Q5conf/ By due dates of each conference call meetings Contributions submission due dates: * For November 30, 2001 conference call is midnight (Pacific standard time) of Nov 28, 2001 * For December 18, 2001 conference call is midnight (Pacific standard time) of Dec 14, 2001 * For January 25, 2002 conference call is midnight (Pacific standard time) of Jan 18, 2001 2. Reply to this email to paul.k.reddy(a)intel.com <mailto:paul.k.reddy@intel.com> and get confirmation of your attendance on each of the conference call meetings in order to reserve the bridge port for a guarantee access during the conference call meetings. 3. Agenda for each Conference call meeting: * Introduction * Review contributions in the following order(Note: continue where we left off in one conference call meeting to another) i. H.MMS.1 (Terminal Mobility for H.323 MM systems) and H.22x.x (Mobility Management protocol and procedures) contributions. This recommendation is targeted for approval during Feb, 2002 SG16 meeting in Geneva. ii. H.MMS.0 (User Mobility, Service Mobility for Multimedia systems) contributions. This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iii. H.MMS.3 (Presence and IM services for mobile and non-mobile Multimedia Systems (e.g., H.323 systems)). This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iv. H.MMS.4 (Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems). This recommendation is targeted for approval during Feb, 2003 SG16 meeting in Geneva. v. H.MMS.2 (Inter-working and Interoperability between Mobility Management for MM systems and Cellular PLMNs). This recommendation is targeted for approval during October, 2003 SG16 meeting in Geneva. vi. H.235 Annex G (Security for Multimedia Mobility Services). This recommendation with Security for Terminal mobility service is targeted for approval during Feb, 2002 SG16 meeting in Geneva. If you have any questions, please email Q.5/16 Rapporteur (Mr. Paul K. Reddy) at paul.k.reddy(a)intel.com <mailto:paul.k.reddy@intel.com> Conference call Bridge information: Conference call Meeting 1: Start: Nov 30, 2001 07:00 Pacific Standard Time End: Nov 30, 2001 09:00 Pacific Standard Time Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 9899887 --------------------------------------------------- Conference Call Meeting 2: Start: Dec 18, 2001 07:00 Pacific Standard Time End: Dec 18, 2001 09:00 Pacific Standard Time User Instructions: Date: Tuesday, December 18, 2001 Lines: 10 Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 6449818 ----------------------------------------------------- Conference Call Meeting 3: Start: Jan 25, 2002 07:00 Pacific Time End: Jan 25, 2002 09:00 Pacific Time Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 3708752 ----------------------------------------------------- regards, Paul Paul K. Reddy Rapporteur of Q.5/16 ITU-T SG16 Working Party 2 Intel Labs, 2111 N.E. 25th Avenue, mailstop: JF3-377 Hillsboro, OR-97124, USA Tel: +1 (503)-264-9896 E-mail: paul.k.reddy(a)intel.com

1 0

Re: [Mobility] ITU-T SG16 WP2 Q.2/Q.5/Q.G Conference Call meeting s information
by Reddy, Paul K 27 Nov '01

27 Nov '01

Dear ITU-T SG16 WP2 Colleagues and Mobility Experts, Sorry for the delay in sending this email to the reflector and also due the outages of the SG16 reflector last week the last sent email could not be posted on this reflector. Please accept our apologies. As Rapporteur of Question_5/SG16 (Mobility for Multimedia Systems and Services) agreed in Dublin, Ireland Rapporteur's meeting to organize 3 two hours conference call meetings during Nov, Dec and January months before ITU-T SG16 face to face meeting during February, 2002 in Geneva, Switzerland. The goal of following conference call meetings are to make progress on the following recommendations: 1. H.MMS.0: User/Service Mobility Management for H.323 Multimedia Systems. 2. H.MMS.1: Terminal Mobility Management for H.323 Multimedia Systems. 3. H.MMS.2: Inter-working and Interoperability between Mobility Management for Multimedia systems and Cellular PLMNs. 4. H.MMS.3: Presence and Instant Messaging Services for mobile and non-mobile Multimedia systems. 5. H.MMS.4: Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems. For the status of the above recommendations and related documents, please see the enclosed Dublin's Q.5 Rapporteur's meeting report. Also, please go to URL http://standard.pictel.com/ftp/avc-site/0110_Dub <http://standard.pictel.com/ftp/avc-site/0110_Dub> for Q.5/16 documents. Guidelines for contributing and participating in the following Conference calls: 1. Companies and individual experts are welcome to contribute by uploading the contributions to ftp site: ftp://standard.pictel.com/avc-site/Incoming/Q5conf/ By due dates of each conference call meetings Contributions submission due dates: * For November 30, 2001 conference call is midnight (Pacific standard time) of Nov 28, 2001 * For December 18, 2001 conference call is midnight (Pacific standard time) of Dec 14, 2001 * For January 25, 2002 conference call is midnight (Pacific standard time) of Jan 18, 2001 2. Reply to this email to paul.k.reddy(a)intel.com <mailto:paul.k.reddy@intel.com> and get confirmation of your attendance on each of the conference call meetings in order to reserve the bridge port for a guarantee access during the conference call meetings. 3. Agenda for each Conference call meeting: * Introduction * Review contributions in the following order(Note: continue where we left off in one conference call meeting to another) i. H.MMS.1 (Terminal Mobility for H.323 MM systems) and H.22x.x (Mobility Management protocol and procedures) contributions. This recommendation is targeted for approval during Feb, 2002 SG16 meeting in Geneva. ii. H.MMS.0 (User Mobility, Service Mobility for Multimedia systems) contributions. This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iii. H.MMS.3 (Presence and IM services for mobile and non-mobile Multimedia Systems (e.g., H.323 systems)). This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iv. H.MMS.4 (Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems). This recommendation is targeted for approval during Feb, 2003 SG16 meeting in Geneva. v. H.MMS.2 (Inter-working and Interoperability between Mobility Management for MM systems and Cellular PLMNs). This recommendation is targeted for approval during October, 2003 SG16 meeting in Geneva. If you have any questions, please email Q.5/16 Rapporteur (Mr. Paul K. Reddy) at paul.k.reddy(a)intel.com <mailto:paul.k.reddy@intel.com> Conference call Bridge information: Conference call Meeting 1: Start: Nov 30, 2001 07:00 Pacific Standard Time End: Nov 30, 2001 09:00 Pacific Standard Time Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 9899887 --------------------------------------------------- Conference Call Meeting 2: Start: Dec 18, 2001 07:00 Pacific Standard Time End: Dec 18, 2001 09:00 Pacific Standard Time User Instructions: Date: Tuesday, December 18, 2001 Lines: 10 Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 6449818 ----------------------------------------------------- Conference Call Meeting 3: Start: Jan 25, 2002 07:00 Pacific Time End: Jan 25, 2002 09:00 Pacific Time Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 3708752 ----------------------------------------------------- regards, Paul Paul K. Reddy Rapporteur of Q.5/16 ITU-T SG16 Working Party 2 Intel Labs, 2111 N.E. 25th Avenue, mailstop: JF3-377 Hillsboro, OR-97124, USA Tel: +1 (503)-264-9896 E-mail: paul.k.reddy(a)intel.com

1 0

Test Ignore
by Allen, Wayne 27 Nov '01

27 Nov '01

Test *^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^ Wayne Allen Network Software Engineer Intel Corporation - Internet and Communications Lab email: wayne.allen(a)intel.com phone: 503-264-8660 *^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^

1 0

Have you ever tried Videosinferencing over ADSL?
by Dr. Heinz Weber 27 Nov '01

27 Nov '01

Hi, my Name is Heinz Weber, I'm the telemedicine-coordinator of our University and as well of the German society of surgery. Apart from Video over ISDN we have been working a lot on Video over ATM and Video over IP. Now I was really interested whether there were some groups having tried out "Video over DSL" already. A second Question was where I could get a description of G.703-Standard and whether there are possibilities to transfer G.703-Data over IP Thank you and please subscribe me to your mailing-list

1 0

ITU-SG16 List Back Online
by Meyer, Greg W 26 Nov '01

26 Nov '01

ITU-SG16 Experts: I apologize for any inconvenience with the ITU-SG16 mail list. The mail server was upgraded over the holiday weekend but a glitch (IOW human error) occurred. As of this afternoon (Pacific time zone), the list is again up and running. If you tried to send mail and have not received the confirmation message from LISTSERV by now, you will need to resend the message. Again, please accept my apologies for any inconvenience. Greg Meyer Intel Labs

1 0

ITU-SG16 Mail Server Scheduled Downtime
by Meyer, Greg W 21 Nov '01

21 Nov '01

All ITU-SG16 Users: The ITU-SG16 mail list server will go down on Wednesday, November 21st starting at 12pm Pacific Standard Time. I don't know the length of the downtime but anticipate it to be no more than a few hours. I apologize for any inconvenience. The server team will notify me when the server is back up and I will send out a notification. Please contact me if you have any questions. Best Regards, Greg Meyer Intel Labs ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Test - ITU-SG16 working?
by Meyer, Greg W 16 Nov '01

16 Nov '01

This site has been inactive since November 1st. Just checking to see if it works. If you have tried to email to the ITU-SG16 mail list without success, please email me at greg.w.meyer(a)intel.com. Thanks, Greg Meyer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Trial Conclusion for New ITU-SG16 Mail List Procedures
by Meyer, Greg W 01 Nov '01

01 Nov '01

All ITU-SG16 Mail List Subscribers: The October trial for the new procedures has concluded. The new procedures include a "confirmation" message from LISTSERV that must be replied to with an "OK" in the body of the message. The goal was to reduce the number of unauthorized mailings to this list (spam and viruses). After monitoring the mail list, appears we have met this goal. During the trial, there have been no unauthorized messages (not counting a few test messages). Conversely, there was one reported case when LISTSERV did not respond with the confirmation message within 10 minutes. I believe this was due to the Nimda virus on our servers at that time (we've since cleaned all that up). I will continue to monitor this parameter carefully. If you send a message to the list and don't receive the confirmation message from LISTSERV quickly, please let me know. There was also one known usage error when replying to the confirmation message. Just to be sure, type "OK" without the quote marks on the first line of your confirmation reply to LISTSERV with nothing else on that line. I will also look into clarifying the subscription and other auto-response messages to reduce confusion. We will continue to use the new two-step procedure on this mail list. This method has shown that it offers higher security with low user impact and minimal administration. If you have any comments, please forward them to me. Best Regards, Greg Meyer Intel Corporation greg.w.meyer(a)intel.com -----Original Message----- From: Meyer, Greg W [mailto:greg.w.meyer@INTEL.COM] Sent: Tuesday, October 02, 2001 12:07 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: New ITU-SG16 Mail List Procedures Implemented for Trial Period All ITU-SG16 Mail List Users: Please note that the mail list, itu-sg16(a)mailbag.intel.com, has a new two-step proceedure for sending mail to the list. Here's how it works: 1. Compose your message. 2. Send it to ITU-SG16(a)MAILBAG.INTEL.COM 3. You will receive a "confirmation" message from LISTSERV(a)MAILBAG.INTEL.COM 4. Reply to the confirmation message with "OK" (without the quotes) in the body. OK, that's four steps but only two "sends." Each confirmation message contains the instructions on how to reply. This procedure will help reduce spam and other unauthorized mail. For security purposes, NO ONE should have any mail list (esp. the ITU-SG16 mail list) in their email address book. Most viruses use the address book information to propogate so we strongly request that you look through your address book and remove this and all other mail lists. This new procedure will be tried through the month of October. Please let me know (directly) if there's any mail list service that is being prohited or significantly inhibited. I'll be especially intested in long times (>10 minutes) before receiving the confirmation message. Our testing to date shows that listserv responds quickly. I was strongly(!) motivated to make this change after that last spam ("Excellent Colon Cleanser"). Thanks, Greg Meyer Intel Corporation mailto:greg.w.meyer@intel.com +1.503.264.9506 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: [imtch323implementors] Conflict resolution for symmetrical OL Cs - which is the preferred mode?
by Lyons, Terry 01 Nov '01

01 Nov '01

Paul, >From B.2.2.2/H.245v7 again: simultaneousCapabilities is a set of AlternativeCapabilitySet. It is used to list the simultaneous capabilities of the terminal. An AlternativeCapabilitySet is a sequence of CapabilityTableEntryNumbers. Only those CapabilityTableEntrys that have been defined shall be present in an AlternativeCapabilitySet, although it is possible to define CapabilityTableEntrys and refer to them in the same TerminalCapabilitySet. If a terminal has a preference for the mode it would like to transmit or receive, and wishes to express this when transmitting its capabilities, it may do so by listing elements in AlternativeCapabilitySets in order of decreasing preference. So I think you mean to refer to the order in AlternativeCapabilitySet. The question remains: how to compare capabilities that are listed in different AlternativeCapabilitySets. These AlternativeCapabilitySets may occur in different elements of simultaneousCapabilities (unlikely) or in different CapabilityDescriptors (more likely). Would you agree that the preference between two capabilities is structured as follows? 1. compare descriptor numbers - lowest is preferred 2. else compare simultaneousCapability element index - lowest is preferred 3. else compare AlternativeCapabilitySet element index - lowest is preferred There is text in B.2.2.2 to support #1 and #3 of the above. Nothing is said about #2. And since other permutations of logic are possible, some clarification would help. - TLyons(a)sonusnet.com +1 732 625-3003 ext 212 -----Original Message----- From: Paul Long [mailto:plong@IPDIALOG.COM] Sent: Thursday, November 01, 2001 3:04 PM To: ITU-SG16(a)mailbag.cps.INTEL.COM Subject: Re: [imtch323implementors] Conflict resolution for symmetrical OLCs - which is the preferred mode? Terry, B.2.2.2 refers to capabilityDescriptors, which are numbered according to preference, whereas C.4.1.3 refers to simultaneousCapabilities, which are arranged in order of preference. There is no conflict. Paul Long ipDialog, Inc. -----Original Message----- From: Lyons, Terry [mailto:TLyons@sonusnet.com] Sent: Thursday, November 01, 2001 10:41 AM To: ITU-SG16(a)mailbag.cps.INTEL.COM Cc: 'imtch323implementors(a)mail.imtc.org'; Lyons, Terry Subject: [imtch323implementors] Conflict resolution for symmetrical OLCs - which is the preferred mode? Please consider these two extracts from RECOMMENDATION H.245 - VERSION 7 B.2.2.2 Capability Descriptors If a terminal has a preference for the mode it would like to transmit or receive, and wishes to express this when transmitting its capabilities, it may do so by giving CapabilityDescriptors that relate to its preferred mode or modes small values of capabilityDescriptorNumber. C.4.1.3 Conflict resolution When the master and the slave have indicated choices of receive capabilities for a particular media type, the slave should attempt to open a logical channel for the master's most preferred capability for which it has capability, as given by the order the master has expressed its capabilities; and the master should attempt to open a logical channel for its most preferred capability for which the slave has capability, as given by the order it has expressed its capabilities. --------------------------------------- The new wording "the order the master has expressed its capabilities" is insufficiently defined to act on and seems to conflict with the old definition of prefered mode. As explained in section B.2.1, a terminal's total capabilities may be expressed over an extended period of time, not in a single message (Terminals may dynamically add capabilities during a communication session by issuing additional CapabilityDescriptor structures, or remove capabilities by sending revised CapabilityDescriptor structures). And the capability table entries by themselves are incomplete without accompanying descriptors (The terminal's total capabilities are described by a set of CapabilityDescriptor structures). Both capabililty table entries and capability descriptors are already numbered. Is the Order of Expression an additional attribute that needs to be inferred when processing the pieces of a received Terminal Capability Set? It seems that some clarification is needed. Preferrably, C.4.1.3 should refer back to B.2.2.2 for an operational definition. - TLyons(a)sonusnet.com +1 732 625-3003 ext 212 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0