Comments on H.bmultipoint

[Li Yan]

Dear Mr. Okubo, Mr. Harasaki and other Q.12/16 experts,

Attached please find some comments on the suggestions/changes proposed
by Mr. Okubo and Mr.Haraski.

Thanks,

Li Yan
****************************************************************
Lucent Technologies                     Phone: 732-957-3877
2E-433, 200 Laurel Ave.,                Fax:   732-957-5627
Middletown, NJ, 07733                   E-amil:lyan at lucent.com
U.S.A.
****************************************************************

1. Structure of Chapter 5 and Chapter 7

SO> I would suggest to leave in Chapter 5 the current 5.1 Various VC
SO> connection configurations, explanations of "meet-me" and "dial-out"
SO> and general configuration of MCU as described in 5.2 and illustrated
SO> in Figure 3, but to move other materials (5.3 and subsequent
SO> sub-sections) to Chapter 7 and merge them with the materials there.
If
SO> this idea is agreeable, the title of the current 5.2 should exclude
SO> "characteristics" and the description should be without "shall".

This is fine with me.

2. Figure 3 and functions of MC, MP, MR and network Interface

SO> MC handles DSS2 call signaling and H.245 control signaling in AAL
SO> or higher layers of each port to the terminal. In addition to them,
MC
SO> contains intelligence on top of DSS2 and H.245 handling to manage
SO> multiple ports participating in a multipoint conference. This
SO> intelligence corresponds to "Call Management" in Figure 2/H.310. The
SO> "Call Control" in MC should more appropriately be named "Call
SO> Management".

This is just a possibility. Another possible implementation is that MC
handles all H.245 related control and some of the DSS2 call control
management (on top of DSS2) while network interface card handles DSS2
and below layer3 functions.


SO> MP handles audio, video and data signals in AAL or higher layers.

I thank so too.

SO> MR handles ATM cells in the ATM layer? Or it handles signals above
SO> ATM (between ATM and AAL)?

Is this implementation dependent?

HH>According to your and Mr. Okubo's comments, I have put revised Figure
3
HH> as hbmul3v2.ppt in incoming directory of ftp.gctech.co.jp.The
PowerPoint HH> file Have two figures.  One is single physical network
interface HH> version, the other is virtual network interface per peer
version like HH> H.231.

HH> Which figure is better?
HH> Should we need to include "call control" next to Network Interface?

Either one is ok with me. But I don't want to exclude the possibility of
implementing DSS2 call control in Network Interface. We could either
include "call control" next to network Interface or put some text to
explain it.

3. H.245 for multipoint and Video mixing in Section 8

I will get back to you tomorrow.