Dear Senthil
In response to your request, APC-1705 and APC-1706
have been allocated to your contributions.
APC-1705
> Source: Nokia
> Title: On H.323 QoS
APC-1706
> Source: Nokia
> Title: On H.323 Mobility
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: +…
[View More]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???.???
------------------------------------------------------------------------
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 et al Call Flows Supporting H.323 QOS
1669 AT&T et al 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 et al 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 HellstromR
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
1708
1709
1710
----------------------------------------------------------------------------
----
[View Less]
Dear Francois Audet
In response to your request, APC-1703 and APC-1704
have been allocated to your contributions.
APC-1703
> Source: Nortel Networks
> Title: Tones and announcement in fast start
APC-1704
> Source: Nortel Networks
> Title: Modification to gateway decomposition architecture
Best regards,
Sakae OKUBO (Mr.)
***********************************************************
Waseda Research Center
Telecommunications Advancement Organization of Japan (TAO)
5th Floor, …
[View More]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???.???
------------------------------------------------------------------------
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 et al Call Flows Supporting H.323 QOS
1669 AT&T et al 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 et al Framework for Mapping of H.323 QOS over Packet-based
Networks
1671 Intel The H.323 terminal with secured software based Universal
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 HellstromR
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
1706
1708
1709
1710
----------------------------------------------------------------------------
[View Less]
The following contributions have been uploaded in the incoming
directory:
APC-1656 Tunnelling of signalling messages in H.225.0
APC-1657 Applicability of tunnelling mechanism to QSIG
-----
François Audet Tel:+1 408 565 5675 mailto:audet@NortelNetworks.com
Nortel Networks Fax:+1 408 565 2375 http://www.NortelNetworks.com
It was brought to my attention, that one of the last revisions to Annex G
before decision was omitted in the decided version due to my fault as an
editor. This is the syntax of the Annex G message:
Message ::= SEQUENCE
{
body AnnexGMessageBody,
common AnnexGCommonInfo,
...
}
Since the "common" part includes the Sequence Number and other information
needed for lower level treatment of the message, this part should be
decoded first, and the natural order should have been …
[View More]reversed. This is
important since the size of the "body" is not fixed, and for cases in which
there is an error in the encoding of the body.
Message ::= SEQUENCE
{
common AnnexGCommonInfo,
body AnnexGMessageBody,
...
}
This was proposed in the SG16 meeting in Santiago, but during the editing
session, it was omitted.
Since this is already decided, and the change breaks possible existing
implementations, changing it now is next to impossible.
I would like to explore how "impossible" it is: I have a reason to believe
that there are no officially released products that implement Annex G, so
if absolute consensus is reached, we may have a chance to change it in the
Red Bank meeting.
I know this brings painful memories with the H.235 ClearToken, and I really
don't want this to cause frustration and pain. Therefore I ask everyone
whom it might concern, to say if he has any objection in making the change.
If there is even only one objection, I will drop everything, but if there
is none, I will submit this to the Red Bank meeting. Even then, the
acceptance is not guaranteed.
Lior
Lior Moscovici
Program Manager, Servers Group R&D
VocalTec Communications Ltd.
Voice: +972 9 9707767
E-mail: liorm(a)vocaltec.com
Fax: +972 9 9561867
[View Less]
Dear Q12-14/16 experts,
Please find attached the current list of registered documents. Please advise
me if your contributions is missing.
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
*************…
[View More]**********************************************
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???.???
------------------------------------------------------------------------
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 et al Call Flows Supporting H.323 QOS
1669 AT&T et al 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 et al Framework for Mapping of H.323 QOS over Packet-based
Networks
1671 Intel The H.323 terminal with secured software based Universal
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 HellstromR
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
1701
1702
1703
1704
1705
1706
1708
1709
1710
----------------------------------------------------------------------------
----
[View Less]
Dear Archana Nehru,
In response to your request, APC-1699 has been allocated to your contribution.
Source: Trillium Digital Systems
Title: Modifications to the H.225 Annex G protocol
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 …
[View More]7287
e-mail: okubo(a)giti.or.jp
***********************************************************
[View Less]
Dear Mr. Burkert,
In response to your request, APC-1698 has been allocated to your contributions.
> Document Title: Progressive AV coding for packet switched lossy
> networks - a principle approach
>
> Source: Frank Burkert, Siemens AG
> J $B]S (Bgen Pandel, Siemens AG
> Thomas Stockhammer, Munich University of Technology
>
> Scope: Contribution to H.323 Annex I, Packet Switched Visual
> Telephone Systems Over Error Prone Channels
Best regards,
Sakae OKUBO (Mr.)
**…
[View More]*********************************************************
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
***********************************************************
[View Less]
Dear Mr. Skjaeran,
In response to your request, the following APC numbers have been allocated
to your contributions:
APC-1696
> Title: Draft H.323 Annex K (HTTP based service control)
> Source: Editor (E.Skjaeran, Ericsson)
APC-1697
> Title: Additions of codepoints to H.225.0 for service control channel
> Source: Ericsson (E.Skjaeran)
Best regards,
Sakae OKUBO (Mr.)
***********************************************************
Waseda Research Center
Telecommunications Advancement …
[View More]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
***********************************************************
[View Less]
Dear All,
I just went through the descriptions of the Capability Exchange in both the
H.323 and the H.245 documents and it would seem that they are not quite
clear.
The first two sentences in the first paragraph in H.245, "5.2 Capability
Exchange", seem to mean that a terminal should not send any media that "can
not be received" by the receive terminal. The only way to achieve this is
that the receive terminal send a TCS Reject for all those media types that
it can not receive. However, the …
[View More]third sentence contradicts this by stating
that those capabilities that are not understood (or can be used) should be
ignored. Furthermore, the fourth sentence states that not understood
extensions to a capability that is understood (and can be used) should be
ignored, which could result in unsuccessful communication. So how should
this paragraph be read.
The second paragraph in H.245, "5.2 Capability Exchange", states: "The total
capability of a terminal to receive and decode various signals is made known
to the other terminal by transmission of its capability set."
I would say that the "total capability" includes both the receive and the
transmit capabilities and not just its "receive (and decode)" capabilities.
Furthermore, most of section 5.2 talks about capabilities and not about
their exchange.
The fourth paragraph in H.245, "5.2 Capability Exchange", states: "The
absence of _a_ transmit capability indicates that ....". This phrasing (the
"a") suggests that the absence of just one of the capabilities indicates
that no choices are offered.
Section 7.2.3 "Terminal Capability Set Acknowledge", states: "This is used
to confirm receipt of a TerminalCapabilitySet from the peer CESE". In other
words upon reception of a TCS, the Acknowledge should always be sent. So
when should a Reject be sent? The logical succession of TCS messages between
two CESEs is not well documented and clarifying text is required to make
this clear.
Frank
-----------------------------------------------------
Frank Derks |Tel +31 35 6893238 |
Advanced Development |Fax +31 35 6891030 |
Philip Business Communications |P.O. Box 32 |
|1200 JD Hilversum |
|The Netherlands |
----------------------------------------------------|
E-mail: mailto:f.derks@pbc.be.philips.com |
WWW: http://www.business-comms.be.philips.com |
-----------------------------------------------------
[View Less]
