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

H.235 decided clean text
by Sakae Okubo 26 Feb '98

26 Feb '98

Dear Q.12-14/16 colleagues, H.235 decided version is now available at the GCL ftp site: ftp://itu-t:sg15!avc@ftp.gctech.co.jp/9801_Gen/h235fin2.zip some time later at (mirror ftp://standard.pictel.com/video-site/h235fin2.zip ) ( http://standard.pictel.com/ftp/avc-site/h235fin2.zip) Best regards, Sakae OKUBO (Mr.) ******************************************************************** Graphics Communication Laboratories Phone: +81 3 5351 0181 6F ANNEX TOSHIN BLDG. Fax: +81 3 5351 0184 4-36-19 Yoyogi, Shibuya-ku, Tokyo e-mail: okubo(a)gctech.co.jp 151-0053 Japan ********************************************************************

1 0

H.323 integrated in the ftp site
by Sakae Okubo 26 Feb '98

26 Feb '98

Dear Francois Audet, >>Something must have gone wrong, because I just downloaded >>/9801_Gen/H323v2_D.zip and it does NOT have the changes of >>TD72_PLEN integrated in it. com-16-54-w323-chgs-accepted-final.doc >>does have the changes. They are not the same file. Also, on >>the Web page TD72_PLE.zip also points to H323v2nc_6.zip which is >>also not the final H.323. >> >>I am sending it to you again. Thank you again for your help. I have found that link setting was not correct for H.323 decided version and TD72_PLEN. To my surprise, this error happened here and there in 9801_Gen.html. File contents with indicated file names were correct. (This was my first try to use links.) All link errors have now been corrected. Best regards, Sakae OKUBO (Mr.) ******************************************************************** Graphics Communication Laboratories Phone: +81 3 5351 0181 6F ANNEX TOSHIN BLDG. Fax: +81 3 5351 0184 4-36-19 Yoyogi, Shibuya-ku, Tokyo e-mail: okubo(a)gctech.co.jp 151-0053 Japan ********************************************************************

1 0

Re: Addressing information in H.450.1
by Karl Klaghofer 25 Feb '98

25 Feb '98

Pete, Table 6/H.450.1 has not changed in Geneva, i.e. the table within the H.450.1 whitepaper you are referring to is still o.k. Remark: Since the ISDN like concept of Calling / Connected Line Identification Presentation / Restriction is not known in H.323, types like Table 6/H.450.1 PresentedNumberScreened, etc. have not been used within H.450.2, .3 (Only PresentationAllowedIndicator is used within Call Diversion). Once we want to make use of ISDN like Identification Presentation / Restriction concept within Supplementary Services, I would for consistency reasons also see the PartyNumber within types like NumberScreened or Address being replaced by EndpointAddress (which would e.g. enable to request presentation restriction at the destination side of an Alias other than PartyNumber). Karl ============================ Karl Klaghofer Siemens AG, Dpt. PN VS LP 3 D-81359 Munich, Germany Hofmannstr. 51 Tel.: +49 89 722 31488 Fax.: +49 89 722 22909 Mail.: karl.klaghofer(a)pn.siemens.de ============================ -----Original Message----- From: Pete Cordell [SMTP:pete.cordell@BT-SYS.BT.CO.UK] Sent: Mittwoch, 25. Februar 1998 09:04 To: ITU-SG16(a)mailbag.jf.intel.com Subject: Addressing information in H.450.1 Dear Karl (or anybody else who can answer), Please can you assure me that the majority of the partyNumber fields in Table 6/H.450.1 (white) should indeed refer PartyNumber and not to EndpointAddress as I would have first expected!!! Many thanks, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell(a)bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 =================================

1 0

H.323 integrated in the ftp site
by Sakae Okubo 25 Feb '98

25 Feb '98

