August 2006 - sg16-avd - lists.packetizer.com

RE: [rac] Audio T.140 evaluation?
by Paul E. Jones 19 Aug '06

19 Aug '06

Arnoud, I feel compelled to reply to just one point: If Paul wants audio/t140c so much Personally, I do not care whether audio/t140c or text/t140 is adopted as the industry standard. It makes absolutely no difference to me, as I view both as a viable means of delivering real-time text in a way that we can use it. What has mattered to me is delivering real-time text capability at all, which was incredibly hard in the face of constant customer requests for instant messaging. Ive given both technical and business reasons why text/t140 cannot be universally deployed today and the near future. Ive given other business reasons why text/t140 is not favored presently (cost factors). Working within those constraints, I wrote the audio/t140c document. I might be blamed for creating something evil (and I have been accused of trying to screw over deaf people), but the truth is that I tried to create something that is a stepping stone that will allow us to deploy RTT universally and will not exclude legacy TTY devices: the roadmap that I have proposed is easier (and therefore more likely to succeed) than taking the bigger leap to text/t140, in my opinion. (Note: text/t140 is now 6 years old, so I do not think my assessment is wrong.) Ive said before that I think text/t140 is where we want to be. How do you suggest we get there? 1) We can simply demanding text/t140 support on platforms. Some platforms cannot support it. Some platforms could support it, but would require coordination with other products that also need to implement it (e.g., softswitches, firewalls, NAT devices, and policy enforcement devices). You end up having an end-to-end tug of war between product teams who wait for the others to take the first step. Worse, you isolate anybody using a technology that simply cannot do it. (How long until the last MGCP or NCS gateway is decommissioned?) 2) Shall we demand that service providers deploy special text gateway devices and just use V.152 to those gateways? (That pushes all of the cost and burden onto the service provider, rather than GW vendors. However, it also presents special dialing requirements or line provisioning requirements. For reasons that would require another full page of text, I will say this will not work unless we remove the requirement that users be able to go anywhere with their TTY devices.) 3) Shall we just forget about TTY devices and move everybody to IP, letting those with TTY devices just limp along until such time as theyre tired of being isolated or things not working part of the time? Other ideas? Paul _____ From: Arnoud van Wijk [mailto:arnoud@annies.nl] Sent: Friday, August 18, 2006 6:02 AM To: Rac(a)lists.wisc.edu Subject: RE: [rac] Audio T.140 evaluation? And that is so absolutely true. Audio/t140c is a very dangerous genie that is almost out of the bottle now. And once deployed outside its limited purpose, we will get a big mess with fragmentation dangers. You only have to look at what has happened to the different text telephone protocols, or the different IM protocols. If it is up to me, I want audio/t140c erased from existence. It will be hard enough to get text/t140 deployed. Now as I always say, audio/t140c is ok in gateway-gateway connections. IP terminals must never be mandated to support audio/t140c. Audio/y140c could be added as a special PSTN functionality. But such IP terminal MUST have text/t140. What about gateways? They must support text/t140 and if they wantaudio/t140c. You will get a number of scenarios all from IP side starting: (gateway supports both text/t140 and audio/t140c) 1. call has audio/t140c and text/t140 in the SDP, nice for the gateway, it selects audio/t140c. No issue here. 2. call has text/t140 in the SDP plus an indicator that text must be used. No issues here. 3. call has text/t140 in the SDP, there is no indicator if text must be used. There are a few possibilities: a: set up text in a reinvite if a key or text telephony is detected. b: set up text/t140 port anyway and close this port if no text input is detected after 60 seconds, it can always then reinvite for text if any text is detected later. So, if Paul wants Audio/t140c so much. OK but only mandate gateways to support both. Text/140 is the universal lina franca real-time text protocol and will also be set for interconnectivity between any text to any text networks. With the coming of WiMax, rural areas will be able to get high speed internet. Sprint is starting to roll out such network. The range is 50 kilometers in rural areas and 2-3 kilometers in cities. So this is quite promising. TTY users should be one of the first to switch then. Perhaps that is the best way to investigate where the move to IP is impossible. Perhaps we can mandate in the US that ToIP must be able to pass through any operators network, and find a way to ensure we have ata boxes for TTY connectivity. Such box can support audio/t140c and text/t140. Just my 2 cents and a bit. Arnoud A. T. van Wijk AnnieS New Technology <http://www.AnnieS.nl> www.AnnieS.nl Mobile textphone (SIP): <mailto:arnoud@annies.nl> arnoud(a)annies.nl _____ From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se] Sent: donderdag 17 augustus 2006 21:34 To: Norman Williams; Rac(a)Lists.Wisc.Edu Subject: RE: [rac] Audio T.140 evaluation? Norman, I hope you will get a sample, and a gateway to use it with. audio/t140c should have very good opportunities to work well, at least for pure text and for alternating text and voice. And that is as far as it needs to be used with the applications that are proposed. As usual, there are many opportunities to do the application integration with different ambition levels. If you find issues, they may have a source in the surrounding software or environment but not in the standard itself. The issues are more on an IP service architecture plane. You simply should not call other media "audio" just for sake of convenience even if it seems to work. We got the RFC classified "historic", and we had to put in a lot of words about how the use was restricted to gateway applications. This is a copy of the words we got from the IETF area director Allison Mankin explaining why it got deemed "historic" from the beginning: --------------------------------------------------------- Gunnar, Paul, t140c was approved today, with the IESG finding it in perfect shape. The only discussion was about the Historic designation. We discussed the Last Call comments, the GEN-ART comment, and my rationale (including the announcement text I wrote in the tracker and my report on the Chairs' views). First, congratulations to you both on the excellent quality of the document as a document. It made it easy to work with. The purpose of making it Historic is not to condemn trunking gateways, it is to avoid setting precedent with a PS for calling text data an audio type. This document does so due to implementation pressures of SDP in these gateways. RFC 4103 has the example (text/t140) we want people to follow. The impact of going to Historic should not block the goals you and Paul have described: the payload specification is in an RFC-to-be, the media type being registered with no blockage from any media experts (which it would have gotten with a different designation on the document!). There is no internal text that says the RFC is Historic. So the only meaning of this designation is for later, when someone pops up with an audio major type with data that is not audio, the AVT or other working group can press back for a very tight applicability statement and cite precedent, or if there's no deployment, ask them to go to a different design. A few more bits inline. I hope this is more understandable now. Let me underline again the point about the problem of media type expert review if we had not gone Historic. With my best regards, Allison --------------------------------------------------------------- I find it very hard to go against these words and strt to use it between terminals. I find it easy and perfectly OK to use it between gateways. To use it between gateways and terminals is a grey area. The words in the RFC does not totally forbid that application, even if it is clearly stated that the intention is for trunking gateways. However accepting it between gateways and terminals makes the idea of media declarations in SIP collapse and the architecture of IP múltimedia to become a mess. I do not want to contribute to that. These issues will not be visible when you try it, but certainly something we, as a global advisory group will need to consider. Gunnar ---------------------------------------------------------------------------- - Gunnar Hellström, Omnitor gunnar.hellstrom(a)omnitor.se Mob: +46 708 204 288 Phone: +46 8 556 002 03 www.omnitor.se -----Original Message----- From: Norman Williams [mailto:norman.williams@gallaudet.edu] Sent: Thursday, August 17, 2006 8:19 PM To: Rac(a)Lists.Wisc.Edu Subject: [rac] Audio T.140 evaluation? Hi, I forgot to bring this topic to the phone conference we had recently. Is there a way for us to evaluate audio T.140 to see if there are issues? Do we have a working audio T.140 solution? Norman --- You are currently subscribed to rac as: gunnar.hellstrom(a)omnitor.se. To unsubscribe click here: https://lists.wisc.edu/u?id)14436N&n=l=c&o455168 or send a blank email to leave-3455168-2914436N(a)lists.wisc.edu --- You are currently subscribed to rac as: arnoud(a)annies.nl. To unsubscribe click here: https://lists.wisc.edu/u?id)14433R&n=l=c&o456252 or send a blank email to leave-3456252-2914433R(a)lists.wisc.edu --- You are currently subscribed to rac as: paulej(a)packetizer.com. To unsubscribe click here: https://lists.wisc.edu/u?id)14439J&n=l=c&o463578 or send a blank email to leave-3463578-2914439J(a)lists.wisc.edu --- You are currently subscribed to rac as: paulej(a)packetizer.com. To unsubscribe click here: https://lists.wisc.edu/u?id)14439J&n=T&l=rac&o474178 or send a blank email to leave-3474178-2914439J(a)lists.wisc.edu

