- sg16-avd - lists.packetizer.com

Re: [Fwd: [Fwd: [Fwd: Re: 14TD058]]]
by Edgar Martinez [1] 09 Jul '99

09 Jul '99

John, see comments below: John Talbot wrote: > Edgar, > > Could you clarify whether your contribution represents an agreed TIPHON > position. > My contribution is a request for Clarification on where the SG11/Q5 IN or in general where does IN components fit in the Tiphon IP Reference Architecture. So we can get some work done before we meet in Berlin. > > Also, it should also be noted that the ITU-T SG11 functional architecture > which you refer to in your contribution does not reflect the decomposed > media gateway architecture. The diagram I provided in 14TD058 shows the SG, MGC and MGW TIPHON's decomposed gateway. In SG11/Q5 they refer to the old C Ref. on a non-decomposed GW. This the type of understanding SG11 has and we need to work together to get agreement and bring very one upto date. > The potential impact this would have on the > location of the CCF does not appear to have been considered by the ITU-T > liaison. The CCF that SG11/Q5 provided in the liaison statement diagram shows the CCF on the IN side, the CCF for IN suspends the calls and/or report events to the SSF. Looking at it from the Tiphon or Megaco IP side the MGW provides the same CCF function using the N interface to report to the MCG. From the SG11/Q5 diagram it is referred to as Call/Bearer (C/B) GF with a C Ref. point to H.323 GK F. I think the information we get from TIPHON and SG16 will help to work out these misunderstandings. Regards, Ed > > > Cheers > > John Talbot > Nortel Networks > > > -----Original Message----- > > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > > Sent: 09 July 1999 10:17 > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: [Fwd: [Fwd: [Fwd: Re: 14TD058]]] > > > > Dear All, > > > > Some TIPHON work going on to address Q5/11 > > Requirements for the Functional Architecture > > for IN support of IP-networks. Tiphon-14 meeting > > is from July 18-24. The Documents are in: > > > > http://docbox.etsi.org/tech-org/tiphon/Document/tiphon/05-9907-Amsterdam/ > > > > If you are interested. > > > > Regards, > > Ed > > > > -------- Original Message -------- > > Subject: Re: 14TD058 > > Date: Fri, 09 Jul 1999 04:47:24 -0400 > > From: "Edgar Martinez [1]" <martinze(a)cig.mot.com> > > Organization: NSS-NAT > > To: Matt Holdrege <matt(a)ascend.com> > > CC: TIPHON(a)LIST.ETSI.FR > > References: <3782F084.E48DC7D5(a)cig.mot.com> > > <199907090807.DAA01209(a)alba.cig.mot.com> > > > > Matt, > > > > Can we get more details on the meeting dates start and end date. > > I am attending a SG16 rapporteur's meeting in Berlin from Aug. 2-6. > > We are looking at the same Liaison statement that SG11/Q5 > > has provided to TIPHON. Basically, I asked SG16 to use the T > > IPHON reference architecture in the response back to SG11/Q5. > > We will have a final reply from SG16 to SG11 > > by the end of the Berlin meeting. > > So I will like to keep SG16 informed. > > > > Regards, > > Ed > > > > Matt Holdrege wrote: > > > > > I tried to include TIPHON architectural issues in the 5/11 architecture > > at > > > the last 5/11 meeting. We couldn't come to a full agreement during the > > > meeting and asked for contributions for the next rapporteur's meeting. > > > > > > Unfortunately the next 5/11 meeting is during the next TIPHON meeting. I > > > was thinking about leaving TIPHON early and going to the 5/11 meeting > > which > > > starts on the 21st. But I'm not sure of my schedule yet. > > > > > > If anyone in TIPHON is going to the WP4/11 meeting, let us know if you > > can > > > represent our architecture. > > > > > > > >At 03:46 PM 7/8/99 -0400, Edgar Martinez [1] wrote: > > > >Dear all, > > > > > > > >The following document has been uploaded onto Inbox: > > > > > > > >Document: > > > >TITLE:Clarification on where the SG11/Q5 IN components > > > > may fit in the Tiphon Reference Architecture. > > > > > > > >Regards, > > > >Ed > > > > > > > > > > > >-- > > > >Edgar Martinez - Principal Staff Engineer > > > >Email mailto:martinze@cig.mot.com > > > >FAX 1-847-632-3145 - - Voice 1-847-632-5278 > > > >1501 West Shure Drive, Arlington Hgts. IL 60004 > > > >Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > > > >Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/ > > > > > > > >------------------------------------------------------------------- > > > >Mail archive for TIPHON can be browsed at the following url : > > > > > > > > http://www.etsi.org/tiphon/mailing.htm > > > >------------------------------------------------------------------- > > > > -- > > Edgar Martinez - Principal Staff Engineer > > Email mailto:martinze@cig.mot.com > > FAX 1-847-632-3145 - - Voice 1-847-632-5278 > > 1501 West Shure Drive, Arlington Hgts. IL 60004 > > Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > > Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/ -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

