- sg16-avd - lists.packetizer.com

For the Red Bank Meeting a late contribution (TD)
by Sebestyen Istvan ICN WN ES SP 4 15 Oct '99

15 Oct '99

<<Td-0x>> Dear all, a last minute late contribution to Red Bank. Regards, Istvan Sebestyen -------------------------------------------------------------------------- Dr. Istvan Sebestyen Siemens AG, ICN M CS27, Hofmannstr. 51 D-81359 Munich Tel:+49-89-722-47230 Fax:+49-89-722-47713 E-Mail: istvan.sebestyen(a)icn.siemens.de Intranet:http://netinfo.icn.siemens.de/es/team/essp/team/essp4 ---------------------------------------------------------------------------- ----------------

1 0

FW: APC-1711, 1712 review
by Nancy-M Greene 15 Oct '99

15 Oct '99

We are getting discussion of the Red Bank contributions on the megaco list. I am crossposting these discussions to the ITU-T SG16 list. Nancy -------------------------------------------------------------------------- Nancy M. Greene Internet & Service Provider Networks, Nortel Networks T:514-271-7221 (internal:ESN853-1077) E:ngreene@nortelnetworks.com > ---------- > From: Rayhan, Abdallah [CAR:5N00:EXCH] > Sent: Thursday, October 14, 1999 11:01 AM > To: megaco(a)standards.nortelnetworks.com > Subject: APC-1711, 1712 review > > > I took a pass through APC-1711 and APC-1712 and I would like to post my > analysis > on the mailing list. I don't claim my analysis to be complete, however I > tried to point > out the main problems I came across while reading APC-1711 ABNF. My > primary > goal is the final ABNF and not the ASN.1 for two reasons. First, I am not > an ASN.1 > expert, so I would leave critiquing it to the ASN.1 experts. Second, it > would > be a big distraction to the IETF having the MEGACO ABNF at an advanced > stage with a set of testbenches (ANNEX G). Hence, I will try to focus on > APC-1711 ABNF > which I call ABNF1711 and MEGACO/H.248 ABNF which I call ABNF248. > > To start with I have noted that the ABNF1711 does not take the ABNF248 as > is > but modifies it to suite ASN.1 encoding ( is ASN.1 so restrictive that it > does not > allow ABNF248 syntax ? ) These discrepancies are found in: (I started > noting > the different PRs but then found myself marking almost every one.) > > - Tagging every value. > ABNF1711: > PkgdName = LBRKT PkgItemID [ PkgName ] RBRKT > PkgName = LBRKT "/" ( ( "PE" EQUAL Name ) / "*" ) RBRKT > PkgItemID = ( ( "PI" EQUAL Name ) / "*" ) > > ABNF248: > pkgdName = [ (PackageName | "*") SLASH ] (ItemID | "*" ) > PackageName = NAME > ItemID = NAME > > You need "PE=" before package name and "PI=" before ItemID. > These differences appear in many production rules. > > - Extra brackets as illustrated in the previous example. In ABNF1711, > there is a curly bracket before and after PkgdName while ABNF248 does not > have that. This is all over ABNF1711. > > - Extensions do not appear any where in ABNF1711 while they are a major > feature of ABNF248. > > -ABNF1711 changes the syntax of the MEGACO constructs. > > ABNF1711: > RequestedActions = LBRKT RequestedAction [ "E" EQUAL > SecondEventsDescriptor ] > [ "SG" EQUAL SignalsDescriptor ] [ "IC" ] RBRKT > > ABNF248: > requestedActions = requestedAction LWSP [COLON LWSP > embeddedSignalEvents ] [COLON LWSP InterceptToken ] > embeddedSignalEvents = firstEmbedding [COMMA firstEmbedding] > > as you can see the first level of embedding (firstEmbedding) is chopped in > ABNF1711. > As a matter of fact, it changes the syntax into something different. > > -ABNF1711 enforces ordering of descriptors and parameters while the > ABNF248 > does not. This issue was raised before and the resolution was made to > enforce no order > since there is no relationship between descriptors, e.g., modems or muxes, > whichever comes > first does not affect the other. > > - ABNF248 uses COMMA as a separator for commands, descriptors > and parameters. This concept is gone in ABNF1711. > > - ABNF1711 changes the syntax and the semantics of MEGACO, e.g., > ABNF1711: > NotifyReply = LBRKT TerminationID [ "ER" EQUAL ErrorDescriptor ] RBRKT > You always have TerminationID regardless of whether it is NotifyReply > error or not, > and ErrorDescriptor is tagged. > > ABNF248 > notifyReply = NotifyToken ( commandError | [EQUAL TerminationID]) > commandError = EQUAL TerminationID LBRKT errorDescriptor RBRKT > TerminationID is optional in pure notify reply and mandatory in notify > error. > ErrorDescriptor is not tagged. > > Also, ABNF1711: > SecurityParmIndex = ( 1( BASE64 ) BASE64END ) > SequenceNum = ( 1( BASE64 ) BASE64END ) > AuthData = ( 5( BASE64 ) BASE64END ) > BASE64 = 4( BASE64CHAR ) > BASE64END = 4( BASE64CHAR ) / ( 3( BASE64CHAR ) "?" ) / ( 2( BASE64CHAR ) > "??" ) > Where did "?" and "??" come from ? > > ABNF248: > SecurityParmIndex = 8(HEXDIG) > SequenceNum = 8(HEXDIG) > AuthData = 32*64(HEXDIG) > > These are some of the differences. If we review each PR, no PR in ABNF1711 > > will be saved. So I will stop here. > > I dont know if the kind of constraints ABNF1711 enforces on the ABNF are > due to > to the ASN.1 encoding constraints or because of ASN.12ABNF. > Whatever the reasoning is, APC1711 should focus on completing the ASN.1 > description and generate similar testbenches as in the MEGACO I-D either > binary or text, or both. The binary will be definitely different than the > text because of > tagging, however the text should be same as the test benches written so > far. > In theory, bin and text should reflect the same protocol and should > introduce the least > entropy into the syntax. > > My recommendation is that rather than writing ASN.12ABNF tool, APC1711 > should write examples that use the ASN.1 and bin2text and text2bin tools > in order to > test the ASN.1 encoding. Once that is out of the way and we know that the > ASN.1 is ok, > we could look into tools like ASN.12ABNF presuming that it would generate > ABNF > that is equivalent to ABNF248 syntactical and semantical wise. Otherwise, > ABNF1711 > approach is unproductive and waste of effort trying to verify every PR of > ABNF1711. > > In addition to that, if we assume that the ASN.1 is ok and the ASN.12ABNF > is > ok, from what I saw both are not, is there any guarantee that when they > change > the ASN.1, that will not introduce problems into the ABNF ? My feeling is > that > it would be a source of confusion and we would need to review the ABNF and > > probably hand craft some PRs to make it consistent and ambiguous free. > If that is that is the case, why should we throw out ABNF248 which > we have tested and have a high degree of confidence in. We are very > familiar > with ABNF248; we know the ins and outs of it; and we know how to fix any > problem > without disturbing the rest of the grammar. How would ABNF1711 do that ? > > As for ASN.1, it is not compatible with the standard. This means that > ASN.1 compilers > can not produce a correct code. > > regards > Abdallah Rayhan > >

