Gary E. Miller via devel writes:
> Which is not what the hackathon people thought.
So, you can mind-read now and expect everyone else to do the same? What
was the problem they've had and how didi they say they wanted to solve
it?
> Can you point out where in the API so I can ask the Hackathon
Sorry for the delay. I got distracted on other things.
While I think of it, did TESTFRAME dump floating point numbers in ASCII or
hex? If ASCII, there are likely to be round off errors when you read them
back in. Were there any floating point numbers that were read back in? (as
compared
Yo Achim!
On Tue, 23 Jul 2019 21:12:37 +0200
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> > Yes, it is the length. Should it be there or not? Opinions
> > differed at the Hackathon.
>
> It should be there in the alpn vector (which in the case of NTS
> consists of just
Gary E. Miller via devel writes:
> Yes, it is the length. Should it be there or not? Opinions differed
> at the Hackathon.
It should be there in the alpn vector (which in the case of NTS consists
of just one single element), per the API description. The out parameter
should point after the
Yo Fred!
On Mon, 22 Jul 2019 21:01:44 -0700 (PDT)
Fred Wright via devel wrote:
> On Mon, 22 Jul 2019, Gary E. Miller via devel wrote:
>
> > No one has a solid answer to the NTS ALPN issue?
> >
> > "at some time the NTPSEC server would return "\x07ntske/1" instead
> > of just "ntske/1"."
>
>
