December 2002 - sg16-avd - lists.packetizer.com

Re: [h323forum] Re: Codec negotiation question
by Paul E. Jones 17 Dec '02

17 Dec '02

Paul, Do you mean RFC 2508? In any case, Robert's point is indeed valid. This is where having a specialize GW that multiplexes the RTP streams for delivery over the long-haul is something practical. Perhaps we could take that up as a work item with SG16? It would be reasonable to specify how such an Gateway might function in order to trunk a large number of active calls over long distance. Anyone interested in such a work item? Paul ----- Original Message ----- From: "Paul Long" <plong(a)packetizer.com> To: <h323forum(a)mail.imtc.org> Sent: Monday, December 16, 2002 7:49 PM Subject: [h323forum] Re: Codec negotiation question > Robert, > > Excellent point. I hadn't thought of that. I wonder what happened to > cRTP. Anybody know? That would sure help. > > Paul > > > > > On Mon, 16 Dec 2002 12:53:34 -0500 > > "Paul Long" <plong(a)packetizer.com> wrote: > > > > > I know lots of folks would like a means of expressing exact > > > packetization, but isn't the solution trivial? All you need is a > small > > > FIFO and a few lines of code to re-packetize according to any > internal > > > requirements. Just write incoming frames regardless of size, e.g., > > > 30fpp, to the FIFO, and read whatever size frames you want, e.g., > 80fpp > > > from the FIFO (only read if there are at least X fpp in the FIFO). > > > > DSP hardware is not the only reason for wanting to have the remote > > endpoint send larger packets. We have many clients on long haul > internet > > links (300ms+ ping times), often with a slow tail circuit (ISDN or > even > > modem) and you REALLY want the other end to send more than one G.723.1 > > frame per packet to reduce the significant overhead that there is in > the > > RTP. > > > > > > > > > > It is unfortunate but true that there is no way of expressing a > > > minimum > > > > acceptable number of frames per packet. > > > > > > > > Regards, > > > > Chris > > > > > > > > Paul Long wrote: > > > > > Davide, > > > > > > > > > > There is nothing in the standard that requires the acceptance > of an > > > OLC > > > > > or precludes terminating the call for any reason whatsoever so > both > > > EPs > > > > > are technically compliant. > > > > > > > > > > Packetization in TCS and OLC expresses the _maximum_ frames per > > > packet, > > > > > but several vendors don't understand this simple concept and > > > continue > > > > > to produce products that expect an exact packetization. There > is a > > > good > > > > > chance that that is why EP A is rejecting the OLC. It wants the > > > channel > > > > > opened at exactly 80fpp, although there is no way to express > this > > > in > > > > > H.323. IMO, if this is the reason, that product is broken. > > > > > > > > > > Paul > > > > > > > > > > > > > > >>Hi all, > > > > >> > > > > >>I have a question about a codec negotiation. > > > > >>During H.245 negotiation, endpoint A (master) exports g711A-law > > > with > > > > > > > > > > packetization 80, endpoint B (slave) exports g711A-law with > > > > > packetization 30. After that, endpoint A opens a channel with > > > > > packetization = 20 ms. Endpoint B acknoledges the OLC and tries > to > > > open > > > > > a channel with packetization = 30 ms. > > > > > > > > > >>Here Endpoint A rejects the OLC and the call is disengaged. > > > > >> > > > > >>Does anybody can tell me which endpoint dosn't behave according > to > > > > > > > > > > the H323 standard? > > > > > > > > > >>Thank you in advance. > > > > >> > > > > >>Davide > > > > > > > > > > > > > > > --- > > > > > You are currently subscribed to h323forum as: cwp@isdn- > comms.co.uk > > > > > To unsubscribe send a blank email to %%email.unsub%% > > > > > > > > > > > > > -- > > > > Dr Chris Purvis -- Development Manager > > > > ISDN Communications Ltd, The Stable Block, Ronans, Chavey Down > Road > > > > Winkfield Row, Berkshire. RG42 6LY ENGLAND > > > > Phone: +44 1344 899 007 > > > > Fax: +44 1344 899 001 > > > > > > > > > --- > > > You are currently subscribed to h323forum as: equival(a)equival.com.au > > > To unsubscribe send a blank email to %%email.unsub%% > > > > > > ---------- > > Robert Jongbloed Equivalence Pty. Ltd. > > Architect Open Phone Abstraction Library (OPAL) & OpenH323 > > Open Source Telecommunication Protocol Libraries > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > Quicknet's revolutionary MicroTelco Services offers > > LOW WORLDWIDE RATES ANY TIME OF THE DAY with > > No monthly fees! No monthly minimums! No connection fees! > > US rates as low as 2.9 cents a minute! To see more rates, > > visit www.microtelco.com > > > > > > ****LIVE VIDEO CONFERENCE NOW AVAILABLE***** > > CUseeMe v5.0 software is an affordable easy-to-use software > > application providing live visual communication between friends, > > family and colleagues worldwide. To learn more, visit, > > www.cuseemeworld.com > > --- > You are currently subscribed to h323forum as: paulej(a)packetizer.com > To unsubscribe send a blank email to leave-h323forum-27407I(a)mail.imtc.org > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