1 0

List of documents
by Sakae OKUBO 15 Oct '99

15 Oct '99

Dear Q12-14/16 experts, Please find attached a list of documents for the next week meeting in Red Bank. See you there! 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 *********************************************************** TD-02 (Red Bank) Documents for Q.12-14/16 Rapporteur meeting in Red Bank (18-22 October 1999) The documents can be retrieved as ftp://standard.pictel.com/avc-site/9910_Red/APC-1???.??? or http://standard.pictel.com/ftp/avc-site/9910_Red/APC-1???.??? # Late arrival document. * Yet to be uploaded (as of 19:30 Friday, 15 October, Tokyo time). ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1645 TIPHON Proposal for an H.323 "Security Profile" 1646 Motorola Annex-H(User and Service Mobility in H.323) 1647 Lucent Mobility Agents in H.323 Reference Architecture 1648 Lucent Registration Procedure for Wireless Mobile H.323 Terminals 1649 Lucent Mobility States for the Mobile H.323 Terminals 1650 Lucent H.245 Generic Capabilities Definition and H.225 Packetization Specification for the Cellular/PCS CDMA EVRC Voice Codec. 1651 AT&T H.323 Mobility Architecture and Protocol for Terminal, User, and Service Mobility 1652 AT&T Viewgraph Presentation of H.323 Mobility Architecture and Protocol for Terminal, User, and Service Mobility 1653a PictureTel Proposed text for G.722.1 capabilities in the H.323 Implementor's Guide 1654 Nortel ISO/IEC 11571 addressing in H.323 Annex V Networks 1655 Hitachi Ltd. Real-time system of H.262 layered video transmission 1656 Nortel Networks Tunnelling of signalling messages in H.225.0 1657 Nortel Networks Applicability of signalling tunnelling mechanism to Q.SIG 1658 Editor (K Klaghofer) Draft H.450.9 Call Completion Supplementary Services for H.323 #1659 Nokia Functional Requirements for H.323 Annex H (Terminal, User and Service Mobility) 1660 Mitel, Siemens Proposed H.323 Annex L (Stimulus Protocol) 1661 VocalTec Communications Ltd. Resolution of H.245 ambiguity when using Fast Connect procedure 1662 Intel Corp, VocalTec Communications Ltd. Changes to H.323 to support operation behind basic NAT devices - version 2 1663 Editor (I Suconick) H.341 V2 contribution 1664 AT&T H.323 User, Service, and Service Provider Mobility Framework for Multimedia Intelligent Networking 1665 AT&T Viewgraph Presentation of H.323 User, Service, and Service Provider Mobility Framework for Multimedia Intelligent Networking 1666 Nortel and Siemens Megaco/H.248 Generic Packages 1667 Editor (P Jones) H.323v4 draft 1668 AT&T,VocalTec, Alcatel, Motorola, and 3Com Call Flows Supporting H.323 QOS 1669 AT&T,VocalTec, Alcatel, Motorola, and 3Com Extensions of H.225.0 and H.225.0 Annex G Signaling Messages and their ASN.1 Syntax to Support H.323 QOS 1670 AT&T,VocalTec, Alcatel, Motorola, and 3Com Framework for Mapping of H.323 QOS over Packet-based Networks #*1671 Intel The H.323 terminal with secured software based Universa Subscriber Identification Module (USIM) and Inter-working Function with PLMN (public land and mobile networks) #*1672 Intel User Mobility and Service Mobility services for Wireless Subscribers with H.323 terminals accessing Multimedia over IP (MoIP) and PLMN networks 1673 Hughes Software Systems Redundancy and Fault Tolerance Procedures in H.323 1674 Editor (M Euchner) H.323 Annex J: Security for H.323 Annex F 1675 Editor (M Euchner) H.235 Version 2 1676 Siemens AG ClearToken enhancement in H.235 Version 2 1677 Siemens AG AES support in H.235 Version 2 1678 Siemens AG Elliptic curve support in H.235 Version 2 1679 Siemens AG Security Profile negotiation in H.235 Version 2 1680 SG16 management Draft Questions for SG16 WP2 for the new study period 1681 Siemens AG Identification of Gateway Protocol #*1682 InterVoice Media Redirection and Replication 1683a UK ISUP Transport in H.225 using a Generic, Extensible Framework 1684 Lucent Technologies and VocalTec Multiple UsageIndications in Annex G #*1685 Lucent Technologies Using CPL with H.323 1686 Editor (R Bowen) Draft H.225.0 v4 1687 Lucent Technologies H.323 Annex F Hookflash Signaling Enhancements 1688 Editor (G Hellstrom) H.323 Annex G Text Conversation, draft 1689 Ericsson RTP-Text for H.323 Annex G Text Conversation 1690 Ericsson F.MCVS conversation service description with Total Conversation and Text telephony 1691 Ericsson H.248 packages and additions for text telephony and total conversation. 1692 Motorola Using SCTP as an Alternate H.248 Transport 1693 Editor (P Jones) H.323 Implementers Guide #1694 BT Object Profile for ISUP Transport in H.225 using Generic Extensible Framework 1695 IETF Megaco Working Group Megaco/H.248 Requirements - Communication from IETF 1696 Editor (E.Skjaeran, Ericsson) H.323 Annex K (HTTP based service control) 1697 Ericsson (E.Skjaeran) Additions of codepoints to H.225.0 for service control channel 1698 Siemens, Munich University of Technology Progressive AV coding for packet switched lossy networks - a principle approach 1699a Trillium Digital Systems Modifications to the H.225 Annex G protocol 1700 Rapporteur of Q.19/16 Support of proposed modifications on H.245 ASN.1 1701 NTT DoCoMo Multiplexed stream transmission over H.323 logical channel 1702 NEC Editorial errors in H.245 version 4, version 5 1703 Nortel Networks Tones and announcement in fast start 1704a Nortel Networks Modification to gateway decomposition architecture #1705 Nokia On H.323 QoS #1706 Nokia On H.323 Mobility 1707 Editor (P Jones) Early Termination of Fast Connect Procedure in H.323 1708 Cisco Systems Early Closure of the Call Signaling Channel 1709 Marc Roelands, Siemens ICN On Terminals, Users, Services and Mobility in H.323 1710 Lucent Technologies Changes to H.248 to allow use in non-IP environments 1711 Lucent Technologies, Tech-know-ware ASN.1 syntax definition for H.248 1712 Lucent,Ericsson,Tech-Know-Ware H.248/Megaco Structured Message Encoding using a Text Line Format 1713 LM Ericsson H.248 Line Encoding 1714 LM Ericsson H.248 IANA consideration for Package extension 1715 LM Ericsson H.248 Signal Direction 1716 LM Ericsson Cause Handling in H248 1717 LM Ericsson H.248 Functional Outage 1718 LM Ericsson H.248 ServiceChange 1719 LM Ericsson Monitoring in H248 1720 LM Ericsson H.248 Event Enhancements 1721 LM Ericsson H.248 Multiple Virtual MG Enhancements 1722 ITU-TSB (Frank Cohen) Terminology difference between T.35 and H.225.0 1723 LM Ericsson H.248 Priority calls 1724 LM Ericsson Native Descriptors in H248 1725 LM Ericsson H.248 Signalling Transport Converter for MTP 1726 LM Ericsson H.248 Description of the generic signalling 1727 Editor (Christian Groves) Draft H.246 Annex C 1728 LM Ericsson Negotiation of Protocol Capabilities in H225 RAS 1729 LM Ericsson Sigtran in H225 1730 LM Ericsson Architectural strives for Conversational Multi Media with Multi Access 1731 LM Ericsson Layered Mobility Management architecture in MultiMedia/ MultiAccess 1732 Cisco Systems Proposed FacilityReason Codepoint for New Tokens 1733 Cisco Systems Addition of Billing Information to RAS Messages #*1734 Cisco Systems Support for Multiple Payload Types in Logical Channels 1735 Editors (John Segers, Brian Rosen) Draft H.248 1736 FORE Systems H.248 Transport for ATM #1737 BT Methods of transporting ISUP across H.323: Issues for consideration 1738 Editor (Barry Aronson) H.323 Annex I Terms of Reference, v2 1739 Teles, Universitaet Bremen H.323 robustness mechanisms #*1740 Teles et al Organizing work on H.323 - SIP - Interworking #*1741 RADVision Clarifications for Fast Connect Procedure #*1742 RADVision Clarifications for the use of Call Signaling Address in H.225.0 SETUP Procedure #1743 Q.14 Rapporteur Resolving References to IETF Documents in H.248 #1744 Lucent MG Initiated Call Disconnect #1745 Cisco Clarification of the Alternate Gatekeeper Procedures 1746 SG8 Q4 Liaison Statement on Resolving T.38 Annex B inconsistencies with H.245/H.323 Annex D 1747 SG8 T.38 Call Establishment Ad Hoc Group SG16 Liaison Regarding H.248 & H.248 Call Establishment for T.38 ---------------------------------------------------------------------------- Temporary Documents - Red Bank TD- Source Title 01 Rapps. Q.12, Q.13, Q.14 Agenda for the Red Bank meeting - General 02 Rapps. Q.12, Q.13, Q.14 Documentation for the Red Bank meeting 03 Rapp. Q.12 Agenda for Q.12/16 04 Rapp. Q.13 Agenda for Q.13/16 05 Rapp. Q.14 Agenda for Q.14/16 06 Hughes Software System H.341 Entity-Relationship Diagram 07 Robert R. Gilman (informal contribution in support of Document APC-1660) 08 S Okubo TV Anytime Forum Press Release 09 Siemens Proposal for an enhancement of H.248 protocol for the support of Data connections 10 Cisco Systems Example Call Flows for H.248 support of T1 Robbed Bit Signaling