1 0

RE: Document number allocation request
by Paul E. Jones 18 Aug '06

18 Aug '06

Takashima-san, Please use AVD-2935. Thanks! Paul > -----Original Message----- > From: youichi.takashima(a)ubin.jp [mailto:youichi.takashima@ubin.jp] > Sent: Friday, August 18, 2006 4:33 AM > To: Paul Jones > Cc: Noboru Koshizuka; Ishikawa, Chiaki > Subject: Document number allocation request > > Dear Paul, > > Could you allocate a document number to the following contribution? > > Source: YRP Ubiquitous Networking Laboratory > Title: Analysis of Information Delivery Applications using Networked ID > Question: 22 > > This is a "proposal" document. > > Best regards, > ---------------------------------------------------------------------- > Youichi TAKASHIMA > YRP Ubiquitous Networking Laboratory > Phone +81 3 5437 2270 > Facsimile +81 3 5437 2329 > 2-20-1 Nishi-Gotanda, Shinagawa-ku, Tokyo 141-0031 JAPAN > >

1 0

Document number allocation request
by youichi.takashima＠ubin.jp 18 Aug '06

18 Aug '06

Dear Paul, Could you allocate a document number to the following contribution? Source: YRP Ubiquitous Networking Laboratory Title: Analysis of Information Delivery Applications using Networked ID Question: 22 This is a "proposal" document. Best regards, ---------------------------------------------------------------------- Youichi TAKASHIMA YRP Ubiquitous Networking Laboratory Phone +81 3 5437 2270 Facsimile +81 3 5437 2329 2-20-1 Nishi-Gotanda, Shinagawa-ku, Tokyo 141-0031 JAPAN

