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

Re: About Contribution submission
by Sakae OKUBO 04 Feb '99

04 Feb '99

Dear Mr. Audet, APC-1520 has been allocated to your contribution "Corrections to H.323 and H.245 regarding fast start procedures." 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 *********************************************************** ---------------------------------------------------------------------- APC- Source Title ---------------------------------------------------------------------- 1486 SG11 Q.20/11 DSS2 protocol provision of adaptive timing recovery used for transmitting clock 1487 SG9 Q.31/9 Progress report on Webcasting 1488 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q 11, 12, 13 and 14 on MPEG-4 Systems on H.32X 1489 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q11, 12, 13, and 14 on MPEG-4 Audio on H.32X 1490 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q12 on Common Text Recommendations 1491 Nokia GSM in H.323 1492 AT&T H.323 Differentiated Services and Their Protocol Architectures 1493 AT&T Viewgraphs presentation for "H.323 Differentiated Services and Their Protocol Architectures" 1494 AT&T TIA/EIA IS-641 Enhanced Full-Rate Speech Codec for H.323 1495 Editor (G Kajos) Changes to H.341 Annexes 1496 Editors (D Gurle, G Kimchi) Editorial changes to H.323 Annex E text 1497 TIPHON Requirements for a Protocol at Reference Point N: Media Gateway Controller to Media Gateway 1498 VTEL H.323 QoS (Quality of Service) in the Policy Based Network 1499 VTEL Slides Presentation for H.323 QoS (Quality of Service) in the Policy Based Network 1500 Editor (B Hill) Gateway Control Protocol H.GCP 1501 Editor (J Ott) H.323 Annex F White Paper (for a final review) 1502 Teles OpenLogicalChannel structures for Annex F 1503 PTS Sweden H.323 Annex "Text", Text Conversation Capable SUD 1504 PTS Sweden Text conversation in H.323 1505 Editor (M Korpi) Draft H.450.8 - Conference out of Consultation Supplementary Service for H.323 1506 Siemens CallIdentifier and ConferenceIdentifier value setting in H.450.2and H.450.3 1507 PictureTel Fixing inconsistency between Annex E and H.283 and Annex G 1508 Chairman WP2/13 Status report on AAL2 signalling and switching 1509 Q12 Rapporteur Draft H.321 Implementors Guide 1510 Madge Networks cryptoTokens in H.225.0 Annex G 1511 Madge Networks Master/slave determination for inter-zone calls in H.323 environments where gatekeepers are routing H.245 signalling 1512 Madge Networks Submissions for the H.323 implementer's guide 1513 Ascend Extension Proposals for Gateway MIB of H.341 revison 2 1514 Siemens Comparison of Tunneling and Interworking 1515 Siemens H.450.x - Tunneling of External protocols 1516 ATMF "H.323 Over ATM Media Transport" specification 1517 ATMF H.245 codepoint for transport of compressed RTP over AAL5 1518 ATMF GIT for the transporting the portNumber 1519 Korea Telecom Dynamic Multicast Tree Building Procedure 1520 Nortel Networks Corrections to H.323 and H.245 regarding fast start procedures ----------------------------------------------------------------------

1 0

APC-1507 uploaded to Incoming directory
by Mark Duckworth 04 Feb '99

04 Feb '99

I have uploaded APC-1507.zip, Fixing Inconsistency Between Annex E and H.283 and Annex G, to ftp://standard.pictel.com/avc-site/Incoming This contribution proposes removing references to H.283 and H.225.0 Annex G from H.323 Annexe E, so that Annex E is consistent with H.283 and Annex G. Mark Duckworth

2 1

Re: About Contribution submission
by Sakae OKUBO 04 Feb '99

04 Feb '99

