15 Apr 16 20:06, you wrote to me:

 SH>   Re: FSP-1040.001 draft 2
 SH>   By: mark lewis to Rob Swindell on Fri Apr 15 2016 11:44 am

 >> confirmed... i see it here in the latest posting, too...

 SH> Do you mean you see it in draft 3?  If so, please point it out, I can't
 SH> find it happening here.

i haven't seen a draft 3 yet... at least not one by subject line and i don't
recall seeing one by the header of the proposal... it may be arriving in
another pkt, though...

in either case, here in the "draft 2" subject thread, the breakage is seen in
section 5 at the end where you describe the contents of the datetime field...
specifically, the breakage is in the section where you give the values for the
hour field...


in the "draft 1" thread, this portion looks like this...

----- snip -----
    hour        = "00" / "01" / "02" / "03" / "04" / "05" / "06" / "07" /
                  "08" / "09" / "10" / "11" / "12" / "13" / "14" / "15" /
                  "16" / "17" / "18" / "19" / "20" / "21" / "22" / "23" /
                  "24"

    zeroToSixty = "00" / "01" / "02" / "03" / "04" / "05" / "06" / "07" /
                  "08" / "09" / "10" / "11" / "12" / "13" / "14" / "15" /
                  "16" / "17" / "18" / "19" / "20" / "21" / "22" / "23" /
                  "24" / "25" / "26" / "27" / "28" / "29" / "30" / "31" /
                  "32" / "33" / "34" / "35" / "36" / "37" / "38" / "39" /
                  "40" / "41" / "42" / "43" / "44" / "45" / "46" / "47" /
                  "48" / "49" / "50" / "51" / "52" / "53" / "54" / "55" /
                  "56" / "57" / "58" / "59" / "60"

    minute      = zeroToSixty

    second      = zeroToSixty

    dateTime    = dayOfMonth " " month " " year "  " hour ":" minute ":"
                 second %x00

    January 1st, 2016 at 11:15:55pm would therefore be
    "01 Jan 16  23:15:55" with a NUL at the end.  Notice the two spaces
    between the year and the hour.

    This format ensures the broadest compatibility however, other
    formats are known to be in use.  SEAdog has been known to use the
    format "Mon  1 Jan 86 02:34" with a single NUL terminator.

  After the message text is either the next message or the two-NUL
  packet terminator.

  Note that some old systems MAY terminate the message text with an EOF
  (0x1A) or the literal end of the file.  Some even older systems MAY
  terminate the message text with an empty line (0x0D 0x0A 0x0D 0x0A).
  To detect this, software MAY use the NUL in the second byte of the Type
  field to attempt to resynchronize.  It is up to the developer if this
  needs to be supported.

  Since the packed message header only contains 2D addresses, the text
  SHOULD have addressing control paragraphs as specified in FTS-4001
  added when messages are packed
----- snip -----


but in this "draft 2" thread, it looks like this...


----- snip -----
    hour        = "00" / "01" / "02" / "03" / "04" / "05" / "06" / "07" /
                  "08" /ystems MAY terminate the message text with an EOF
  (0x1A) or the literal end of the file.  Some even older systems MAY
  terminate the message text with an empty line (0x0D 0x0A 0x0D 0x0A).
  To detect this, software MAY use the NUL in the second byte of the Type
  field to attempt to resynchronize.  It is up to the developer if this
  needs to be supported.

  Since the packed message header only contains 2D addresses, the text
  SHOULD have addressing control paragraphs as specified in FTS-4001
  added when messages are packed
----- snip -----


i don't know what changes there may have been in that area between "draft 1"
and "draft 2"...


NOTE that the last paragraph needs an ending period (.) too ;)

)\/(ark

Always Mount a Scratch Monkey

... If it's on television, it must be good.
---