Re: [Fwd: [Fwd: [Fwd: Re: 14TD058]]]
by John Talbot 09 Jul '99

09 Jul '99

Edgar, Could you clarify whether your contribution represents an agreed TIPHON position. Also, it should also be noted that the ITU-T SG11 functional architecture which you refer to in your contribution does not reflect the decomposed media gateway architecture. The potential impact this would have on the location of the CCF does not appear to have been considered by the ITU-T liaison. Cheers John Talbot Nortel Networks > -----Original Message----- > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > Sent: 09 July 1999 10:17 > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: [Fwd: [Fwd: [Fwd: Re: 14TD058]]] > > Dear All, > > Some TIPHON work going on to address Q5/11 > Requirements for the Functional Architecture > for IN support of IP-networks. Tiphon-14 meeting > is from July 18-24. The Documents are in: > > http://docbox.etsi.org/tech-org/tiphon/Document/tiphon/05-9907-Amsterdam/ > > If you are interested. > > Regards, > Ed > > -------- Original Message -------- > Subject: Re: 14TD058 > Date: Fri, 09 Jul 1999 04:47:24 -0400 > From: "Edgar Martinez [1]" <martinze(a)cig.mot.com> > Organization: NSS-NAT > To: Matt Holdrege <matt(a)ascend.com> > CC: TIPHON(a)LIST.ETSI.FR > References: <3782F084.E48DC7D5(a)cig.mot.com> > <199907090807.DAA01209(a)alba.cig.mot.com> > > Matt, > > Can we get more details on the meeting dates start and end date. > I am attending a SG16 rapporteur's meeting in Berlin from Aug. 2-6. > We are looking at the same Liaison statement that SG11/Q5 > has provided to TIPHON. Basically, I asked SG16 to use the T > IPHON reference architecture in the response back to SG11/Q5. > We will have a final reply from SG16 to SG11 > by the end of the Berlin meeting. > So I will like to keep SG16 informed. > > Regards, > Ed > > Matt Holdrege wrote: > > > I tried to include TIPHON architectural issues in the 5/11 architecture > at > > the last 5/11 meeting. We couldn't come to a full agreement during the > > meeting and asked for contributions for the next rapporteur's meeting. > > > > Unfortunately the next 5/11 meeting is during the next TIPHON meeting. I > > was thinking about leaving TIPHON early and going to the 5/11 meeting > which > > starts on the 21st. But I'm not sure of my schedule yet. > > > > If anyone in TIPHON is going to the WP4/11 meeting, let us know if you > can > > represent our architecture. > > > > >At 03:46 PM 7/8/99 -0400, Edgar Martinez [1] wrote: > > >Dear all, > > > > > >The following document has been uploaded onto Inbox: > > > > > >Document: > > >TITLE:Clarification on where the SG11/Q5 IN components > > > may fit in the Tiphon Reference Architecture. > > > > > >Regards, > > >Ed > > > > > > > > >-- > > >Edgar Martinez - Principal Staff Engineer > > >Email mailto:martinze@cig.mot.com > > >FAX 1-847-632-3145 - - Voice 1-847-632-5278 > > >1501 West Shure Drive, Arlington Hgts. IL 60004 > > >Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > > >Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/ > > > > > >------------------------------------------------------------------- > > >Mail archive for TIPHON can be browsed at the following url : > > > > > > http://www.etsi.org/tiphon/mailing.htm > > >------------------------------------------------------------------- > > -- > Edgar Martinez - Principal Staff Engineer > Email mailto:martinze@cig.mot.com > FAX 1-847-632-3145 - - Voice 1-847-632-5278 > 1501 West Shure Drive, Arlington Hgts. IL 60004 > Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