1 0

TD - 06 Document
by PVSAK Viswanadham 15 Oct '99

15 Oct '99

Hi, I am sending TD-06 tittled "H.341 Entity-Relationship Diagram" as attachment to this mail as my firewall does not allow me to upload it to the ftp site. With Regards, Viswanadham Hughes Software System, India (See attached file: TD-06.zip)

1 0

Delegates staying at Courtyard Lincroft
by Sakae OKUBO 15 Oct '99

15 Oct '99

Dear Red Bank meeting participants, In response to my query, the following two persons have kindly offered rides for my colleague (Mr. Ryo Takahashi, NTT) staying at Courtyard Lincroft: Rex Coldren Lucent Technologies coldrenr(a)agcs.com -or- rcoldren(a)lucent.com Paul K. Reddy Intel paul.k.reddy(a)intel.com If you stay at Courtyard Lincroft without a car, please contact them for car pool. 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

Re: Request for at TD number
by Sakae OKUBO 15 Oct '99

15 Oct '99

Dear Mr. Sharp, Please use TD-10. SOURCE Cisco Systems, Inc. TITLE Example Call Flows for H.248 support of T1 Robbed Bit Signaling PURPOSE Information 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

Uploading TD-08, TD-09
by Sakae OKUBO 14 Oct '99

