- sg16-avd - lists.packetizer.com

FW: ITU-T SG 16 request for registration of new SDP att-field ("T38VendorInfo")(Completed)
by simao.campos＠itu.int 26 Jul '05

26 Jul '05

For your information. Simao -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: 25 July 2005 21:15 To: 'Hiroshi Tamura' Cc: Campos, Simao; sob(a)harvard.edu; Frost, Isabelle Subject: RE: ITU-T SG 16 request for registration of new SDP att-field ("T38VendorInfo")(Completed) Dear Hiroshi Tamura, Please accept our apologies for the delay in processing your request. It took an unusally long time for one of our experts to respond to our inquiry regarding your request. We have registered the SDP att-field "T38VendorInfo". See the following: http://www.iana.org/assignments/sdp-parameters Thank you, Michelle Cotton IANA > > > > -----Original Message----- > > > > From: simao.campos(a)itu.int [mailto:simao.campos@itu.int] > > > > Sent: Monday, January 24, 2005 4:15 AM > > > > To: iana(a)iana.org > > > > Cc: sob(a)harvard.edu; tamura(a)toda.ricoh.co.jp; > > > > webmaster(a)iana.org; Isabelle.Frost(a)itu.int > > > > Subject: ITU-T SG 16 request for registration of new SDP > > > > att-field > > > > ("T38VendorInfo") > > > > > > > > To: > > > > Internet Assigned Numbers Authority > > > > 4676 Admiralty Way, Suite 330 > > > > Marina del Rey, CA 90292 > > > > USA > > > > > > > > +1-310-823-9358 (phone) > > > > +1-310-823-8649 (facsimile) > > > > > > > > > > > > Dear Sirs > > > > > > > > Recently, an Amendment was approved to ITU-T Rec.T.38 and a new > > > > SDP att-field called "T38VendorInfo" was defined, necessitating > > > > its registration in your database. > > > > > > > > This request was initially communicated via a Liaison Statement > > > > sent to statements(a)ietf.org on 01/Dec/2004, and in this message > > > > I would like to check what is the status of our request, as I > > > > was not able to locate a "tracker" tool in the IANA website. I > > > > also verified in http://www.iana.org/assignments/sdp-parameters > > > > that the said field is not yet available, hence it hopefully is already under processing. > > > > > > > > I would appreciate to know when could this registration be ready. > > > > > > > > For easier reference, I added below the specific information of > > > > the requested registration (between --START and --END). > > > > > > > > Your prompt feedback will be deeply appreciated, and we remain > > > > at your disposal for any subsequent clarification needed. > > > > > > > > Best regards, > > > > Simão Campos > > > > Counsellor, ITU-T SG 16 Secretariat ("Multimedia"). > > > > > > > > > > > > ===================================================================== > > > > Simão Ferraz de Campos Neto Counsellor, ITU-T SG 6&16 > > > > International Telecommunication Union Tel: +41-22-730-6805 > > > > Place des Nations Fax: +41-22-730-5853 > > > > Geneva CH1211 - Switzerland E-mail: simao.campos(a)itu.int > > > > On the web: www.itu.int/ITU-T/studygroups/com16 > > > > ===================================================================== > > > > ***** Practice random kindness and senseless acts of beauty > > > > ***** > > > > ================================================================ > > > > ===== > > > > > > > > --START > > > > Subject: Request of SDP att-field registration > > > > > > > > Contact Name: Hiroshi Tamura > > > > Email address: tamura(a)toda.ricoh.co.jp > > > > Telephone number: +81-3-3777-8124 > > > > Attribute-Name: T38VendorInfo > > > > Long-Form attribute name in English: Vendor Information > > > > Type of attribute: media level > > > > Whether the attribute value is subject to the charset attribute: no > > > > One paragraph explanation: > > > > This attribute is specified for use with ITU-T Recommendation > > > > T.38 Annex > > > D. > > > > It indicates the vendor information, the values of which are > > > > defined in ITU-T Recommendation T.35. > > > > Specification of appropriate values: > > > > Att-value = t35country-code SP t35extention SP manufacturer-code > > > > t35country-code = 1*(DIGIT) t35extention = 1*(DIGIT) > > > > manufacturer-code = 1*(DIGIT) ;optional > > > > Reference to the specification: ITU-T Rec. T.38 Annex D > > > > --END > > > > > > >

1 0

Re: ABOUT F.VTIP
by Zhang Qing 21 Jul '05

21 Jul '05

