- sg16-avd - lists.packetizer.com

draft-hellstrom-avt-rtp-text-01.txt Result of Oslo discussion.
by Gunnar Hellstrom 26 Jul '99

26 Jul '99

The draft rtp specification for text conversation that is discussed in the IETF AVT group is now available in the following URL. www.omnitor.se/english/standards/rtp/draft-hellstrom-avt-rtp-text-01.txt It is referenced in the H.323 Annex G Text Conversation draft that is entered as a contribution to the ITU-T Q13/16 meeting next week as document APC1561. I would like to receive comments on this draft. I am aware of the following points that might need discussion. 1. Timestamp clock frequency. I had put a low figure 10 Hz in the specification. It was questioned and proposed that a figure of some thousands should be selected. I am willing to accept that, and propose that 1000 Hz is used. A millisecond per tick is a handy figure. This will however lead to the timestamp offset in the redundancy data headers that use only 14 bits, flip around in only 16 seconds. If correct timing information is wanted, the data flush procedure described in next section should be used. 2. Retransmission of text before a pause. Text does not flow continously, but only when a user enter text. Therefore, a recommended procedure could specify that for the redundancy scheme, it is advisable to send the ISO 10646 synch character FEFF after some inactivity timer to flush out redundant data - see section 3.4. 3. Recommended procedures section. In the draft that accompanies this mail, section 3 documents the recommended procedures for using the payload format. Does the group want it to be kept there or shall it be moved to the specification specifying use of this RTP Payload? ( The first user being H.323 Annex G) Any other comments are welcome. Gunnar Hellström ----------------------------------------------- Gunnar Hellstrom LM Ericsson E-mail gunnar.hellstrom(a)omnitor.se Tel +46 751 100 501 fax +46 8 556 002 06

1 0

uploaded new document
by Mickey Nasiri 26 Jul '99

26 Jul '99

Dear colleagues, I have uploaded the document Q11-J-07 to ftp://standards.pictel.com/q11-site/dropbox/ This document is the same as document APC-1564 (White H.224 modified for text conversation with correction). Best regards //Mickey -- //Mickey Nasiri Ericsson Telecom AB Home Communications SE-126 25 STOCKHOLM Tel: +46-8-719 38 61 Mob: +46-70-319 38 61 email: mickey.nasiri(a)ericsson.com

1 0

APC-1609 Uploaded
by Robert J. Abrams 26 Jul '99

26 Jul '99

APC-1609, a proposal to support Q.931 TNS and NSF IEs in H.225.0, has been uploaded to the Incoming directory of the FTP site. Bob Abrams Lucent Technologies

1 0

APC-1580 - Megaco/H.248 reqs - uploaded
by Nancy-M Greene 26 Jul '99

26 Jul '99

I've just uploaded APC-1580 - Media Gateway control protocol architecture and requirements. It is the same as the internet-draft ftp://ftp.ietf.org/internet-drafts/draft-ietf-megaco-reqs-05.txt put out June 25th. Mr. Okubo, Please note that the source for this document is the IETF Megaco Working Group, and NOT Nortel Networks as I previously indicated. Nancy -------------------------------------------------------------------------- Nancy M. Greene Internet & Service Provider Networks, Nortel Networks T:514-271-7221 (internal:ESN853-1077) E:ngreene@nortelnetworks.com

1 0

APC1634
by El-Gebaly, Hani 26 Jul '99

26 Jul '99

Dear Q12/13/14 experts, I uploaded APC1634.doc to the Incoming directory. This is a proposal to add security tokens to the releaseComplete message. Regards, Hani ElGebaly Intel Corp.

1 0

Comment on APC-1636 (Was: Documents uploaded)
by Pete Cordell 26 Jul '99

26 Jul '99

Well it seems the Telcordia crowd still haven't read my proposal!!!!!! What I am proposing is an ASN.1-LIKE specification. That means similar to, but not exactly the same as. In my proposal your line: quarenteenProcessing QuarenteenProcessing OPTIONAL would be represented as: quarenteenProcessing AS q QuarenteenProcessing OPTIONAL. and q would be used as the on the wire tag for precisely the reasons quoted in APC-1636. If there are worries that this isn't ASN.1 (if that is worth worrying about!), then all you have to do is go through removing any AS specifiers either manually or automatically. It's no big deal. Pete ============================================= Pete Cordell pete(a)tech-know-ware.com ============================================= -----Original Message----- From: Hong Liu <lhong(a)RESEARCH.TELCORDIA.COM> To: ITU-SG16(a)MAILBAG.INTEL.COM <ITU-SG16(a)MAILBAG.INTEL.COM> Date: 26 July 1999 17:01 Subject: Documents uploaded >Hi, all, > >I have uploaded two contributions from Telcordia Technologies to the ftp >incoming directory for the Berlin meeting: > >APC-1635: Mapping H.245 Semantics to SDP >APC-1636: Comparing EBNF and ASN.1 for Text Encoding > >Cheers, > >--Hong >

2 1

Comment on apc-1612 Re: Documents uploaded
by Steve.Carr＠ICN.SIEMENS.COM 26 Jul '99

26 Jul '99

I'm not sure why the MG needs to know the OPC/DPC and CIC, there could just be a common naming of DS0s between the MGC and MG, and the MGC would map to OPC/DPC/CIC. However, if they are needed, then the Network Indicator (2 bits) should also be included. In addition, in the US (and China) SS7 Point Codes are 24 bits, and the CIC is 14 bits, not 14, 14 and 12 as shown in section 3.4 Steve Carr Unisphere Solutions John Segers <jsegers(a)LUCENT.COM> on 07/26/99 10:33:24 AM 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: Steve Carr/Internet/ICN) Subject: Documents uploaded All, I just uploaded the following documents for the Berlin meeting to <ftp://standard.pictel.com/ftp/avc-site/Incoming/>: * apc-1612.zip Title: Proposing structured media and bearers for H.248 Source: Lucent Technologies, Intel Corporation, FORE Systems Inc., Teles AG * apc-1613.zip Title: proposal for PUT and DELETE commands in H.248 Source: Lucent Technologies * apc-1614.zip Title: Scripting framework for H.248 Source: Lucent Technologies * apc-1615.zip Title: H.242 package for support of decomposed H.323-to-H.320 gateways in H.248 Source: Lucent Technologies * apc-1632.zip Title: Structured syntax for H.248 Source: Lucent Technologies, Tech-Know-Ware, Intel Corporation, FORE Systems, VocalTec Communications, Teles AG Regards, John Segers -- John Segers email: jsegers(a)lucent.com Lucent Technologies Room HE 306 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954

1 0

APC-1633 uploaded
by Dave Walker 26 Jul '99

26 Jul '99

Dear Colleagues, I have uploaded APC-1633, Proposals for Enhanced Feature Support in H.323, to the Incoming directory. Dave Walker Mitel Corporation Ontario, CANADA

1 0

APCs 1581, 1582 uploaded
by Rex Coldren 26 Jul '99

26 Jul '99

Dear Q.12-14 experts, I've uploaded the following proposals to the Incoming directory: - APC-1581 H.323 v3 and H.225 v3 Support for Improved Alias Registrations - APC-1582 H.323 v3 and H.225 v3 Endpoint Registration Clarifications Regards, Rex

1 0

Documents uploaded
by Hong Liu 26 Jul '99

26 Jul '99

Hi, all, I have uploaded two contributions from Telcordia Technologies to the ftp incoming directory for the Berlin meeting: APC-1635: Mapping H.245 Semantics to SDP APC-1636: Comparing EBNF and ASN.1 for Text Encoding Cheers, --Hong

1 0