- sg16-avd - lists.packetizer.com

Re: Request for document number
by OKUBO Sakae 15 Feb '05

15 Feb '05

Dear Bob and Jean-Pierre, In response to your requests, AVD-numbers have been allocated as follows: At 10:48 -0700 05/02/15, Robert R. Gilman wrote: >Please allocate AVD numbers for the following Avaya contributions to >the Melbourne meeting: AVD-2673 Draft version of H.235.5 - Framework for secure authentication in RAS using weak shared secrets. Avaya AVD-2674 H.323 Extensions for NAT/Application Level Gateway Traversal Avaya AVD-2675 Application Level Gateway Discovery During RAS Avaya At 19:58 +0100 05/02/15, BLIN Jean-Pierre RD-MAPS-ISS wrote: >I intend to write a contribution dealing the Videotelephony service >description. I suggest to name this contribution "Futher >requirements for IP network-based videotelephony services". AVD-2676 Futher requirements for IP network-based videotelephony services France Telecom The current list of registered documents can be found at: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.html http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.xls -- Best regards, OKUBO Sakae e-mail: sokubo(a)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 ******************************************************************

1 0

Re: Re: Request any expert advice to the proposed revises about H.248
by Noah Luo 15 Feb '05

15 Feb '05

Dear All I also wish you all a happy Chinese New Year! whether MG should have certain degree of autonomy has always been a problem for heated debates in SG16 as it was at the last two meetings. To tackle this problem,one should be open-minded.Just as Yangbo analysized,H.248 can be used either for control purpose,or other communications purposes between the MGC and MG.H.248 is a tool to serve more than one objectives.If we view the question from a communications perspective,the MGC and the MG should have a relationship that is more of a peer-to-peer one than a master-and-slave one. As a matter of fact,H.248 is being given more tasks to perform since it is the only communications protocol between the MGC and the MG,an increase in demands for MGC-MG communications can be seen to arise.For example,Ericsson recently proposed to use H.248 for RACS control interface "Ia" in a contribution to the last TISPAN meeting in middle January. As Yangbo pointed out,"the actual networks condition is very complex and the protocol should have the ability to accommodate the different requests as much as possible."Though there are some more reliable protocols like SCTP,one cannot rely solely on such reliable protocols. >From a system engineering point of view,to ensure the reliability of a system,one cannot depends on only one link of the chain even if it is very strong. It seems we still need adequate reasons to reject some thing new that has many potential benefits and few harms. With Best Regards Noah Luo 　　 ======== 2005-02-12 15:20:00 您在来信中写道： ======== Dear All, From 9 to 23 Feb in this year is the "Spring Festival" of China, the most importantest traditional festival for the East, just like the Christmas for the West. Thus, let me bring all the best wishes to all of you ---- Happy Chinese New Year! All of the effort we continue to do for H.248 is to make such most importantest protocol between MG and MGC more perfect. We need to edit or supply the base protocol and the appendix packages once and again just for meeting the more and more requests. So the package maybe full fit the request of the day when it was defined, but the current request from the actual application need it been revised. firstly, the relation of MGC and MG is principal and subordinate from the point of view of control, but peer to peer from the point of view of communication. So MGC monitors MG's status by AuditValue command with empty Audit descriptor and MG monitors MGC's status by Notify command with "ito" observed event are independent each other in theory. MGC can tell MG how to monitor itself, for example using the "mit" parameter to tell MG the message silence limit of MGC. However it is unreasonable for MGC to determine whether MG should monitor itself as the package's original definition. Typically, without MG startup the monitor mechanism on its own initiative, how can we resolve those scenarios described in this contribution's "problem discussion" section? Secondly, the actual networks condition is very complex and the protocol should have the ability to accommodate the different requests as more as possible. We can not only depend the transport to provide the all reliability, just like besides IPSec we should have Interim AH Scheme. The section "MGC-MG link monitoring" in the newest Draft H.248.1 v3 also indicates that we should adopt this application level monitoring when the transport layer can't supply the same function. So the UDP is just a example, the essential we need is a communication-link monitoring mechanism which is independent to the transport layer. In fact, the UDP is also the most common transport layer, should we make a protocol without considering it? finally, the proposed revises to H.248.14 in this contribution is completely compatible with the existing mechanism defined in H.248.14. We recommend the implementer to adopt the new enhanced mechanism because it can resolve more problems, however it is no mandatory. In fact, the implementer may remain the existing devices which comply the original mechanism and develop the new devices which comply the enhanced mechanism in a same networks. It is just a version different and fully backward compatible. Please take above clarifies into your consideration. Thank you very much! Sincerely, Yangbo ----- Original Message ----- From: <mailto:kboyle@nortel.com> Kevin Boyle To: <mailto:linyangbo@huawei.com> Yangbo Lin ; <mailto:itu-sg16@external.cisco.com> ITU-T SG16 Sent: Tuesday, February 08, 2005 5:00 AM Subject: RE: Request any expert advice to the proposed revises about H.248 .14 I believe this is the third meeting at which we will consider these changes, with the Question rejecting the changes the previous two times (Beijing last May, and Geneva in November). I will reiterate for everyone's benefit that the current definition of the package came about as a result of a significant amount of debate across several meetings. The mandate that the MGC first enable this mechanism was one of the key items in those discussions, and was specifically one of the criteria that had to be met to allow the package to consent. I do not believe that we need to attempt to build UDP reliability at the H.248 application layer -- reliability is a transport issue and needs to be solved there. As was mentioned the last two times this was brought up, if guaranteed connections are a requirement for your implementation, then you should use SCTP or TCP as the transport. Forcing additional requirements on other systems that may not need them doesn't appear to be the right way to solve this to me. Kevin _____ From: Yangbo Lin [mailto:linyangbo@huawei.com] Sent: Friday, February 04, 2005 8:59 PM To: ITU-T SG16 Cc: Yangbo Lin Subject: Request any expert advice to the proposed revises about H.248.14 Dear All: The attached document is about some proposed revises to H.248.14 Inactivity Timer Package. It is intended to ITU-T SG16 Rapporteur Meeting on Melbourne (Feb-Mar 2005), but maybe no the final contribution. The delay contribution with the same subject (D0021) had been discussed in the ITU-T SG16 Plenary Meeting on Geneva (Nov 2004). However there were some misunderstanding for that contribution had not been clarified adequately then. So I renewed the document to give more detail about the essentiality of these revises. Please pay attention to the section "Problem Discussion" for the object secenario we aim to resolve, and the chapter "Conclusion" for the detailed revises we proposed. I issue the document inside this mail-list in order to gain your expert advices as more as possible. Any advice or comment from anyone of you is highly appreciated. Thank you very much! Sincerely, Yangbo = = = = = = = = = = = = = = = = = = = = = = 　　　　　　　　致礼！　　　　　　　　　　　　　　Noah Luo 　　　　　　　　　　　　　　noah(a)huawei.com 　　　　　　　　　　　　　　　　　2005-02-16