Dear Gunnar Hellstrom, Very thanks for your comments. About your reminded questions, I have some opinion as below for your reference. "1.Scope collision with F.703 Multimedia Conversation Service Description..." Here is a clarification for scope description about F.703 and F.VTIP. F.703 describes a general requirements of multimedia conversation service, many conversation services are covered in it, such as videotelephony, etc. And for each specific service, for example videotelephony service, it is necessary to describe the detailed requirement. So F.720 describes the sub-general requirements of videotelephony service, then F.721 for ISDN, F.723 for PSTN videotelephony service respectively, and F.VTIP intends to describe the requirements of IP videotelephony service. "2. The real time text medium is missing in the definition..." I agree that real time text medium is very important for people with hearing or speech disabilities. In F.VTIP, the IP videotelephony service is divided into basic and enhanced service, the real time text medium has been included in enhanced IP videotelephony service, I'm considering how to emphasize these features in F.VTIP. Sincerely thanks again for your kind advice. Best Regards, Qing Zhang > > ----- Original Message ----- > From: "Gunnar Hellstrom" <gunnar.hellstrom(a)omnitor.se> > To: "OKUBO Sakae" <okubo(a)MXZ.MESH.NE.JP>; "zhangqing" <q_zhang(a)huawei.com> > Cc: <itu-sg16(a)external.cisco.com> > Sent: Wednesday, July 20, 2005 5:48 AM > Subject: RE: ABOUT F.VTIP > > > Dear Qing Zhang, > > I have read the F.VTIP draft and have a couple of questions/comments: > > 1. Scope collision with F.703 Multimedia Conversation Service Description. > -------------------------------------------------------------------------- > It is not earlier habit of F.70x Recommendations to be network type specific. They describe multimedia service requirements in general terms, from the human point of view regardless of network type. F.703 already defines and describes the Video Telephony service and should be interpreted to define it on both circuit switched and IP networks. I think having an IP specific definition of Video Telephony in the F.70x series creates confusion. > Today, we also have an emphasis of evening out network influence on service experience in the NGN activities. > I suggest that you drop the IP specifics in this draft and merge it as an update to F.703. > > 2. The real time text medium is missing in the definition. > ---------------------------------------------------------- > In F.703 there is a service defined called "total conversation". It is a very impotant superset of video telephony created by adding real time conversational text medium to video telephony. The text is transmitted with the same flow as it is typed in order to give the call participants a good feeling of being in contact. No irritating waiting for the other one to complete a sentence, it all can be read by the participants as it is produced. > This addition has been driven by requirements from people with hearing or speech disabilities, but the feature has very general value. > > SG16 has been quite aware of the need to take accessibility for people with disabilities in account when creating Recommendations. This trend is finally spreading to other groups, and F.703 and other mainstream Recommendations with accessibility included form very important references in the work with deployment of accessible mainstream services. > > If advice no 1 to merge your document with F.703 is not followed, I suggest that IP total conversation is added to the F.VTIP draft with a description similar to the one for total conversation and the text medium in F.703. > I suggest that you declare three media to be normal for IP Video telephony; video, text and audio. > > Best regards > > Gunnar Hellström > ------------------------------------------- > Gunnar Hellström > Omnitor AB > Renathvägen 2 > SE 121 37 Johanneshov > SWEDEN > +46 8 556 002 03 > Mob: +46 708 204 288 > www.omnitor.se > Gunnar.Hellstrom(a)Omnitor.se > -------------------------------------------- > > >>-----Original Message----- >>From: zhangqing [mailto:q_zhang@huawei.com] >>Sent: Tuesday, July 12, 2005 6:09 PM >>To: OKUBO Sakae >>Cc: itu-sg16(a)external.cisco.com >>Subject: ABOUT F.VTIP >> >> >>Dear Mr. Okubo and all, >> >>Attached file is the new edition of F.VTIP. >> >>I appreciate the comments from Mr.Okubo and Mr. Blin >>Jean-Pierre, more comments and suggestions are solicited. >> >>Best regards, >> >>Qing Zhang >>Huawei Technologies Co., Ltd >>Tel : +86-755-89650436 >>Fax : +86-755-89651312 >>Mobile: +86-13316881228 >>E-mail: q_zhang(a)huawei.com >> >>----- Original Message ----- >>From: "OKUBO Sakae" <okubo(a)MXZ.MESH.NE.JP> >>To: <itu-sg16(a)external.cisco.com> >>Sent: Tuesday, July 12, 2005 10:49 AM >>Subject: SG16 meeting during 26 July - 5 August >> >> >>> Dear WP2/16 experts, >>> >>> Here are two pieces of information and request toward the upcoming >>> SG16 meeting. >>> >>> 1/ Q.5 Rapporteur >>> >>> Very unfortunately Mr. Bob Gilman advised the SG16 management of his >>> resignation from Q.5 Rapporteur and we reluctantly have to accept >>> this. As an emergency measure we have asked Mr. Paul Jones to lead >>> the Q.5 works at the upcoming SG16 meeting. >>> >>> Using this opportunity I would like to thank Bob not only for his >>> excellent leadership in the NAT/firewall traversal issue as >>> Rapporteur, but also for his valuable contributions to the H.323, >>> H.235 and other SG16 topics as expert since around 1999. >>> >>> 2/ Documents for the meeting >>> >>> Since this meeting is of Study Group level, all the documents are >>> handled by TSB, not by a Rapporteur. >>> >>> However, you may wish to upload your documents to the avc-site for >>> advance review by the experts. In that case, place your document at: >>> >>> ftp://ftp3.itu.int/avc-site/Incoming/ >>> user: avguest >>> password: Avguest >>> >>> or email it to me, then I will move it to: >>> >>> http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen >>> ftp://ftp3.itu.int/avc-site/2005-2008/0507_Gen >>> 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: ABOUT F.VTIP
by Gunnar Hellstrom 19 Jul '05

19 Jul '05

Dear Qing Zhang, I have read the F.VTIP draft and have a couple of questions/comments: 1. Scope collision with F.703 Multimedia Conversation Service Description. -------------------------------------------------------------------------- It is not earlier habit of F.70x Recommendations to be network type specific. They describe multimedia service requirements in general terms, from the human point of view regardless of network type. F.703 already defines and describes the Video Telephony service and should be interpreted to define it on both circuit switched and IP networks. I think having an IP specific definition of Video Telephony in the F.70x series creates confusion. Today, we also have an emphasis of evening out network influence on service experience in the NGN activities. I suggest that you drop the IP specifics in this draft and merge it as an update to F.703. 2. The real time text medium is missing in the definition. ---------------------------------------------------------- In F.703 there is a service defined called "total conversation". It is a very impotant superset of video telephony created by adding real time conversational text medium to video telephony. The text is transmitted with the same flow as it is typed in order to give the call participants a good feeling of being in contact. No irritating waiting for the other one to complete a sentence, it all can be read by the participants as it is produced. This addition has been driven by requirements from people with hearing or speech disabilities, but the feature has very general value. SG16 has been quite aware of the need to take accessibility for people with disabilities in account when creating Recommendations. This trend is finally spreading to other groups, and F.703 and other mainstream Recommendations with accessibility included form very important references in the work with deployment of accessible mainstream services. If advice no 1 to merge your document with F.703 is not followed, I suggest that IP total conversation is added to the F.VTIP draft with a description similar to the one for total conversation and the text medium in F.703. I suggest that you declare three media to be normal for IP Video telephony; video, text and audio. Best regards Gunnar HellstrÃ¶m ------------------------------------------- Gunnar HellstrÃ¶m Omnitor AB RenathvÃ¤gen 2 SE 121 37 Johanneshov SWEDEN +46 8 556 002 03 Mob: +46 708 204 288 www.omnitor.se Gunnar.Hellstrom(a)Omnitor.se -------------------------------------------- >-----Original Message----- >From: zhangqing [mailto:q_zhang@huawei.com] >Sent: Tuesday, July 12, 2005 6:09 PM >To: OKUBO Sakae >Cc: itu-sg16(a)external.cisco.com >Subject: ABOUT F.VTIP > > >Dear Mr. Okubo and all, > >Attached file is the new edition of F.VTIP. > >I appreciate the comments from Mr.Okubo and Mr. Blin >Jean-Pierre, more comments and suggestions are solicited. > >Best regardsï¼OE > >Qing Zhang >Huawei Technologies Co., Ltd >Tel : +86-755-89650436 >Fax : +86-755-89651312 >Mobile: +86-13316881228 >E-mail: q_zhang(a)huawei.com > >----- Original Message ----- >From: "OKUBO Sakae" <okubo(a)MXZ.MESH.NE.JP> >To: <itu-sg16(a)external.cisco.com> >Sent: Tuesday, July 12, 2005 10:49 AM >Subject: SG16 meeting during 26 July - 5 August > > >> Dear WP2/16 experts, >> >> Here are two pieces of information and request toward the upcoming >> SG16 meeting. >> >> 1/ Q.5 Rapporteur >> >> Very unfortunately Mr. Bob Gilman advised the SG16 management of his >> resignation from Q.5 Rapporteur and we reluctantly have to accept >> this. As an emergency measure we have asked Mr. Paul Jones to lead >> the Q.5 works at the upcoming SG16 meeting. >> >> Using this opportunity I would like to thank Bob not only for his >> excellent leadership in the NAT/firewall traversal issue as >> Rapporteur, but also for his valuable contributions to the H.323, >> H.235 and other SG16 topics as expert since around 1999. >> >> 2/ Documents for the meeting >> >> Since this meeting is of Study Group level, all the documents are >> handled by TSB, not by a Rapporteur. >> >> However, you may wish to upload your documents to the avc-site for >> advance review by the experts. In that case, place your document at: >> >> ftp://ftp3.itu.int/avc-site/Incoming/ >> user: avguest >> password: Avguest >> >> or email it to me, then I will move it to: >> >> http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen >> ftp://ftp3.itu.int/avc-site/2005-2008/0507_Gen >> 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