14 Oct '99

Dear Q12-14/16 experts, The following two TDs have been uploaded at /Incoming for later moving to /9910_Red: TD-08 Source: S Okubo Title: TV Anytime Forum Press Release TD-09 Source: Siemens Title: Proposal for an enhancement of H.248 protocol for the support of Data connections 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-1653A uploaded
by Tony Crossman 14 Oct '99

14 Oct '99

APC-1653A has now been uploaded to ftp://standard.pictel.com/avc-site/incoming This contribution supercedes APC-1653 uploaded earlier this week. Tony Crossman ********************************************* Antony Crossman PictureTel Corporation 100 Minuteman Road, Andover, MA 01810, USA Tel. +1 (978) 292 4557 Fax. +1 (978) 292 3228 email. tonyc(a)pictel.com *********************************************

1 0

H.323v3 and H.225.0v3 with change marks against v2(v2+v2Impl.G)
by Karl.Klaghofer＠ICN.SIEMENS.DE 14 Oct '99

14 Oct '99

Paul, On H.323v3: In the pictel directory 9909_Gen referred to below, there is only the clean copy of H.323v3. Where can I find the H.323v3 decided that shows change marks compared to (H.323v2 + v2 Impl. Guide changes) ? I.e. a change marked H.323v3 document that highlights only v3 changes (i.e. everything that was already part of the v2 Impl Guide should appear as clean text). Glen, On H.225.0v3: The latest files on the pictel 9909_Gen directory are from August 18/August 20. 1) Was there no change anymore up to final decision on Sept. 30 ? 2) The file h225v3bcm.doc on the ftp site has change marks. It appears, that these change marks are against the v3 whitepaper. Where can I find the change marked H.225.0v3 document that highlights only v3 changes (i.e. everything that was already part of the v2 Impl Guide should appear as clean text). Thanks, Karl ------------------------------------------------ Karl Klaghofer, Siemens AG, Dpmt. ICN IB NL D1 Hofmannstr. 51, D-81359 Munich, Germany Tel.: +49 89 722 31488, Fax.: +49 89 722 37629 e-mail: karl.klaghofer(a)icn.siemens.de > -----Ursprüngliche Nachricht----- > Von: Paul E. Jones [SMTP:paul.jones@TIES.ITU.INT] > Gesendet am: Mittwoch, 13. Oktober 1999 05:12 > An: ITU-SG16(a)mailbag.cps.intel.com > Betreff: Re: New H.323v3 document > > Mr. Okubo, > > I have sent e-mail to Mr. Bigi regarding this editorial change, including > the specific details of the change. I also mentioned that I will be > sending > paper and electronic copies of the H.323v3 document, including a copy with > and one without revision marks, that includes this small change. > > Hopefully, this will not cause too much confusion. > > Best Regards, > Paul > > ----- Original Message ----- > From: Sakae OKUBO <okubo(a)giti.or.jp> > To: Paul E. Jones <paul.jones(a)ties.itu.int> > Cc: Q.12-14/16 Reflector <ITU-SG16(a)mailbag.cps.intel.com> > Sent: Tuesday, October 12, 1999 10:48 PM > Subject: Re: New H.323v3 document > > > > Dear Mr. Jones, > > > > I have replaced H323v3_decided_990930.zip in /9909_Gen as requested. I > hope > > the mentioned deletion has been reflected in the file handed (or to be > > handed) to ITU-TSB for publication. > > > > 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 > > *********************************************************** > > > > Date: Tue, 12 Oct 1999 18:28:20 +0200 (MET DST) > > From: "Paul E. Jones" <paul.jones(a)ties.itu.int> > > X-Sender: jonesp(a)ties.itu.ch > > To: Sakae OKUBO <okubo(a)GITI.OR.JP> > > Subject: New H.323v3 document > > MIME-Version: 1.0 > > > > Mr. Okubo, > > > > There was a minor editorial correction made to the H.323v3 document. > The > > document posted made a forward reference to an H.323v4 feature (the > > "additive RRQ", specifically). > > > > I have removed that reference and have also placed a more visible notice > > at the top of the first page and "Summary" page to alert people to the > > fact that this is not the official ITU publication. > > > > Will you please replace the document H323v3_decided_990930.zip in the > > 9909_Gen directory with one with the same name in the Incoming > directory? > > > > Thank you, > > Paul E. Jones > >