Daer Francois Audet, >>The integrated H.323 referencend in >>ftp://itu-t:sg15!avc@ftp.gctech.co.jp/9801_Gen/9801_Gen.html seem to >>be the wrong version. My understanding is that the file named >>"com-16-54-w323-chgs-accepted-final.doc" contained all the changes >>(including TD72). The file was in the Incoming directory, but seems >>to have been deleted. Thank you for your advice. I should have mentioned this, but the file /9801_Gen/H323v2_D.zip is the same as the one you found in the Incoming directory. Due to its very long file name, my Mac could not unzip the original posting. So I shortened the file name to H323v2_D.doc, zipped and moved it to 9801_Gen directory. Best regards, Sakae OKUBO (Mr.) ******************************************************************** Graphics Communication Laboratories Phone: +81 3 5351 0181 6F ANNEX TOSHIN BLDG. Fax: +81 3 5351 0184 4-36-19 Yoyogi, Shibuya-ku, Tokyo e-mail: okubo(a)gctech.co.jp 151-0053 Japan ********************************************************************

1 0

Edit to Q14 report
by Mark Reid 24 Feb '98

24 Feb '98

In the Question 14 meeting report, In the middle line of clause 3.8.5.2 bullet 3, "TD50 (PLEN)", should be "TD50 (WP2/16)" Thanks to Ken Krechmer for spotting this error. Mark Reid VideoServer Inc 781-505-2368 (tele) mreid(a)videoserver.com

1 0

Technical Corrigendums to ASN.1 (X.680)
by Toby Nixon 24 Feb '98

24 Feb '98

I noticed in ITU Operational Bulletin No. 660 (1 Feb 1998) that two technical corrigenda and a second amendment to X.680 have been adopted. They are described in the Bulletin as follows: - Technical Corrigendum 1 to Amendment 1 of ITU-T Recommendation X.680: Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation - Amendment 1: Rules of extensibility - Technical Corrigendum 1 - Technical Corrigendum 2 to ITU-T Recommendation X.680: Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation - Technical Corrigendum 2 - Amendment 2 to ITU-T Recommendation X.680: Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation - Amendment 2: Remove Definition of Root Arcs of Object Identifier Tree Has anyone checked these changes to X.680 to see if they have any impact on the usage of ASN.1 in Recommendations under the control of SG 16? -- Toby ___________________________________________________________ Toby Nixon, Program Manager - NetMeeting http://www.microsoft.com/netmeeting Microsoft Corporation, Applications and Internet Client Group, Redmond WA USA +1 (425) 936-2792 Fax: +1 (425) 936-7329 mailto:tnixon@microsoft.com

1 0

Geneva outcome at the ftp site - corrected
by Sakae Okubo 24 Feb '98

24 Feb '98

/// Please discard my previous mail; I have found H.323 v2 update /// /// in the /Incoming directory. /// Dear Q.12-14/16 colleagues, I have collected files from the Geneva SG16 meeting at ftp://itu-t:sg15!avc@ftp.gctech.co.jp/9801_Gen/ (mirror ftp://standard.pictel.com/avc-site/9801_Gen/) but the following are missing: H.235 (decided) TD-1/PLEN or more desirably integrated text H.323 Annex D (determined) TD-71/PLEN Please owners of these files upload them at /Incoming directory. For retrieval, please take a look first at 9801_Gen.html. Best regards, Sakae OKUBO (Mr.) ******************************************************************** Graphics Communication Laboratories Phone: +81 3 5351 0181 6F ANNEX TOSHIN BLDG. Fax: +81 3 5351 0184 4-36-19 Yoyogi, Shibuya-ku, Tokyo e-mail: okubo(a)gctech.co.jp 151-0053 Japan ********************************************************************

1 0

Geneva outcome at the ftp site
by Sakae Okubo 24 Feb '98

24 Feb '98