Dear Mr. Sang Gil Kim, In response to your request, APC-1519 has been allocated to your contribution "Dynamic Multicast Tree Building Procedure" as attached. 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 *********************************************************** ---------------------------------------------------------------------- APC- Source Title ---------------------------------------------------------------------- 1486 SG11 Q.20/11 DSS2 protocol provision of adaptive timing recovery used for transmitting clock 1487 SG9 Q.31/9 Progress report on Webcasting 1488 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q 11, 12, 13 and 14 on MPEG-4 Systems on H.32X 1489 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q11, 12, 13, and 14 on MPEG-4 Audio on H.32X 1490 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q12 on Common Text Recommendations 1491 Nokia GSM in H.323 1492 AT&T H.323 Differentiated Services and Their Protocol Architectures 1493 AT&T Viewgraphs presentation for "H.323 Differentiated Services and Their Protocol Architectures" 1494 AT&T TIA/EIA IS-641 Enhanced Full-Rate Speech Codec for H.323 1495 Editor (G Kajos) Changes to H.341 Annexes 1496 Editors (D Gurle, G Kimchi) Editorial changes to H.323 Annex E text 1497 TIPHON Requirements for a Protocol at Reference Point N: Media Gateway Controller to Media Gateway 1498 VTEL H.323 QoS (Quality of Service) in the Policy Based Network 1499 VTEL Slides Presentation for H.323 QoS (Quality of Service) in the Policy Based Network 1500 Editor (B Hill) Gateway Control Protocol H.GCP 1501 Editor (J Ott) H.323 Annex F White Paper (for a final review) 1502 Teles OpenLogicalChannel structures for Annex F 1503 PTS Sweden H.323 Annex "Text", Text Conversation Capable SUD 1504 PTS Sweden Text conversation in H.323 1505 Editor (M Korpi) Draft H.450.8 - Conference out of Consultation Supplementary Service for H.323 1506 Siemens CallIdentifier and ConferenceIdentifier value setting in H.450.2and H.450.3 1507 PictureTel Fixing inconsistency between Annex E and H.283 and Annex G 1508 Chairman WP2/13 Status report on AAL2 signalling and switching 1509 Q12 Rapporteur Draft H.321 Implementors Guide 1510 Madge Networks cryptoTokens in H.225.0 Annex G 1511 Madge Networks Master/slave determination for inter-zone calls in H.323 environments where gatekeepers are routing H.245 signalling 1512 Madge Networks Submissions for the H.323 implementer's guide 1513 Ascend Extension Proposals for Gateway MIB of H.341 revison 2 1514 Siemens Comparison of Tunneling and Interworking 1515 Siemens H.450.x - Tunneling of External protocols 1516 ATMF "H.323 Over ATM Media Transport" specification 1517 ATMF H.245 codepoint for transport of compressed RTP over AAL5 1518 ATMF GIT for the transporting the portNumber 1519 Korea Telecom Dynamic Multicast Tree Building Procedure ----------------------------------------------------------------------

1 0

Reps and interrupted dinners
by hlt＠zurich.ibm.com 03 Feb '99

03 Feb '99