AW: Rapporteur meeting in February 2003
by Sebestyen Istvan ICN M SR 3 17 Dec '02

17 Dec '02

Dear Mr. Okubo, Thanks. For mid February also a one day WP3 meeting in Geneva was planned to make "consent" for H.264. Has that also gone away? Regards, Istvan Sebestyen -----Ursprungliche Nachricht----- Von: OKUBO Sakae [mailto:okubo@MXZ.MESH.NE.JP] Gesendet: Montag, 16. Dezember 2002 05:12 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: Fwd: Rapporteur meeting in February 2003 Dear Q.D,F,G,1-5/16 experts, The conclusion last week in Awajishima, Japan, was that Q.6/WP3 would not meet as a whole next February. So we will meet in San Jose during 11-14 February 2003 according to 2/ below. Mr. Jones will issue the meeting notice very soon. At 16:23 +0900 02/12/07, OKUBO Sakae wrote: >[...] >Rapporteurs have been seeking the best place to hold this meeting. >This is to report the progress. > >1/ As default, we will meet in Geneva to handle video related topics >with Q.6 experts who will meet there for WP3 consent of H.264. > >2/ In case Q.6 and WP3 should not meet at that time depending on the >interim achievements, Q.D,F,G,1-5/16 will meet in the US, San Jose or >Raleigh, thanks to the offer of Cisco. > >3/ Q.6 is now working in Japan and will have a definite answer next >Friday if they meet in Geneva during the mentioned week next >February. So our final decision will be made at that time. Please >stay tuned on this mailinglist. > >4/ For this Rapporteur meeting, Paul Jones acts as meeting organizer, >and myself as document manager. -- Best regards, OKUBO Sakae e-mail: okubo(a)giti.waseda.ac.jp ******************************************************************* YRP Office Global Information and Telecommunication Institute (GITI) Waseda University YRP Ichibankan 312 Tel: +81 468 47 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 468 47 5413 239-0847 Japan GITI Headquarter 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ******************************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

2 1

AW: Rapporteur meeting in February 2003
by Sebestyen Istvan ICN M SR 3 16 Dec '02

16 Dec '02

