Templates for November Geneva Meeting

OKUBO Sakae okubo at MXZ.MESH.NE.JP
Tue Oct 12 18:43:02 EDT 2004

Dear Mr. Sakae:

I am so happy to receive much suggestion from you. 
And we will carefully think about all of these . 
The following is our some consideration for disscuss.
Thanks for your suggestion.

Best Regards

Jianfang Li

>>Thank you for your draft. Here are some suggestions for your 
>>consideration, mostly for clarifying the description.
>>1/ I assume this document addresses requirements for the technical 
>>solution of H.323 NAT/firewall traversal, but some statements in 
>>Section 9 might be addressing requirements for the study (or 
>>guidelines), I feel. Though both are important, we need distinction.

Ok. We will think carefully about how to solve this question.

>>2/ I see the following expressions that may already state solutions.
>>- In order to simplify scenarios in figure 2, it is recommended all 
>>realm including GKs are connected by VPN. (Section 7.1)
>>- In these case , it is recommended that all GKs are connected by 
>>VPN, (Section 8.1.2)
>>- If  a  enterprise realm includes more than one GK, it is 
>>recommended that all realms including GKs are connected by VPN. 
>>(Section 8.2)
>>- If GKs is more than one realms, it is recommended that all realms 
>>including GKs are connected by VPN. (Section 9.1.1)
>>- If H.323 endpoints are in the same realm and in the same 
>>multi-level realm, it is recommended that media streams directly go 
>>through between H.323 endpoints.  (Section 9.3)
>>I wonder if these are rather assumptions for this requirement document.

Yes, Indeed, there maybe have some other solutions for these scenarios,
Therefore, we will revise them and provide no specific solution for them. 

>>3/ In each scenario of Section 8, there is a statement "Each H.323 
>>endpoint can act on a caller or a callee. " This looks the 
>>requirement for the NAT/firewall traversal. It could be stated in 
>>Section 9 like "Each H.323 endpoint shall be able to act as a caller 
>>or a callee."

Yes, It is right. We will add this basic requirement in section 9.

>>4/ I wonder if there are essential requirements (stated with "shall") 
>>and optional ones (stated with "should").

OK. we will state more carelly about  essential requirements by "Shall"and optional ones by "Should".
>>5/ I see the term "realm" is one of key words here. It should be 
>>defined in the terminology section and hopefully relevance to "zone" 
>>or "domain" used in other H.323 documents should be stated.

In this document, we use "realm" as many IETF documents do.
do you mean we should use "domain" or "zone" rather than "realm"?

>>Best regards,
>>OKUBO Sakae
>>e-mail: sokubo at waseda.jp
>>Visiting Professor
>>Graduate School of Science and Engineering
>>Waseda University
>>Waseda University, YRP Ichibankan 312        Tel: +81 46 847 5406
>>3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken  Fax: +81 46 847 5413
>>239-0847 Japan
>>                       H.323 videoconferencing: arranged by advice

More information about the sg16-avd mailing list