1 0

RE: LSs from SG11 and TIPSAN; Re: Document number requests
by Paul E. Jones 18 Aug '06

18 Aug '06

If they get posted, I will grab them. Otherwise, do you think it will present an issue if we do not review them until the November meeting? Paul > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] > Sent: Thursday, August 17, 2006 10:17 AM > To: Paul E. Jones > Cc: itu-sg16(a)external.cisco.com > Subject: RE: LSs from SG11 and TIPSAN; Re: Document number requests > > > Both meetings took place in July. > Don't know the LS handling process by the EDH. > Would be surprised if they were not already in the pipeline. > - Albrecht > > > > > "Paul E. Jones" > <paulej@packetiz To: Albrecht > SCHWARZ/DE/ALCATEL@ALCATEL > er.com> cc: <itu- > sg16(a)external.cisco.com> > Subject: RE: LSs from SG11 > and TIPSAN; Re: Document number requests > 17.08.2006 15:50 > > > > > > Albrecht, > > I have been watching the liaison statements that have been made available > for SG16 since the last meeting. > > I did not see these. Were those just released? > > Paul > > > -----Original Message----- > > From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] > > Sent: Thursday, August 17, 2006 5:49 AM > > To: Paul E. Jones > > Cc: itu-sg16(a)external.cisco.com > > Subject: LSs from SG11 and TIPSAN; Re: Document number requests > > > > > > Paul, > > this email is only fyi. > > I'm aware of 3 LSs from SG11 & ETSI, submitted to Q.3 and Q.23 (see > > below), > > which are not yet in our Ottawa contributions list. > > Guess that the LSs will appear as GEN-xxx-16 input sometime. > > > > Regards, Albrecht > > > > > > > > Reference: T05-SG11-060724-TD-PLEN-0105!!MSW-E > > > |-------+-----------+----------------------+------------------------ > > ------------------| > > | 1 | 3/11 | ITU-T SG 16 (Q.23/16)|Media Codec > requirements > > in NGN | > > > |-------+-----------+----------------------+------------------------ > > ------------------| > > | 2 | 5/11 | ITU-T SG 16 (Q.3/16) |H.248 items related to > > Draft ITU-T Rec. | > > | | | |Q.rcp3.2 "H.248 Rw > > Profile" | > > > |-------+-----------+----------------------+------------------------ > > ------------------| > > > > > > > > > > > > ETSI reference: 11TD045; > > > > http://docbox.etsi.org/tispan/tispan/50-20060711-Sophia- > > P11/11TD045%20LSreply_to_ITUTSG16_on_H248packages.doc > > > > > > > > > > > > > > >

2 1

RE: Request for AVD number
by Paul E. Jones 17 Aug '06

17 Aug '06

Dave, Please use AVD-2932. Thanks! Paul > -----Original Message----- > From: Dave Lindbergh [mailto:lindbergh@92F1.com] > Sent: Thursday, August 17, 2006 10:22 AM > To: Paul Jones > Subject: Request for AVD number > > Question(s): 1, 2, 21 > > Source*: Polycom, Inc. > > Title: Comments on Videotelephony Requirements > > Purpose: Discussion > > > ---------- > Dave Lindbergh > Polycom, Inc. > 100 Minuteman Road > Andover MA 01810 USA > Voice: +1 978 292 5366 > Video: +1 978 292 2004 > Email: lindbergh(a)92F1.com >

1 0

RE: LSs from SG11 and TIPSAN; Re: Document number requests
by Albrecht.Schwarz＠alcatel.de 17 Aug '06

17 Aug '06