1 0

FW: I-D ACTION:draft-iab-nat-traversal-considerations-00.txt
by Euchner Martin 15 Feb '05

15 Feb '05

The following document may be of interest to Q.5 -----Original Message----- From: i-d-announce-bounces(a)ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts(a)ietf.org Sent: Dienstag, 15. Februar 2005 16:32 To: i-d-announce(a)ietf.org Cc: iab(a)iab.org Subject: I-D ACTION:draft-iab-nat-traversal-considerations-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Architecture Board Working Group of the IETF. Title : Considerations for Selection of Techniques for NAT Traversal Author(s) : J. Rosenberg Filename : draft-iab-nat-traversal-considerations-00.txt Pages : 21 Date : 2005-2-14 There are many protocols designed and deployed on the Internet today which do not naturally traverse Network Address Translators (NAT). In order to allow these protocols to work in the presence of NAT, additional logic needs to be added to the network. This logic modifies the behavior of the protocol in some way. There are choices where this logic can be placed in the network. It can reside in the NATs themselves, transparently altering the protocol; when this occurs, it is called an Application Layer Gateway (ALG). It can reside in server components, hiding the changes from NATs and clients alike, it can reside in the clients, or it can reside in a combination thereof. The choice of the placement of this logic typically has implications on many aspects of the protocol, including security, deployability, manageability and availability. This document provides a set of considerations that should be taken into account by protocol and network designers when making this choice. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-iab-nat-traversal-considerations -00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request(a)ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-iab-nat-traversal-considerations-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-iab-nat-traversal-considerations-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- In order to maintain computing infrastructure integrity, Cisco Systems Enterprise Messaging Services and InfoSec teams have set a mail policy disallowing executable attachments in email. This message contained an executable attachment type that is prohibited by this policy. The attachment has been removed from this message and copied to quarantine by our systems. It will be held in quarantine for seven days in the event that the content needs to be retrieved. Please be aware many viruses attempt to look like legitimate email or notifications from anti-virus systems. We will clearly mark a seperation between our notifications and the original email as follows: "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY" For further reference information about viruses and email antivirus efforts within Cisco, please visit: http://wwwin.cisco.com/it/ems/services/antiviral If your concern isn't addressed by the information in this notification or the above web page, you may open a support request: http://wwwin.cisco.com/support/ Select "Messaging", "Email-Related", "Mail Routing" Please include in the text of your case the following information: * Full headers of the message. Documentation on displaying the full headers is available at this URL: http://wwwin.cisco.com/support/library/faqs/solution002471.html * This unique quarantine identifier: j1FIX8Tj029899 If the matter is urgent, you may follow up by calling one of the below referenced numbers. Please make every effort to provide the above requested information via the support web tool prior to calling as it will greatly aid the resolution of your issue. Americas: 1 408 526 8888 Asiapac +61 2 8446 8888 EMEA +31 20 485 4888 Japan +81 3 5549 6888 US (Toll Free) 1| 800| 888| 8187| (ext.68888) Thank you for your cooperation, Enterprise Messaging Services Cisco Systems, Inc

