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

B.3.1/H.245v8 - Error in the description of the encryptionSync field
by Frank Derks 27 Apr '01

27 Apr '01

B.3.1/H.245 describes the use of fields in the openLogicalChannel message. The text about the encryptionSync field looks like a literal copy of the corresponding text for the OpenLogicalChannelAck message. This would not seem to be correct, because it talks about the acknowledgement of the opening of a channel by the slave. Shouldn't the text read: "The encryptionSync field is (shall?) used by the master to provide the ebcryption key value and the synchronization point at which the key should be used. ....." Regards, Frank ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: Two documents at /0105_Por
by OKUBO Sakae 26 Apr '01

26 Apr '01

Dear Mr. Sayre, > > 2) WhitePaperMMGateway.zip -- "Multimedia Support Using the > > Decomposed $B!! (BGateway Architecture" by Mr. Clifford Sayre et al > >I just wanted to clarify the status and intent of item #2. I do intend to >present this document at the Porto Seguro meeting. It will be a Delay >Contribution with a source of Lucent Tech. Lucent needs to have this >approved by the US government process (SGD) for approving company >contributions to ITU SG 16 meetings and I am working this process in >conjunction with Terry Anderson (the lead Lucent delegate). > >The purpose of the document is to answer some delegate questions and >issues raised in the Launceston meeting on contribution AVD-2057. Thus it >is for discussion and the text will not go directly into the draft H.248 >annex that I am working on. Sorry about using the term "white paper". I >realized after reading your email that the term white paper has had a >different meaning in the context of SG 16 documents. Thank you for your clarification. When your delayed contribution is provided, I will replace WhitePaperMMGateway.zip with that. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 ********************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

silenceSuppression in h2250LogicalChannelParameters
by Frank Derks 25 Apr '01

25 Apr '01

Can any one explain what the meaning of the silenceSuppression element in h2250LogicalChannelParameters is? If set to TRUE, does this indicate that silence suppression is supported on the channel, but that this is actually dependent on the support of this functionality by the codec? So why duplicate the information? Regards, Frank ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

2 1

potential change to SCTP
by Glen Freundlich 25 Apr '01

25 Apr '01

Dear Colleagues, There are apparently are some problems with the checksum mechanism defined in SCTP. If a new mechanism is deemed necessary, a new RFC could be issued and it would likely not be backward compatible with RFC 2960. This may effect any work in SG16 that references SCTP. Discussions of SCTP are taking place over either the sigtran mailing list or the tsv mailing list. Check the IETF site to find contact info on these working groups. Regards, Glen

1 0

Message from Mr. Bigi
by OKUBO Sakae 25 Apr '01

25 Apr '01

Dear SG16 experts, We have been advised as follows: >Dear Colleagues, > >I am leaving for Study Group 13 meeting in Caracas on 11 May. I would >appreciate if you could send your documents, if possible, by 10 May. I >would also be thankful if you could let the editors and other participants >know. > >Best regards > >Fabio Bigi >TSB, Senior Counsellor Your kind cooperation is requested. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 ********************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: H.MMS.3: Presence and IM for H.323 Mobile systems.
by SAMOU Jean-claude FTRD/DAC/ISS 24 Apr '01

24 Apr '01