3 2

Re: APC-1683
by Sakae OKUBO 14 Oct '99

14 Oct '99

Dear Mike, > Since uploading APC-1683, the source of the document has been changed > from BT to UK. Could you please make this change on your list of > contributions and to the document on the ftp site. Actioned. APC-1683a with requested change is now available at /9910_Red. 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

Someone stays at Courtyard Lincroft?
by Sakae OKUBO 14 Oct '99

14 Oct '99

Dear Red Bank meeting participants, This is a personal message. Please advise me (to okubo(a)giti.or.jp) if someone who will stay at Courtyard Lincroft hotel could kindly help my colleague to commute to the meeting place (Molly Pitcher) by giving him a ride. He will participate in Q12-14 sessions Monday through Friday. 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

Re: Request for Temporary Document number
by Sakae OKUBO 13 Oct '99

13 Oct '99

Dear Mr. Gilman, > My colleague, Nick Palumbo, and I with to request a > temporary document number in order to make an informal > contribution in support of Document APC-1660. Please use TD-07. 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

Additional APC document registration
by Sakae OKUBO 13 Oct '99

13 Oct '99

Dear Q12-14/16 experts, Please be advised that we will review and respond to the following liaison statements from SG8 at the next week meeting: APC-1746 Source: SG8 Q4 Title: Liaison Statement on Resolving T.38 Annex B inconsistencies with H.245/H.323 Annex D APC-1747 Source: SG8 T.38 Call Establishment Ad Hoc Group Title: SG16 Liaison Regarding H.248 & H.248 Call Establishment for T.38 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

