There must be a new one to handle the new (Thai-excepted) non-latin character sets.
i ------ Original Message ------ Received: 08:13 PM COT, 11/05/2009 From: Paul Gilmartin <[email protected]> To: [email protected] Subject: Re: Using PIPE to obtain the GMT time from an ntp server? > On 11/05/09 11:17, Rob van der Heij wrote: > > > > On Thu, Nov 5, 2009 at 6:54 PM, Jack Woehr <[email protected]> wrote: > > > >> But it's on VMTOOLS and that's part of the distrib, right, not something I > >> can download and look at the Rexx? > > > > It has nothing to do with the built-in stage, so would not be helpful > > to see the cause. > > From what I can tell, CMS Pipelines just decides it must be an IP > > address based on the first character of the parameter. I believe this > > was a valid test in the past (until 3COM got some arms bent for the > > domain). > > > I was unaware of such arm-bending. However RFCs 882 and 883 (November > 1983) say: > > Appendix 1 - Domain Name Syntax Specification > > The preferred syntax of domain names is given by the following BNF > rules. Adherence to this syntax will result in fewer problems ... > > The labels must follow the rules for ARPANET host names. They must > start with a letter, end with a letter or digit, and have as interior > characters only letters, digits, and hyphen. ... > > "preferred" is dismayingly noncommittal. > > RFC 1035 (November 1987) describes a binary form which allows any octet > (even ".") to appear within a label, but specifies no representation as > text. Ugh. Does anyone know of an RFC that's more definitive about this? > > -- gil >