FW: I-D ACTION:draft-ma-h323-sip-conf-requirement-00.txt
by simao.campos＠ITU.INT 18 Jul '05

18 Jul '05

Dear colleagues, For your information. Best regards Simao -----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: Wednesday, July 13, 2005 16:50 To: i-d-announce(a)ietf.org Subject: I-D ACTION:draft-ma-h323-sip-conf-requirement-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Requirements for the interworking between IPv4-based H.323 system and IPv6-based SIP conference system Author(s) : Y. Ma, et al. Filename : draft-ma-h323-sip-conf-requirement-00.txt Pages : 13 Date : 2005-7-13 H.323 conference system is well defined and widely deployed today. It is important for SIP UA, both IPv4 and IPv6, to access H.323 conference system. This document defines an architecture for a SIP UA to access H.323 conference system. The requirements for the elements in this architecture are examined. Also the transition scenario for IPv6 SIP UA to access IPv4 H.323 conference system is discussed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ma-h323-sip-conf-requirement-0 0.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-ma-h323-sip-conf-requirement-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-ma-h323-sip-conf-requirement-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.

1 0

H.460.ma
by Sasha Ruditsky 18 Jul '05

18 Jul '05

Hi The latest draft of H.460.ma is attached. I expect that the final submission to the Geneva meeting will only contain minor editorial changes from this. Sasha

1 0

H.460.fantas
by Giles Chamberlin 18 Jul '05

18 Jul '05

<<h460.fantas_v4.doc>> Latest draft oof H.460.fantas attached. I expect that the final submission to the Geneva meeting will only contain minor editorial changes from this. Giles Chamberlin

1 0

RE: SG16 meeting during 26 July - 5 August
by Venkata Nanduri (vnanduri) 14 Jul '05

14 Jul '05

Hi, What is the last date to submit the document? Thanks Venkata -----Original Message----- From: OKUBO Sakae [mailto:okubo@MXZ.MESH.NE.JP] Sent: Thursday, July 14, 2005 6:55 PM To: itu-sg16(a)external.cisco.com Subject: Re: SG16 meeting during 26 July - 5 August Dear WP2/16 experts, At 22:49 -0400 05/07/11, OKUBO Sakae wrote: >[...] > >2/ Documents for the meeting > >Since this meeting is of Study Group level, all the documents are >handled by TSB, not by a Rapporteur. > >However, you may wish to upload your documents to the avc-site for >advance review by the experts. In that case, place your document at: > >ftp://ftp3.itu.int/avc-site/Incoming/ >user: avguest >password: Avguest > >or email it to me, then I will move it to: > >http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen >ftp://ftp3.itu.int/avc-site/2005-2008/0507_Gen >user: avguest >password: Avguest I have placed the documents provided so far at the above place. You can see their index at: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/0507_Gen.html I will continue to upload whatever advised to facilitate your advance review, but without individual announcements. -- 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: SG16 meeting during 26 July - 5 August
by OKUBO Sakae 14 Jul '05

14 Jul '05

Dear WP2/16 experts, At 22:49 -0400 05/07/11, OKUBO Sakae wrote: >[...] > >2/ Documents for the meeting > >Since this meeting is of Study Group level, all the documents are >handled by TSB, not by a Rapporteur. > >However, you may wish to upload your documents to the avc-site for >advance review by the experts. In that case, place your document at: > >ftp://ftp3.itu.int/avc-site/Incoming/ >user: avguest >password: Avguest > >or email it to me, then I will move it to: > >http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen >ftp://ftp3.itu.int/avc-site/2005-2008/0507_Gen >user: avguest >password: Avguest I have placed the documents provided so far at the above place. You can see their index at: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/0507_Gen.html I will continue to upload whatever advised to facilitate your advance review, but without individual announcements. -- 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: ASN problem in H.245v11
by mike.nilsson＠BT.COM 13 Jul '05

13 Jul '05