Both meetings took place in July. Don't know the LS handling process by the EDH. Would be surprised if they were not already in the pipeline. - Albrecht "Paul E. Jones" <paulej@packetiz To: Albrecht SCHWARZ/DE/ALCATEL@ALCATEL er.com> cc: <itu-sg16(a)external.cisco.com> Subject: RE: LSs from SG11 and TIPSAN; Re: Document number requests 17.08.2006 15:50 Albrecht, I have been watching the liaison statements that have been made available for SG16 since the last meeting. I did not see these. Were those just released? Paul > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] > Sent: Thursday, August 17, 2006 5:49 AM > To: Paul E. Jones > Cc: itu-sg16(a)external.cisco.com > Subject: LSs from SG11 and TIPSAN; Re: Document number requests > > > Paul, > this email is only fyi. > I'm aware of 3 LSs from SG11 & ETSI, submitted to Q.3 and Q.23 (see > below), > which are not yet in our Ottawa contributions list. > Guess that the LSs will appear as GEN-xxx-16 input sometime. > > Regards, Albrecht > > > > Reference: T05-SG11-060724-TD-PLEN-0105!!MSW-E > |-------+-----------+----------------------+------------------------ > ------------------| > | 1 | 3/11 | ITU-T SG 16 (Q.23/16)|Media Codec requirements > in NGN | > |-------+-----------+----------------------+------------------------ > ------------------| > | 2 | 5/11 | ITU-T SG 16 (Q.3/16) |H.248 items related to > Draft ITU-T Rec. | > | | | |Q.rcp3.2 "H.248 Rw > Profile" | > |-------+-----------+----------------------+------------------------ > ------------------| > > > > > > ETSI reference: 11TD045; > > http://docbox.etsi.org/tispan/tispan/50-20060711-Sophia- > P11/11TD045%20LSreply_to_ITUTSG16_on_H248packages.doc > > > >

1 0

Q.1 Rapporteur meeting - registration deadline
by Patrick Luthi 17 Aug '06

17 Aug '06

Dear Q1 experts, The Geneva meeting of Q.1/16 experts is rapidly approaching. Please register your participation and submission of contribution as quickly as possible according to the meeting notice available: http://avguest@ftp3.itu.int/av-arch/lbc-site/0608_Ottawa/q1f02.doc ** Document submission: Ask me for a Q.1 document number according to the procedure in the meeting announcement by 23:59 UTC, Saturday 19 August 2006 at the latest. Below is the list of contributions registered as of today: Q1-F00 Q1/16 Rapporteur List of Documents for Meeting F of the ITU-T SG16 Q.1 Experts Group Q1-F01 Nortel Invitation for Questions 1,2,3,4,5,21,22,24,25,29 Experts Group in Ottawa, Canada --> Ott_Invitation.doc Q1-F02 Q1/16 Rapporteur Meeting announcement for Meeting F of Q.1/16 Experts Ottawa, Canada, 29-31 August 2006 Q1-F03 Q1/16 Rapporteur Meeting report of Working Party 2 of ITU-T Study Group 16, Geneva, 3-13 April 2006 Q1-F04 AHG Chair Report of the H.324 text conversation Ad-hoc Group Q1-F05 Editors Draft new H.gamma Q1-F06 Editor Draft new H.324 Annex Text Conversation Q1-F07 Editor Draft revised T.120 Q1-F08 Editor Draft revised T.123 Q1-F09 France Telecom Videotelephony Requirements Q1-F10 Polycom Comments on Videotelephony Requirements Best regards, Patrick Luthi Rapporteur for Q.1/16

1 0

RE: LSs from SG11 and TIPSAN; Re: Document number requests
by Paul E. Jones 17 Aug '06

17 Aug '06

Albrecht, I have been watching the liaison statements that have been made available for SG16 since the last meeting. I did not see these. Were those just released? Paul > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] > Sent: Thursday, August 17, 2006 5:49 AM > To: Paul E. Jones > Cc: itu-sg16(a)external.cisco.com > Subject: LSs from SG11 and TIPSAN; Re: Document number requests > > > Paul, > this email is only fyi. > I'm aware of 3 LSs from SG11 & ETSI, submitted to Q.3 and Q.23 (see > below), > which are not yet in our Ottawa contributions list. > Guess that the LSs will appear as GEN-xxx-16 input sometime. > > Regards, Albrecht > > > > Reference: T05-SG11-060724-TD-PLEN-0105!!MSW-E > |-------+-----------+----------------------+------------------------ > ------------------| > | 1 | 3/11 | ITU-T SG 16 (Q.23/16)|Media Codec requirements > in NGN | > |-------+-----------+----------------------+------------------------ > ------------------| > | 2 | 5/11 | ITU-T SG 16 (Q.3/16) |H.248 items related to > Draft ITU-T Rec. | > | | | |Q.rcp3.2 "H.248 Rw > Profile" | > |-------+-----------+----------------------+------------------------ > ------------------| > > > > > > ETSI reference: 11TD045; > > http://docbox.etsi.org/tispan/tispan/50-20060711-Sophia- > P11/11TD045%20LSreply_to_ITUTSG16_on_H248packages.doc > > > >

1 0

RE: Further numbers; Re: Document number requests
by Paul E. Jones 17 Aug '06

17 Aug '06