I'm now forwarding the emails relating to that thread to your ITU account. Is that OK for you or do you prefer your Databeam one? Linh ---------------------- Forwarded by Hong Linh Truong/Zurich/IBM on 03.02.99 17:34 --------------------------- Chris Purvis <CPurvis(a)Madge.com> on 03.02.99 16:49:50 To: Hong Linh Truong/Zurich/IBM, Klaghofer Karl ICN IB NL IP 7 <Karl.Klaghofer(a)vs.siemens.de>, Korpi Markku USA <markku.korpi(a)icn.siemens.com>, "'wiryaman santo (VideoServer)'" <swiryaman(a)VideoServer.com>, "'Kumar Vineet (Intel)'" <vineet.kumar(a)intel.com>, "'Freundlich Glen'" <ggf(a)lucent.com>, "'Walker Dave (Mitel)'" <dave_walker(a)mitel.com>, "'Ruditsky Sasha (RadVision)'" <sasha(a)radvision.rad.co.il> cc: Subject: Reps and interrupted dinners Santo, Linh et al, Sorry for the subject line change, but this is a bit of a side-track (however interesting) from the main stream discussion... My feeling is that I would wish to be able to set up policy for my endpoint that to make it ignore these messages (or at least ask me very nicely) if they were about to involve me in spending large amounts of money. The routeCallToMC FACILITY message is for the express purpose of telling me that the endpoint I've tried to call is already in a conference, and how to join it. Possible ways that I can see of adding extra endpoints to an extant call in Santo's scenario are: 1. Use Linh's method, and allow the man with the interrupted dinner to put the phone down and then ring it again. 2. Something like Karl's H.450.8-proposal that allows us to "replace" one call with another. This would need to be combined with Linh's comments in order to avoid 1. 3. Give the "rep" in that scenario an endpoint containing an MC, or a clever enough gatekeeper (one containing, or "with access to" an MC) that any calls can be made at the rep's expense. In this scenario any call control signalling (H.225 and H.245) to the interrupted-dinner-person are routed via the rep's GK, and these stay open when the GK pulls in the MC. Of these, 1. is inconvenient to the user, 2. requires some standardisation work, and 3. requires the annoying rep to spend money. Any preferences? Regards, Chris > -----Original Message----- > From: hlt(a)zurich.ibm.com [mailto:hlt@zurich.ibm.com] > Sent: 03 February 1999 1:20 > To: Klaghofer Karl ICN IB NL IP 7; Korpi Markku USA; 'wiryaman santo > (VideoServer)'; 'Kumar Vineet (Intel)'; 'Freundlich Glen'; > 'Walker Dave > (Mitel)'; 'Ruditsky Sasha (RadVision)'; hlt(a)zurich.ibm.com; > Chris Purvis > Subject: RE: Draft H.450.8 Conference out of Consultation Suppl. Serv. > for H.323 > > > > > My apologies. I forget to cc: to the whole group my reply to Santo. > Linh > ---------------------- Forwarded by Hong Linh > Truong/Zurich/IBM on 03.02.99 > 14:18 --------------------------- > > From: Hong Linh Truong on 03.02.99 10:00 > > To: Santo Wiryaman <swiryaman(a)VideoServer.com> > cc: > > Subject: RE: Draft H.450.8 Conference out of Consultation > Suppl. Serv. for > H.323 (Document link not converted) > > Santo, > > Although I do not know how the charging model for IP > telephony will look > like, I do agree with the excellent point you made below. > Assuming that in > general the calling party has to pay for the call, then any > conferencing > approach that modifies the setup direction of a call will run > into that > unacceptable problem. Unfortunately, both conferencing > approaches we have > identified so far do modify the direction of the calls. > > Let me take your scenario and modify it a little bit. Instead > the agent > conferencing-in his boss, you conference-in your wife. In > this case you'd > be fine with the Facility "re-route to MC" but not with > 450.8. Using 450.8 > you'd get a bill at the end of the month ;-). > > To solve the above problem, we need an approach that DO NOT modify the > setup direction of the calls. Fortunately, we can build such > an approach > based on the current H.323. Endpoint A (the one that wants to create a > conference with B and C) has now to handle a call differently based on > whether it is an incoming or an outgoing call (from A's view > point). If it > was an incoming call, then A will send out a FACILITY > "re-route to MC". If > it was an outgoing call, then A has to request the MC to invite the > corresponding endpoint. H.323 Figure 28 shows how the > invitation procedure > looks like. > > Any other opinions? > > Regards, > > Linh > > > > > Santo Wiryaman <swiryaman(a)VideoServer.com> on 02.02.99 17:02:55 > > To: Klaghofer Karl ICN IB NL IP 7 > <Karl.Klaghofer(a)vs.siemens.de>, Korpi > Markku USA <markku.korpi(a)icn.siemens.com>, "'wiryaman santo > (VideoServer)'" <swiryaman(a)VideoServer.com>, "'Kumar > Vineet (Intel)'" > <vineet.kumar(a)intel.com>, "'Freundlich Glen'" <ggf(a)lucent.com>, > "'Walker Dave (Mitel)'" <dave_walker(a)mitel.com>, > "'Ruditsky Sasha > (RadVision)'" <sasha(a)radvision.rad.co.il>, Hong Linh > Truong/Zurich/IBM, Chris Purvis <CPurvis(a)Madge.com> > cc: > > Subject: RE: Draft H.450.8 Conference out of Consultation > Suppl. Serv. for > H.323 > > > > > Karl, > > I share your concern on the fact that not all endpoints > support the H.225.0 > FACILITY "re-route to MC". Even though Linh pointed out that this is > mandatory, I envision a general deployment problem with these > "re-route to > SOMETHING" messages. > > The problem I see is that the receiver of this message is to > make a new > call > somewhere else, presumably automatically, without the user's > consent. I > can > imagine the following scenario: > > 1. I am at home eating my dinner > 2. The phone rings and it was a courtesy call from my long > distance carrier > to check if I am satisfied with their service > 3. My dinner interrupted, I am already somewhat annoyed. > However, while the > rep is on the phone, I might as well ask if they have special > deals for > calling Switzerland > 4. The rep is not familiar with any, so he conferences-in his > manager using > the "re-route to MC" message > 5. The conference call went OK, but at the end of the month, > I got this > charge for calling an MCU in the Cayman Island > > As an engineer, I can see how the scheme might work, but as a > consumer, I > would have problem with the above scenario. Even if the > endpoint prompts > me > for authorization to call the MCU, I would probably said no > and continued > with my dinner. > > I can see consumer pressure for an option to block the "re-route to > SOMETHING" messages. > > Any opinions? > > > Regards, > > Santo Wiryaman > VideoServer Inc. > +1.781.505.2348 > > > > -----Original Message----- > > From: Klaghofer Karl ICN IB NL IP 7 > [SMTP:Karl.Klaghofer@vs.siemens.de] > > Sent: Monday, February 01, 1999 11:36 AM > > To: Korpi Markku USA; 'wiryaman santo (VideoServer)'; > 'Kumar Vineet > > (Intel)'; 'Freundlich Glen'; 'Walker Dave (Mitel)'; 'Ruditsky Sasha > > (RadVision)'; 'hlt(a)zurich.ibm.com'; Chris Purvis > > Subject: AW: Draft H.450.8 Conference out of Consultation Suppl. > > Serv. for H.323 > > > > To all "conference participants": > > > > I had not yet answered the last comments/proposals > received on Draft > > H.450.8. The attached memo provides a summary. > > > > Thanks for your contributions so far. > > > > Regards, > > Karl > > > > > > <<H4508comments990201.doc>> > > > > > > > > ------------------------------------------------ > > Karl Klaghofer, Siemens AG, Dpmt. ICN IB NL IP7 > > Hofmannstr. 51, D-81359 Munich, Germany > > Tel.: +49 89 722 31488, Fax.: +49 89 722 37629 > > e-mail: karl.klaghofer(a)vs.siemens.de > > > > > > << File: H4508comments990201.doc >> > >

1 0

FW: TIA to create IP phone performance & interoperability reqts s td
by Nancy-M Greene 03 Feb '99

03 Feb '99

The following may be of interest to some of you. The Telecommunications Industry Association (TIA) has started a new project (TR-41.3.4) to create a standard for "Performance and Interoperability Requirements for VoIP Telephone Terminals. First meeting will be the Monday of the next TIA meeting Feb 15-19 in Sarasota. They plan to establish relationships with related work in the IETF, ITU and ETSI. > Press release is online at > http://www.tiaonline.org/pubs/press_releases/1999/99-11.html > > Nancy > -------------------------------------------------------------------------- > Nancy M. Greene > Internet & Service Provider Networks, Nortel Networks > T:514-271-7221 (internal:ESN853-1077) E:ngreene@nortelnetworks.com

1 0

Re: APC-1495 uploaded
by Sakae OKUBO 03 Feb '99

03 Feb '99

Dear Mr. Kajos, > APC1495.zip has been uploaded to the incoming directory. This has been moved to /9902_Mon directory. > Please leave H341wht6.{zip,doc} in the incoming directory a few > days to allow people on the reflector to get the document. Many > people can't get mail attachments of files that large. Understood. 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 ***********************************************************

1 0

APC numbers
by Sakae OKUBO 03 Feb '99

03 Feb '99

Dear Ping Wang, Dear Robert Callaghan, Dear Francois Audet, In response to your requests, APC numbers have been allocated to your contributions as attached. 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 *********************************************************** ---------------------------------------------------------------------- APC- Source Title ---------------------------------------------------------------------- 1486 SG11 Q.20/11 DSS2 protocol provision of adaptive timing recovery used for transmitting clock 1487 SG9 Q.31/9 Progress report on Webcasting 1488 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q 11, 12, 13 and 14 on MPEG-4 Systems on H.32X 1489 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q11, 12, 13, and 14 on MPEG-4 Audio on H.32X 1490 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q12 on Common Text Recommendations 1491 Nokia GSM in H.323 1492 AT&T H.323 Differentiated Services and Their Protocol Architectures 1493 AT&T Viewgraphs presentation for "H.323 Differentiated Services and Their Protocol Architectures" 1494 AT&T TIA/EIA IS-641 Enhanced Full-Rate Speech Codec for H.323 1495 Editor (G Kajos) Changes to H.341 Annexes 1496 Editors (D Gurle, G Kimchi) Editorial changes to H.323 Annex E text 1497 TIPHON Requirements for a Protocol at Reference Point N: Media Gateway Controller to Media Gateway 1498 VTEL H.323 QoS (Quality of Service) in the Policy Based Network 1499 VTEL Slides Presentation for H.323 QoS (Quality of Service) in the Policy Based Network 1500 Editor (B Hill) Gateway Control Protocol H.GCP 1501 Editor (J Ott) H.323 Annex F White Paper (for a final review) 1502 Teles OpenLogicalChannel structures for Annex F 1503 PTS Sweden H.323 Annex "Text", Text Conversation Capable SUD 1504 PTS Sweden Text conversation in H.323 1505 Editor (M Korpi) Draft H.450.8 - Conference out of Consultation Supplementary Service for H.323 1506 Siemens CallIdentifier and ConferenceIdentifier value setting in H.450.2and H.450.3 1507 PictureTel Fixing inconsistency between Annex E and H.283 and Annex G 1508 Chairman WP2/13 Status report on AAL2 signalling and switching 1509 Q12 Rapporteur Draft H.321 Implementors Guide 1510 Madge Networks cryptoTokens in H.225.0 Annex G 1511 Madge Networks Master/slave determination for inter-zone calls in H.323 environments where gatekeepers are routing H.245 signalling 1512 Madge Networks Submissions for the H.323 implementer's guide 1513 Ascend Extension Proposals for Gateway MIB of H.341 revison 2 1514 Siemens Comparison of Tunneling and Interworking 1515 Siemens H.450.x - Tunneling of External protocols 1516 ATMF "H.323 Over ATM Media Transport" specification 1517 ATMF H.245 codepoint for transport of compressed RTP over AAL5 1518 ATMF GIT for the transporting the portNumber ----------------------------------------------------------------------

1 0

Re: TPKT in H.225.0
by Tom-PT Taylor 02 Feb '99

02 Feb '99

I'd swear the reference to RFC1006 used to be in H.225.0 Appendix D, but I can't find it there now. > -----Original Message----- > From: Derks, Frank [SMTP:F.Derks@PBC.BE.PHILIPS.COM] > Sent: Tuesday, February 02, 1999 4:05 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: TPKT in H.225.0 > > Hi Paul, > > I received two responses to my question, one from you and one from Tom > Taylor. The fact that there are at least two people that know about it > (and > several dozens more that have actually implemented the protocol stacks), > makes it hard to believe that this is an "oversight" in the > recommendation. > In fact, not knowing about this makes it impossible to implement an > interoperable protocol stack! Shouldn't action be taken to get this into > the > recommendation ASAP (e.g. through the Implementor's Guide)? > > Regards, > > Frank > > -----Original Message----- > From: Paul Long [mailto:Plong@SMITHMICRO.COM] > Sent: 01 February 1999 18:50 > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: TPKT in H.225.0 > > > TPKT is defined in RFC 1006. Not identifying TPKT was an oversight that > has > never been fixed in the Recommendation. > > Paul Long > Smith Micro Software, Inc.

