October 1999 - sg16-avd - lists.packetizer.com

Re: H.323v3 Final Text Posted
by Boaz Michaely 11 Oct '99

11 Oct '99

Hi Paul, It is not there now. Has it been moved elsewhere ? Boaz "Paul E. Jones" <paul.jones(a)TIES.ITU.INT> on 10/03/99 04:21:08 PM Please respond to Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.cps.intel.com> To: ITU-SG16(a)mailbag.cps.intel.com cc: (bcc: Boaz Michaely) Subject: H.323v3 Final Text Posted Folks, I posted the final text of H.323v3 here: ftp://standard.pictel.com/avc-site/Incoming/H323v3.zip This document should represent the combination of the white paper contribution, D.314, and two temporary documents submitted at the meeting to make corrections discussed and approved during the Berlin meeting. Please keep in mind that this is not the final text published by the ITU, so it has no official standing. There may still be strictly editorial corrections that may be applied before the final publication of this document. If you see such errors, please forward them to me. If you find technical errors, please notify me of that, as well, so that we can take steps to correct the problem. Best Regards, Paul

3 2

H.243 white doc uplopaded
by Patrick Luthi 11 Oct '99

11 Oct '99

Dear experts, The H.243 white document was uploaded to the Redbank directory of the Q11 FTP site (ftp://standard.pictel.com/lbc-site/1999_10_Redbank/) The file name is q11k04.zip. See you in Red Bank ! Patrick Luthi PictureTel

1 0

Re: submitting APC-1692
by Qiaobing Xie 11 Oct '99

11 Oct '99

Thanks, Chip! -Qiaobing On Oct 11, 4:41pm, Chip Sharp wrote: > Subject: Re: submitting APC-1692 > I've uploaded APC-1692 into the avc-site/incoming directory for Qiaobing. > > Chip > > At 12:08 PM 10/11/99 -0500, Qiaobing Xie wrote: > >Please find in the attached .zip file our APC-1692 submission to > >the Red Bank meeting. I have difficulty to directly upload the > >file into the ftp directory due to our company security control. > > > >Thanks, > > > >=============================================================== > > Qiaobing Xie, Ph.D > > Network Architecture & Technology > > Motorola, Inc. > > 1501 W. Shure Dr., Arlington Heights, IL 60004 > >=============================================================== > > > > > > > >X-Zm-Content-Name: APC-1692.zip > >Content-Description: Data > >Content-Type: application/octet-stream ; name="APC-1692.zip" > >X-Zm-Decoding-Hint: mimencode -b -u > > Support NetAid! http://www.netaid.org > -------------------------------------------------- > Chip Sharp Consulting Engineering > Cisco Systems Telco Bio-region > Reality - Love it or Leave it. > -------------------------------------------------- >-- End of excerpt from Chip Sharp

1 0

submitting APC-1692
by Qiaobing Xie 11 Oct '99

11 Oct '99

Please find in the attached .zip file our APC-1692 submission to the Red Bank meeting. I have difficulty to directly upload the file into the ftp directory due to our company security control. Thanks, =============================================================== Qiaobing Xie, Ph.D Network Architecture & Technology Motorola, Inc. 1501 W. Shure Dr., Arlington Heights, IL 60004 ===============================================================

2 1

APC-1735 (draft H.248)
by John Segers 11 Oct '99

11 Oct '99

Dear SG16 experts, The draft text for H.248 is availabe at <ftp://standards.nortelnetworks.com/megaco/docs/latest/MegacoH248v11.pdf >. From this document I will create APC-1735, showing the changes that were made, and upload that as soon as possible. With apologies for not meeting the deadline with APC-1735. Regards, John Segers -- John Segers email: jsegers(a)lucent.com Lucent Technologies Room HE 344 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954

1 0

Re: APC-1735 (draft H.248)
by Nancy-M Greene 11 Oct '99

11 Oct '99

Please note that the pdf file pointed to below does NOT have the ITU text in it, as it had the IETF text macro on when I created it - you will see the ITU text in APC-1735 though. At least two places where this is an issue is the scope, and the last paragraphs in Annex G. There are probably more places. Nancy -------------------------------------------------------------------------- Nancy M. Greene Internet & Service Provider Networks, Nortel Networks T:514-271-7221 (internal:ESN853-1077) E:ngreene@nortelnetworks.com > ---------- > From: John Segers[SMTP:jsegers@LUCENT.COM] > Sent: Monday, October 11, 1999 4:15 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: APC-1735 (draft H.248) > > Dear SG16 experts, > > The draft text for H.248 is availabe at > <ftp://standards.nortelnetworks.com/megaco/docs/latest/MegacoH248v11.pdf > >. From this document I will create APC-1735, showing the changes that > were made, and upload that as soon as possible. > > With apologies for not meeting the deadline with APC-1735. > > Regards, > > John Segers > -- > John Segers email: jsegers(a)lucent.com > Lucent Technologies Room HE 344 > Dept. Forward Looking Work phone: +31 35 687 4724 > P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954 >

1 0

Uploaded apc-1653
by Tony Crossman 11 Oct '99

11 Oct '99

Dear colleagues, I have uploaded the proposal to include G.722.1 capabilities in the H.323 Implementors Guide. The contribution can be found at the following location: ftp://standard.pictel.com/avc-site/Incoming/APC1653.zip Tony Crossman ********************************************* Antony Crossman PictureTel Corporation 100 Minuteman Road, Andover, MA 01810, USA Tel. +1 (978) 292 4557 Fax. +1 (978) 292 3228 email. tonyc(a)pictel.com *********************************************

1 0

Annex G use of releaseCompleteReason
by Rich Bowen 11 Oct '99

11 Oct '99

In the TerminationCause structure of Annex G, the releaseCompleteReason field is mandatory. However, in the H.225.0 Release Complete message, the ReleaseCompleteReason is optional, although it must be specified if the Cause IE is not included. What should a border element place in the releaseCompleteReason field of the TerminationCause if there was no releaseCompleteReason specified in the Release Complete? Should this field have been optional in Annex G? Rich -------------------------------------------------------------------- Richard K. Bowen Cisco Systems, Inc. rkbowen(a)cisco.com Research Triangle Park, NC --------------------------------------------------------------------

1 0

Upload
by Espen Skjæran (ETO) 11 Oct '99

11 Oct '99

Colleagues, I've uploaded these two documents to Incoming: APC-1696 H.323 Annex K (HTTP based service control) APC-1697 Additions of codepoints to H.225.0 for service control Regards, Espen

1 0

None
by Barry Aronson 11 Oct '99

11 Oct '99

Dear All, APC-1738 has been uploaded to the PictureTel Incoming directory as APC-1738.ZIP. TITLE: H.323 Annex I Terms of Reference, v2 SOURCE: Editor Regards, Barry

1 0