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

cc:Mail SMTPLINK Undeliverable Message
by Bob_Bean＠MULTILINK.COM 13 Oct '97

13 Oct '97

Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id OAA10685; Mon, 13 Oct 1997 14:18:22 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma010654; Mon Oct 13 14:18:06 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id MAA24282; Mon, 13 Oct 1997 12:11:01 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142731 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 12:10:48 -0700 Received: from woody.multilink.com (multilink.com [38.248.79.2]) by mailbag.jf.intel.com (8.8.6/8.8.5) with SMTP id MAA23897 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 12:00:43 -0700 (PDT) Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id OAA10270 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 14:03:54 -0400 Received: from multimail.multilink.com(172.16.7.3) by woody via smap (V1.3) id sma010261; Mon Oct 13 14:03:51 1997 Received: from cc:Mail SMTPLINK by multimail.multilink.com id 9709138767.AA876781563; Mon, 13 Oct 97 15:26:03 EST Message-ID: <9709138767.AA876781563(a)multimail.multilink.com> Date: Mon, 13 Oct 1997 15:26:03 EST Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: Bob_Bean(a)MULTILINK.COM Subject: cc:Mail SMTPLINK Undeliverable Message To: ITU-SG16(a)mailbag.jf.intel.com Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA10112; Mon, 13 Oct 1997 13:57:04 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma010106; Mon Oct 13 13:56:45 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA23670; Mon, 13 Oct 1997 11:50:47 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142669 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:50:43 -0700 Received: from woody.multilink.com (multilink.com [38.248.79.2]) by mailbag.jf.intel.com (8.8.6/8.8.5) with SMTP id LAA23487 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 11:40:39 -0700 (PDT) Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09696 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:43:47 -0400 Received: from multimail.multilink.com(172.16.7.3) by woody via smap (V1.3) id sma009683; Mon Oct 13 13:43:29 1997 Received: from cc:Mail SMTPLINK by multimail.multilink.com id 9709138767.AA876780346; Mon, 13 Oct 97 15:05:46 EST Message-ID: <9709138767.AA876780346(a)multimail.multilink.com> Date: Mon, 13 Oct 1997 15:05:46 EST Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: Bob_Bean(a)MULTILINK.COM Subject: cc:Mail SMTPLINK Undeliverable Message To: ITU-SG16(a)mailbag.jf.intel.com Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09596; Mon, 13 Oct 1997 13:38:38 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma009593; Mon Oct 13 13:38:34 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA23236; Mon, 13 Oct 1997 11:31:58 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142598 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:31:55 -0700 Received: from woody.multilink.com (multilink.com [38.248.79.2]) by mailbag.jf.intel.com (8.8.6/8.8.5) with SMTP id LAA23081 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 11:21:50 -0700 (PDT) Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09223 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:24:46 -0400 Received: from multimail.multilink.com(172.16.7.3) by woody via smap (V1.3) id sma009208; Mon Oct 13 13:24:42 1997 Received: from cc:Mail SMTPLINK by multimail.multilink.com id 9709138767.AA876779145; Mon, 13 Oct 97 14:45:45 EST Message-ID: <9709138767.AA876779145(a)multimail.multilink.com> Date: Mon, 13 Oct 1997 14:45:45 EST Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: Bob_Bean(a)MULTILINK.COM Subject: cc:Mail SMTPLINK Undeliverable Message To: ITU-SG16(a)mailbag.jf.intel.com Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA08993; Mon, 13 Oct 1997 13:17:28 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma008968; Mon Oct 13 13:17:03 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA22824; Mon, 13 Oct 1997 11:09:09 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142519 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:08:26 -0700 Received: from acme.lex.databeam.com (acme.lex.databeam.com [192.101.205.15]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id KAA22541 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 10:58:21 -0700 (PDT) Received: from pjones (pjones.cs.lex.databeam.com [192.101.203.174]) by acme.lex.databeam.com (8.7.5/8.7.5) with SMTP id NAA16821 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:56:08 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Message-ID: <01bcd801$479debb0$aecb65c0(a)pjones.cs.lex.databeam.com> Date: Mon, 13 Oct 1997 13:56:06 -0400 Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: "Paul E. Jones" <pjones(a)DATABEAM.COM> Subject: Re: H.245 v1 and v2 will not interoperate To: ITU-SG16(a)mailbag.jf.intel.com Tom, I think everyone's gone into hibernation... Regards, Paul -----Original Message----- From: Tom Taylor <taylor(a)NORTEL.CA> To: ITU-SG16(a)mailbag.jf.intel.com <ITU-SG16(a)mailbag.jf.intel.com> Date: Friday, October 10, 1997 2:15 PM Subject: Re: H.245 v1 and v2 will not interoperate >This is the subject of the last message I have received from the SG 16 >reflector, dated September 30. Has everyone gone into hibernation or have >I accidently become unsubscribed? >

1 0

Delivered: Re: H.245 v1 and v2 will not interoperate
by Postmaster 13 Oct '97

13 Oct '97

Your message To: ITU-SG16(a)mailbag.jf.intel.com Subject: Re: H.245 v1 and v2 will not interoperate Sent: 10/13/97 16:12:16 PM was delivered to the following recipient(s): Phillippy, John D. on 10/13/97 16:35:26 PM

1 0

cc:Mail SMTPLINK Undeliverable Message
by Bob_Bean＠MULTILINK.COM 13 Oct '97

13 Oct '97

Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA10112; Mon, 13 Oct 1997 13:57:04 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma010106; Mon Oct 13 13:56:45 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA23670; Mon, 13 Oct 1997 11:50:47 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142669 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:50:43 -0700 Received: from woody.multilink.com (multilink.com [38.248.79.2]) by mailbag.jf.intel.com (8.8.6/8.8.5) with SMTP id LAA23487 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 11:40:39 -0700 (PDT) Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09696 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:43:47 -0400 Received: from multimail.multilink.com(172.16.7.3) by woody via smap (V1.3) id sma009683; Mon Oct 13 13:43:29 1997 Received: from cc:Mail SMTPLINK by multimail.multilink.com id 9709138767.AA876780346; Mon, 13 Oct 97 15:05:46 EST Message-ID: <9709138767.AA876780346(a)multimail.multilink.com> Date: Mon, 13 Oct 1997 15:05:46 EST Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: Bob_Bean(a)MULTILINK.COM Subject: cc:Mail SMTPLINK Undeliverable Message To: ITU-SG16(a)mailbag.jf.intel.com Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09596; Mon, 13 Oct 1997 13:38:38 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma009593; Mon Oct 13 13:38:34 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA23236; Mon, 13 Oct 1997 11:31:58 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142598 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:31:55 -0700 Received: from woody.multilink.com (multilink.com [38.248.79.2]) by mailbag.jf.intel.com (8.8.6/8.8.5) with SMTP id LAA23081 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 11:21:50 -0700 (PDT) Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09223 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:24:46 -0400 Received: from multimail.multilink.com(172.16.7.3) by woody via smap (V1.3) id sma009208; Mon Oct 13 13:24:42 1997 Received: from cc:Mail SMTPLINK by multimail.multilink.com id 9709138767.AA876779145; Mon, 13 Oct 97 14:45:45 EST Message-ID: <9709138767.AA876779145(a)multimail.multilink.com> Date: Mon, 13 Oct 1997 14:45:45 EST Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: Bob_Bean(a)MULTILINK.COM Subject: cc:Mail SMTPLINK Undeliverable Message To: ITU-SG16(a)mailbag.jf.intel.com Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA08993; Mon, 13 Oct 1997 13:17:28 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma008968; Mon Oct 13 13:17:03 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA22824; Mon, 13 Oct 1997 11:09:09 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142519 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:08:26 -0700 Received: from acme.lex.databeam.com (acme.lex.databeam.com [192.101.205.15]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id KAA22541 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 10:58:21 -0700 (PDT) Received: from pjones (pjones.cs.lex.databeam.com [192.101.203.174]) by acme.lex.databeam.com (8.7.5/8.7.5) with SMTP id NAA16821 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:56:08 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Message-ID: <01bcd801$479debb0$aecb65c0(a)pjones.cs.lex.databeam.com> Date: Mon, 13 Oct 1997 13:56:06 -0400 Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: "Paul E. Jones" <pjones(a)DATABEAM.COM> Subject: Re: H.245 v1 and v2 will not interoperate To: ITU-SG16(a)mailbag.jf.intel.com Tom, I think everyone's gone into hibernation... Regards, Paul -----Original Message----- From: Tom Taylor <taylor(a)NORTEL.CA> To: ITU-SG16(a)mailbag.jf.intel.com <ITU-SG16(a)mailbag.jf.intel.com> Date: Friday, October 10, 1997 2:15 PM Subject: Re: H.245 v1 and v2 will not interoperate >This is the subject of the last message I have received from the SG 16 >reflector, dated September 30. Has everyone gone into hibernation or have >I accidently become unsubscribed? >

1 0

Re: H.245 v1 and v2 will not interoperate
by Sean McEnroe 13 Oct '97

13 Oct '97

I agree whar is going on ? Regards, Sean McEnroe V.P. VoIP Engineering --------- From: Paul E. Jones[SMTP:pjones@DATABEAM.COM] Sent: Monday, October 13, 1997 1:56 PM To: ITU-SG16(a)mailbag.jf.intel.com Subject: Re: H.245 v1 and v2 will not interoperate Tom, I think everyone's gone into hibernation... Regards, Paul -----Original Message----- From: Tom Taylor <taylor(a)NORTEL.CA> To: ITU-SG16(a)mailbag.jf.intel.com <ITU-SG16(a)mailbag.jf.intel.com> Date: Friday, October 10, 1997 2:15 PM Subject: Re: H.245 v1 and v2 will not interoperate >This is the subject of the last message I have received from the SG 16 >reflector, dated September 30. Has everyone gone into hibernation or have >I accidently become unsubscribed? > begin 600 WINMAIL.DAT M>)\^(AT4`0:0" `$```````!``$``0>0!@`(````Y 0```````#H``$(@ <` M& ```$E032Y-:6-R;W-O9G0@36%I;"Y.;W1E`#$(`0V ! `"`````0`!``$$ MD 8`C $```$````,`````P``, (````+``\.``````(!_P\!````>0`````` M``"!*Q^DOJ,0&9UN`-T!#U0"`````$UA:6QI;F<@;&ES="!F;W(@<&%R=&EE M<R!A<W-O8VEA=&5D('=I=&@@2515+50@4W1U9'D@1W)O=7 @,38`4TU44 !) M5%4M4T<Q-D!M86EL8F%G+FIF+FEN=&5L+F-O;0`````>``(P`0````4```!3 M3510`````!X``S !````'@```$E452U31S$V0&UA:6QB86<N:F8N:6YT96PN M8V]M`````P`5# $````#`/X/!@```!X``3 !````0 ```"=-86EL:6YG(&QI M<W0@9F]R('!A<G1I97,@87-S;V-I871E9"!W:71H($E452U4(%-T=61Y($=R M;W5P(#$V)P`"`0LP`0```",```!33510.DE452U31S$V0$U!24Q"04<N2D8N M24Y414PN0T]-```#```Y``````L`0#H!`````@'V#P$````$`````````DI7 M`02 `0`J````4D4Z($@N,C0U('8Q(&%N9"!V,B!W:6QL(&YO="!I;G1E<F]P M97)A=&4`7PT!!8 #``X```#-!PH`#0`0``P`$ `!`!@!`2" `P`.````S0<* M``T`$ `+`!H``0`A`0$)@ $`(0```$0W.#%"0C@V134T,T0Q,3%"0D-%,# V M,#DW,4%",$%$`#D'`0.0!@"T! ``% ````L`(P`!`````P`F``$````+`"D` M`0````,`+@```````P`V``````! `#D`H!@Q3138O $>`' ``0```"H```!2 M13H@2"XR-#4@=C$@86YD('8R('=I;&P@;F]T(&EN=&5R;W!E<F%T90````(! M<0`!````%@````&\V!1-+X:[@=A#Y1'1N\X`8)<:L*T``!X`'@P!````!0`` M`%--5% `````'@`?# $````5````<VUC96YR;V5 8F]C871E;"YC;VT````` M`P`&$(\Q2( #``<02P(``!X`"! !````90```$E!1U)%15=(05))4T=/24Y' M3TX_4D5'05)$4RQ314%.34-%3E)/15905D])4$5.1TE.145224Y'+2TM+2TM M+2TM1E)/33I0055,14I/3D534TU44#I02D].15- 1$%404)%04T``````@$) M$ $````2`P``#@,``!(&``!,6D9U7IWOM_\`"@$/`A4"I /D!>L"@P!0$P-4 M`@!C: K <V5T;C(&``;#`H,R`\4"`'!<<G$2( <3`H,S#WIH1&5L`R!$;&<" M@S3K`\83Z#46/7T*@ C/"=GB.QDO,C4U`H *@0VQP0M@;F<Q,#,4@ L**Q=2 M# %C`$ @"HML:0@Q.# "T6DM,30>- WP#- ?@QS_($D@4F$)PB!W$<$@! `@ M)&=O"X!G( (@(#\C"H4*A5)E9PL1<RR'(PP&8 .136-%;@-@0F4*A58N4"XF M8&_H25 @);!G"X )X 409QPP"H<+:#$V"J #8'3[!9 %0"TIIB?/*-,,,"DF M.D8#83HH+RDU#((@4-1A=0,@12:@2@(@!Y `6U--5% Z<&H!+N) 1$%404)% M@$%-+D-/35TJ/U\K309@`C L?RV+30(@9"!A>2P@3REP;V(1!) @,3,U0#$Y M.:(W-= Z-38N0$TPSQDK351O,P\MBTE456@M4T<H\$ `P ,08F$A@"YJ9BX+ M@"E0;!HN!:!M-N\QWG5B:A\I83D/+8LCX#\@2"XRL#0U('8=\ !P9$&0]Q(@ M`_ 5<6XI0"(@/#$#8#IP!)!A*5 C#!Z&,S9O("<6((a)P!.&AM)%TA8'1": N M:R!E=@20>9TNX2<B0B=00L)O($?@U36A;D-@:0(@+DHP(P_O)!HN4DIL*:-/ M!1 G,0= ZP70!Y!S(8!E*>HL-$:19SC0-2 8P2 \`9!0(D! 3D]25$5,,'!! M_CX*A3CB.N\[^E!@4D\[^EU1AD1#83\@+#!I-1PP\38%,CHQ08 VQSZW00_G M0A]#+TJ9/E1'X 0@(C';1] AP',^Q"*P9EY#"V!^<P5 !X%.8B%1$<!(0"#Q M&3!C96E(0%K0`U)>0_M4<#70-EU6&3 <`"EA!;"_-4 U$"E06M &8 4P90;0 M^36Q,S FH%H07Y!()TC?/TGC(K %P&!R758A86-CXU<`,M%L>2 UH#R!(<#> M=0" /L $\C6@9"+V48:_1 \@)Q+R1>D*A1A1`&X0```#`! 0``````,`$1 ! M````0 `',$ LD2\4V+P!0 `(,$ LD2\4V+P!'@`]``$````%````4D4Z( `` ,```#``TT_3<``,!# ` end

1 0

cc:Mail SMTPLINK Undeliverable Message
by Bob_Bean＠MULTILINK.COM 13 Oct '97

13 Oct '97

Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09596; Mon, 13 Oct 1997 13:38:38 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma009593; Mon Oct 13 13:38:34 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA23236; Mon, 13 Oct 1997 11:31:58 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142598 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:31:55 -0700 Received: from woody.multilink.com (multilink.com [38.248.79.2]) by mailbag.jf.intel.com (8.8.6/8.8.5) with SMTP id LAA23081 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 11:21:50 -0700 (PDT) Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA09223 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:24:46 -0400 Received: from multimail.multilink.com(172.16.7.3) by woody via smap (V1.3) id sma009208; Mon Oct 13 13:24:42 1997 Received: from cc:Mail SMTPLINK by multimail.multilink.com id 9709138767.AA876779145; Mon, 13 Oct 97 14:45:45 EST Message-ID: <9709138767.AA876779145(a)multimail.multilink.com> Date: Mon, 13 Oct 1997 14:45:45 EST Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: Bob_Bean(a)MULTILINK.COM Subject: cc:Mail SMTPLINK Undeliverable Message To: ITU-SG16(a)mailbag.jf.intel.com Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA08993; Mon, 13 Oct 1997 13:17:28 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma008968; Mon Oct 13 13:17:03 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA22824; Mon, 13 Oct 1997 11:09:09 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142519 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:08:26 -0700 Received: from acme.lex.databeam.com (acme.lex.databeam.com [192.101.205.15]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id KAA22541 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 10:58:21 -0700 (PDT) Received: from pjones (pjones.cs.lex.databeam.com [192.101.203.174]) by acme.lex.databeam.com (8.7.5/8.7.5) with SMTP id NAA16821 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:56:08 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Message-ID: <01bcd801$479debb0$aecb65c0(a)pjones.cs.lex.databeam.com> Date: Mon, 13 Oct 1997 13:56:06 -0400 Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: "Paul E. Jones" <pjones(a)DATABEAM.COM> Subject: Re: H.245 v1 and v2 will not interoperate To: ITU-SG16(a)mailbag.jf.intel.com Tom, I think everyone's gone into hibernation... Regards, Paul -----Original Message----- From: Tom Taylor <taylor(a)NORTEL.CA> To: ITU-SG16(a)mailbag.jf.intel.com <ITU-SG16(a)mailbag.jf.intel.com> Date: Friday, October 10, 1997 2:15 PM Subject: Re: H.245 v1 and v2 will not interoperate >This is the subject of the last message I have received from the SG 16 >reflector, dated September 30. Has everyone gone into hibernation or have >I accidently become unsubscribed? >

1 0

cc:Mail SMTPLINK Undeliverable Message
by Bob_Bean＠MULTILINK.COM 13 Oct '97

13 Oct '97

Message undeliverable at this time Original text follows ----------------------------------------- Received: by ccmail from woody.multilink.com >From ITU-SG16(a)mailbag.jf.intel.com X-Envelope-From: ITU-SG16(a)mailbag.jf.intel.com Received: (from mail@localhost) by woody.multilink.com (8.6.12/8.7.3) id NAA08993; Mon, 13 Oct 1997 13:17:28 -0400 Received: from mailbag.jf.intel.com(134.134.248.7) by woody via smap (V1.3) id sma008968; Mon Oct 13 13:17:03 1997 Received: from mailbag.jf.intel.com (mailbag.jf.intel.com [134.134.248.7]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id LAA22824; Mon, 13 Oct 1997 11:09:09 -0700 (PDT) Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8c) with spool id 142519 for ITU-SG16(a)MAILBAG.INTEL.COM; Mon, 13 Oct 1997 11:08:26 -0700 Received: from acme.lex.databeam.com (acme.lex.databeam.com [192.101.205.15]) by mailbag.jf.intel.com (8.8.6/8.8.5) with ESMTP id KAA22541 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 10:58:21 -0700 (PDT) Received: from pjones (pjones.cs.lex.databeam.com [192.101.203.174]) by acme.lex.databeam.com (8.7.5/8.7.5) with SMTP id NAA16821 for <ITU-SG16(a)mailbag.jf.intel.com>; Mon, 13 Oct 1997 13:56:08 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Message-ID: <01bcd801$479debb0$aecb65c0(a)pjones.cs.lex.databeam.com> Date: Mon, 13 Oct 1997 13:56:06 -0400 Reply-To: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> Sender: Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.jf.intel.com> From: "Paul E. Jones" <pjones(a)DATABEAM.COM> Subject: Re: H.245 v1 and v2 will not interoperate To: ITU-SG16(a)mailbag.jf.intel.com Tom, I think everyone's gone into hibernation... Regards, Paul -----Original Message----- From: Tom Taylor <taylor(a)NORTEL.CA> To: ITU-SG16(a)mailbag.jf.intel.com <ITU-SG16(a)mailbag.jf.intel.com> Date: Friday, October 10, 1997 2:15 PM Subject: Re: H.245 v1 and v2 will not interoperate >This is the subject of the last message I have received from the SG 16 >reflector, dated September 30. Has everyone gone into hibernation or have >I accidently become unsubscribed? >

1 0

Re: H.245 v1 and v2 will not interoperate
by Paul E. Jones 13 Oct '97

13 Oct '97

Tom, I think everyone's gone into hibernation... Regards, Paul -----Original Message----- From: Tom Taylor <taylor(a)NORTEL.CA> To: ITU-SG16(a)mailbag.jf.intel.com <ITU-SG16(a)mailbag.jf.intel.com> Date: Friday, October 10, 1997 2:15 PM Subject: Re: H.245 v1 and v2 will not interoperate >This is the subject of the last message I have received from the SG 16 >reflector, dated September 30. Has everyone gone into hibernation or have >I accidently become unsubscribed? >

1 0

Clarification of H.245 MTSE
by Paul Long 10 Oct '97

10 Oct '97

(I posted this to the sg16.lbc reflector, but Tom Geary suggested that I also post it here. Sorry for the cross-posting. I believe this only affects H.324, so all you H.323, et al., people can continue with whatever you were doing. :-) ) Here is the text for a proposal I submitted back in Portland and that was supposed to have been discussed in Sunriver. Since it wasn't, we need to discuss this on the reflector before the next meeting in Geneva. If you have any problem at all with this proposed "fix" to the MTSE, please speak up now. This contribution proposes backward-compatible modifications to the H.245 Multiplex Table Signaling Entity (MTSE) in order to fix an apparent oversight. These modifications allow an implementation to use the MultiplexEntrySend message as it was intended-with multiple multiplex entries. 1. Introduction There is a flaw in the H.245 MTSE SDL that precludes sending the MultiplexEntrySend message with multiple entries if there are any entries in common between it and any of the preceeding MultiplexEntrySend messages. When multiple entries are sent in a MultiplexEntrySend message, they all share the same value in the sequenceNumber field, yet each out-going MTSE maintains its own, per-entry sequence number in out_SQ. Therefore, only those entries whose MTSE coincidentally have the same value for out_SQ can be combined in a subsequent MultiplexEntrySend message. The trouble this causes during implementation has resulted in some vendors deciding to not send multiple entries in a MultiplexEntrySend message. 2. Solutions There are two solutions to this problem. 2.1 Avoid multiple entries Never send multiple entries in a MultiplexEntrySend message after the first one. The first MultiplexEntrySend message may or may not contain multiple entries. The downside is that one is not using the MultiplexEntrySend message as it was intended to be used, thus wasting a small amount of bandwidth due to duplicated overhead for each MultiplexEntrySend message containing a single entry and the associated time loss, e.g., during session startup, as the sender waits for responses to each request. 2.2 Use a common sequence-number variable Have all of the out-going MTSEs share a single sequence-number variable for determining what sequence number to use for out-going MultiplexEntrySend messages. Each MTSE continues to use its existing, MTSE-specific sequence-number variable for recording the sequence number used in the MultiplexEntrySend message. This is so that responses can be identified as belonging to the same dialogue as the MultiplexEntrySend request. This is backwards compatible with the MTSE defined in previous versions of H.245 because there is no requirement in the in-coming MTSE that the values of MultiplexEntrySend.sequenceNumber be contiguous from one message to another for a given MTSE instance. In effect, sequenceNumber is used as a somewhat unique handle for a brief transaction, not as something that must increase by one each time. The result is that this allows all out-going MultiplexEntrySend messages to contain multiple entries. 2. Text Modifications Here are the required text modifications for the second, common-sequence-number-variable solution. Replace the out_SQ definition in 8.7.3.2/H.245 with these two variables and their descriptions. out_SQ This state variable is used to indicate the most recently sent MultiplexEntrySend message for this MTSE instance. It is mapped to the MultiplexEntrySend message sequenceNumber field before transmission of a MultiplexEntrySend message. global_out_SQ This state variable is used to indicate the most recently sent MultiplexEntrySend message for any MTSE instance. It is incremented by one and assigned to out_SQ before out_SQ is mapped to the MultiplexEntrySend message sequenceNumber field. Arithmetic performed on global_out_SQ is module 256. Replace the contents of the task symbol in Figure 28(i)/H.245 containing "out_SQ := out_SQ + 1" with this: global_out_SQ := global_out_SQ + 1 out_SQ := global_out_SQ 3. Proposal That the text modifications described above be applied to H.245 version 3 to allow all MultiplexEntrySend messages to contain multiple multiplex entries. [end] -- Paul Long___________________________http://www.cmpu.net/public/plong Smith Micro Software, Inc.__________http://www.smithmicro.com/

1 0

Re: H.245 v1 and v2 will not interoperate
by Tom Taylor 10 Oct '97

10 Oct '97

This is the subject of the last message I have received from the SG 16 reflector, dated September 30. Has everyone gone into hibernation or have I accidently become unsubscribed?

2 1

Clarification of H.245 MTSE
by Paul Long 01 Oct '97

01 Oct '97

(I just posted this to the sg16.lbc reflector, but Tom Geary suggested that I also post it here. Sorry for the cross-posting. I believe this only affects H.324, so all you H.323, et al., people can continue with whatever you were doing. :-) ) Here is the text for a proposal I submitted back in Portland and that was supposed to have been discussed in Sunriver. Since it wasn't, we need to discuss this on the reflector before the next meeting in Geneva. If you have any problem at all with this proposed "fix" to the MTSE, please speak up now. This contribution proposes backward-compatible modifications to the H.245 Multiplex Table Signaling Entity (MTSE) in order to fix an apparent oversight. These modifications allow an implementation to use the MultiplexEntrySend message as it was intended-with multiple multiplex entries. 1. Introduction There is a flaw in the H.245 MTSE SDL that precludes sending the MultiplexEntrySend message with multiple entries if there are any entries in common between it and any of the preceeding MultiplexEntrySend messages. When multiple entries are sent in a MultiplexEntrySend message, they all share the same value in the sequenceNumber field, yet each out-going MTSE maintains its own, per-entry sequence number in out_SQ. Therefore, only those entries whose MTSE coincidentally have the same value for out_SQ can be combined in a subsequent MultiplexEntrySend message. The trouble this causes during implementation has resulted in some vendors deciding to not send multiple entries in a MultiplexEntrySend message. 2. Solutions There are two solutions to this problem. 2.1 Avoid multiple entries Never send multiple entries in a MultiplexEntrySend message after the first one. The first MultiplexEntrySend message may or may not contain multiple entries. The downside is that one is not using the MultiplexEntrySend message as it was intended to be used, thus wasting a small amount of bandwidth due to duplicated overhead for each MultiplexEntrySend message containing a single entry and the associated time loss, e.g., during session startup, as the sender waits for responses to each request. 2.2 Use a common sequence-number variable Have all of the out-going MTSEs share a single sequence-number variable for determining what sequence number to use for out-going MultiplexEntrySend messages. Each MTSE continues to use its existing, MTSE-specific sequence-number variable for recording the sequence number used in the MultiplexEntrySend message. This is so that responses can be identified as belonging to the same dialogue as the MultiplexEntrySend request. This is backwards compatible with the MTSE defined in previous versions of H.245 because there is no requirement in the in-coming MTSE that the values of MultiplexEntrySend.sequenceNumber be contiguous from one message to another for a given MTSE instance. In effect, sequenceNumber is used as a somewhat unique handle for a brief transaction, not as something that must increase by one each time. The result is that this allows all out-going MultiplexEntrySend messages to contain multiple entries. 2. Text Modifications Here are the required text modifications for the second, common-sequence-number-variable solution. Replace the out_SQ definition in 8.7.3.2/H.245 with these two variables and their descriptions. out_SQ This state variable is used to indicate the most recently sent MultiplexEntrySend message for this MTSE instance. It is mapped to the MultiplexEntrySend message sequenceNumber field before transmission of a MultiplexEntrySend message. global_out_SQ This state variable is used to indicate the most recently sent MultiplexEntrySend message for any MTSE instance. It is incremented by one and assigned to out_SQ before out_SQ is mapped to the MultiplexEntrySend message sequenceNumber field. Arithmetic performed on global_out_SQ is module 256. Replace the contents of the task symbol in Figure 28(i)/H.245 containing "out_SQ := out_SQ + 1" with this: global_out_SQ := global_out_SQ + 1 out_SQ := global_out_SQ 3. Proposal That the text modifications described above be applied to H.245 version 3 to allow all MultiplexEntrySend messages to contain multiple multiplex entries. [end] -- Paul Long___________________________http://www.cmpu.net/public/plong Smith Micro Software, Inc.__________http://www.smithmicro.com/

1 0