A side meeting does not need any permissions from the IESG, all that is needed is to decide on a time and place and announce it to the world. At some point the extra rooms will be opened for reservation so you can ensure that you have a room.
Do not expect the same type of turnout for a side meeting that you would get for a BOF. I have been to side meetings with as few as five people and as many as twenty, but it is generally on the lower side. If you are going to try for a BOF, expect that the cutoff date is going to be around the first of February. At a minimum you would need to have a good description of the problem and scope you want to cover. You do not need to have a regular IETF goer make the request, this is open to anybody. Instructions can be found here https://www.ietf.org/how/bofs/. Jim From: jose <[email protected]> On Behalf Of Bret Jordan Sent: Friday, December 7, 2018 10:25 AM To: Anders Rundgren <[email protected]> Cc: [email protected] Subject: Re: [jose] Performance of Canonical JSON Thanks for the test data. Are you going to request a side meeting for Prague? Bret Sent from my Commodore 128D PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 On Dec 7, 2018, at 9:23 AM, Anders Rundgren <[email protected] <mailto:[email protected]> > wrote: Since XML Canonicalization has a reputation of not only being brittle but also terribly slow, I tested JCS [1] with the following JSON file: { "1": {"f": {"f": "hi","F": 5} ,"\n": 56.0}, "10": { }, "": "empty", "a": { }, "111": [ {"e": "yes","E": "no" } ], "A": { } } Expected output: {"":"empty","1":{"\n":56,"f":{"F":5,"f":"hi"}},"10":{},"111":[{"E":"no","e":"yes"}],"A":{},"a":{}} Since JCS only is a serialization concept (parsing is unaffected), I compared the execution speed of standard serialization versus canonicalized serialization. Using https://www.npmjs.com/package/canonicalize the performance penalty was about 2.4 compared to JSON.stringify(). Using my homegrown JSON tools written in Java having an integrated "canonicalize" serializer option the performance penalty was about 1.4 Anders 1] https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-01 _______________________________________________ jose mailing list [email protected] <mailto:[email protected]> https://www.ietf.org/mailman/listinfo/jose
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