So, how then are the plans concretely? On March 11-15, 2003 there is an MPEG Meeting in Pattaya. So, H.264 goes to FDIS. But: 1) When and where is the JVT Meeting? 2) When and where is the WP3 Meeting? Kind regards, Istvan -----Ursprüngliche Nachricht----- Von: Gary Sullivan [mailto:garysull@microsoft.com] Gesendet: Montag, 16. Dezember 2002 12:05 An: Sebestyen Istvan ICN M SR 3; ITU-SG16(a)echo.jf.INTEL.COM Betreff: RE: Rapporteur meeting in February 2003 Yes, we are planning for WP3 consent for H.264/AVC sometime between March 15 and March 30. This will let us consent a better draft and coordinate better with the ISO/IEC approval process. Best Regards, -Gary S. _____ From: Sebestyen Istvan ICN M SR 3 [mailto:istvan.sebestyen@SIEMENS.COM] Sent: Mon 12/16/2002 2:32 AM To: ITU-SG16(a)echo.jf.INTEL.COM Subject: AW: Rapporteur meeting in February 2003 Dear Mr. Okubo, Thanks. For mid February also a one day WP3 meeting in Geneva was planned to make "consent" for H.264. Has that also gone away? Regards, Istvan Sebestyen -----Ursprungliche Nachricht----- Von: OKUBO Sakae [ mailto:okubo@MXZ.MESH.NE.JP <mailto:okubo@MXZ.MESH.NE.JP> ] Gesendet: Montag, 16. Dezember 2002 05:12 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: Fwd: Rapporteur meeting in February 2003 Dear Q.D,F,G,1-5/16 experts, The conclusion last week in Awajishima, Japan, was that Q.6/WP3 would not meet as a whole next February. So we will meet in San Jose during 11-14 February 2003 according to 2/ below. Mr. Jones will issue the meeting notice very soon. At 16:23 +0900 02/12/07, OKUBO Sakae wrote: >[...] >Rapporteurs have been seeking the best place to hold this meeting. >This is to report the progress. > >1/ As default, we will meet in Geneva to handle video related topics >with Q.6 experts who will meet there for WP3 consent of H.264. > >2/ In case Q.6 and WP3 should not meet at that time depending on the >interim achievements, Q.D,F,G,1-5/16 will meet in the US, San Jose or >Raleigh, thanks to the offer of Cisco. > >3/ Q.6 is now working in Japan and will have a definite answer next >Friday if they meet in Geneva during the mentioned week next >February. So our final decision will be made at that time. Please >stay tuned on this mailinglist. > >4/ For this Rapporteur meeting, Paul Jones acts as meeting organizer, >and myself as document manager. -- Best regards, OKUBO Sakae e-mail: okubo(a)giti.waseda.ac.jp ******************************************************************* YRP Office Global Information and Telecommunication Institute (GITI) Waseda University YRP Ichibankan 312 Tel: +81 468 47 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 468 47 5413 239-0847 Japan GITI Headquarter 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ******************************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Fwd: Rapporteur meeting in February 2003
by OKUBO Sakae 16 Dec '02

16 Dec '02

Dear Q.D,F,G,1-5/16 experts, The conclusion last week in Awajishima, Japan, was that Q.6/WP3 would not meet as a whole next February. So we will meet in San Jose during 11-14 February 2003 according to 2/ below. Mr. Jones will issue the meeting notice very soon. At 16:23 +0900 02/12/07, OKUBO Sakae wrote: >[...] >Rapporteurs have been seeking the best place to hold this meeting. >This is to report the progress. > >1/ As default, we will meet in Geneva to handle video related topics >with Q.6 experts who will meet there for WP3 consent of H.264. > >2/ In case Q.6 and WP3 should not meet at that time depending on the >interim achievements, Q.D,F,G,1-5/16 will meet in the US, San Jose or >Raleigh, thanks to the offer of Cisco. > >3/ Q.6 is now working in Japan and will have a definite answer next >Friday if they meet in Geneva during the mentioned week next >February. So our final decision will be made at that time. Please >stay tuned on this mailinglist. > >4/ For this Rapporteur meeting, Paul Jones acts as meeting organizer, >and myself as document manager. -- Best regards, OKUBO Sakae e-mail: okubo(a)giti.waseda.ac.jp ******************************************************************* YRP Office Global Information and Telecommunication Institute (GITI) Waseda University YRP Ichibankan 312 Tel: +81 468 47 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 468 47 5413 239-0847 Japan GITI Headquarter 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ******************************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Fwd: AAP Comments during last call on H245v9
by OKUBO Sakae 14 Dec '02