Albrecht, Please use the numbers assigned as shown in the below table. Note that for AVD-2921, I could not see the entire title, so I have shaded that to fill in later. AVD-2914 H Series Supp. 7: Gateway Control Protocol: Establishment Procedures for the H.248 MGC-MG Control Association Editor AVD-2915 H Series Supp. RTPXtalk: Guidelines for Resource Management of Resources for H.248 RTP Terminations Editor AVD-2916 Implementers Guide for H.248.1 Version 2 & 3 ABNF Grammar for § E.12.4.3 Packet Loss rtp/pl Alcatel AVD-2917 Implementers Guide for H.248.1 Version 2 & 3 ServiceChange Parameter ServiceChangeAddress Alcatel AVD-2918 Implementers Guide for H.248.1 Version 2 & 3 Discussion on Service State Alcatel AVD-2919 Implementers Guide for H.248.1 Profile Negotiation Procedure Alcatel AVD-2920 Implementers Guide for H.248.1 Version 3 Appendix II: Clarification to Reference Clause Alcatel AVD-2921 Implementers Guide for H.248.1 Version 3 Appendix III: Typo in § ???? Alcatel AVD-2922 Implementers Guide for H.248.1 Version 3 Clarification for ASN.1 Length Encoding Alcatel AVD-2923 IMG Update or new release of H.248.1 Version 3? Replacement of obsoleted RFC 2327 by RFC 4566 Alcatel AVD-2924 Implementers Guide for H.248.1 Version 2 & 3 Clarification for § 6.1.2 on Context Attributes Alcatel AVD-2925 Implementers Guide for H.248.1 Version 2 & 3 ServiceChange with Disconnect Alcatel AVD-2926 H.248.gmgc Explicit Address Out Package (Package aout) Alcatel AVD-2927 H.248.tman New Appendix: Deriving PEP parameters from H.248 tman parameters Alcatel AVD-2928 Extension for H.248.37: Address Reporting Package Alcatel AVD-2929 H.Sup7.CtrlAssoc Further Text for Scope Section Alcatel AVD-2930 H.Sup7.CtrlAssoc Check of § 5.5.1.2 Address Changes Alcatel AVD-2931 H.248.40 Non-normative References Alcatel Thanks! Paul > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] > Sent: Wednesday, August 16, 2006 11:52 AM > To: Paul E. Jones > Subject: Further numbers; Re: Document number requests > > > Paul, > > please allocate numbers for following 18 Q3/16 contributions. > > Thanks, > Albrecht >

2 1

RE: Document number request
by Paul E. Jones 16 Aug '06

16 Aug '06

Mr. Okubo, > 1/ > Source: Chairman of SG16 > Title: Short reports from IPTV-FG meeting, Geneva 10-14 July 2006 > Questions: 21/16, 22/16 > Purpose: Report and discussion Please use AVD-2911 > 2/ > Source: Waseda University > Title: Comments on videotelephony standardization > Questions: 22/16, 2/16 > Purpose: Discussion Please use AVD-2912 > 3/ > Source: Chairman of SG16 > Title: Short Report on NGN-GSI Meetings in July 2006 > Questions: All > Purpose: Report and discussion Please use AVD-2913 Thanks! Paul

1 0

RE: Document Number Request
by Paul E. Jones 16 Aug '06

16 Aug '06

Christian, Please use AVD-2908 - 2910, ordered as you have them listed. Thanks! Paul > -----Original Message----- > From: Christian Groves [mailto:Christian.Groves@nteczone.com] > Sent: Wednesday, August 16, 2006 12:55 AM > To: Paul E. Jones > Subject: Document Number Request > > G'Day Paul, > > Could I please have AVD numbers for the following documents? > > H.248 Living List: Possible Additions [Source: Q.3 Rapporteur] > H.248 Package Supplement [Source: Editor (C.Groves)] > H.248 Living List [Source: Q.3 Rapporteur] > > Regards, Christian >

1 0

RE: Q.2/16 Contributions
by Paul E. Jones 15 Aug '06

15 Aug '06

Viqar, I have assigned AVD-2903 and AVD-2904 to your documents as you have them ordered below. The deadline for uploading the documents (or e-mailing them to me) is Monday, August 21. Please use this document template as you prepare your contributions: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0608_Ott/AVD-template.doc Other information related to the meeting is here: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0608_Ott/Notice_Ottawa_0608.tx t Thanks! Paul _____ From: Shaikh, Viqar A [mailto:vshaikh@telcordia.com] Sent: Tuesday, August 15, 2006 10:31 AM To: paulej(a)packetizer.com Subject: Q.2/16 Contributions Paul, I will have the following 2 contributions for Q.2/16 meeting. Please let me know the logistics, nos., deadline, etc. 1. Proposed Enhancements to the H.460.4 in Support of Country/International Network of Call Origination 2. Enhancements to H.246 in Support of User Priority Level and Country/International Network of Call Origination Mapping Thanks, Viqar

1 0

RE: Request for AVD numbers
by Paul E. Jones 15 Aug '06

15 Aug '06