Giles, I do not think this is an error or a problem in any sense as the bits that are transmitted are not changed. The reason for the change is as follows. Up to and including version 10, I, as editor of H.245, have maintained my own version of the recommendation, and as each version has been approved, I have submitted it to the ITU-T TSB for publication. They then made editorial changes to it to align the look and feel of it to the ITU-T template. Each time I gave them a new version, they would have to make similar changes. Due to the rapid approval of new versions, 10 versions in 10 years, the ITU-T publication process was continually a little behind. But by version 11 they had caught up, and the decision was made for future (including version 11) editor's drafts to be based on the previous ITU-T published version. Hence various changes to spelling and style have been made between the editor's drafts of version 10 and 11 - you have found one of them. Hopefully none of the differences are significant - a lot of effort went into verifying this. Anyone looking at the published versions would not have seen any such changes between versions 10 and 11 - they would only see the intended technical enhancements. I hope this clarifies the situation. Best regards Mike Nilsson Mike Nilsson Multimedia Analysis and Coding ___________________________ Sirius House (B54-MH), Room 124 Adastral Park, Martlesham Heath, Ipswich, IP5 3RE, UK Tel: +44 1473 645413 Mobile: +44 7917 025433 Fax: +44 1908 862365 Email: mike.nilsson(a)bt.com BT Group plc Registered office: 81 Newgate Street London EC1A 7AJ Registered in England and Wales no. 4190816 This electronic message contains information from BT Group plc which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (to the numbers or address above) immediately. Activity and use of the BT Group plc E-mail system is monitored to secure its effective operation and for other lawful business purposes. Communications using this system will also be monitored and may be recorded to secure effective operation and for other lawful business purposes. -----Original Message----- From: Giles Chamberlin [mailto:giles.chamberlin@tandberg.net] Sent: 11 July 2005 15:52 To: itu-sg16(a)external.cisco.com Subject: ASN problem in H.245v11 Latest H.245v11 document (H245WCM28.doc) obtained from packetizer.com (http://www.packetizer.com/voip/h245/Version11/H245WCM28.zip) has an error in the asn.1 definition: GenericMessage ::=SEQUENCE { messageIdentifier CapabilityIdentifier, subMessageIdentifier INTEGER(0..127) OPTIONAL, messageContent SEQUENCE OF GenericParameter OPTIONAL, ... } subMessageIdentifier appears to have been spellchecked and is now different to previous versions. (It was subMessageIdentifer in v10). Giles Chamberlin

1 0

ABOUT F.VTIP
by zhangqing 12 Jul '05

12 Jul '05

Dear Mr. Okubo and all, Attached file is the new edition of F.VTIP. I appreciate the comments from Mr.Okubo and Mr. Blin Jean-Pierre, more comments and suggestions are solicited. Best regards, Qing Zhang Huawei Technologies Co., Ltd Tel : +86-755-89650436 Fax : +86-755-89651312 Mobile: +86-13316881228 E-mail: q_zhang(a)huawei.com ----- Original Message ----- From: "OKUBO Sakae" <okubo(a)MXZ.MESH.NE.JP> To: <itu-sg16(a)external.cisco.com> Sent: Tuesday, July 12, 2005 10:49 AM Subject: SG16 meeting during 26 July - 5 August > Dear WP2/16 experts, > > Here are two pieces of information and request toward the upcoming > SG16 meeting. > > 1/ Q.5 Rapporteur > > Very unfortunately Mr. Bob Gilman advised the SG16 management of his > resignation from Q.5 Rapporteur and we reluctantly have to accept > this. As an emergency measure we have asked Mr. Paul Jones to lead > the Q.5 works at the upcoming SG16 meeting. > > Using this opportunity I would like to thank Bob not only for his > excellent leadership in the NAT/firewall traversal issue as > Rapporteur, but also for his valuable contributions to the H.323, > H.235 and other SG16 topics as expert since around 1999. > > 2/ Documents for the meeting > > Since this meeting is of Study Group level, all the documents are > handled by TSB, not by a Rapporteur. > > However, you may wish to upload your documents to the avc-site for > advance review by the experts. In that case, place your document at: > > ftp://ftp3.itu.int/avc-site/Incoming/ > user: avguest > password: Avguest > > or email it to me, then I will move it to: > > http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen > ftp://ftp3.itu.int/avc-site/2005-2008/0507_Gen > 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

SG16 meeting during 26 July - 5 August
by OKUBO Sakae 11 Jul '05

11 Jul '05

Dear WP2/16 experts, Here are two pieces of information and request toward the upcoming SG16 meeting. 1/ Q.5 Rapporteur Very unfortunately Mr. Bob Gilman advised the SG16 management of his resignation from Q.5 Rapporteur and we reluctantly have to accept this. As an emergency measure we have asked Mr. Paul Jones to lead the Q.5 works at the upcoming SG16 meeting. Using this opportunity I would like to thank Bob not only for his excellent leadership in the NAT/firewall traversal issue as Rapporteur, but also for his valuable contributions to the H.323, H.235 and other SG16 topics as expert since around 1999. 2/ Documents for the meeting Since this meeting is of Study Group level, all the documents are handled by TSB, not by a Rapporteur. However, you may wish to upload your documents to the avc-site for advance review by the experts. In that case, place your document at: ftp://ftp3.itu.int/avc-site/Incoming/ user: avguest password: Avguest or email it to me, then I will move it to: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen ftp://ftp3.itu.int/avc-site/2005-2008/0507_Gen 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

ASN problem in H.245v11
by Giles Chamberlin 11 Jul '05

11 Jul '05

Latest H.245v11 document (H245WCM28.doc) obtained from packetizer.com (http://www.packetizer.com/voip/h245/Version11/H245WCM28.zip) has an error in the asn.1 definition: GenericMessage ::=SEQUENCE { messageIdentifier CapabilityIdentifier, subMessageIdentifier INTEGER(0..127) OPTIONAL, messageContent SEQUENCE OF GenericParameter OPTIONAL, ... } subMessageIdentifier appears to have been spellchecked and is now different to previous versions. (It was subMessageIdentifer in v10). Giles Chamberlin

1 0

Media signal multiplexing in H.ma
by OKUBO Sakae 11 Jul '05

11 Jul '05

Dear Sasha and other NAT/firewall traversal experts, When I reported the Q.5 progress at the recent Japan national meeting for the coming SG16 meeting, Mr. Hideaki Yamada, KDDI, pointed out that G.769/Y.1242 (Circuit multiplication equipment optimized for IP-based networks) uses the following RTP multiplexing: 1/ Ordinary RTP header is used with a particular payload type. 2/ Inside the RTP payload, multiple voice, facsimile and voice band data channels are multiplexed with the "short packet" structure. A relevant part excerpt of G.769 is attached. Since G.769 is under the responsibility of WP1/16, we should at least be aware of this method of media signal multiplexing. I do not have a particular reason to make alignment between H.ma and G.769 due to their different requirements. But if there is anything good for our NAT/firewall traversal solution, please take that into account. -- 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

FW: RFC 4123 on Session Initiation Protocol (SIP)-H.323 Interwork
by Euchner Martin 08 Jul '05

08 Jul '05

FYI: After a long time, the SIP-H.323 Interworking Requirements have made it into an RFC. So SG16 can now consider the next steps ahead on H.323-SIP Interworking beyond the requirements stage. With kind regards Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Rapporteur | Martin Euchner Phone: +49 89 722 55790 | Siemens AG.....................Fax : +49 89 722 62366 | COM GC PS 3 mailto:Martin.Euchner@siemens.com | mailto:martin.euchner@ties.itu.int | Hofmannstr. 51 Intranet: http://ietf.icn.siemens.de/sr3/Standardisation_Topics/security/ | D-81359 Muenchen Internet: http://www.siemens.de/ | __________________ | Germany ----------------------------------------------------------------------- -----Original Message----- From: ietf-announce-bounces(a)ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of rfc-editor(a)rfc-editor.org Sent: Donnerstag, 7. Juli 2005 20:26 To: ietf-announce(a)ietf.org Cc: rfc-editor(a)rfc-editor.org Subject: RFC 4123 on Session Initiation Protocol (SIP)-H.323 Interworking Requirements A new Request for Comments is now available in online RFC libraries. RFC 4123 Title: Session Initiation Protocol (SIP)-H.323 Interworking Requirements Author(s): H. Schulzrinne, C. Agboh Status: Informational Date: July 2005 Mailbox: hgs(a)cs.columbia.edu, charles.agboh(a)packetizer.com Pages: 16 Characters: 29244 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-agrawal-sip-h323-interworking-reqs-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4123.txt This document describes the requirements for the logical entity known as the Session Initiation Protocol (SIP)-H.323 Interworking Function (SIP-H.323 IWF) that will allow the interworking between SIP and H.323. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info(a)RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute .. Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.

1 0

Re: Warwick Hotel
by Eliot Lear 07 Jul '05

07 Jul '05

I was just there, and it's fine. Clean rooms, and they have no smoking rooms as well. Good location next to the train station, and an okay breakfast so long as you're not a vegetarian. Can be a bit pricy. Eliot Paul E. Jones wrote: > > > Folks, > > > > Has anybody stayed at the Warwick hotel in the past few years? Is it a > reasonable place to stay? > > > > Paul >

1 0

Warwick Hotel
by Paul E. Jones 07 Jul '05

07 Jul '05

Folks, Has anybody stayed at the Warwick hotel in the past few years? Is it a reasonable place to stay? Paul

1 0

[SUSPECT ATTACHMENT] H.248.1v3 Appendix III Profile Template Editing Comments
by Christian Groves 01 Jul '05

01 Jul '05

Hello Kevin, all, Attached are some further editor comments on H.248.1 Appendix III Profile Template. Regards, Christian ------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- WARNING: This message has an attachment that could contain executable code. Please review the attachment carefully to ensure you do not inadvertently execute embedded programs that could contain viruses. We suggest you review the following URL to stay up-to-date with current virus threats: http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml 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: j61Cl1VY012814 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: H.248.1 Editing meeting
by Christian Groves 29 Jun '05

29 Jun '05

Hello Kevin, I have added some additional comments to the Alcatel comments in: ftp3.itu.int/avc-site/Incoming/ TD9 Updated Draft_h248.1v3 Clean_comments_Ericsson.zip As part of the review I went through my IG style comments in: ftp3.itu.int/avc-site/Incoming/ DC-xxx_H_248_1v3_Corrections_Clarifications_v3.zip I've marked up the items in green that haven't been included (no. 1,4,5,6,10). I can understand why 5 was not included. What is the reasoning behind 1,4,6,10? I don't think there is any new functionality??? Regards, Christian Albrecht.Schwarz(a)alcatel.de wrote: > Thanks Simao for assistance and clarifications! > > Actually I was using Windows Commander 4.51 as FTP client, and the > Netscape > browser only as cross-check "tool". > I was unsure because the file wasn't visible in the Commander. > > I've the same opinion as you with regard to the previous settings. > Meaning, > I may live with a period of uncertainity ("time from unconfirmed, hiding > uploading in Incoming till visibility in working directory"). > > Thanks again, > Albrecht > > > > > > <simao.campos@it > > u.int> To: Albrecht > SCHWARZ/DE/ALCATEL@ALCATEL, <kboyle(a)nortel.com> > cc: > <itu-sg16(a)external.cisco.com> > 28.06.2005 14:52 Subject: RE: H.248.1 > Editing meeting > > > > > > > Dear Albrecht, > > to upload comments to the Incoming directory, please use an FTP client > using the current guest username and password, instead of a web browser > (http://...) > > Best, > Simao > > >>-----Original Message----- >>From: Albrecht.Schwarz(a)alcatel.de >>[mailto:Albrecht.Schwarz@alcatel.de] >>Sent: 28 June 2005 13:17 >>To: Kevin Boyle >>Cc: itu-sg16(a)external.cisco.com >>Subject: Re: H.248.1 Editing meeting >> >> >>Kevin, thanks for your effort! >> >>Can imagine that you can't see the text anymore;-) >>Nevertheless; I'd like to propose some more editorial change >>proposals, almost all originating from types or space characters. >> >>Unfortunately I'm unable to upload my comments on the avc site: >> >>http://ftp3.itu.int/av-arch/avc-site/Incoming/ >>"You don't have permission to access >>/av-arch/avc-site/Incoming/ on this server." >> >> >>That's why I'll send the file >>TD9 Updated Draft_h248.1v3 Clean_commentsALCATEL.doc >> >>in a separate email to Kevin directly. >> >>Regards >>Albrecht >> >> >> >> >> >> >> >> >> "Kevin Boyle" >> >> <kboyle(a)nortel.c To: >>itu-sg16(a)external.cisco.com >> >> om> cc: >> >> Subject: >>H.248.1 Editing meeting >> >> 27.06.2005 11:36 >> >> >> >> >> >> >> >>All, >> >> >>I have uploaded two versions of the working document to the >>Incoming folder on the FTP site -- one with change marks as >>TD8R1 and one without as TD9. >>These reflect all the changes through all 5 weeks thus far. >>The only change I have not made was the addition of Notify to >>the profile template. >>There seems to be a problem with the FTP site, in that it >>will not list the contents of the folders. Once that problem >>has been resolved, I will update the document to include it. >> >> >>Please look over the document. I have been over the spec in >>great detail making the capitalization uniform as best I can. >> If you see any cases that do not align with the rest of the >>document, please let me know. Also, have a look across the >>document for the changes you suggested. In some cases, I >>took the suggestion for change and altered the wording a >>little differently than suggested. In some cases there were >>multiple changes to the same place suggested, and I did the >>best I could to merge the suggestions. >>Hopefully I have captured the intent of all. >> >> >>I hope you all find my many hours of work satisfactory. As a >>reminder, this is the week to suggest any further edits. The >>document that emerges at the end of this week will be the >>input document to Geneva. >> >> >>Kevin >> >> >> > > >

1 0

Re: H.248.1 Editing meeting
by Yangbo Lin 29 Jun '05

29 Jun '05

Thanks for your effort! However I have to bother you again because I cannot find the changes my suggested in the updated document TD8R1 or TD9. I think that maybe you have not noticed the reviewing comments from me to the week 5 section because I had uploaded it by mail directly and no FTP. Please refer to the document which is already in the directory and consider the reviewing comments. Thank you! ----- Original Message ----- From: Kevin Boyle <mailto:kboyle@nortel.com> To: itu-sg16(a)external.cisco.com Sent: Monday, June 27, 2005 5:36 PM Subject: H.248.1 Editing meeting All, I have uploaded two versions of the working document to the Incoming folder on the FTP site -- one with change marks as TD8R1 and one without as TD9. These reflect all the changes through all 5 weeks thus far. The only change I have not made was the addition of Notify to the profile template. There seems to be a problem with the FTP site, in that it will not list the contents of the folders. Once that problem has been resolved, I will update the document to include it. Please look over the document. I have been over the spec in great detail making the capitalization uniform as best I can. If you see any cases that do not align with the rest of the document, please let me know. Also, have a look across the document for the changes you suggested. In some cases, I took the suggestion for change and altered the wording a little differently than suggested. In some cases there were multiple changes to the same place suggested, and I did the best I could to merge the suggestions. Hopefully I have captured the intent of all. I hope you all find my many hours of work satisfactory. As a reminder, this is the week to suggest any further edits. The document that emerges at the end of this week will be the input document to Geneva. Kevin

1 0

Preparation for the SG16 Q.25 meeting: H.235.x drafts uploaded
by Euchner Martin 28 Jun '05

28 Jun '05

Dear security experts, In preparation of the forthcoming SG16 meeting Q.25 session, I've uploaded all draft H.235.x subseries Recommendations (H.235.0, .1, .2, .3, .4, .6 and .7) under my own editorship to the working docs directory at http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/ <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/> The documents encompass the current draft Recommendation texts (H.235.x) as well as the cover sheets (TD-WP2-AAA) where the recent changes are recorded. Also provided are the A.5 qualification drafts (TD-PLEN-aaa) rectifying the external normative references. I've also uploaded a TD-WP2-xxx with a proposed draft corrigendum2 for H.235v3. All drafts are subjects to change. Two major open issues are worth noting: * In H.235.4, I've removed contents of clause 10 "Procedure DRC2 - Interdomain Environment"; added editor note that clause is FFS pending contributions for the unification approach. * In H.235.6, Clause 7.8 holds an {Editor's note: Fix the problem of Diffie-Hellman key exchange in conjunction with H.450.x supplementary services. } which deserves fixing. If no solution is found, add a note that there is problem, while the solution of the problem is left FFS. Both areas are of particular importance where I particularly solicit contributions (deadline for submission July 14th). I appreciate very much your review and feedback of the drafts. With kind regards Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Rapporteur | Martin Euchner Phone: +49 89 722 55790 | Siemens AG.....................Fax : +49 89 722 62366 | COM GC PS 3 mailto:Martin.Euchner@siemens.com <mailto:Martin.Euchner@siemens.com> | mailto:martin.euchner@ties.itu.int <mailto:martin.euchner@ties.itu.int> | Hofmannstr. 51 Intranet: http://ietf.icn.siemens.de/sr3/Standardisation_Topics/security/ <http://ietf.icn.siemens.de/sr3/Standardisation_Topics/security/> | D-81359 Muenchen Internet: http://www.siemens.de/ <http://www.siemens.de/> | __________________ | Germany -----------------------------------------------------------------------