Call_id for H.245 messages
by Sunil Mahajan 09 Jul '99

09 Jul '99

Hi, We are new to this list and need some clarification related to H.245 call signaling on TCP/IP channel.. Considering a separate H.245 connection is required per call implies that each connection shall have a separate port to associate H.245 messages with its call. This requires the endpoint application to maintain an association between ports and the call_id/call_ref value. Isn't it useful to have some correlation_id or call_ref (or call_id) value in each of the H.245 messages to associate H.245 messages with call instances at the endpoints (gateways). Regards, Ravi Kiran Sunil Mahajan

1 0

[Fwd: [Fwd: [Fwd: Re: 14TD058]]]
by Edgar Martinez [1] 09 Jul '99

09 Jul '99

Dear All, Some TIPHON work going on to address Q5/11 Requirements for the Functional Architecture for IN support of IP-networks. Tiphon-14 meeting is from July 18-24. The Documents are in: http://docbox.etsi.org/tech-org/tiphon/Document/tiphon/05-9907-Amsterdam/ If you are interested. Regards, Ed -------- Original Message -------- Subject: Re: 14TD058 Date: Fri, 09 Jul 1999 04:47:24 -0400 From: "Edgar Martinez [1]" <martinze(a)cig.mot.com> Organization: NSS-NAT To: Matt Holdrege <matt(a)ascend.com> CC: TIPHON(a)LIST.ETSI.FR References: <3782F084.E48DC7D5(a)cig.mot.com> <199907090807.DAA01209(a)alba.cig.mot.com> Matt, Can we get more details on the meeting dates start and end date. I am attending a SG16 rapporteur's meeting in Berlin from Aug. 2-6. We are looking at the same Liaison statement that SG11/Q5 has provided to TIPHON. Basically, I asked SG16 to use the T IPHON reference architecture in the response back to SG11/Q5. We will have a final reply from SG16 to SG11 by the end of the Berlin meeting. So I will like to keep SG16 informed. Regards, Ed Matt Holdrege wrote: > I tried to include TIPHON architectural issues in the 5/11 architecture at > the last 5/11 meeting. We couldn't come to a full agreement during the > meeting and asked for contributions for the next rapporteur's meeting. > > Unfortunately the next 5/11 meeting is during the next TIPHON meeting. I > was thinking about leaving TIPHON early and going to the 5/11 meeting which > starts on the 21st. But I'm not sure of my schedule yet. > > If anyone in TIPHON is going to the WP4/11 meeting, let us know if you can > represent our architecture. > >At 03:46 PM 7/8/99 -0400, Edgar Martinez [1] wrote: > >Dear all, > > > >The following document has been uploaded onto Inbox: > > > >Document: > >TITLE:Clarification on where the SG11/Q5 IN components > > may fit in the Tiphon Reference Architecture. > > > >Regards, > >Ed > > > > > >-- > >Edgar Martinez - Principal Staff Engineer > >Email mailto:martinze@cig.mot.com > >FAX 1-847-632-3145 - - Voice 1-847-632-5278 > >1501 West Shure Drive, Arlington Hgts. IL 60004 > >Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ > >Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/ > > > >------------------------------------------------------------------- > >Mail archive for TIPHON can be browsed at the following url : > > > > http://www.etsi.org/tiphon/mailing.htm > >------------------------------------------------------------------- -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

