July 1998 - sg16-avd - lists.packetizer.com

H.324 and laptop kits
by Mathieu Weill 01 Jul '98

01 Jul '98

Currently testing some H.324 and H.323 applications, and how they interwork, I am looking for H.324 compliant videoconferencing kits, with camera, software, modem and so on that would be available in Europe. Has anyone details about such products? I also want to set up a demonstration of H.323 or H.324 using a notebook and I'm looking for a kit that could be adapted to both standards, the main concern being the H.324 compatibility of the modem and its tying to the software. Any information would be most valuable Thanks Mathieu Weill Mathieu_Weill(a)inmarsat.org Reply by email please

1 0

Re: ASN.1 accross revisions
by Pete Cordell 01 Jul '98

01 Jul '98

Bancroft, Security is an optional feature, so no endpoint should be required to send ICVs. Does that help, or ruin your plan!? Regards, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell(a)bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 ================================= >---------- >From: Bancroft Scott[SMTP:baos@OSS.COM] >Sent: 30 June 1998 21:21 >To: ITU-SG16(a)MAILBAG.INTEL.COM >Subject: Re: ASN.1 accross revisions > >On Tue, 30 Jun 1998, Pete Cordell wrote: > >> I admit that I am only just hanging in there with this debate, but I >> think I have a possible solution 5 to throw in as a contender. >> >> Looking at the problem a bit laterally, we have RasMessage in UDP >> packets that we want to sign, and H323-UserInformation in the UUIE that >> we want to sign. Currently these are the only chunks of ASN.1 in these >> fields. >> >> We could add a second piece of ASN.1 into these fields (UDP packet and >> UUIE) that contains the signatures, such as: >> >> H323Extra ::= CHOICE >> { >> icv ICV, >> ... >> } >> >> This would be a separate ASN.1 tree. Therefore in a RAS UDP packet you >> would get: >> >> RasMessage chunk of ASN.1 >> H323Extra chunk of ASN.1 typically containing signature >> >> Similarly in the UUIE, you would have >> >> H323-UserInformation chunk of ASN.1 >> H323Extra chunk of ASN.1 >> >> Note that all the key ids and time stamps etc., would remain in the >> RasMessage and H323-UserInformation parts (so they get signed). >> >> I agree this is not beautiful, but it does not require multiple ASN.1 >> encodings, and doesn't radically change the format of the message >> depending on whether you want to sign it or not (as solution 4 seems >> to). > >This crossed my mind a couple days ago, but it is not clear how this >would >be backward compatible. That is, how would an older version handle >this >added information that comes after the H323-UserInformation? I like >the >general idea, but if I am not mistaken it is not backward compatible. > >I have an idea as to how to do as you suggest in a backward compatible >manner, but before I go down that path I need to know the answer to >the question: Are the most recent implementations that know of H.323 >required to transmit an ICV with each RasMessage or >H323-UserInformation? > >------------------------------------------------------------------------ >-- >Bancroft Scott Toll Free >:1-888-OSS-ASN1 >Open Systems Solutions, Inc. >International:1-609-987-9073 >baos(a)oss.com Tech Support >:1-732-249-5107 >http://www.oss.com Fax >:1-732-249-4636 >

1 0

Re: Q11-14 Joint Rapporteur Meeting
by Sakae OKUBO 01 Jul '98

01 Jul '98

Dear Mr. Tosco, >>I confirm the possibility of having the Q11-14 joint Rapporteur meeting >>at CSELT. >>...... Thank you very much for your kind offer. Rapporteurs of Q.11-14/16 would like to gratefully accept this offer. The date will be 17 (Tuesday) - 20 (Friday) November 1998. Let us fix further details when we meet at the September SG16 meeting. 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