Rapporteur meeting in February 2003
Paul E. Jones
paulej at PACKETIZER.COM
Tue Dec 24 15:19:57 EST 2002
Roni,
Yes, I recall the issues we had with H.263 and I agree we'd want to avoid
that. Even so, if the PT format is recommended by JVT, I would expect that
we can avoid these issues. What was the nature of the changes made before?
Can we avoid such changes in the RTP profile document? Of course, unless
the royalty-free baseline is accepted, I don't expect there to be any reason
to be in a hurry to get the profile work complete.
Paul
----- Original Message -----
From: "Even, Roni" <roni.even at polycom.co.il>
To: "'Paul E. Jones'" <paulej at PACKETIZER.COM>; <ITU-SG16 at echo.jf.INTEL.COM>
Sent: Tuesday, December 24, 2002 7:44 AM
Subject: RE: Rapporteur meeting in February 2003
> Paul,
> The least we will need is to have Stephan's draft in some agreed upon
stage
> like after WG last call before we put in H.225. We had some interop
problem
> in H.263 due to different payload. BTW it will be dynamic PT
> Roni
>
> > -----Original Message-----
> > From: Paul E. Jones [mailto:paulej at PACKETIZER.COM]
> > Sent: Tuesday, December 24, 2002 4:06 AM
> > To: ITU-SG16 at echo.jf.INTEL.COM
> > Subject: Re: Rapporteur meeting in February 2003
> >
> >
> > Roni,
> >
> > It is possible to specify the use of H.264 without an RFC.
> > Even today,
> > there is not RFC for G.723.1... though it has been in the
> > works for several
> > years. All we would need is an agreed-upon payload format and to ask
> > Henning to assign a PT value or decide on the use of a
> > dynamic PT value. We
> > can insert the payload format into H.225.0 if we want and use
> > that until the
> > RFC is available.
> >
> > Paul
> >
> > ----- Original Message -----
> > From: "Even, Roni" <roni.even at POLYCOM.CO.IL>
> > To: <ITU-SG16 at echo.jf.INTEL.COM>
> > Sent: Friday, December 20, 2002 11:35 AM
> > Subject: Re: Rapporteur meeting in February 2003
> >
> >
> > > Hi,
> > > I want to pint out that in order to use H.264 in H.323 and
> > H.320 we need a
> > > final version of H.264 and an RFC describing the RTPformat.
> > So having
> > H.264
> > > in May will not make it usable in a standrad mode unless we
> > can progress
> > on
> > > all fronts.
> > > Roni Even
> > >
> > > -----Original Message-----
> > > From: Gary Sullivan
> > > To: ITU-SG16 at echo.jf.INTEL.COM
> > > Sent: 18/12/2002 03:17
> > > Subject: Re: Rapporteur meeting in February 2003
> > >
> > > Istvan et al,
> > >
> > > The current plan is for JVT to meet in Pattaya with MPEG.
> > WP3 will then
> > > either be in Pattaya on or
> > > about the 15th of March or soon thereafter elsewhere.
> > >
> > > The previous plan was drafted under the expectation that we
> > would need
> > > to deliver FDIS text in
> > > mid-February as an interim editing output on the MPEG side.
> > > We now plan to allow more time for editing and final technical
> > > double-check, so FDIS text is not needed
> > > that soon. Although technical freeze was declared last
> > week, FDIS is
> > > not going to happen until March now
> > > so that we can have a more mature document. This lessens
> > the schedule
> > > pressure on the MPEG side
> > > somewhat. We can benefit from that extra time by doing the same
> > > thing on the ITU side and aligning text delivery and final technical
> > > double-check in both organizations.
> > > This will still enable ITU-T decision no later than May,
> > which is what
> > > it probably would have been anyway
> > > regardless of whether we did consent somwhat earlier.
> > >
> > > Best Regards,
> > >
> > > -Gary
> > >
> > > -----Original Message-----
> > > From: Sebestyen Istvan ICN M SR 3
> > [mailto:istvan.sebestyen at SIEMENS.COM]
> > > Sent: Monday, December 16, 2002 6:46 AM
> > > To: ITU-SG16 at echo.jf.INTEL.COM
> > > Subject: AW: Rapporteur meeting in February 2003
> > >
> > >
> > > 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 at microsoft.com]
> > > Gesendet: Montag, 16. Dezember 2002 12:05
> > > An: Sebestyen Istvan ICN M SR 3; ITU-SG16 at 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 at SIEMENS.COM]
> > > Sent: Mon 12/16/2002 2:32 AM
> > > To: ITU-SG16 at 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 at MXZ.MESH.NE.JP
> > > <mailto:okubo at MXZ.MESH.NE.JP> ]
> > > Gesendet: Montag, 16. Dezember 2002 05:12
> > > An: ITU-SG16 at 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 at 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 at lists.intel.com
> > >
> > >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > For help on this mail list, send "HELP ITU-SG16" in a message to
> > > listserv at lists.intel.com
> > >
> > >
> > >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > For help on this mail list, send "HELP ITU-SG16" in a message to
> > > listserv at lists.intel.com
> > >
> > >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > For help on this mail list, send "HELP ITU-SG16" in a message to
> > > listserv at lists.intel.com
> > >
> > >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > For help on this mail list, send "HELP ITU-SG16" in a message to
> > > listserv at lists.intel.com
> > >
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > For help on this mail list, send "HELP ITU-SG16" in a message to
> > listserv at lists.intel.com
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at lists.intel.com
More information about the sg16-avd
mailing list