W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

Re: New Version Notification for draft-kamp-httpbis-structure-01.txt (fwd)

From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 17 Nov 2016 18:11:51 +0900
Message-ID: <CANatvzx1mASDCBKdFNWWHAK5SFB-wv5F0n+NvD0R7K9cRGMyBA@mail.gmail.com>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Willy Tarreau <w@1wt.eu>, HTTP Working Group <ietf-http-wg@w3.org>
2016-11-17 17:34 GMT+09:00 Poul-Henning Kamp <phk@phk.freebsd.dk>:
> --------
> In message <CANatvzwrPxyRPET5SO6fYGZ_6NnqToU9a630x1gjZXx5uAbeuw@mail.gmail.com>
> , Kazuho Oku writes:
>
>>Yes. Therefore, I believe that the we should discourage people from
>>using fixed point numbers.
>
> That ship has already sailed since q=0.5 does not use integers.
>
> But please note that this is a generic *data model*, and therefore
> it should "deliver tools, not policies".

Hi,

Thank you for the response. I totally support your intention to
deliver tools, not policies.

My point is that the draft should not “enforce a policy” to implement
floating point parsers even in case you need to only handle integers.

For example, consider the case in which I am writing a draft that
passes an integer using Common Structure.

Since Common Structure allows an integral number to be sent with a
dot, a sender is permitted to send 100 as “100.00”, which means that
you would need to decode a floating point number even in the case
where you only need to deal with integers.

My understanding is that most (if not all) headers that will use
Common Structure would need to encode floating point numbers. And
therefore I am looking for a clause that makes decoders without a
floating point parser to be comformant to the specification (until
actually facing a need to decode floating points).

> By this I mean that people may legitimately want to move non-integers,
> deep structures and unicode strings, and it would be counterproductive
> to force them to invent a parallel format to do that.
>
> However, each individual header will have to define which _actual_
> data you are allowed to put in it, and a general antipathy against
> non-integers is probably wise there.
>
> Summary: So if you don't like non-integers, don't use them in the
> HTTP-headers you invent, but don't tell other people what data
> types they are allowed to use.
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.



-- 
Kazuho Oku
Received on Thursday, 17 November 2016 09:12:30 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 17 November 2016 09:12:32 UTC