Red Bank meeting reminder
by Glen Freundlich 13 Oct '99

13 Oct '99

Colleagues, Don't forget to bring your own cable to connect your PC to the network. Glen -- 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

2 1

e-mail address SG16
by Patrick Luthi 13 Oct '99

13 Oct '99

ITU-SG16(a)mailbag.cps.intel.com

1 0

APC-1744
by Matt Holdrege 13 Oct '99

13 Oct '99

Q14'ers... I've uploaded APC-1744 (MG Initiated Call Disconnect) to the incoming directory.

1 0

duplicate mail problem
by Chip Sharp 13 Oct '99

13 Oct '99

Is anyone else having a problem with receiving several duplicates for every email posted to the list? Thanks, Chip Support NetAid! http://www.netaid.org -------------------------------------------------- Chip Sharp Consulting Engineering Cisco Systems Telco Bio-region Reality - Love it or Leave it. --------------------------------------------------

1 0

APC-1659
by jaakko.sundquist＠NOKIA.COM 13 Oct '99

13 Oct '99

I am sending the APC-1659 to the reflector as I seem to have trouble uploading it to the Incoming-directory. Sorry about the delay of the contribution. <<APC1659.doc>> - Jaakko Sundquist ------------------------------------------------------- In a hole in the ground there lived a hobbit. Not a nasty, dirty, wet hole, filled with the ends of worms and an oozy smell, nor yet a dry, bare, sandy hole with nothing in it to sit down on or to eat: it was a hobbit-hole, and that means comfort. -------------------------------------------------------

1 0

Re: Req for APC number.
by Sakae OKUBO 13 Oct '99

13 Oct '99