1 0

Re: Madge contributions for Monterey Meeting
by Sakae OKUBO 02 Feb '99

02 Feb '99

Dear Mr. Purvis, In response to your request, APC-1510, 1511 and 1512 have been allocated to your three contributions as attached. 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 *********************************************************** ---------------------------------------------------------------------- APC- Source Title ---------------------------------------------------------------------- 1486 SG11 Q.20/11 DSS2 protocol provision of adaptive timing recovery used for transmitting clock 1487 SG9 Q.31/9 Progress report on Webcasting 1488 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q 11, 12, 13 and 14 on MPEG-4 Systems on H.32X 1489 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q11, 12, 13, and 14 on MPEG-4 Audio on H.32X 1490 MPEG Liaison statement from SC 29/WG 11 to ITU-T SG 16/Q12 on Common Text Recommendations 1491 Nokia GSM in H.323 1492 AT&T H.323 Differentiated Services and Their Protocol Architectures 1493 AT&T Viewgraphs presentation for "H.323 Differentiated Services and Their Protocol Architectures" 1494 AT&T TIA/EIA IS-641 Enhanced Full-Rate Speech Codec for H.323 1495 Editor (G Kajos) Changes to H.341 Annexes 1496 Editors (D Gurle, G Kimchi) Editorial changes to H.323 Annex E text 1497 TIPHON Requirements for a Protocol at Reference Point N: Media Gateway Controller to Media Gateway 1498 VTEL H.323 QoS (Quality of Service) in the Policy Based Network 1499 VTEL Slides Presentation for H.323 QoS (Quality of Service) in the Policy Based Network 1500 Editor (B Hill) Gateway Control Protocol H.GCP 1501 Editor (J Ott) H.323 Annex F White Paper (for a final review) 1502 Teles OpenLogicalChannel structures for Annex F 1503 PTS Sweden H.323 Annex "Text", Text Conversation Capable SUD 1504 PTS Sweden Text conversation in H.323 1505 Editor (M Korpi) Draft H.450.8 - Conference out of Consultation Supplementary Service for H.323 1506 Siemens CallIdentifier and ConferenceIdentifier value setting in H.450.2and H.450.3 1507 PictureTel Fixing inconsistency between Annex E and H.283 and Annex G 1508 Chairman WP2/13 Status report on AAL2 signalling and switching 1509 Q12 Rapporteur Draft H.321 Implementors Guide 1510 Madge Networks cryptoTokens in H.225.0 Annex G 1511 Madge Networks Master/slave determination for inter-zone calls in H.323 environments where gatekeepers are routing H.245 signalling 1512 Madge Networks Submissions for the H.323 implementer's guide ----------------------------------------------------------------------

1 0

Re: TPKT in H.225.0
by Derks, Frank 02 Feb '99

02 Feb '99

Hi Paul, I received two responses to my question, one from you and one from Tom Taylor. The fact that there are at least two people that know about it (and several dozens more that have actually implemented the protocol stacks), makes it hard to believe that this is an "oversight" in the recommendation. In fact, not knowing about this makes it impossible to implement an interoperable protocol stack! Shouldn't action be taken to get this into the recommendation ASAP (e.g. through the Implementor's Guide)? Regards, Frank -----Original Message----- From: Paul Long [mailto:Plong@SMITHMICRO.COM] Sent: 01 February 1999 18:50 To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: TPKT in H.225.0 TPKT is defined in RFC 1006. Not identifying TPKT was an oversight that has never been fixed in the Recommendation. Paul Long Smith Micro Software, Inc.

1 0