- sg16-avd - lists.packetizer.com

Q.H/16 Meeting notes and new Text over IP Requirements spec
by Gunnar Hellstrom 31 Mar '03

31 Mar '03

Draft meeting notes from the ITU-T Q.H/16 "Accessibility" meeting March 18-19 are now available as document number QH16-03014 in the Standards area of www.totalconversation.org An output document with draft edited ToIP requirements is available as document QH16-03013 in the same location. An overview paper on Total Conversation and Text Telephony including wireless aspects, made for a presentation in the CEN/CENELEC/ETSI conference "Accessibility for All" is available in the "White Papers" area of the same site. 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 -------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Retirement and a New Career
by Folts, Harold 25 Mar '03

25 Mar '03

Greetings, I will be retiring from Government service on March 28 and entering a new career in real estate in Virginia to handle residential properties. It has been a real pleasure to work with you all over the many past years. I will always cherish the many friendships. After a 43-year career in the IT/telecommunications field, I have witnessed a dramatic revolution in technology. I have had the pleasure to work with people from all over the world and visit many countries and enjoy the many different cultures. I will keep these wonderful experiences in my memories through the oncoming years. I greatly appreciate the opportunity to work with you all. If you ever get to the Washington and Northern Virginia area, please give me a call : +1 703 281-0761 email: hal(a)catchingahome.com 400 Holloway Ct. NE Vienna, VA 22180-3545 USA I wish you all the best success in the future. Hopefully, we will see a comprehensive family of telecommunication capabilities for disaster relief become a reality. My warmest regards for all, Hal ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Re: Corrected - Planning the SG16 meeting in May
by OKUBO Sakae 20 Mar '03

20 Mar '03

Dear all, At 18:38 +0900 03/03/20, OKUBO Sakae wrote: >[...]SG16 Chairman and TSB have finalized the framework of the >meeting for issuance of the Collective Letter that will soon be >posted at the ITU-T web site. [...] Now it is available at the following place: http://www.itu.int/md/meetingdoc.asp?type=sitems&lang=e&parent=T01-SG16-COL… -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp ******************************************************************* YRP Office Global Information and Telecommunication Institute (GITI) 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 GITI Headquarter 29-7 Waseda University Bldg. Tel: +81 3 5286 3831 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ******************************************************************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Re: T.38 potentially broken by recent Corrigendum
by Kevin Boyle 15 Mar '03

15 Mar '03

All, It is my understanding that the ellipsis was intended to be there, and that it wasn't until folks started implementing that it was noticed that it got dropped somewhere between the editor's hands and publication. There was a TD in the Feb 2000 meeting noting this typo. I can produce it if anyone wants to see it. It is also my understanding that care was taken to ensure that all known vendors were made aware of the change at the time. Kevin -----Original Message----- From: Klaghofer Karl ICN EN HS D 11 [mailto:karl.klaghofer@SIEMENS.COM] Sent: Friday, March 14, 2003 3:44 AM To: ITU-SG16(a)echo.jf.INTEL.COM Subject: AW: T.38 potentially broken by recent Corrigendum Paul, I fully agree with you, that the T.38 (1998) asn.1 and the Revision of T.38 (2002) asn.1 needs to be backwards compatible. Regards, Karl Klaghofer Siemens -----Ursprüngliche Nachricht----- Von: Paul E. Jones [mailto:paulej@PACKETIZER.COM] Gesendet: Montag, 3. März 2003 03:21 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: T.38 potentially broken by recent Corrigendum Folks, I just recently discovered that the ITU-T published a corrigendum to T.38 (1998) that apparently breaks backward compatibility for all T.38 devices currently deployed that follow the original 1998 specifications. The particular document in question is Corrigendum 1, which was approved in 2000 and subsequently published in May 2001. You can download the corrigendum document for free from this site: http://www.itu.int/rec/recommendation.asp?type=folders <http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC- T.38> &lang=e&parent=T-REC-T.38 The issue at hand is a change in the ASN.1 syntax found in Annex A/T.38. The particular data structure is shown here: Data-Field ::= SEQUENCE OF SEQUENCE { field-type ENUMERATED { hdlc-data, hdlc-sig-end, hdlc-fcs-OK, hdlc-fcs-BAD, hdlc-fcs-OK-sig-end, hdlc-fcs-BAD-sig-end, t4-non-ecm-data, t4-non-ecm-sig-end, ... }, field-data OCTET STRING (SIZE(1..65535)) OPTIONAL } The syntactical change was the addition of an ellipsis at the end of the ENUMERATED "field-type". In the published 1998 specification, this ellipsis did not exist. What I would like to know is whether this change impacts your product or not. I am aware of many deployed devices on the market today that employs the 1998 syntax without this ellipsis. I would like to find out to what extent this change is going to present problems for companies represented on various lists and, if I get sufficient support, I want to take a contribution to the ITU-T SG16 meeting in May to try to resolve this problem in such a way as to not break backward compatibility and interoperability. I am looking forward to your replies. Kindest Regards, Paul E. Jones ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