Dear Q.12-14/16 colleagues, I have collected files from the Geneva SG16 meeting at ftp://itu-t:sg15!avc@ftp.gctech.co.jp/9801_Gen/ (mirror ftp://standard.pictel.com/avc-site/9801_Gen/) but the following are missing: H.235 (decided) TD-1/PLEN or more desirably integrated text H.323 (decided) TD-72/PLEN or more desirably integrated text H.323 Annex D (determined) TD-71/PLEN Please owners of these files upload them at /Incoming directory. For retrieval, please take a look first at 9801_Gen.html. Best regards, Sakae OKUBO (Mr.) ******************************************************************** Graphics Communication Laboratories Phone: +81 3 5351 0181 6F ANNEX TOSHIN BLDG. Fax: +81 3 5351 0184 4-36-19 Yoyogi, Shibuya-ku, Tokyo e-mail: okubo(a)gctech.co.jp 151-0053 Japan ********************************************************************

1 0

Addressing information in H.450.1
by Pete Cordell 24 Feb '98

24 Feb '98

Dear Karl (or anybody else who can answer), Please can you assure me that the majority of the partyNumber fields in Table 6/H.450.1 (white) should indeed refer PartyNumber and not to EndpointAddress as I would have first expected!!! Many thanks, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell(a)bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 =================================

1 0

Re: User Information or Information in H.225.0
by Callaghan, Robert 23 Feb '98

23 Feb '98

Pete, Just a minor adjustment. H.450.1 specifies the use of call-independent signaling. Bob -------------------------------------- Robert Callaghan Siemens Business Communication Systems Email: Robert.Callaghan(a)Siemenscom.com Tel: +1.561.997.3756 FAX: +1.561.997.3403 >-----Original Message----- >From: Pete Cordell [SMTP:pete.cordell@BT-SYS.BT.CO.UK] >Sent: Friday, February 20, 1998 8:44 AM >To: ITU-SG16(a)MAILBAG.INTEL.COM >Subject: Re: User Information or Information in H.225.0 > >Glen, > >On closer examination there seem to be a few errors in Table 4/H.225.0. >The 6th paragraph of section 7.1/H.225.0 (white paper at least) says >that the "The procedures of Q.931/Section 3.1 for circuit mode >connection setup are followed." According to this section the messages >"User Information" and "Congestion Control" do not apply. They are used >in the call-independent signalling part that we are not using. > >Also "Status Inquiry" is spelt "Status Enquiry" in Q.931 (not that I >would know what is the right form!!!). > >We need to go with option 1 of your suggestions. The Information >message is what we need for overlap sending. The description part of >7.3.6 is correct for the "Information" message (including the reference >to the table in Q.931). > >If we can silently remove "Congestion Control" at the same time so much >the better!!!!! > >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: Glen Freundlich[SMTP:ggf@LUCENT.COM] >>Sent: 19 February 1998 16:09 >>To: ITU-SG16(a)MAILBAG.INTEL.COM >>Subject: User Information or Information in H.225.0 >> >>In H.225.0 V1, section 7.3.6 describes the User Information message. >>The >>related ASN.1 definition is named UI-UUIE, but the table and caption >>(Table 9) describe the Q.931 Information message. >> >>H.323 V2 describes the use of the Information message (for example, to >>support overlap sending), but H.225.0 V2 contains no section describing >>the Information message and no ASN.1 has been defined specifically for >>use with the Information message. >> >>Possible fixes seem to be: >> >>1 - rename section 7.3.6 from "User Information" to "Information" and >>add some text stating that the Information message is used to support >>overlap sending >> >>2 - correct section 7.3.6 to align with the User Information message >>(correct the table, correct the reference to Q.931) and add a new >>section (and associated ASN.1) for the Information message >> >>3 - other suggestions? >> >>As backward compatibility is a concern, the best approach depends on >>existing implementations and the use of User Information or Information >>messages. So, a vendor that decides to implement might interpret this >>to >>be a User Information message with a different set of information >>elements (not as described in table 9/H225) or an Information message >>with the set of information elements as defined in table 9. >> >>Please comment. >> >>Regards, >>Glen Freundlich (editor H.225.0) >> >> >>-- >>Glen Freundlich ggf(a)lucent.com >>Lucent Technologies office: +1 303 538 2899 >>11900 N. Pecos fax: +1 303 538 3907 >>Westminster, Colorado 80234 USA >>

1 0