From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsahern@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Xin Long <lucien.xin@gmail.com>,
network dev <netdev@vger.kernel.org>,
Simon Horman <simon.horman@netronome.com>
Subject: Re: [PATCHv3 iproute2-next 3/7] iproute_lwtunnel: add options support for erspan metadata
Date: Mon, 27 Apr 2020 16:07:57 -0700 [thread overview]
Message-ID: <20200427160757.38ebc7a5@hermes.lan> (raw)
In-Reply-To: <70c448c7-cf2e-1f63-e4ea-03e73077c0d1@gmail.com>
On Mon, 27 Apr 2020 06:38:03 -0600
David Ahern <dsahern@gmail.com> wrote:
> On 4/23/20 12:03 PM, Jakub Kicinski wrote:
> > On Thu, 23 Apr 2020 08:23:51 -0700 Stephen Hemminger wrote:
> >> 3. If non json uses hex, then json should use hex
> >> json is type less so { "ver":2 } and { "ver":"0x2" } are the same
> >
> > I may be missing something or misunderstanding you, but in my humble
> > experience that's emphatically not true:
> >
> > $ echo '{ "a" : 2 }' | python -c 'import sys, json; print(json.load(sys.stdin)["a"] + 1)'
> > 3
> > $ echo '{ "a" : "2" }' | python -c 'import sys, json; print(json.load(sys.stdin)["a"] + 1)'
> > Traceback (most recent call last):
> > File "<string>", line 1, in <module>
> > TypeError: can only concatenate str (not "int") to str
> >
>
> I don't know which site is the definitive source for json, but several
> do state json has several types - strings, number, true / false / null,
> object, array.
Probably I got confused because Python tries to be helpful...
JSON is ossified/standardized http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf
Best answer on the web was https://stackoverflow.com/questions/52671719/can-hex-format-be-used-with-json-files-if-so-how
"JSON does not support hexadecimal numbers but they are supported in JSON5. json5.org"
next prev parent reply other threads:[~2020-04-27 23:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 10:30 [PATCHv3 iproute2-next 0/7] iproute2: fully support for geneve/vxlan/erspan options Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 1/7] iproute_lwtunnel: add options support for geneve metadata Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 2/7] iproute_lwtunnel: add options support for vxlan metadata Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 3/7] iproute_lwtunnel: add options support for erspan metadata Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 4/7] tc: m_tunnel_key: add options support for vxlan Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 5/7] tc: m_tunnel_key: add options support for erpsan Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 6/7] tc: f_flower: add options support for vxlan Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 7/7] tc: f_flower: add options support for erspan Xin Long
2020-02-14 16:13 ` [PATCHv3 iproute2-next 3/7] iproute_lwtunnel: add options support for erspan metadata Stephen Hemminger
2020-02-14 17:40 ` Xin Long
2020-02-15 0:21 ` Stephen Hemminger
2020-02-15 4:18 ` Xin Long
2020-02-15 16:51 ` David Ahern
2020-02-16 6:38 ` Xin Long
2020-02-17 19:53 ` David Ahern
2020-02-17 21:02 ` Stephen Hemminger
2020-02-18 4:29 ` Xin Long
2020-04-19 8:39 ` Xin Long
2020-04-19 22:28 ` David Ahern
2020-04-23 11:06 ` Xin Long
2020-04-26 18:29 ` David Ahern
2020-04-27 5:51 ` Xin Long
2020-04-23 15:23 ` Stephen Hemminger
2020-04-23 18:03 ` Jakub Kicinski
2020-04-27 12:38 ` David Ahern
2020-04-27 23:07 ` Stephen Hemminger [this message]
2020-04-28 7:22 ` Xin Long
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200427160757.38ebc7a5@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).