Yangbo, I have assigned the following numbers: AVD-2885 Requirements for H.248.GMGC Huawei AVD-2886 Proposed Resolution of some issues of H.248.CCC Huawei AVD-2887 Proposed additions to H.248.CCC Huawei AVD-2888 Proposed new Termination Connection Model Package for H.248 Huawei AVD-2889 Proposed new NAT Traversal Toolkit Packages for H.248 Huawei AVD-2890 Proposed Additions to H.248 Sub-Series IG Huawei AVD-2891 Proposal for WI of H.248 TMAN, VLAN, DS and MPLS Packages Huawei AVD-2892 Proposed Amendment to H.248.9 for adding the direction parameter to the aasb package Huawei AVD-2893 Proposed Amendment to H.248.9 for adding the package of multimedia play Huawei AVD-2894 Proposed Amendment to H.248.9 for terminating the recording by command key sequence Huawei AVD-2895 Proposed Amendment to H.248.19 for ASR package Huawei AVD-2896 Proposed Amendment to H.248.19 for floor control package Huawei AVD-2897 Proposed Amendment to H.248.19 for supporting floor control policy Huawei AVD-2898 Proposed Amendment to H.248.19 for supporting floor status change detection Huawei AVD-2899 Draft H.248.CCC - Connection Capability Control Package Editor AVD-2900 Draft H.248.SCR - Statistic Conditional Reporting Package Editor AVD-2901 Draft H.248.2 Amendment 1 Editor AVD-2902 Draft H.248.9 Amendment 1 Editor Thanks! Paul _____ From: Yangbo Lin [mailto:linyangbo@huawei.com] Sent: Tuesday, August 15, 2006 3:26 AM To: Paul E. Jones Cc: OKUBO Sakae; Christian Groves; Noah Luo Subject: Request for AVD numbers Hello Paul, Please allocate the AVD numbers for the following 14 Huawei contributions to Q3/16: 1. Requirements for H.248.GMGC 2. Proposed Resolution of some issues of H.248.CCC 3. Proposed additions to H.248.CCC 4. Proposed new Termination Connection Model Package for H.248 5. Proposed new NAT Traversal Toolkit Packages for H.248 6. Proposed Additions to H.248 Sub-Series IG 7. Proposal for WI of H.248 TMAN, VLAN, DS and MPLS Packages 8. Proposed Amendment to H.248.9 for adding the direction parameter to the aasb package 9. Proposed Amendment to H.248.9 for adding the package of multimedia play 10. Proposed Amendment to H.248.9 for terminating the recording by command key sequence 11. Proposed Amendment to H.248.19 for ASR package 12. Proposed Amendment to H.248.19 for floor control package 13. Proposed Amendment to H.248.19 for supporting floor control policy 14. Proposed Amendment to H.248.19 for supporting floor status change detection And the following 4 Editor drafts of Q3/16: 1. Draft H.248.CCC - Connection Capability Control Package 2. Draft H.248.SCR - Statistic Conditional Reporting Package 3. Draft H.248.2 Amendment 1 4. Draft H.248.9 Amendment 1 Regards, Yangbo

1 0

Document number requests
by Paul E. Jones 15 Aug '06

15 Aug '06

SG16 Experts, As Mr. Okubo mentioned, if you wish to request document numbers, those requests need to be sent to me by the end of the week. I have replied to every request that I have received. However, I discovered that I had a configuration error on one of my mail servers that resulted in no mail being delivered to me for the entire business day on Monday. So, if you sent a request and did not get a reply, please send another message to me. Thanks! Paul

1 0

Reminder for the Ottawa meeting participants
by OKUBO Sakae 13 Aug '06

13 Aug '06

Dear WP2/16 experts, Please register your input documents as follows: Q.1 Contact Mr Patrick Luthi <patrick.luthi(a)tandberg.no> by 19 August. Upload your documents by 22 August. Q.2, 3, 4, 5, 21, 22, 24, 25, 29 Contact Mr Paul Jones <paulej(a)packetizer.com> by 18 August. Upload your documents by 21 August. Those documents registered or uploaded after the deadlines are handled as "late arrival" and considered at the meeting with the participants' agreement. Please also note the following advice from the meeting host, Mr Kevin Boyle <kboyle(a)nortel.com>: At 23:30 -0400 06/08/10, Kevin Boyle wrote: >Please note that as of today (8/10), on flights in, into or out of the >US, UK or Canada no liquids, gels, creams, perfumes, cologne, >cosmetics, shampoo, suntan lotion, toothpaste and other items of >similar consistency will be allowed to be carried onto the plane >into the passenger cabins. Liquids include soft drinks, bottled >water and other beverages. These items are allowed in checked >baggage. Note that on all flights originating in the UK, NO baggage >is allowed to be carried on the plane: all bags must be checked. > >See the following URLs for more information: >http://www.tsa.gov/press/happenings/threat-change.shtm >http://www.tc.gc.ca/mediaroom/releases/nat/2006/06-gc010e.htm >http://www.dft.gov.uk/stellent/groups/dft_about/documents/page/dft_about_61… -- Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp (<== sokubo(a)waseda.jp, valid until 31 March 2007) Visiting Professor Global Information and Telecommunication Institute (GITI) 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