14 Dec '02

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" This is to forward Mr. Anderson's announcement, which should have been distributed through this reflector but looks not having gone through. Please also note that you can find the mentioned Avaya's comments in Word form at the following place: http://standard.pictel.com/ftp/avc-site/0210_Gen/lc1_H245_Avaya.zip """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" >Date: Fri, 13 Dec 2002 18:20:24 -0500 >From: Terry L Anderson <tlatla(a)verizon.net> >X-Accept-Language: en-us, en >To: ITU SG-16 <ITU-SG16(a)mailbag.cps.intel.com>, tsg16q3@itu.int,tsgwp2@itu.int >Subject: AAP Comments during last call on H245v9 >X-Authentication-Info: Submitted using SMTP AUTH PLAIN at >out002.verizon.net from [138.89.124.43] at Fri, 13 Dec 2002 17:20:35 >-0600 >X-OriginalArrivalTime: 13 Dec 2002 23:15:45.0551 (UTC) >FILETIME=[908EF9F0:01C2A2FD] >Sender: owner-tsg16q3(a)itu.int >Reply-To: Terry L Anderson <tlatla(a)verizon.net> >X-Biglobe-VirusCheck: Sat, 14 Dec 2002 08:21:17 +0900 > >A new version of H.245 (version 9) was consented at the October >Study Group 16 meeting in Geneva. One official comment was submitted >by Avaya against H.245 V9 during the last call period. According to >ITU procedures we need to resolve this issue and then have an >"additional review" (a second last call) before it can be considered >approved. > >The issue raised by Avaya concerned the use of encrypted media >channels for MoIP and included specific suggestions for additional >ASN.1 items and description in H.245 to support this. The changes >are not extensive. > >From the comment: > >>Introduction >>As it now stands, version 9 of H.245 does not permit the >>specification of encryption of media channels using the new >>Modem-over-IP (MoIP) data types RedundancyEncoding, >>MultiplePayloadStream, and FECdata. Inasmuch as these types of >>channels can be subject to eavesdropping, and can carry the same >>information as other audio or data channels, it seems appropriate >>to provide the means to encrypt them. > >The issue and suggested changes have been discussed by several of >parties involved with the MoIP work (Paul Jones, Cisco, Martin >Euchner and Sasha Ruditsky along with Bob Gilman from Avaya) and >they support the suggested changes. > >As rapporteur, I am proposing that adopt the suggested changes and >submit the revised version for the Additional Review at the next >review period (I believe in January) unless there are objections >from others. Any discussion should be sent to the >ITU-SG16(a)mailbag.cps.intel.com reflector. I am including the >tsg16q3 and tsg16wp2 lists in this message so that all interested >parties are aware of the process. If I do not see any objections by >17:00 UT a week from today, Dec 20, we will proceed with the >additional review of the text as revised. > >For those with TIES logins, the Avaya comment document can be accessed at: > http://www.itu.int/itudoc/itu-t/aap/sg16aap/recaap/h245v9/lcc/index.html > >For any that may not, I will summarize the changes below: >1. Annex A (page 47) >Add the new data types RedundancyEncoding, MultiplePayloadStream, >and FECdata to H235Media. This will permit the specification of >encryption for these data types in the same way it is specified for >other media types. > >As follows: >H235Media ::=SEQUENCE >{ > encryptionAuthenticationAndIntegrity >EncryptionAuthenticationAndIntegrity, > mediaType CHOICE > { > nonStandard NonStandardParameter, > videoData VideoCapability, > audioData AudioCapability, > data DataApplicationCapability, > ..., > redundancyEncoding RedundancyEncoding, > multiplePayloadStream MultiplePayloadStream, > fec FECData > }, > > ... >} >---------------------------------------- >2. Annex B, Section B.3.1 (page 108) >Add a description of the use of H235Media in DataType to indicate >that the channel is to be encrypted. > >As follows: >A dataType of h235Media is used to specify encryption of the logical >channel; the actual >data type is indicted within H235Media, along with the encryption >specification. >----------------------------------------- >3. Annex B, Section B.3.1 (page 111) >Add a description of the use of redundancyEncoding for media >encryption when the dataType specifies multiple payload types within >the channel. > >As follows: >When encryption is specified for a channel carrying multiple >payloads, redundancy encoding using RFC 2198 is used to preserve the >actual payload types transmitted. The Encapsulating payload type is >set to the value specified in the syncFlag field of the >encryptionSync element. > >-- >------------------------------------------------------- >Terry L Anderson tlatla(a)verizon.net >Voice: +1 908.766.4463 Mobile: +1 908.342.9595 >http://www.gti.net/tla >------------------------------------------------------- -- Best regards, OKUBO Sakae e-mail: okubo(a)giti.waseda.ac.jp ******************************************************************* YRP Office Global Information and Telecommunication Institute (GITI) Waseda University YRP Ichibankan 312 Tel: +81 468 47 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 468 47 5413 239-0847 Japan GITI Headquarter 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ******************************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