1 0

RE: H.248.1 Editing meeting
by Albrecht.Schwarz＠alcatel.de 28 Jun '05

28 Jun '05

Thanks Simao for assistance and clarifications! Actually I was using Windows Commander 4.51 as FTP client, and the Netscape browser only as cross-check "tool". I was unsure because the file wasn't visible in the Commander. I've the same opinion as you with regard to the previous settings. Meaning, I may live with a period of uncertainity ("time from unconfirmed, hiding uploading in Incoming till visibility in working directory"). Thanks again, Albrecht <simao.campos@it u.int> To: Albrecht SCHWARZ/DE/ALCATEL@ALCATEL, <kboyle(a)nortel.com> cc: <itu-sg16(a)external.cisco.com> 28.06.2005 14:52 Subject: RE: H.248.1 Editing meeting Dear Albrecht, to upload comments to the Incoming directory, please use an FTP client using the current guest username and password, instead of a web browser (http://...) Best, Simao > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de > [mailto:Albrecht.Schwarz@alcatel.de] > Sent: 28 June 2005 13:17 > To: Kevin Boyle > Cc: itu-sg16(a)external.cisco.com > Subject: Re: H.248.1 Editing meeting > > > Kevin, thanks for your effort! > > Can imagine that you can't see the text anymore;-) > Nevertheless; I'd like to propose some more editorial change > proposals, almost all originating from types or space characters. > > Unfortunately I'm unable to upload my comments on the avc site: > > http://ftp3.itu.int/av-arch/avc-site/Incoming/ > "You don't have permission to access > /av-arch/avc-site/Incoming/ on this server." > > > That's why I'll send the file > TD9 Updated Draft_h248.1v3 Clean_commentsALCATEL.doc > > in a separate email to Kevin directly. > > Regards > Albrecht > > > > > > > > > "Kevin Boyle" > > <kboyle(a)nortel.c To: > itu-sg16(a)external.cisco.com > > om> cc: > > Subject: > H.248.1 Editing meeting > > 27.06.2005 11:36 > > > > > > > > All, > > > I have uploaded two versions of the working document to the > Incoming folder on the FTP site -- one with change marks as > TD8R1 and one without as TD9. > These reflect all the changes through all 5 weeks thus far. > The only change I have not made was the addition of Notify to > the profile template. > There seems to be a problem with the FTP site, in that it > will not list the contents of the folders. Once that problem > has been resolved, I will update the document to include it. > > > Please look over the document. I have been over the spec in > great detail making the capitalization uniform as best I can. > If you see any cases that do not align with the rest of the > document, please let me know. Also, have a look across the > document for the changes you suggested. In some cases, I > took the suggestion for change and altered the wording a > little differently than suggested. In some cases there were > multiple changes to the same place suggested, and I did the > best I could to merge the suggestions. > Hopefully I have captured the intent of all. > > > I hope you all find my many hours of work satisfactory. As a > reminder, this is the week to suggest any further edits. The > document that emerges at the end of this week will be the > input document to Geneva. > > > Kevin > > >

1 0

RE: H.248.1 Editing meeting
by simao.campos＠ITU.INT 28 Jun '05

28 Jun '05

Dear Albrecht, to upload comments to the Incoming directory, please use an FTP client using the current guest username and password, instead of a web browser (http://...) Best, Simao > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de > [mailto:Albrecht.Schwarz@alcatel.de] > Sent: 28 June 2005 13:17 > To: Kevin Boyle > Cc: itu-sg16(a)external.cisco.com > Subject: Re: H.248.1 Editing meeting > > > Kevin, thanks for your effort! > > Can imagine that you can't see the text anymore;-) > Nevertheless; I'd like to propose some more editorial change > proposals, almost all originating from types or space characters. > > Unfortunately I'm unable to upload my comments on the avc site: > > http://ftp3.itu.int/av-arch/avc-site/Incoming/ > "You don't have permission to access > /av-arch/avc-site/Incoming/ on this server." > > > That's why I'll send the file > TD9 Updated Draft_h248.1v3 Clean_commentsALCATEL.doc > > in a separate email to Kevin directly. > > Regards > Albrecht > > > > > > > > > "Kevin Boyle" > > <kboyle(a)nortel.c To: > itu-sg16(a)external.cisco.com > > om> cc: > > Subject: > H.248.1 Editing meeting > > 27.06.2005 11:36 > > > > > > > > All, > > > I have uploaded two versions of the working document to the > Incoming folder on the FTP site -- one with change marks as > TD8R1 and one without as TD9. > These reflect all the changes through all 5 weeks thus far. > The only change I have not made was the addition of Notify to > the profile template. > There seems to be a problem with the FTP site, in that it > will not list the contents of the folders. Once that problem > has been resolved, I will update the document to include it. > > > Please look over the document. I have been over the spec in > great detail making the capitalization uniform as best I can. > If you see any cases that do not align with the rest of the > document, please let me know. Also, have a look across the > document for the changes you suggested. In some cases, I > took the suggestion for change and altered the wording a > little differently than suggested. In some cases there were > multiple changes to the same place suggested, and I did the > best I could to merge the suggestions. > Hopefully I have captured the intent of all. > > > I hope you all find my many hours of work satisfactory. As a > reminder, this is the week to suggest any further edits. The > document that emerges at the end of this week will be the > input document to Geneva. > > > Kevin > > >

1 0

Re: H.248.1 Editing meeting
by Albrecht.Schwarz＠alcatel.de 28 Jun '05

28 Jun '05

Kevin, thanks for your effort! Can imagine that you can't see the text anymore;-) Nevertheless; I'd like to propose some more editorial change proposals, almost all originating from types or space characters. Unfortunately I'm unable to upload my comments on the avc site: http://ftp3.itu.int/av-arch/avc-site/Incoming/ "You don't have permission to access /av-arch/avc-site/Incoming/ on this server." That's why I'll send the file TD9 Updated Draft_h248.1v3 Clean_commentsALCATEL.doc in a separate email to Kevin directly. Regards Albrecht "Kevin Boyle" <kboyle(a)nortel.c To: itu-sg16(a)external.cisco.com om> cc: Subject: H.248.1 Editing meeting 27.06.2005 11:36 All, I have uploaded two versions of the working document to the Incoming folder on the FTP site -- one with change marks as TD8R1 and one without as TD9. These reflect all the changes through all 5 weeks thus far. The only change I have not made was the addition of Notify to the profile template. There seems to be a problem with the FTP site, in that it will not list the contents of the folders. Once that problem has been resolved, I will update the document to include it. Please look over the document. I have been over the spec in great detail making the capitalization uniform as best I can. If you see any cases that do not align with the rest of the document, please let me know. Also, have a look across the document for the changes you suggested. In some cases, I took the suggestion for change and altered the wording a little differently than suggested. In some cases there were multiple changes to the same place suggested, and I did the best I could to merge the suggestions. Hopefully I have captured the intent of all. I hope you all find my many hours of work satisfactory. As a reminder, this is the week to suggest any further edits. The document that emerges at the end of this week will be the input document to Geneva. Kevin

1 0

H.248.1 Editing meeting
by Kevin Boyle 27 Jun '05

27 Jun '05

All, I have uploaded two versions of the working document to the Incoming folder on the FTP site -- one with change marks as TD8R1 and one without as TD9. These reflect all the changes through all 5 weeks thus far. The only change I have not made was the addition of Notify to the profile template. There seems to be a problem with the FTP site, in that it will not list the contents of the folders. Once that problem has been resolved, I will update the document to include it. Please look over the document. I have been over the spec in great detail making the capitalization uniform as best I can. If you see any cases that do not align with the rest of the document, please let me know. Also, have a look across the document for the changes you suggested. In some cases, I took the suggestion for change and altered the wording a little differently than suggested. In some cases there were multiple changes to the same place suggested, and I did the best I could to merge the suggestions. Hopefully I have captured the intent of all. I hope you all find my many hours of work satisfactory. As a reminder, this is the week to suggest any further edits. The document that emerges at the end of this week will be the input document to Geneva. Kevin

1 0

RE: [Megaco] The ABNF coding of VALUE doesn't allow to represent ageneric UTF-8 string/char
by Steve Cipolli 24 Jun '05

24 Jun '05

Angelo, Today all ASCII characters except double quotes can be specified by the VALUE production (some of the characters need to be in the quotedstring form). Adding UTF-8 does not change this. The part of UTF-8 that is < 0x80 is exactly ASCII and does not change or need to change the way in which VALUE is encoded. UTF-8 characters above 0x7F are encoded as multiple bytes in which each byte of the character is guaranteed to be > 0x7F. So UTF-8 characters are either < 0x80 and are simply the equivalent of ASCII or they are encoded into multiple bytes in which every byte of the character is > 0x7F. There will never be a circumstance where a byte of a UTF-8 multibyte character collides with _any_ ASCII character. Perhaps the table below will help clarify Scalar Value 1st Byte 2nd Byte 3rd Byte 4th Byte 00000000 0xxxxxxx 0xxxxxxx 00000yyy yyxxxxxx 110yyyyy 10xxxxxx zzzzyyyy yyxxxxxx 1110zzzz 10yyyyyy 10xxxxxx 000uuuuu zzzzyyyy yyxxxxxx 11110uuu 10uuzzzz 10yyyyyy 10xxxxxx Notice that "one byte" UTF-8 characters have their high order bit cleared (0) and that all bytes of all multi-byte UTF-8 encodings have the high-order bit set (1). In other words all multi-byte character's bytes are > 0x7F. So changing the productions to: VALUE = quotedString / 1*(SafeChar / %x80-F7) quotedString = DQUOTE *(SafeChar / %x80-F7 / RestChar / WSP) DQUOTE as Sasha Ruditsky suggests will allow UTF-8 characters to be used in VALUEs. ASCII characters (and UTF-8 equvialents < 0x80) that are in the RestChar set will need to be quoted just as they have always been. UTF-8 characters above 0x7F may or may not be quoted, just as all the ASCII characters in the SafeChar set. --Stephen > -----Original Message----- > From: Contardi Angelo [mailto:Angelo.Contardi@italtel.it] > Sent: Friday, June 24, 2005 12:25 PM > To: Steve Cipolli > Subject: R: [Megaco] The ABNF coding of VALUE doesn't allow > to represent ageneric UTF-8 string/char > > > > > -----Messaggio originale----- > Da: Steve Cipolli [mailto:SCipolli@radvision.com] > Inviato: venerdì 24 giugno 2005 18.01 > A: Contardi Angelo; Megaco IETF - Mail List (E-mail) > Cc: Christian Groves (E-mail) > Oggetto: RE: [Megaco] The ABNF coding of VALUE doesn't allow > to represent ageneric UTF-8 string/char > > > > Two points: > > 1. It is not necessary to quote the UTF-8 characters as you > define in your second solution. VALUE can be extended to > accept characters (quoted and unquoted) in the range 0x80-0xFF. > > The problem is that VALUE don't allow to "carry" ALL ASCII > (0x00-0x7F) too, NEEDED to code UTF-8 characters < 0x80. So > the only "extension" 0x80-0xFF is NOT enough to allow the TX > of ALL UTF-8 with ABNF. The quotation is NEEDED becaue of if > you "scan" an input sequence and allow a VALUE as "any > sequence of ono or more 0x00-0xFF", all "tokens" identified > as VALUEs. The extension of quoted form of VALUE i propose > don't increment the number of the forms of VALUE, just EXEND > the actual Quoted form of VALUE > > 2. Providing a mechanism to allow double quotes (") in a > (double) quotedstring is essentially a separate issue, since > addition of UTF-8 chars does not motivate the need for this > mechanism nor complicate its addition. > > See point 1. > > --Stephen > > > -----Original Message----- > > From: megaco-bounces(a)ietf.org > > [mailto:megaco-bounces@ietf.org] On Behalf Of Contardi Angelo > > Sent: Friday, June 24, 2005 11:34 AM > > To: Megaco IETF - Mail List (E-mail) > > Cc: Christian Groves (E-mail) > > Subject: [Megaco] The ABNF coding of VALUE doesn't allow to > > represent ageneric UTF-8 string/char > > > > > > Hello, > > > > from my previous private discussion with Christian Groves, > > i have deduce this: > > > > The ABNF coding of VALUE doesn't allow to represent a > > generic UTF-8 string or char (RFC 3629) because of: > > > > 1) The FIRST byte of an UTF-8 char may be ANY ASCII char in > > the range 0x00-0x7E > > and, for instance, the ASCII 0x00-0x07 and 0x22 (") are > > not allowed in ANY > > ABNF form of VALUE. > > > > 2) Furthermore, UTF-8 chars "greater than 0x7E", need "ASCII > > chars" (to better > > say, Octets) in the range 0x80-0xFF (not ALL), not allowed > > in ANY ABNF form > > of VALUE. > > > > So, to "correct" this problem, i can suggest two possible solutions: > > > > 1) The simple one, code the UTF-8 string/char in "Octect > > Mode", as described in > > ANNEX B.3. This is a BAD solution from the efficiency > > transmission point of > > view because of it "halve the TX band": to TX one UTF-8 > > char (max 4 Octet) > > i must TX max 2 x 4 = 8 Octet (ASCII chars). > > > > 2) The difficult one, allow the ABNF quoted form of VALUE to > > TX ALL ASCII chars > > 0x01-0xFF (the range 0x80-0xFF are more properly named > > OCTET in RFC2234 ), > > except 0x22 ("), that should be ESCAPED with "\", as > > already done for ABNF > > Local and Remote Descriptor (see SDP). Note that '\0' > > (0x00) is NOT ALLOWED > > in this new quoted string form as in the present one, but > > it's not a problem > > because in UTF-8 the char '\0' (0x00) is same as in ASCII > > (string terminator) > > and is NOT used to code "non ASCII" UTF-8 chars, all > > those chars > 0x7F that > > require more than one ASCII chars to be encoded (from 2 to > > 4 ASCII chars). In > > fact the "extra chars" needed to code an UTF-8 char are > > all above 0x7F. > > > > While the 1st mode doesn't require any modification of > > ABNF syntax (but is it applicable in any case ?), the 2nd one > > require this ABNF modification: > > > > quotedString = DQUOTE *(quotedChar) DQUOTE > > > > ; %x22 (") is allowed just if "escaped" with "\" > > quotedChar = ( %x01-21 / "\" DQUOTE / %x23-FF ) > > > > In a parser implementation, i think, this is not a > > "terrible complication" and can be solved in the same way of > > "octetString" of Local and RemoteDescriptor. It require also > > to implement an ESCAPE "strip(rx)/padding(tx)" mechanism, as > > already required for SDP. > > > > P.S.: I suppose NO ONE need to send the "string terminator" > > '\0' (0x00) in an > > UTF-8 string or char. If my assertion is false, in > > the "solution 2)" the > > %x00 should also be "escaped". Viceversa, the > > "solution 1)" can already > > "transport" %x00 octet. > > > > Best regards > > > > o o o o o o o . . . ___________________________________ > > o _____ || Angelo Contardi | > > .][__n_n_|DD[ ====_____ | angelo.contardi(a)italtel.it | > > >(________|__|_[_________]_|________________________________| > > _/oo OOOOO oo` ooo ooo 'o!o!o o!o!o` > > > > _______________________________________________ > > Megaco mailing list > > Megaco(a)ietf.org > > https://www1.ietf.org/mailman/listinfo/megaco > > > > > > > >

1 0