Live data from Hacker News

Viewing profile — jlivingood

jlivingood

HN member
Joined
Mon, Sep 15, 2014, 6:54 PM UTC
HN karma
209
Public activity
23 items

About jlivingood

No profile information was provided.

Recent public activity

  1. comment
    Comment #46046743

    For folks following this here - node and neighborhood look clean. The issue appears to be a failing cable modem (MB8611 - they seem to suffer frequent disconnects when they fail). …

  2. comment
    Comment #38601281

    Several D3.1 modems support it now but most will need to be updated. Many of the vendors have been testing at quarterly L4S interop events, so I would expect them all to have produ…

  3. comment
    Comment #38601261

    UTP is intended to be less than best effort priority. This is about all the apps trying to share queues at best effort (1 level up).

  4. comment
    Comment #38601257

    I wrote a simplified summary of the IETF specs FWIW: https://github.com/jlivingood/IETF-L4S-Deployment/blob/main/...

  5. comment
    Comment #38601247

    It makes new cloud-based apps realistically & reliably workable - think cloud gaming and cloud AR. It also makes interactive stuff like gaming and video conferencing perform a lot …

  6. comment
    Comment #38601226

    See my comment above - doubt this will happen - rather it will become a differentiator like thoughput.

  7. comment
    Comment #38601220

    100% agree - read my IETF Internet Draft for more on that. :-) https://www.ietf.org/archive/id/draft-livingood-low-latency-...

  8. comment
    Comment #38601209

    > "Not sure where this leads but I guess ISPs will start charging toll for express lanes" Doubtful IMO. I think latency becomes another competitive differentiator, much like throug…

  9. comment
    Comment #38601182

    It has definitely changed. Looking at measurements on this it seems there is only 1 major transit network doing that, and they are working to fix it.

  10. comment
    Comment #23644068

    > How would this work? A 1st draft of the steering mechanism just posted today for comment at https://tools.ietf.org/id/draft-rescorla-doh-cdisco-00.txt

  11. comment
    Comment #23644021

    > Comcast sniffs / records / tracks their user's DNS traffic Actually not only does Comcast say they don't do that ( https://www.xfinity.com/privacy/policy/dns ) but now has signed…

  12. comment
    Comment #23643986

    > Why would DNS have "optimized, localized results"? Any content that is CDN-based (which is most content) dynamically responds to DNS queries based on network and geographic locat…

  13. comment
    Comment #15892951

    > Why traffic injection instead of mail pieces? I mean, I open all of mine, even the 75%+ that are upsells I don't want, on the off chance one of them will tell me something I need…

  14. comment
    Comment #15892886

    It usually means you are about to get a speed upgrade that will go beyond what your modem is capable of delivering. In that case it is possible you could have a 1st generation 4x4 …

  15. comment
    Comment #15892839

    > They emailed my Comcast.net address, which I didn't even know I had. I recommend you add your primary email address. You can do this via the self-service portal. Go to https://cu…

  16. comment
    Comment #15892806

    > edit: Proof https://imgur.com/lzKBkMs If you look at the far right device you see a non-EOL SB6121. The one on the left that is EOL is the leased one, and the retail one is still…

  17. comment
    Comment #15891858

    An RFC is not always a standard - often they are simply 'informational'. For us, when we wrote the document, it was a way to document as transparently as possible how the system wo…

  18. comment
    Comment #15891697

    > I sincerely disagree, especially as per the report Comcast's own second level confirmed there was no need to replace the modem. I am skeptical of this - maybe we made a mistake i…

  19. comment
    Comment #15891584

    What I meant in the context of that exchange was that the notifications come only after for example multiple emails have not resulted in the device being replaced.

  20. comment
    Comment #15891565

    > HTTPS everywhere is excellent advice I couldn't agree more! That's one of the reasons for example we have supported groups like Let's Encrypt ( http://labs.comcast.com/innovation…

  21. comment
    Comment #15891549

    > Exactly. And the response, "we're not trying to sell you a modem, we're just encouraging you to strongly consider buying a new one" is such a hair-splittingly asinine response co…

  22. comment
    Comment #15891477

    > Although I disagree with Comcast's method and categorization, it would be interesting to learn what modem the OP was using. We start telling customers that a modem needs to be up…

  23. comment
    Comment #8320690

    Great quote!