1 0

Re: Number Allocations
by OKUBO Sakae 15 Feb '05

15 Feb '05

Dear Mr. Lehmann and Mr. Schwarz, At 10:00 +0100 05/02/15, Leo.Lehmann(a)bakom.admin.ch wrote: >Attached you will find my report from last SG13 meeting. May Iask >you to register the docuemnt for our Melbourne meeting? It has been registered as AVD-2670 and uploaded to the Melbourne directory. At 12:21 +0100 05/02/15, Albrecht.Schwarz(a)alcatel.de wrote: >Please allocate numbers for following two contributions: They have been numbered as follows: AVD-2671 Question(s): Q.3/16 Source*: ALCATEL Title: H.248.14 ? Analysis of Potential Issues AVD-2672 Question(s): Q.3/16 Source*: ALCATEL Title: H.248.14 ? Feedback on Inactivity Counter Proposal The current list of registered documents can be found at the following place: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.html http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.xls You can download documents by ftp with the following URL: ftp://ftp3.itu.int/avc-site/2005-2008/0502_Mel User: avguest Password: Avguest -- Best regards, OKUBO Sakae e-mail: sokubo(a)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 ******************************************************************

1 0

Re: Request Document Numbers
by OKUBO Sakae 15 Feb '05

15 Feb '05

Dear Paul and all, At 00:32 -0500 05/02/15, Paul E. Jones wrote: >Please allocate numbers for the following documents: AVD-numbers have been allocated to them as follows: AVD-2668 Support for the Internet Low Bit Rate Codec (iLBC) within H.323 Systems Cisco Systems AVD-2669 Transport of Geographic Information in H.323 Systems (H.460.geo) Editor (P Jones) Using this opportunity, can I ask all the contributors to check if your documents are properly registered? I might have lost a couple of e-mails. The current list is as follows: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.html http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.xls -- Best regards, OKUBO Sakae e-mail: sokubo(a)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 ******************************************************************

