Hello Hugo,
Thank you for this very thorough review of the QLOG documents!
Some of your remarks were clear (editorial) errors and I have changed them
in a single commit here:
https://github.com/quicwg/qlog/commit/21a3de1ec3dbcef1c636d91d841fa597f683c8f9
Others also indicate valid problems, but
Hello Damien,
Thank you for bringing this to our attention.
I agree you have a point and have to admit that, at first, I was confused,
because I thought we already defaulted to logging the wire image/unscaled
value instead of the scaled one.
As such, I think your suggestion is a sensible one and
Hello all,
Sorry for the late reply from my end; I had some troubles posting to the
list and my original reply got lost in moderation.
I can appreciate both sides of the argument here.
Originally I tended more towards Damien's suggestion and opened a PR for it
at
qlog RFCs, shall we? :)
With best regards,
Robin
[1]:
https://www.ietf.org/archive/id/draft-ietf-quic-qlog-main-schema-04.html#name-security-and-privacy-consid
[2]: https://github.com/quicwg/qlog/issues/259
--
dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Digital Media
*Cel
uic-qlog-datagram
[7]: https://github.com/quicwg/qlog/issues/261
[8]: https://github.com/quicwg/qlog/issues/134
[9]: https://github.com/quicwg/qlog/issues/262
--
dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Digital Media
*Cellphone *+32(0)497 72 86 94
www.uhasselt.be
uld
> become accustomed to a new version of QUIC being released on a regular
> cycle, so that implementer and operators build out the processes needed to
> stay compatible and up-to-date.
>
> Cheers
> Lucas
>
>
> [1] - https://www.w3.org/2001/tag/doc/evergreen-web/
>
>
>
>>
--
dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Digital Media
*Cellphone *+32(0)497 72 86 94
www.uhasselt.be
Universiteit Hasselt - Campus Diepenbeek
Agoralaan Gebouw D - B-3590 Diepenbeek
Kantoor EDM-2.05
interesting QUIC discussions!
Robin, Chris, Lars and Jörg
On Tue, 14 Sept 2021 at 21:58, Robin MARX wrote:
> Hello everyone,
>
> Just a small update on the upcoming EPIQ workshop, which will be
> co-located with the CoNEXT conference in December.
>
> The paper and poster submission
e
> when replying, or save it for the meeting :)
>
>
>
> [1] https://www.mail-archive.com/openssl-project@openssl.org/msg02585.html
>
> [2]
> https://mta.openssl.org/pipermail/openssl-project/2021-October/002777.html
>
> [3] https://trac.ietf.org/trac/ietf/meeting/wik
e
> when replying, or save it for the meeting :)
>
>
>
> [1] https://www.mail-archive.com/openssl-project@openssl.org/msg02585.html
>
> [2]
> https://mta.openssl.org/pipermail/openssl-project/2021-October/002777.html
>
> [3] https://trac.ietf.org/trac/ietf/meeting/wik
. if people are interested.
[1]: https://www.ietf.org/id/draft-ietf-quic-qlog-main-schema-01.html
[2]: https://qvis.quictools.info/
With best regards,
Robin
On Wed, 20 Oct 2021 at 16:19, Robin MARX wrote:
> Hello everyone,
>
> As discussed during IETF 111, we are looking to update qlo
st regards,
the qlog editors
P.S. note that we also still plan to keep the normal JSON non-streaming
format intact, leading to two "main" formats defined in the spec: 1) normal
JSON and 2) JSON text sequences.
--
dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Di
a bit more time to submit interesting work.
All other information can still be found on the web page:
https://epiq21.github.io
Looking forward to reading lots of interesting stuff,
Robin, Chris, Lars and Jörg
On Tue, 20 Jul 2021 at 14:35, Robin MARX wrote:
> Hello everyone,
>
> I
eating
> a robust data definition.
>
> Speaking as a co-chair, getting clear consensus about the topic of schema
> and serialization is important at this stage of the document's lifecycle. I
> want to make sure we're asking the right questions now, and we understand
> the potential impac
.github.io
Hoping to receive an abundance of interesting work,
Robin, Lars, Jörg and Chris
On Thu, 10 Jun 2021 at 16:59, Robin MARX wrote:
> Hello all,
>
> I wanted to send a small update regarding the academic EPIQ workshop.
>
> In an email earlier this year (see below) we wanted t
need a heuristic to determine if
> the potential benefit of going multipath is worth the energy cost of
> probing multiple paths before you do so.
>
> Thanks,
> Lars
>
>
--
dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Digital Media
*Cellphone *+32(0)497 72 86 94
www.uhasselt.be
Universiteit Hasselt - Campus Diepenbeek
Agoralaan Gebouw D - B-3590 Diepenbeek
Kantoor EDM-2.05
is interested in the experimental details about multi-path quic,
> please let us know.
> All the feedbacks and suggestions are appreciated!
>
> Best regards,
> Yanmei
>
--
dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Digital Media
*Cellphone *+32(0)
ity and privacy aspects for EPIQ.
This is aided by Christopher Wood from Apple joining the team.
If you have any questions or remarks, please let us know!
[1]: https://www.ndss-symposium.org/ndss2020/cfp-quips-workshop/
With best regards,
Robin, Lars, Jörg and Chris
On Tue, 26 Jan 2021 at 18:40, Robin M
quot; but I prefer
> if it comes with URLs and/or approximate datetimes.) Is it, for
> instance, a good idea to advise privacy-oriented clients to always
> shut down QUIC connections when IP address changes?
>
>
>
>
>
>
--
dr. Robin Marx
Postdoc researcher - Web proto
QUIC wg adoption will be escalated to the ADs. Thanks for
mentioning this.
With best regards,
Robin
On Mon, 10 May 2021 at 16:45, Michael Richardson
wrote:
>
> Robin MARX wrote:
> > I agree there is significant overlap between PCAP and qlog
> conceptually
> > (thoug
t; I would have liked
> > RFC 1 more :)
> > that is the number we would brake the 4 digit RFC numbering
> >
>
> That is comming, it is roughly 4-5 years into the future. So starting a
> moderate
> complex specification today and you have some chance for RFC 10000.
>
ing streams from both ends,
> and interleaving actual captured traffic at the same time.
> (And still doesn't require access to cleartext to debug)
>
> --
> Michael Richardson. o O ( IPv6 IøT consulting )
>Sandelman Software Works Inc, Ottawa and Worldwide
> --
&
m/ipfs-rust/quinn-noise
> [4] https://matrix.to/#/#quinn:matrix.org
>
>
--
dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Digital Media
*Cellphone *+32(0)497 72 86 94
www.uhasselt.be
Universiteit Hasselt - Campus Diepenbeek
Agoralaan Gebouw D - B-3590 Diepenbeek
Kantoor EDM-2.05
wider IETF energy to pursue
>> qlog extensions. If so, the case for putting the main schema outside quicwg
>> is pretty strong.
>>
>> On Mon, Nov 23, 2020 at 12:14 PM Lucas Pardue
>> wrote:
>>
>>> Thanks Robin!
>>>
>>> I have some resp
ietf.org/html/rfc5234
> 2 - https://tools.ietf.org/html/rfc8610
> 3 - https://tools.ietf.org/html/rfc7950
> 4 - https://tools.ietf.org/html/rfc7951
> 5 - https://tools.ietf.org/html/rfc8618
> 6 - https://tools.ietf.org/html/rfc8949
> --
> Pieter Lexis
> PowerDNS.COM BV
.
With best regards,
Robin, Lars and Jörg
On Tue, 26 Jan 2021 at 18:40, Robin MARX wrote:
> Hello all,
>
> With this email, we would like to gauge the interest for a new edition of
> the academic EPIQ workshop in 2021.
>
> For those unfamiliar, the Workshop on the Evol
let us know by Tuesday February 2nd, as the SIGCOMM Workshop
submission deadline is February 5th.
If interest is deemed too low or the workshop is not accepted at SIGCOMM,
we will postpone the workshop to another conference (likely CoNEXT) or next
year.
With best regards,
Robin Marx (joining the team
another venue. However, it would be valuable for you to request a
>> HotRFC slot to encourage the parallel development of qlog-based standards
>> in other working groups.
>>
>> If that's agreeable to you, feel free to proceed.
>>
>> Martin
>>
>
--
Robin Marx
PhD researcher - web performance
Expertise centre for Digital Media
T +32(0)11 26 84 79 - GSM +32(0)497 72 86 94
www.uhasselt.be
Universiteit Hasselt - Campus Diepenbeek
Agoralaan Gebouw D - B-3590 Diepenbeek
Kantoor EDM-2.05
f.org/html/draft-marx-qlog-main-schema-02
[2]: https://tools.ietf.org/html/draft-marx-qlog
-event-definitions-quic-h3-02
[3]: https://github.com/quiclog/qvis
On Thu, 5 Nov 2020 at 17:51, Robin MARX wrote:
> Hello everyone,
>
> As you might have seen, I submitted draft-02 of the qlog f
n2020.pdf
[4]: https://github.com/quiclog/internet-drafts/issues/53
[5]: https://github.com/quiclog/internet-drafts/issues/85
[6]: https://www.youtube.com/watch?v=LiNLz1QuT0s=3233
--
Robin Marx
PhD researcher - web performance
Expertise centre for Digital Media
T +32(0)11 26 84 79 - GS
serious and
> easily detectable performance problems.
>
> Presenting a bunch of uniflows to a sever and leaving it responsible for
> using them properly seems to me quite a similar problem.
>
> Lucas
>
>
>>
--
Robin Marx
PhD researcher - web performance
Expertise c
This is actually a post that belongs in this thread :
http://groups.google.com/group/android-developers/browse_thread/thread/e677b894b4c502d9/5eb4d892c12a8393
But since it is closed I will open a new thread. If a moderator could
add this post to the above thread and re-open it, that would be
Since I can't seem to find the answer on google, nor in the docs, I
hope someone here can help me.
Whenever I try to do a query with more then 1 SUM-field in it, it will
only return the first SUM-field, not the other ones in its results.
So for instance :
SUM( amount1 ) as amountOne, SUM(
First of all, we have no idea whatsoever on how to access the opencore
functionality from our native code (or from java). We found a lot of
posts from people saying they are using the encoders/decoders
directly, or trying to add extra format-support etc. but nowhere do we
find documentation on
Hello,
For a research project we need to capture video on the HTC magic and
transmit this video over a network to other devices, both HTC magic's
and desktop pc's (which have their own implementations of the
codecs).
For the transmission over the network we are using some of our own
native
34 matches
Mail list logo