Hi, Folks: I fully support what Roy is saying here. I assume that H.MMS.3 as well as H.MMS.2 will be based on H.MMS.1 protocol extensions. My understanding is that this 'new' H.MMS.1 protocol should be designed in a way that it is applicable not only to H.323 but to other applications protocols (e.g., H.234, H.310) as well. This will give more flexibility since it will not be specific to a particular application (i.e. no need of having a specific mobility management protocol for H.323, another one for H.324, etc.). Therefore, this 'new' protocol should be made independent as much as possible of others and not be called as H.225.0 annex G or its extension. Please also see an earlier message sent by François Bougant which gives more clarification on these issues. I appreciate this good start of Q5/16 work. Best regards, Jean-Claude Samou FTR&D -----Message d'origine----- De: Roy, Radhika R, ALCOO [mailto:rrroy@ATT.COM] Date: mardi 17 avril 2001 15:25 À: ITU-SG16(a)MAILBAG.INTEL.COM Objet: Re: H.MMS.3: Presence and IM for H.323 Mobile systems. Hi, Manoj: I am providing a very quick comment. It is a good proposal and you are assuming that H.MMS.1 will be the base protocol to be used. With respect to H.MMS.1 protocol, I like to mention that the mobility management part of H.MMS.1 will be "called" a NEW protocol and will NOT be called as "H.225.0 Annex G or its extension." Based on this assumption, probably you can start your work. As time goes on, more comments will be provided. I appreciate your work. Best regards, Radhika R. Roy AT&T -----Original Message----- From: Paul, Manoj [mailto:mpaul@TRILLIUM.COM] Sent: Monday, April 16, 2001 10:28 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: H.MMS.3: Presence and IM for H.323 Mobile systems. Hi All, The purpose of this mail is to initiate work on H.MMS.3 standard, which is a part of H.MMS series for H.323 mobility systems. H.MMS.3 will address Presence and Instant Messaging services in H.323 Mobility multimedia systems. H.MMS.3 standard shall address the architecture, procedures and new message/ information elements to enable H.323 as the transport protocol for Presence and Instant Messaging in mobile environment. As editor of H.MMS.3 document, I solicit contributions and discussions to begin work in this area. Enclosed is the Scope and Terms of Reference document that was presented in SG16 Launceston meeting for H.MMS.3. thanks Manoj Paul. Trillium Digital Systems, (an Intel company). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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: H.MMS.3: Presence and IM for H.323 Mobile systems.
by Paul, Manoj 22 Apr '01

22 Apr '01

Hi Chern, According to my understanding, when you say "Context Transfer", it refers to some protocol having procedures and methods to trasfer the "Context". And in IM and Presence, this context is the relevant IM and Presence information. Is that understanding correct? If yes, then the H.MMS.3 will define the methods and procedures in H.323 protocol to enable H.323 to act as a "Context Transfer" protocol.(Like SIP defines new methods SUBSCRIBE etc. to act as transport protocol for IM and Presence). I think the concept of IM and Presence shall be derived from IETF IMPP, but work needs to be done to define their mapping in context of H.323 signalling. Could you elaborate when you said "Hopefully some meaningful protocol name would be link to it.Example (M.RCTP - Robust Context Transfer Protocol)". thanks Manoj. -----Original Message----- From: cny [mailto:cny@DCS.SHEF.AC.UK] Sent: Saturday, April 21, 2001 12:58 PM To: ITU-SG16(a)mailbag.cps.INTEL.COM Subject: Re: H.MMS.3: Presence and IM for H.323 Mobile systems. Hi all, May I know how much this thing will link to IETF BXXP (Blocks Extensible Exchange Protocol), and IETF IMPP (Instant Messaging and Presence Protocol) ????? As for the new protocol mentioned below, I suppose what is normally involved is known as Context Transfer, Hopefully some meaningful protocol name would be link to it. Example (M.RCTP - Robust Context Transfer Protocol) When is the dead line for the Brazil Meeting, I am still rushing out some spec of this new protocol. Cheers Chern Nam Yap ----- Original Message ----- From: "Roy, Radhika R, ALCOO" <rrroy(a)ATT.COM> To: <ITU-SG16(a)mailbag.cps.intel.com> Sent: Tuesday, April 17, 2001 3:24 PM Subject: Re: H.MMS.3: Presence and IM for H.323 Mobile systems. > Hi, Manoj: > > I am providing a very quick comment. It is a good proposal and you are > assuming that H.MMS.1 will be the base protocol to be used. > > With respect to H.MMS.1 protocol, I like to mention that the mobility > management part of H.MMS.1 will be "called" a NEW protocol and will NOT be > called as "H.225.0 Annex G or its extension." > > Based on this assumption, probably you can start your work. > > As time goes on, more comments will be provided. > > I appreciate your work. > > Best regards, > Radhika R. Roy > AT&T > > -----Original Message----- > From: Paul, Manoj [mailto:mpaul@TRILLIUM.COM] > Sent: Monday, April 16, 2001 10:28 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: H.MMS.3: Presence and IM for H.323 Mobile systems. > > > Hi All, > The purpose of this mail is to initiate work on H.MMS.3 standard, which > is > a part of H.MMS series for H.323 mobility systems. H.MMS.3 will address > Presence > and Instant Messaging services in H.323 Mobility multimedia systems. > H.MMS.3 standard shall address the architecture, procedures and new > message/ > information elements to enable H.323 as the transport protocol for Presence > and > Instant Messaging in mobile environment. > As editor of H.MMS.3 document, I solicit contributions and discussions > to > begin work in this area. Enclosed is the Scope and Terms of Reference > document > that was presented in SG16 Launceston meeting for H.MMS.3. > > thanks > Manoj Paul. > Trillium Digital Systems, (an Intel company). > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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