1 0

Re: Document number request
by OKUBO Sakae 14 Feb '05

14 Feb '05

Dear Faisal, At 20:24 +0530 05/02/14, faisal.siyavudeen(a)cisco.com wrote: >I have uploaded AVD-2666 and AVD-2667 to /avc-site/Incoming/ folder. They have been moved to /avc-site/2005-2008/0502_Mel/ directory. -- Best regards, OKUBO Sakae e-mail: sokubo(a)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 ******************************************************************

1 0

Re: Document number request
by OKUBO Sakae 14 Feb '05

14 Feb '05

Dear Faisal, At 12:36 +0530 05/02/14, faisal.siyavudeen(a)cisco.com wrote: >I would like to request document numbers for the following documents >to bepresented at the Melbourne meeting. Thank you for your input contributions. The following AVD-numbers have been allocated to them: AVD-2666 Title: New no-bandwidth error code in H.225.0 AdmissionRejectReason Question(s): Q.2 Source: Cisco Systems, Inc. Purpose: Proposal AVD-2667 Title: Revised H.225.0 Recommendation Question(s): Q.2 Source: Editor Purpose: Proposal (Revised recommendation for discussion and approval) The current list of registered documents can be found at the following place: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.html http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.xls -- Best regards, OKUBO Sakae e-mail: sokubo(a)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 ******************************************************************

1 0

Re: Request any expert advice to the proposed revises about H.248 .14
by Albrecht.Schwarz＠alcatel.de 14 Feb '05

14 Feb '05

Dear LinYangbo, just a feedback: we are presently preparing comments on your preliminary contribution. But we are still struggling with your scenario C because of it's overlapping with ServiceChange procedures. Nevertheless, we'll write down our view latest end of this week for submission to our meeting. Best regards Albrecht Yangbo Lin <linyangbo@huawe To: Kevin Boyle <kboyle(a)nortel.com>, ITU-T SG16 i.com> <itu-sg16(a)external.cisco.com> cc: 12.02.2005 21:20 Subject: Re: Request any expert advice to the proposed revises about H.248 .14 Dear All, From 9 to 23 Feb in this year is the "Spring Festival" of China, the most importantest traditional festival for the East, just like the Christmas for the West. Thus, let me bring all the best wishes to all of you ---- Happy Chinese New Year! All of the effort we continue to do for H.248 is to make such most importantest protocol between MG and MGC more perfect. We need to edit or supply the base protocol and the appendix packages once and again just for meeting the more and more requests. So the package maybe full fit the request of the day when it was defined, but the current request from the actual application need it been revised. firstly, the relation of MGC and MG is principal and subordinate from the point of view of control, but peer to peer from the point of view of communication. So MGC monitors MG's status by AuditValue command with empty Audit descriptor and MG monitors MGC's status by Notify command with "ito" observed event are independent each other in theory. MGC can tell MG how to monitor itself, for example using the "mit" parameter to tell MG the message silence limit of MGC. However it is unreasonable for MGC to determine whether MG should monitor itself as the package's original definition. Typically, without MG startup the monitor mechanism on its own initiative, how can we resolve those scenarios described in this contribution's "problem discussion" section? Secondly, the actual networks condition is very complex and the protocol should have the ability to accommodate the different requests as more as possible. We can not only depend the transport to provide the all reliability, just like besides IPSec we should have Interim AH Scheme. The section "MGC-MG link monitoring" in the newest Draft H.248.1 v3 also indicates that we should adopt this application level monitoring when the transport layer can't supply the same function. So the UDP is just a example, the essential we need is a communication-link monitoring mechanism which is independent to the transport layer. In fact, the UDP is also the most common transport layer, should we make a protocol without considering it? finally, the proposed revises to H.248.14 in this contribution is completely compatible with the existing mechanism defined in H.248.14. We recommend the implementer to adopt the new enhanced mechanism because it can resolve more problems, however it is no mandatory. In fact, the implementer may remain the existing devices which comply the original mechanism and develop the new devices which comply the enhanced mechanism in a same networks. It is just a version different and fully backward compatible. Please take above clarifies into your consideration. Thank you very much! Sincerely, Yangbo ----- Original Message ----- From: Kevin Boyle To: Yangbo Lin ; ITU-T SG16 Sent: Tuesday, February 08, 2005 5:00 AM Subject: RE: Request any expert advice to the proposed revises about H.248 .14 I believe this is the third meeting at which we will consider these changes, with the Question rejecting the changes the previous two times (Beijing last May, and Geneva in November). I will reiterate for everyone's benefit that the current definition of the package came about as a result of a significant amount of debate across several meetings. The mandate that the MGC first enable this mechanism was one of the key items in those discussions, and was specifically one of the criteria that had to be met to allow the package to consent. I do not believe that we need to attempt to build UDP reliability at the H.248 application layer -- reliability is a transport issue and needs to be solved there. As was mentioned the last two times this was brought up, if guaranteed connections are a requirement for your implementation, then you should use SCTP or TCP as the transport. Forcing additional requirements on other systems that may not need them doesn't appear to be the right way to solve this to me. Kevin From: Yangbo Lin [mailto:linyangbo@huawei.com] Sent: Friday, February 04, 2005 8:59 PM To: ITU-T SG16 Cc: Yangbo Lin Subject: Request any expert advice to the proposed revises about H.248.14 Dear All: The attached document is about some proposed revises to H.248.14 Inactivity Timer Package. It is intended to ITU-T SG16 Rapporteur Meeting on Melbourne (Feb-Mar 2005), but maybe no the final contribution. The delay contribution with the same subject (D0021) had been discussed in the ITU-T SG16 Plenary Meeting on Geneva (Nov 2004). However there were some misunderstanding for that contribution had not been clarified adequately then. So I renewed the document to give more detail about the essentiality of these revises. Please pay attention to the section "Problem Discussion" for the object secenario we aim to resolve, and the chapter "Conclusion" for the detailed revises we proposed. I issue the document inside this mail-list in order to gain your expert advices as more as possible. Any advice or comment from anyone of you is highly appreciated. Thank you very much! Sincerely, Yangbo