Reminder for the Ottawa meeting participants
by OKUBO Sakae 13 Aug '06

13 Aug '06

Dear WP2/16 experts, Please register your input documents as follows: Q.1 Contact Mr Patrick Luthi <patrick.luthi(a)tandberg.no> by 19 August. Upload your documents by 22 August. Q.2, 3, 4, 5, 21, 22, 24, 25, 29 Contact Mr Paul Jones <paulej(a)packetizer.com> by 18 August. Upload your documents by 21 August. Those documents registered or uploaded after the deadlines are handled as "late arrival" and considered at the meeting with the participants' agreement. Please also note the following advice from the meeting host, Mr Kevin Boyle <kboyle(a)nortel.com>: At 23:30 -0400 06/08/10, Kevin Boyle wrote: >Please note that as of today (8/10), on flights in, into or out of the >US, UK or Canada no liquids, gels, creams, perfumes, cologne, >cosmetics, shampoo, suntan lotion, toothpaste and other items of >similar consistency will be allowed to be carried onto the plane >into the passenger cabins. Liquids include soft drinks, bottled >water and other beverages. These items are allowed in checked >baggage. Note that on all flights originating in the UK, NO baggage >is allowed to be carried on the plane: all bags must be checked. > >See the following URLs for more information: >http://www.tsa.gov/press/happenings/threat-change.shtm >http://www.tc.gc.ca/mediaroom/releases/nat/2006/06-gc010e.htm >http://www.dft.gov.uk/stellent/groups/dft_about/documents/page/dft_about_61… -- Best regards, OKUBO Sakae e-mail: okubo(a)aoni.waseda.jp (<== sokubo(a)waseda.jp, valid until 31 March 2007) Visiting Professor Global Information and Telecommunication Institute (GITI) 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

Meeting Documents Uploaded
by Paul E. Jones 12 Aug '06

12 Aug '06

SG16 Experts, I have uploaded all of the documents received for the meeting this far to: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0608_Ott/ May I please remind everyone to use this template when preparing documents: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0608_Ott/AVD-template.doc For Rapporteur meetings, the normal ITU templates are not used. Thanks! Paul

1 0

RE: Document request
by Paul E. Jones 11 Aug '06

11 Aug '06

Kevin, > Draft Updated H.248 Subseries Implementors' Guide > Draft Updated H.248 V2 Implementors' Guide > Draft New H.248.44 "Multi-level Precedence and Pre-emption Package" > Draft New H.248.25 Amendment 1 > Draft New H.248.28 Amendment 1 > Draft New H.248.30 Amendment 1 I have allocated AVD-2678 to AVD-2683 to these documents in the order shown. Thanks! Paul

1 0

RE: AVD number
by Paul E. Jones 11 Aug '06

11 Aug '06

Mingjun, I have assigned AVD-2677 for you. Thanks! Paul _____ From: smj [mailto:sunmjun@hotmail.com] Sent: Friday, August 11, 2006 1:03 PM To: 'Paul E. Jones' Subject: AVD number Hello, Paul, Could you please assign AVD number for the following draft: Question(s): 25 Source*: Editor Title: Draft new Rec. H.460.spn "Negotiation of Security Protocols to Protect H.225.0 Call Signaling Message" Best Regards, Mingjun

1 0

RE: AVD number
by Paul E. Jones 09 Aug '06

09 Aug '06

Patrick, I have assigned AVD-2674 for your document. Thanks! Paul > -----Original Message----- > From: Patrick Luthi [mailto:patrick.luthi@tandberg.net] > Sent: Tuesday, August 08, 2006 10:36 PM > To: Paul Jones > Subject: AVD number > > Hi Paul, > > Could you please assign an AVD number for the following contribution: > > Source: Tandberg > Title: clarifications to the scope of proposed draft H.proxy > Question: 5 > >

1 0

RE: Request for AVD numbers
by Paul E. Jones 02 Aug '06

02 Aug '06

Bruno, I have assigned AVD-2869 and AVD-2860 to your documents in the order listed. Who should be listed as the source? Orange or France Telecom? Paul _____ From: CHATRAS Bruno RD-CORE-ISS [mailto:bruno.chatras@orange-ft.com] Sent: Wednesday, August 02, 2006 1:17 PM To: paulej(a)packetizer.com Subject: Request for AVD numbers Dear Mr Jones, Could you please allocate two AVD-numbers to the following documents for the next Q.3/16 meeting. - Package selection for supporting Gate Control mechanisms - Comments on new H.248 properties for supporting Gate Control mechanisms Best Regards, Bruno Chatras

1 0

Request for AVD numbers
by CHATRAS Bruno RD-CORE-ISS 02 Aug '06

02 Aug '06

