<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2716.2200" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=096305015-14032003><FONT face=Arial color=#0000ff size=2>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. </FONT></SPAN></DIV>
<DIV><SPAN class=096305015-14032003><FONT face=Arial color=#0000ff
size=2>Dominic.</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Boyle, Kevin
[NCRTP:3Z40:EXCH] <BR><B>Sent:</B> Friday, March 14, 2003 2:16
PM<BR><B>To:</B> ITU-SG16@echo.jf.INTEL.COM<BR><B>Subject:</B> Re: T.38
potentially broken by recent Corrigendum<BR><BR></FONT></DIV>
<DIV><SPAN class=712071214-14032003><FONT face=Arial color=#0000ff
size=2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=712071214-14032003></SPAN> </DIV>
<DIV><SPAN class=712071214-14032003></SPAN><SPAN
class=712071214-14032003><FONT face=Arial color=#0000ff size=2>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.</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2>It is<SPAN
class=712071214-14032003> also my understanding that care was taken to ensure
that all known vendors were made aware of the change at the
time.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=712071214-14032003></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=712071214-14032003>Kevin</SPAN></FONT></FONT></FONT></SPAN></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Klaghofer Karl
ICN EN HS D 11 [mailto:karl.klaghofer@SIEMENS.COM] <BR><B>Sent:</B> Friday,
March 14, 2003 3:44 AM<BR><B>To:</B>
ITU-SG16@echo.jf.INTEL.COM<BR><B>Subject:</B> AW: T.38 potentially broken by
recent Corrigendum<BR><BR></FONT></DIV>
<DIV><SPAN class=420224008-14032003><FONT face=Arial color=#0000ff
size=2>Paul,</FONT></SPAN></DIV>
<DIV><SPAN class=420224008-14032003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420224008-14032003><FONT face=Arial color=#0000ff size=2>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. </FONT></SPAN></DIV>
<DIV><SPAN class=420224008-14032003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=420224008-14032003><FONT face=Arial color=#0000ff
size=2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=420224008-14032003><FONT face=Arial color=#0000ff
size=2>Karl Klaghofer</FONT></SPAN></DIV>
<DIV><SPAN class=420224008-14032003><FONT face=Arial color=#0000ff
size=2>Siemens</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Ursprüngliche Nachricht-----<BR><B>Von:</B> Paul E. Jones
[mailto:paulej@PACKETIZER.COM]<BR><B>Gesendet:</B> Montag, 3. März 2003
03:21<BR><B>An:</B> ITU-SG16@echo.jf.INTEL.COM<BR><B>Betreff:</B> T.38
potentially broken by recent Corrigendum<BR><BR></FONT></DIV>
<DIV><FONT face=Arial>
<DIV><FONT face=Arial>Folks,</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>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:</FONT></DIV><FONT face=Arial><A
href="http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-T.38">http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-T.38</A></FONT>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>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:</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV>Data-Field ::= SEQUENCE OF SEQUENCE<BR>{<BR>
field-type ENUMERATED<BR> {<BR> hdlc-data,<BR> hdlc-sig-end,<BR> hdlc-fcs-OK,<BR> hdlc-fcs-BAD,<BR> hdlc-fcs-OK-sig-end,<BR> hdlc-fcs-BAD-sig-end,<BR> t4-non-ecm-data,<BR> t4-non-ecm-sig-end<U><FONT
color=#ff0000>,</FONT></U><BR> <U><FONT
color=#ff0000>...</FONT></U><BR> },<BR> field-data OCTET
STRING (SIZE(1..65535)) OPTIONAL<BR>}</DIV>
<DIV><FONT face=Arial></FONT> </DIV></BLOCKQUOTE>
<DIV dir=ltr><FONT face=Arial>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.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>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.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>I am looking forward to your
replies.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>Kindest Regards,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>Paul E.
Jones</FONT></DIV></FONT></DIV>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@lists.intel.com
</BLOCKQUOTE>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@lists.intel.com
</BLOCKQUOTE>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@lists.intel.com </BLOCKQUOTE></BODY></HTML>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@lists.intel.com