1 0

Re: Document number request
by OKUBO Sakae 14 Feb '05

14 Feb '05

Dear Christian, At 14:36 +1100 05/02/14, Christian Groves wrote: >I'd like to request document numbers for the following documents: Thank you for your contributions. They have been numbered as follows: AVD-2660: H.248.1 Annex F: Editorial Improvements and Corrections AVD-2661: H.248.1v3: Corrections and Improvements AVD-2662: H.248.1: Enhancements to the Profile Template AVD-2663: H.248.x Sub Series IG: Additions AVD-2664: Introduction of a H.248.x Symmetric RTP/RTCP NAPT Package >The above documents are source : LM Ericsson AVD-2665: Draft H Series Supplement 2 - H.248.x sub-series Package Guide Release 7 >The above document is source : Editor An updated list of registered documents can be found at: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.html http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.xls -- Best regards, OKUBO Sakae e-mail: sokubo(a)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 ******************************************************************

1 0

Re: Contributions to the Melbourne meeting
by OKUBO Sakae 12 Feb '05

12 Feb '05

Dear Sasha, At 19:15 -0500 05/02/12, Sasha Ruditsky wrote: >Can I have a document numbers for the following contribution to Q5: Thank you for your contributions. They have been registered as follows: AVD-2657 "FW/NAT traversal problems" AVD-2658 "Using H.225.0 as transport for H.323 RAS messages" AVD-2659 "Method for media traversal of FW/NAT for H.323" An updated list of registered documents can be found at: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.html http://ftp3.itu.int/av-arch/avc-site/2005-2008/0502_Mel/0502_Mel.xls -- Best regards, OKUBO Sakae e-mail: sokubo(a)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 ******************************************************************

1 0