2 1

Two documents at /0105_Por
by OKUBO Sakae 21 Apr '01

21 Apr '01

Dear SG16 experts, I have placed the following two documents at the Porto Seguro meeting directory http://standard.pictel.com/ftp/avc-site/0105_Por/, 1) H323_AnnexQ.zip -- Draft H.323 Annex Q "Far End Camera Control and H.281 / H.224" by Editor Roni Even 2) WhitePaperMMGateway.zip -- "Multimedia Support Using the Decomposed Gateway Architecture" by Mr. Clifford Sayre et al I wonder if 2) has been, or will be submitted for the Porto Seguro meeting as "white contribution" or is an informational document for the study of experts on the mailing list. For safety, I have dealt it as above. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 ********************************************************* My contract with TAO finished on 31 March. Please change my e-mail address as above, though okubo(a)giti.or.jp will continue to work for some time. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: H.MMS.3: Presence and IM for H.323 Mobile systems.
by Roy, Radhika R, ALCOO 21 Apr '01

21 Apr '01

Hi, Manoj: I am providing a very quick comment. It is a good proposal and you are assuming that H.MMS.1 will be the base protocol to be used. With respect to H.MMS.1 protocol, I like to mention that the mobility management part of H.MMS.1 will be "called" a NEW protocol and will NOT be called as "H.225.0 Annex G or its extension." Based on this assumption, probably you can start your work. As time goes on, more comments will be provided. I appreciate your work. Best regards, Radhika R. Roy AT&T -----Original Message----- From: Paul, Manoj [mailto:mpaul@TRILLIUM.COM] Sent: Monday, April 16, 2001 10:28 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: H.MMS.3: Presence and IM for H.323 Mobile systems. Hi All, The purpose of this mail is to initiate work on H.MMS.3 standard, which is a part of H.MMS series for H.323 mobility systems. H.MMS.3 will address Presence and Instant Messaging services in H.323 Mobility multimedia systems. H.MMS.3 standard shall address the architecture, procedures and new message/ information elements to enable H.323 as the transport protocol for Presence and Instant Messaging in mobile environment. As editor of H.MMS.3 document, I solicit contributions and discussions to begin work in this area. Enclosed is the Scope and Terms of Reference document that was presented in SG16 Launceston meeting for H.MMS.3. thanks Manoj Paul. Trillium Digital Systems, (an Intel company). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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

2 1

Architectures for Multimedia Gateways
by Sayre, Clifford L, III (Clifford) 20 Apr '01

20 Apr '01

Dear SG 16 Experts, At the Launceston meeting two contributions, AVD-2057 & AVD-2056, were presented proposing enhancements to support interworking for H.324 Annex C terminals and multimedia gateways. AVD-2057 describes several H.248 packages that can be used in a decomposed gateway with an MGC and MG to support this type of multimedia interworking. The delegates in Launceston requested additional information on the background behind these packages; consequently, we have prepared the attached white paper. The white paper describes some of the issues behind supporting multimedia interworking gateways for H.324 & H.323 and thus the rationale for the work behind AVD-2057. <<WhitePaperMultimediaGateways.zip>> Comments are welcome. The co-authors of the white paper are listed on the footer of the paper. Regards, Cliff Sayre Clifford Sayre Lucent Technologies Phone (732) 332-6060 clsayre(a)lucent.com

1 0