Re: H.323v3 for decision in September
by Callaghan, Robert 09 Jul '99

09 Jul '99

Dale, This discussion has introduced a degree of confusion. The meeting report from Santiago clearly states that H.323v3 and H.225.0v3 will be decided in 2/00. Now we are discussing a decision of 9/99. Which is correct? Are all the additions people feel are needed immediately going to be provided in Berlin for inclusion in v3? Will be have a full meeting including Q.13, Wp2, and SG16 in September? If so, how many days are scheduled for the meeting? Another words --- What's happening. Bob ------------------------------------------------------------------ Robert Callaghan Siemens Information & Communication Networks Enterprise Switching Networks, Architecture Tel: +1.561.997.3756 Fax: +1.561.997.3403 Email: Robert.Callaghan(a)ICN.Siemens.com ------------------------------------------------------------------ -----Original Message----- From: Paul E. Jones [mailto:paul.jones@TIES.ITU.INT] Sent: Tuesday, June 29, 1999 11:38 AM To: ITU-SG16(a)mailbag.cps.intel.com Subject: Re: H.323v3 for decision in September Pete, I would venture to say that, given the nature of this work, it would not be included in H.323v3. However, it could certainly be included in H.323v4, which, as I noted below, will be determined in February. There are actually a number of new features people want to add to H.323, which is one reason for adjusting the schedule. By deciding v3 in September, we can focus our attention on v4, which will give us the time to enrich H.323 in a reasonable timeframe. It would be nearly impossible to properly add all of the new features to v3 between now and February. Would you be willing to bring that document as a contribution toward v4? Paul ----- Original Message ----- From: Pete Cordell <pete(a)TECH-KNOW-WARE.COM> To: <ITU-SG16(a)MAILBAG.INTEL.COM> Sent: Tuesday, June 29, 1999 4:01 AM Subject: Re: H.323v3 for decision in September > One issue I was discussing with my BT colleagues was installing an open > framework for extensibility and feature negotiation into H.323v3. The > motivation for this was to enable transport of SS7, but also other protocols > such as DPNSS, (is CAS a digital one?) and so on. If we were to go ahead I > guess we would have presented something in Berlin. > > Given that September is fast approaching waiting for such a scheme to > transport things like SS7 does not seem too onerous. > > Unfortunately my colleagues are out this week, but I will attach the latest > text so that people can have early sight of it. > > Regards, > > Pete > > ============================================= > Pete Cordell > pete(a)tech-know-ware.com > ============================================= > > -----Original Message----- > From: Paul E. Jones <paul.jones(a)TIES.ITU.INT> > To: ITU-SG16(a)MAILBAG.INTEL.COM <ITU-SG16(a)MAILBAG.INTEL.COM> > Date: 29 June 1999 01:25 > Subject: H.323v3 for decision in September > > > >Folks, > > > >We may attempt to decide H.323v3 in September and determine version 4 in > >February. Mr. Skran has asked that I post the current draft so that people > >can review the document. This document must be delivered to the ITU by 30 > >June 1999. (Please note that Annex C/H.323 is also a candidate for > decision > >in Septemer.) > > > >This document contains only minor editorial changes to the document that > was > >determined in Santiago. Nonetheless, I encourage you to review the > document > >for any errors or omissions. > > > >The change marks indicate all changes that have been made since version 2. > > > >Please direct any comments on the document to me. > > > >The document can be found here: > > > >ftp://standards.pictel.com/avc-site/Incoming/H.323v3-990628.doc > > > >Best Regards, > >Paul E. Jones > >DataBeam Corporation > > >

2 1

APC document number
by Noriko Hosokawa 08 Jul '99

08 Jul '99