Dear Mr Jones, Could you please allocate two AVD-numbers to the following documents for the next Q.3/16 meeting. - Package selection for supporting Gate Control mechanisms - Comments on new H.248 properties for supporting Gate Control mechanisms Best Regards, Bruno Chatras

1 0

RE: Request for AVD numbers
by Albrecht.Schwarz＠alcatel.de 02 Aug '06

02 Aug '06

Paul: All are Alcatel documents. Following ones are already uploaded in http://ftp3.itu.int/av-arch/avc-site/Incoming/ AVD-2834 H.248.37_Addendum.zip 02-Aug-2006 08:43 207k AVD-2851 Alcatelo1 T05-SG16-060828-D H.248.tman_Package_Ed01_20060731.doc 02-Aug-2006 08:44 105k AVD-2852 Alcateln1 T05-SG16-060828-D H.248.ds_Package_Ed01_20060731.doc 02-Aug-2006 08:44 100k AVD-2853 Alcatelp1 T05-SG16-060828-D H.248.mpls_Package_Ed01_20060731.doc 02-Aug-2006 08:44 98k AVD-2854 Alcatelq1 T05-SG16-060828-D H.248.vlan_Package_Ed01_20060731.doc 02-Aug-2006 08:44 99k AVD-2856 Alcatelr3 T05-SG16-060828-D H.248.rsb_Package_Ed01_20060731.doc 02-Aug-2006 08:51 102k Thanks, Albrecht "Paul E. Jones" <paulej@packetiz To: Albrecht SCHWARZ/DE/ALCATEL@ALCATEL er.com> cc: <itu-sg16(a)external.cisco.com> Subject: RE: Request for AVD numbers 01.08.2006 18:41 Albrecht, I have allocated numbers as follows: AVD-2851 Draft new Rec. H.248.tman: Traffic Management Package AVD-2852 Draft new Rec. H.248.ds: Differentiated Services Package AVD-2853 Draft new Rec. H.248.mpls: MPLS Package AVD-2854 Draft new Rec. H.248.vlan: VLAN Package AVD-2855 Extension for H.248.tman Package: new Packet Size Package AVD-2856 Draft new Rec. H.248.rsb Package: RTP Specific Behavior Package AVD-2857 Draft new Rec. H.248.qos Package: QoS Class Package AVD-2858 Draft new Rec. H.248.pm: Pull Mode Package Can you tell me which of these are editor's documents and which are Alcatel documents? Paul > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] > Sent: Tuesday, August 01, 2006 11:37 AM > To: Paul E. Jones > Subject: RE: Request for AVD numbers > > > Paul, > > pls allocate numbers to following ALCATEL contributions. > Thanks, > Albrecht > >

1 0

RE: Request for AVD numbers
by Paul E. Jones 01 Aug '06

01 Aug '06

Albrecht, I have allocated numbers as follows: AVD-2851 Draft new Rec. H.248.tman: Traffic Management Package AVD-2852 Draft new Rec. H.248.ds: Differentiated Services Package AVD-2853 Draft new Rec. H.248.mpls: MPLS Package AVD-2854 Draft new Rec. H.248.vlan: VLAN Package AVD-2855 Extension for H.248.tman Package: new Packet Size Package AVD-2856 Draft new Rec. H.248.rsb Package: RTP Specific Behavior Package AVD-2857 Draft new Rec. H.248.qos Package: QoS Class Package AVD-2858 Draft new Rec. H.248.pm: Pull Mode Package Can you tell me which of these are editor's documents and which are Alcatel documents? Paul > -----Original Message----- > From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] > Sent: Tuesday, August 01, 2006 11:37 AM > To: Paul E. Jones > Subject: RE: Request for AVD numbers > > > Paul, > > pls allocate numbers to following ALCATEL contributions. > Thanks, > Albrecht > >

1 0

RE: Document number allocation
by Paul E. Jones 01 Aug '06

01 Aug '06

Mr. Okubo, I have allocated AVD-2850 for this document. For the source, is "TTC" sufficient? (I need a relatively short name.) Thanks! Paul > -----Original Message----- > From: OKUBO Sakae [mailto:okubo@mxz.mesh.ne.jp] > Sent: Tuesday, August 01, 2006 4:07 AM > To: Paul E. Jones > Cc: Toshikazu Aoki > Subject: Document number allocation > > Dear Paul, > > Could you allocate a document number to the following contribution? > > Source: TTC / Media Coding WG / Multimedia System SWG > Title: Proposed Corrections to Technical Paper (05/05) "Firewall and > NAT Traversal Problems in H.323 Systems" > Question: 5 > > This is to summarize the corrections that we have found necessary and > Editor confirmed. > > -- > Best regards, > > OKUBO Sakae > e-mail: okubo(a)aoni.waseda.jp > (<== sokubo(a)waseda.jp, valid until 31 March 2007) > Visiting Professor > Global Information and Telecommunication Institute (GITI) > 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