Dear Viswanadham, > I represent Hughes Software System, India. I request you to allocate an > APC number for a contribution tittled "H.341 Entity-Relationship Diagram". Unfortunately the APC document registration has been closed (the deadline passed). However, your contribution is welcome as TD-06. How Temporary Documents are considered is subject to the meeting agreement. Please make it available according to the procedure for APC documents (see http://standard.pictel.com/ftp/avc-site/9910_Red/Notice_Red_Bank.txt) 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

Contributions for the Red Bank meeting
by Sakae OKUBO 13 Oct '99

13 Oct '99

Dear Q12-14/16 experts, Please find attached an updated list of APC numbered contributions as of 14:00 Wednesday (Tokyo time). To implement the following agreement at the Berlin meeting, I have marked late arrival documents (those not uploaded on time) with #. "Late contributions which were not uploaded on time can be considered if the meeting agrees. This should be handled on a case by case basis; some documents may have no problems, but others may need review of experts. Rapporteur in charge will consult with the meeting at his session if it accepts the late contribution." - Section 2/APC-1644 Please note that original APC-1722 (from Ericsson) has been withdrawn and this number is reused for the message from Mr. F Cohen (ITU-TSB) addressing the different terminology in T.35 and H.225.0. Please also note that APC-1653 and APC-1704 have been (will be) revised; their file names have an alphabet after the number like APC-1704a.zip. 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 Red Bank (18-22 October 1999) The documents can be retrieved as ftp://standard.pictel.com/avc-site/9910_Red/APC-1???.??? or http://standard.pictel.com/ftp/avc-site/9910_Red/APC-1???.??? # Late arrival document. * Yet to be uploaded. ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1645 TIPHON Proposal for an H.323 "Security Profile" 1646 Motorola Annex-H(User and Service Mobility in H.323) 1647 Lucent Mobility Agents in H.323 Reference Architecture 1648 Lucent Registration Procedure for Wireless Mobile H.323 Terminals 1649 Lucent Mobility States for the Mobile H.323 Terminals 1650 Lucent H.245 Generic Capabilities Definition and H.225 Packetization Specification for the Cellular/PCS CDMA EVRC Voice Codec. 1651 AT&T H.323 Mobility Architecture and Protocol for Terminal, User, and Service Mobility 1652 AT&T Viewgraph Presentation of H.323 Mobility Architecture and Protocol for Terminal, User, and Service Mobility 1653 PictureTel Proposed text for G.722.1 capabilities in the H.323 Implementor's Guide 1654 Nortel ISO/IEC 11571 addressing in H.323 Annex V Networks 1655 Hitachi Ltd. Real-time system of H.262 layered video transmission 1656 Nortel Networks Tunnelling of signalling messages in H.225.0 1657 Nortel Networks Applicability of signalling tunnelling mechanism to Q.SIG 1658 Editor (K Klaghofer) Draft H.450.9 Call Completion Supplementary Services for H.323 #*1659 Nokia Functional Requirements for H.323 Annex H (Terminal, User and Service Mobility) 1660 Mitel Proposed H.323 Annex L (Stimulus Protocol) 1661 VocalTec Communications Ltd. Resolution of H.245 ambiguity when using Fast Connect procedure 1662 VocalTec Communications Ltd. et. al. Changes to H.323 to support operation behind basic NAT devices - version 2 1663 Editor (I Suconick) H.341 V2 contribution 1664 AT&T H.323 User, Service, and Service Provider Mobility Framework for Multimedia Intelligent Networking 1665 AT&T Viewgraph Presentation of H.323 User, Service, and Service Provider Mobility Framework for Multimedia Intelligent Networking 1666 Nortel and Siemens Megaco/H.248 Generic Packages 1667 Editor (P Jones) H.323v4 draft 1668 AT&T,VocalTec, Alcatel, Motorola, and 3Com Call Flows Supporting H.323 QOS 1669 AT&T,VocalTec, Alcatel, Motorola, and 3Com Extensions of H.225.0 and H.225.0 Annex G Signaling Messages and their ASN.1 Syntax to Support H.323 QOS 1670 AT&T,VocalTec, Alcatel, Motorola, and 3Com Framework for Mapping of H.323 QOS over Packet-based Networks #*1671 Intel The H.323 terminal with secured software based Universa Subscriber Identification Module (USIM) and Inter-working Function with PLMN (public land and mobile networks) #*1672 Intel User Mobility and Service Mobility services for Wireless Subscribers with H.323 terminals accessing Multimedia over IP (MoIP) and PLMN networks 1673 Hughes Software Systems Redundancy and Fault Tolerance Procedures in H.323 1674 Editor (M Euchner) H.323 Annex J: Security for H.323 Annex F 1675 Editor (M Euchner) H.235 Version 2 1676 Siemens AG ClearToken enhancement in H.235 Version 2 1677 Siemens AG AES support in H.235 Version 2 1678 Siemens AG Elliptic curve support in H.235 Version 2 1679 Siemens AG Security Profile negotiation in H.235 Version 2 1680 SG16 management Draft Questions for SG16 WP2 for the new study period 1681 Siemens AG Identification of Gateway Protocol #*1682 InterVoice Media Redirection and Replication 1683 BT ISUP Transport in H.225 using a Generic, Extensible Framework 1684 Lucent Technologies and VocalTec Multiple UsageIndications in Annex G #*1685 Lucent Technologies Using CPL with H.323 1686 Editor (R Bowen) Draft H.225.0 v4 1687 Lucent Technologies H.323 Annex F Hookflash Signaling Enhancements 1688 Editor (G Hellstrom) H.323 Annex G Text Conversation, draft 1689 Ericsson RTP-Text for H.323 Annex G Text Conversation 1690 Ericsson F.MCVS conversation service description with Total Conversation and Text telephony 1691 Ericsson H.248 packages and additions for text telephony and total conversation. 1692 Motorola Using SCTP as an Alternate H.248 Transport 1693 Editor (P Jones) H.323 Implementers Guide #*1694 BT Object Profile for ISUP Transport in H.225 using Generic Extensible Framework 1695 IETF Megaco Working Group Megaco/H.248 Requirements - Communication from IETF 1696 Editor (E.Skjaeran, Ericsson) H.323 Annex K (HTTP based service control) 1697 Ericsson (E.Skjaeran) Additions of codepoints to H.225.0 for service control channel 1698 Siemens, Munich University of Technology Progressive AV coding for packet switched lossy networks - a principle approach 1699 Trillium Digital Systems Modifications to the H.225 Annex G protocol 1700 Rapporteur of Q.19/16 Support of proposed modifications on H.245 ASN.1 1701 NTT DoCoMo Multiplexed stream transmission over H.323 logical channel 1702 NEC Editorial errors in H.245 version 4, version 5 1703 Nortel Networks Tones and announcement in fast start 1704 Nortel Networks Modification to gateway decomposition architecture #*1705 Nokia On H.323 QoS #*1706 Nokia On H.323 Mobility 1707 Editor (P Jones) Early Termination of Fast Connect Procedure in H.323 1708 Cisco Systems Early Closure of the Call Signaling Channel 1709 Marc Roelands, Siemens ICN On Terminals, Users, Services and Mobility in H.323 1710 Lucent Technologies Changes to H.248 to allow use in non-IP environments 1711 Lucent Technologies, Tech-know-ware ASN.1 syntax definition for H.248 1712 Lucent,Ericsson,Tech-Know-Ware H.248/Megaco Structured Message Encoding using a Text Line Format 1713 LM Ericsson H.248 Line Encoding 1714 LM Ericsson H.248 IANA consideration for Package extension 1715 LM Ericsson H.248 Signal Direction 1716 LM Ericsson Cause Handling in H248 1717 LM Ericsson H.248 Functional Outage 1718 LM Ericsson H.248 ServiceChange 1719 LM Ericsson Monitoring in H248 1720 LM Ericsson H.248 Event Enhancements 1721 LM Ericsson H.248 Multiple Virtual MG Enhancements 1722 ITU-TSB (Frank Cohen) Terminology difference between T.35 and H.225.0 1723 LM Ericsson H.248 Priority calls 1724 LM Ericsson Native Descriptors in H248 1725 LM Ericsson H.248 Signalling Transport Converter for MTP 1726 LM Ericsson H.248 Description of the generic signalling 1727 Editor (Christian Groves) Draft H.246 Annex C 1728 LM Ericsson Negotiation of Protocol Capabilities in H225 RAS 1729 LM Ericsson Sigtran in H225 1730 LM Ericsson Architectural strives for Conversational Multi Media with Multi Access 1731 LM Ericsson Layered Mobility Management architecture in MultiMedia/ MultiAccess 1732 Cisco Systems Proposed FacilityReason Codepoint for New Tokens 1733 Cisco Systems Addition of Billing Information to RAS Messages #*1734 Cisco Systems Support for Multiple Payload Types in Logical Channels 1735 Editors (John Segers, Brian Rosen) Draft H.248 1736 FORE Systems H.248 Transport for ATM #*1737 BT Methods of transporting ISUP across H.323: Issues for consideration 1738 Editor (Barry Aronson) H.323 Annex I Terms of Reference, v2 1739 Teles, Universitaet Bremen H.323 robustness mechanisms #*1740 Teles et al Organizing work on H.323 - SIP - Interworking #*1741 RADVision Clarifications for Fast Connect Procedure #*1742 RADVision Clarifications for the use of Call Signaling Address in H.225.0 SETUP Procedure #*1743 Q.14 Rapporteur Resolving References to IETF Documents in H.248 #*1744 Lucent MG Initiated Call Disconnect #*1745 Cisco Clarification of the Alternate Gatekeeper Procedures ----------------------------------------------------------------------------

1 0

Re: New H.323v3 document
by Sakae OKUBO 13 Oct '99

13 Oct '99

Dear Mr. Jones, I have replaced H323v3_decided_990930.zip in /9909_Gen as requested. I hope the mentioned deletion has been reflected in the file handed (or to be handed) to ITU-TSB for publication. 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 *********************************************************** Date: Tue, 12 Oct 1999 18:28:20 +0200 (MET DST) From: "Paul E. Jones" <paul.jones(a)ties.itu.int> X-Sender: jonesp(a)ties.itu.ch To: Sakae OKUBO <okubo(a)GITI.OR.JP> Subject: New H.323v3 document MIME-Version: 1.0 Mr. Okubo, There was a minor editorial correction made to the H.323v3 document. The document posted made a forward reference to an H.323v4 feature (the "additive RRQ", specifically). I have removed that reference and have also placed a more visible notice at the top of the first page and "Summary" page to alert people to the fact that this is not the official ITU publication. Will you please replace the document H323v3_decided_990930.zip in the 9909_Gen directory with one with the same name in the Incoming directory? Thank you, Paul E. Jones

2 1

Corrupted APC-1714, 1715, 1717, 1720, 1724
by Sakae OKUBO 12 Oct '99

12 Oct '99

Dear Mr. Groves, Dear Mr. Euchner, I have found that their long files names are not friendly to my zip software. I have opened each of them, "saved as" with a short file name like APC-1714.doc and then zipped it. Now they are at /9910_Red directory replacing corrupted ones. 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

Re: Urgent Request for doc # for Red Bank meeting
by Sakae OKUBO 12 Oct '99

12 Oct '99

Dear Mr. Crossman, > The PictureTel contribution apc-1653 has some error and omission > in it. Would you object if we submit a new revised apc-1653 as revision > R1. (e.g. apc-1653R1). the new content adds a missing table. > > This work (in apc 1653) was reviewed and approved in Berlin, and part of > the work is now in the Determination stage in WP3. It is important we > correct it quickly. Please upload it as APC-1653a which will replace the original one. 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 number allocation
by Sakae OKUBO 12 Oct '99

12 Oct '99

Dear Mr. Skran, Dear Mr. Jones, The following APC numbers have been allocated to your contributions: APC-1744 Source: Lucent Title: MG Initiated Call Disconnect APC-1745 Source: Cisco Title: Clarification of the Alternate Gatekeeper Procedures These will be the last APC documents for the Red Bank meeting. From this point, new inputs, if any, are handled as TDs. 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-1673
by Sunil Chandra 12 Oct '99

12 Oct '99

Hi, I am sending APC 1673 as attachment to this mail as my I could not upload it due to network problems. Sorry for the inconvenience. With regards, Sunil Chandra Hughes Software Systems Ltd. (See attached file: apc-1673.zip)

1 0