Dear Mr. Luthi In response to your request, APC-1566 has been allocated to your contribution. APC-1566 > Source: Editor H.243 > Title: Draft revised ITU-T Recommendation H.243 (white doc.) > Purpose: Draft > Question: 14 > Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1555 ITU-T SG8 Recommendation T.38 Indications in Recommendation H.245 (TD1/WP2 of the SG16 Santiago meeting) 1556 ITU-T SG11 Support of IN services for H.323 and other IP Network based terminals (TD4/WP2 of the SG16 Santiago meeting) 1557 ITU-T SG9 Draft New Rec. J.Web "Distribution of Sound and Television Programmes over the Internet "Webcasting"" (TD22/WP2 of the SG16 Santiago meeting) 1558 ITU-T SG2 Routing of Multimedia Connections When Interworking with PSTN, ATM, and IP Networks (TD24/GEN of the SG16 Santiago meeting) 1559 SG16 WP2 Proposed Organisation going forward to new Study Period 1560 Editor (E Martinez) Annex-H (User and Service Mobility in H.323) Proposed Architecture 1561 Editor (G Hellstrom) H.323 Annex G Text Conversation and Text SET 1562 L M Ericsson H.gcp Modification proposals for Text Conversation 1563 L M Ericsson First draft of a H.246 Annex for text conversation and text telephony 1564 L M Ericsson H.224 Modified for text conversation 1565 (P Jones) T.35 (1999) country codes 1566 Editor H.243 Draft revised ITU-T Recommendation H.243 (white doc.) ------------------------------------------------------------------------

1 0

Re: Defining what is a TCS=0 for the IG
by Pete Cordell 08 Jul '99

08 Jul '99

Dear All, We are happy to go with an empty TCS being just the protocol identifier and sequence number AS LONG AS we can send immediately prior to that a cap set delta that removes all existing capabilities WITHOUT waiting for it to be acked. i.e. something like: EP A EP B -- TCS delta to zero --> -- TCS prot and seq only --> ..(transmission delay etc)... <-- TCS Ack for delta --- <-- TCS Ack for prot and seq only -- We want to do this as we feel that the removal of the capabilities should result in the majority of the TCS0 functionality on well behaved H.245 endpoints that don't know about TCS0 (although there is an issue as to whether there are any such terminals!) whereas the other form of TCS will have no effect. If this is acceptable to people, then I will write up some text to say that an empty cap set consists only of protocol identifier and sequence number. Regards, Pete ============================================= Pete Cordell pete(a)tech-know-ware.com =============================================

1 0

APC document numbers
by Sakae OKUBO 08 Jul '99

08 Jul '99