AAP comments during last call on H245v9
by Terry L Anderson 13 Dec '02

13 Dec '02

A new version of H.245 (version 9) was consented at the October Study Group 16 meeting in Geneva. One official comment was submitted by Avaya against H.245 V9 during the last call period. According to ITU procedures we need to resolve this issue and then have an "additional review" (a second last call) before it can be considered approved. The issue raised by Avaya concerned the use of encrypted media channels for MoIP and included specific suggestions for additional ASN.1 items and description in H.245 to support this. The changes are not extensive. From the comment: > Introduction > As it now stands, version 9 of H.245 does not permit the specification > of encryption of media channels using the new Modem-over-IP (MoIP) > data types RedundancyEncoding, MultiplePayloadStream, and FECdata. > Inasmuch as these types of channels can be subject to eavesdropping, > and can carry the same information as other audio or data channels, it > seems appropriate to provide the means to encrypt them. The issue and suggested changes have been discussed by several of parties involved with the MoIP work (Paul Jones, Cisco, Martin Euchner and Sasha Ruditsky along with Bob Gilman from Avaya) and they support the suggested changes. As rapporteur, I am proposing that adopt the suggested changes and submit the revised version for the Additional Review at the next review period (I believe in January) unless there are objections from others. Any discussion should be sent to the ITU-SG16(a)mailbag.cps.intel.com reflector. I am including the tsg16q3 and tsg16wp2 lists in this message so that all interested parties are aware of the process. If I do not see any objections by 17:00 UT a week from today, Dec 20, we will proceed with the additional review of the text as revised. For those with TIES logins, the Avaya comment document can be accessed at: http://www.itu.int/itudoc/itu-t/aap/sg16aap/recaap/h245v9/lcc/index.html For any that may not, I will summarize the changes below: 1. Annex A (page 47) Add the new data types RedundancyEncoding, MultiplePayloadStream, and FECdata to H235Media. This will permit the specification of encryption for these data types in the same way it is specified for other media types. As follows: H235Media ::=SEQUENCE { encryptionAuthenticationAndIntegrity EncryptionAuthenticationAndIntegrity, mediaType CHOICE { nonStandard NonStandardParameter, videoData VideoCapability, audioData AudioCapability, data DataApplicationCapability, ..., redundancyEncoding RedundancyEncoding, multiplePayloadStream MultiplePayloadStream, fec FECData }, ... } ---------------------------------------- 2. Annex B, Section B.3.1 (page 108) Add a description of the use of H235Media in DataType to indicate that the channel is to be encrypted. As follows: A dataType of h235Media is used to specify encryption of the logical channel; the actual data type is indicted within H235Media, along with the encryption specification. ----------------------------------------- 3. Annex B, Section B.3.1 (page 111) Add a description of the use of redundancyEncoding for media encryption when the dataType specifies multiple payload types within the channel. As follows: When encryption is specified for a channel carrying multiple payloads, redundancy encoding using RFC 2198 is used to preserve the actual payload types transmitted. The Encapsulating payload type is set to the value specified in the syncFlag field of the encryptionSync element. -- ------------------------------------------------------- Terry L Anderson tlatla(a)verizon.net Voice: +1 908.766.4463 Mobile: +1 908.342.9595 http://www.gti.net/tla ------------------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Re: Rapporteur meeting in February 2003
by Even, Roni 08 Dec '02

08 Dec '02