2 1

Re: T.38 potentially broken by recent Corrigendum
by Dominic Walker 14 Mar '03

14 Mar '03

FYI, we are currently discussing the issue within the Q.14 e-mail reflector, and the Q.14 experts are looking at a one possible solution that may link a version number to the support of the two ASN.1 version.With this mechanism, version 0 (and possibly version 1) would refer to the ASN.1 definition published in the 06/1998 T.38 spec, and version 2 or higher would refer to the ASN.1 definition published in the 03/2002 T.38 spec. I believe a decision will be made at the Q.14 May 2003 Geneva meeting. Dominic. -----Original Message----- From: Boyle, Kevin [NCRTP:3Z40:EXCH] Sent: Friday, March 14, 2003 2:16 PM To: ITU-SG16(a)echo.jf.INTEL.COM Subject: Re: T.38 potentially broken by recent Corrigendum All, It is my understanding that the ellipsis was intended to be there, and that it wasn't until folks started implementing that it was noticed that it got dropped somewhere between the editor's hands and publication. There was a TD in the Feb 2000 meeting noting this typo. I can produce it if anyone wants to see it. It is also my understanding that care was taken to ensure that all known vendors were made aware of the change at the time. Kevin -----Original Message----- From: Klaghofer Karl ICN EN HS D 11 [mailto:karl.klaghofer@SIEMENS.COM] Sent: Friday, March 14, 2003 3:44 AM To: ITU-SG16(a)echo.jf.INTEL.COM Subject: AW: T.38 potentially broken by recent Corrigendum Paul, I fully agree with you, that the T.38 (1998) asn.1 and the Revision of T.38 (2002) asn.1 needs to be backwards compatible. Regards, Karl Klaghofer Siemens -----Ursprüngliche Nachricht----- Von: Paul E. Jones [mailto:paulej@PACKETIZER.COM] Gesendet: Montag, 3. März 2003 03:21 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: T.38 potentially broken by recent Corrigendum Folks, I just recently discovered that the ITU-T published a corrigendum to T.38 (1998) that apparently breaks backward compatibility for all T.38 devices currently deployed that follow the original 1998 specifications. The particular document in question is Corrigendum 1, which was approved in 2000 and subsequently published in May 2001. You can download the corrigendum document for free from this site: http://www.itu.int/rec/recommendation.asp?type=folders <http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC- T.38> &lang=e&parent=T-REC-T.38 The issue at hand is a change in the ASN.1 syntax found in Annex A/T.38. The particular data structure is shown here: Data-Field ::= SEQUENCE OF SEQUENCE { field-type ENUMERATED { hdlc-data, hdlc-sig-end, hdlc-fcs-OK, hdlc-fcs-BAD, hdlc-fcs-OK-sig-end, hdlc-fcs-BAD-sig-end, t4-non-ecm-data, t4-non-ecm-sig-end, ... }, field-data OCTET STRING (SIZE(1..65535)) OPTIONAL } The syntactical change was the addition of an ellipsis at the end of the ENUMERATED "field-type". In the published 1998 specification, this ellipsis did not exist. What I would like to know is whether this change impacts your product or not. I am aware of many deployed devices on the market today that employs the 1998 syntax without this ellipsis. I would like to find out to what extent this change is going to present problems for companies represented on various lists and, if I get sufficient support, I want to take a contribution to the ITU-T SG16 meeting in May to try to resolve this problem in such a way as to not break backward compatibility and interoperability. I am looking forward to your replies. Kindest Regards, Paul E. Jones ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Re: T.38 potentially broken by recent Corrigendum
by James Rafferty 14 Mar '03