Dear Mr. Hellstrom, Dear Mr. Jones, GH> Please register the following documents for the Berlin meeting, GH> and return APC numbers. APC-1561, 1562, 1563 have been allocated. GH> Note that the H.224 document is probably handled by Q11. Do they have GH> their own document handling? Mr. Geary will also allocate a Q11-J-nn number to your contribution, I expect. APV-1561--------------------------------- > Title: H.323 Annex G Text Conversation and Text SET. > > Source: Gunnar Hellstr $BSN (B, L M Ericsson > > Abstract: The Text Annex to H.323 with modifications reflecting progress in > IETF about RTP Payload format and genreral editorials. > > Purpose: Proposal for white doc. > > ---------------------------------------------------------------------------- APC-1562--------------------------------- > Title: H.gcp Modification proposals for Text Conversation. > > Source: Gunnar Hellstr $BSN (B, L M Ericsson > > Abstract: Modification proposals to H.gcp to define text conversation and > text telephone support. > > Purpose: Proposal to include in white doc. > ---------------------------------------------------------------------------- APC-1563--------------------------------- > Title: H.246 Annex Text > > Source: Gunnar Hellstr $BSN (B, L M Ericsson > > Abstract: First draft of a H.246 Annex for text conversation and text > telephony > > Purpose: Discussion > ---------------------------------------------------------------------------- APC-1564--------------------------------- > Title: H.224 Modified for text conversation > > Source: Mickey Nasiri, L M Ericsson > > Abstract: White doc proposal for H.224 with added standard client ID for > T.140 text and correction for an old data syntax description error. > > Purpose: Proposal > ---------------------------------------------------------------------------- PJ> I would like to request an APC number for a contribution PJ> on the topic of addressing T.35 (1999) country codes. APC-1565 has been allocated to your contribution. Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1555 ITU-T SG8 Recommendation T.38 Indications in Recommendation H.245 (TD1/WP2 of the SG16 Santiago meeting) 1556 ITU-T SG11 Support of IN services for H.323 and other IP Network based terminals (TD4/WP2 of the SG16 Santiago meeting) 1557 ITU-T SG9 Draft New Rec. J.Web "Distribution of Sound and Television Programmes over the Internet "Webcasting"" (TD22/WP2 of the SG16 Santiago meeting) 1558 ITU-T SG2 Routing of Multimedia Connections When Interworking with PSTN, ATM, and IP Networks (TD24/GEN of the SG16 Santiago meeting) 1559 SG16 WP2 Proposed Organisation going forward to new Study Period 1560 Editor (E Martinez) Annex-H (User and Service Mobility in H.323) Proposed Architecture 1561 Editor (G Hellstrom) H.323 Annex G Text Conversation and Text SET 1562 L M Ericsson H.gcp Modification proposals for Text Conversation 1563 L M Ericsson First draft of a H.246 Annex for text conversation and text telephony 1564 L M Ericsson H.224 Modified for text conversation 1565 (P Jones) T.35 (1999) country codes ------------------------------------------------------------------------

1 0

Moving on
by Chris Purvis 07 Jul '99

07 Jul '99

All, I will be leaving Madge Networks at the end of the week, and with it (at least for the moment) the H.323 arena - so don't be surprised that I'll no longer be posting to these lists! Although I've enjoyed working with you all, a new opportunity beckons... Regards, Chris -- Until Friday 9th July 1999: Dr Chris Purvis - Senior Development Engineer, WAVE CC Software Madge Networks Ltd, Wexham Springs, Framewood Road, Wexham, Berks. ENGLAND Phone: +44 1753 661 359 email: cpurvis(a)madge.com >From Monday 12th July 1999: 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 email: Chris.Purvis(a)isdn-comms.co.uk ------------------------------------------------------------------------- for list subscription instructions, send email to h323implementors-request(a)imtc.org with text "info"

2 1

Re: H.323v3 for decision in September - Annex G Text
by Michael Sung 07 Jul '99

07 Jul '99

How do I unsubscribe from this list? -----Original Message----- From: Gunnar Hellstrom [mailto:gunnar.hellstrom@OMNITOR.SE] Sent: Tuesday, June 29, 1999 2:59 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: H.323v3 for decision in September - Annex G Text It might be wise to tie in Annex G Text Conversation and Text SET with a few words into the body of H.323 V3. Do we have a policy to introduce Annexes with some text in the main body or can it hang loose as it does now? I am not ready with the RTP payload type for text in IETF until later this year, and was aiming at a February decision for H.323 V3 with Annex G. Regards Gunnar Hellström At 20:20 1999-06-28 -0400, Paul E. Jones wrote: >Folks, > >We may attempt to decide H.323v3 in September and determine version 4 in >February. Mr. Skran has asked that I post the current draft so that people >can review the document. This document must be delivered to the ITU by 30 >June 1999. (Please note that Annex C/H.323 is also a candidate for decision >in Septemer.) > >This document contains only minor editorial changes to the document that was >determined in Santiago. Nonetheless, I encourage you to review the document >for any errors or omissions. > >The change marks indicate all changes that have been made since version 2. > >Please direct any comments on the document to me. > >The document can be found here: > >ftp://standards.pictel.com/avc-site/Incoming/H.323v3-990628.doc > >Best Regards, >Paul E. Jones >DataBeam Corporation > > ----------------------------------------------- Gunnar Hellstrom LM Ericsson E-mail gunnar.hellstrom(a)omnitor.se Tel +46 751 100 501 fax +46 8 556 002 06

1 0