Mr Okubo, Is the meeting Tuesday till Friday? Thanks Roni Even Polycom > -----Original Message----- > From: OKUBO Sakae [mailto:okubo@MXZ.MESH.NE.JP] > Sent: Saturday, December 07, 2002 9:23 AM > To: ITU-SG16(a)echo.jf.INTEL.COM > Subject: Rapporteur meeting in February 2003 > > > Dear Q.D,F,G,1-5/16 experts, > > At 01:18 +0900 02/10/26, OKUBO Sakae wrote just after the October > SG16 meeting ended: > >Please note that the next Rapporteur meeting is planned during 11-14 > >February 2003. Its details are yet to be fixed. > > Rapporteurs have been seeking the best place to hold this meeting. > This is to report the progress. > > 1/ As default, we will meet in Geneva to handle video related topics > with Q.6 experts who will meet there for WP3 consent of H.264. > > 2/ In case Q.6 and WP3 should not meet at that time depending on the > interim achievements, Q.D,F,G,1-5/16 will meet in the US, San Jose or > Raleigh, thanks to the offer of Cisco. > > 3/ Q.6 is now working in Japan and will have a definite answer next > Friday if they meet in Geneva during the mentioned week next > February. So our final decision will be made at that time. Please > stay tuned on this mailinglist. > > 4/ For this Rapporteur meeting, Paul Jones acts as meeting organizer, > and myself as document manager. > > -- > Best regards, > > OKUBO Sakae > e-mail: okubo(a)giti.waseda.ac.jp > ******************************************************************* > YRP Office > Global Information and Telecommunication Institute (GITI) > Waseda University > YRP Ichibankan 312 Tel: +81 468 47 5406 > 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 468 47 5413 > 239-0847 Japan > > GITI Headquarter > 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 > 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 > 169-0051 Japan > ******************************************************************* > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > For help on this mail list, send "HELP ITU-SG16" in a message to > listserv(a)lists.intel.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

2 1

Rapporteur meeting in February 2003
by OKUBO Sakae 07 Dec '02

07 Dec '02

Dear Q.D,F,G,1-5/16 experts, At 01:18 +0900 02/10/26, OKUBO Sakae wrote just after the October SG16 meeting ended: >Please note that the next Rapporteur meeting is planned during 11-14 >February 2003. Its details are yet to be fixed. Rapporteurs have been seeking the best place to hold this meeting. This is to report the progress. 1/ As default, we will meet in Geneva to handle video related topics with Q.6 experts who will meet there for WP3 consent of H.264. 2/ In case Q.6 and WP3 should not meet at that time depending on the interim achievements, Q.D,F,G,1-5/16 will meet in the US, San Jose or Raleigh, thanks to the offer of Cisco. 3/ Q.6 is now working in Japan and will have a definite answer next Friday if they meet in Geneva during the mentioned week next February. So our final decision will be made at that time. Please stay tuned on this mailinglist. 4/ For this Rapporteur meeting, Paul Jones acts as meeting organizer, and myself as document manager. -- Best regards, OKUBO Sakae e-mail: okubo(a)giti.waseda.ac.jp ******************************************************************* YRP Office Global Information and Telecommunication Institute (GITI) Waseda University YRP Ichibankan 312 Tel: +81 468 47 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 468 47 5413 239-0847 Japan GITI Headquarter 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ******************************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Thanks to Greg Meyer and Chris Hansen
by OKUBO Sakae 07 Dec '02

07 Dec '02

Dear all the subscribers of this mailinglist, This is to announce that the administrator of this mailinglist has changed from Mr. Greg Meyer to Mr. Chris Hansen due to the change of Mr. Meyer's job in Intel. Using this opportunity, I would like to thank Greg for all of his efforts to manage this indispensable tool for the activities of ITU-T SG16 WP2 Questions D,F,G,1-5. Thanks are also to Chris who has kindly undertaken to take care of the mailinglist. Appreciation is extended to Intel Corporation that has been providing the human and network resource to support the SG16 works. Originally KPN had operated this mailinglist service and Intel kindly succeeded it in 1997. -- Best regards, OKUBO Sakae e-mail: okubo(a)giti.waseda.ac.jp ******************************************************************* YRP Office Global Information and Telecommunication Institute (GITI) Waseda University YRP Ichibankan 312 Tel: +81 468 47 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 468 47 5413 239-0847 Japan GITI Headquarter 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ******************************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0