14 Mar '03

Kevin , Glenn Parsons, Dave Duehren and I have all pointed out that the ellipsis was supposed to be there but was dropped by the TSB during publication. We had a Rapporteur's/ Working Party meeting in in Fall 1999 that confirmed the need to reinstate it. The driver for the reinstatement was based on the need we foresaw to extend T.38 to support new features such as V.34 fax. And yes, we all tried to let people know about the issue at the time. But, it did take a while for the ITU to document the change, which has created today's issue. In a related vein, the fax question also saw that there were variations emerging as new T.38 features emerged, such as the TPKT support for TCP/IP, so we agreed to start adding a version to the T.38. New implementations will need to recognize that there are different versions of T.38 in order to gain proper interoperation. IP call control will also need to expose versions during negotiations if interoperability is to be assured. Given where we are, the relevant questions will need to sort this out at the next SG16 meeting in May. Gaining a rough consensus on how to resolve it before then would be a good thing. James -----Original Message----- From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] Sent: Friday, March 14, 2003 9:16 AM To: ITU-SG16(a)echo.jf.INTEL.COM Subject: Re: T.38 potentially broken by recent Corrigendum All, It is my understanding that the ellipsis was intended to be there, and that it wasn't until folks started implementing that it was noticed that it got dropped somewhere between the editor's hands and publication. There was a TD in the Feb 2000 meeting noting this typo. I can produce it if anyone wants to see it. It is also my understanding that care was taken to ensure that all known vendors were made aware of the change at the time. Kevin -----Original Message----- From: Klaghofer Karl ICN EN HS D 11 [mailto:karl.klaghofer@SIEMENS.COM] Sent: Friday, March 14, 2003 3:44 AM To: ITU-SG16(a)echo.jf.INTEL.COM Subject: AW: T.38 potentially broken by recent Corrigendum Paul, I fully agree with you, that the T.38 (1998) asn.1 and the Revision of T.38 (2002) asn.1 needs to be backwards compatible. Regards, Karl Klaghofer Siemens -----Ursprüngliche Nachricht----- Von: Paul E. Jones [mailto:paulej@PACKETIZER.COM] Gesendet: Montag, 3. März 2003 03:21 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: T.38 potentially broken by recent Corrigendum Folks, I just recently discovered that the ITU-T published a corrigendum to T.38 (1998) that apparently breaks backward compatibility for all T.38 devices currently deployed that follow the original 1998 specifications. The particular document in question is Corrigendum 1, which was approved in 2000 and subsequently published in May 2001. You can download the corrigendum document for free from this site: http://www.itu.int/rec/recommendation.asp?type=folders <http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC- T.38> &lang=e&parent=T-REC-T.38 The issue at hand is a change in the ASN.1 syntax found in Annex A/T.38. The particular data structure is shown here: Data-Field ::= SEQUENCE OF SEQUENCE { field-type ENUMERATED { hdlc-data, hdlc-sig-end, hdlc-fcs-OK, hdlc-fcs-BAD, hdlc-fcs-OK-sig-end, hdlc-fcs-BAD-sig-end, t4-non-ecm-data, t4-non-ecm-sig-end, ... }, field-data OCTET STRING (SIZE(1..65535)) OPTIONAL } The syntactical change was the addition of an ellipsis at the end of the ENUMERATED "field-type". In the published 1998 specification, this ellipsis did not exist. What I would like to know is whether this change impacts your product or not. I am aware of many deployed devices on the market today that employs the 1998 syntax without this ellipsis. I would like to find out to what extent this change is going to present problems for companies represented on various lists and, if I get sufficient support, I want to take a contribution to the ITU-T SG16 meeting in May to try to resolve this problem in such a way as to not break backward compatibility and interoperability. I am looking forward to your replies. Kindest Regards, Paul E. Jones ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

AW: T.38 potentially broken by recent Corrigendum
by Klaghofer Karl ICN EN HS D 11 14 Mar '03

14 Mar '03

Paul, I fully agree with you, that the T.38 (1998) asn.1 and the Revision of T.38 (2002) asn.1 needs to be backwards compatible. Regards, Karl Klaghofer Siemens -----Ursprüngliche Nachricht----- Von: Paul E. Jones [mailto:paulej@PACKETIZER.COM] Gesendet: Montag, 3. März 2003 03:21 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: T.38 potentially broken by recent Corrigendum Folks, I just recently discovered that the ITU-T published a corrigendum to T.38 (1998) that apparently breaks backward compatibility for all T.38 devices currently deployed that follow the original 1998 specifications. The particular document in question is Corrigendum 1, which was approved in 2000 and subsequently published in May 2001. You can download the corrigendum document for free from this site: http://www.itu.int/rec/recommendation.asp?type=folders <http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC- T.38> &lang=e&parent=T-REC-T.38 The issue at hand is a change in the ASN.1 syntax found in Annex A/T.38. The particular data structure is shown here: Data-Field ::= SEQUENCE OF SEQUENCE { field-type ENUMERATED { hdlc-data, hdlc-sig-end, hdlc-fcs-OK, hdlc-fcs-BAD, hdlc-fcs-OK-sig-end, hdlc-fcs-BAD-sig-end, t4-non-ecm-data, t4-non-ecm-sig-end, ... }, field-data OCTET STRING (SIZE(1..65535)) OPTIONAL } The syntactical change was the addition of an ellipsis at the end of the ENUMERATED "field-type". In the published 1998 specification, this ellipsis did not exist. What I would like to know is whether this change impacts your product or not. I am aware of many deployed devices on the market today that employs the 1998 syntax without this ellipsis. I would like to find out to what extent this change is going to present problems for companies represented on various lists and, if I get sufficient support, I want to take a contribution to the ITU-T SG16 meeting in May to try to resolve this problem in such a way as to not break backward compatibility and interoperability. I am looking forward to your replies. Kindest Regards, Paul E. Jones ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Q.H/16 documents on Text over IP for Rapporteur meeting next week
by Gunnar Hellström 14 Mar '03

14 Mar '03

A set of documents from Omnitor, Cisco, Gallaudet University and TR30.1 are available at the informal site for the coming meeting of ITU-T Q.H/16 (Accessibility) next week in UK. A few more are to be provided. The topic of all documents so far is Text over IP. The site is www.totalconversation.org/standard 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 -------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

[H460.9] - Update on status of RTCP Reporting Extensions
by Alan Clark 06 Mar '03

06 Mar '03

Attached is an initial rough pass at an Annex for H.460.9 to incorporate the RTCP Reporting Extensions metrics. My ASN.1 may be a little rusty, hence apologies for any syntax errors. Regards Alan Clark Telchemy PS I mailed this to the reflector yesterday however it appeared not to "reflect". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0

Text over IP draft Requirements spec available in new version
by Gunnar Hellström 04 Mar '03

04 Mar '03

The draft requirements specification for Text over IP is available in a new version (0.0.5) in http://www.totalconversation.org/standard/index.htm It will be handled as document number QH16-03001 in the coming ITU Q.H/16 meeting in UK on March 18-19, and also for information as Q1103-006. Please provide comments to me, if possible before March 10, or as contributions to the meeting. 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 -------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)lists.intel.com

1 0