Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] meanwhile... .home, finally has a home.arpa.
Date: Tue, 23 Oct 2018 09:15:59 -0700	[thread overview]
Message-ID: <CAA93jw5asbkp2ZvAbOBNa-zOAq2aYf42CA=2gZ++5-gjJxhXow@mail.gmail.com> (raw)
In-Reply-To: <CAPt1N1nfMfH5NP8DXjNpHZSE83UfBRKbwUb8xE6Cv8c5VrczOw@mail.gmail.com>

On Tue, Oct 23, 2018 at 8:42 AM Ted Lemon <mellon@fugue.com> wrote:
>
> That is good feedback, if depressing.   I'm kind of in the same boat—I really want to do some work on this for OpenWRT, but it hasn't come up to the top of the stack yet.   The reason I was asking is that when I've said at IETF that I don't think HNCP is actually complete yet, I get a lot of rotten tomatoes from the authors.

Did they ever get it to work over dtls?

  reply	other threads:[~2018-10-23 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  3:51 Dave Taht
2018-10-23  4:13 ` Ted Lemon
2018-10-23 15:09   ` Dave Taht
2018-10-23 15:42     ` Ted Lemon
2018-10-23 16:15       ` Dave Taht [this message]
2018-10-23 16:44         ` Ted Lemon
2018-10-23 15:47     ` Mikael Abrahamsson
2018-10-23 16:12       ` Dave Taht
2018-10-24  8:22         ` Mikael Abrahamsson
2018-10-24 16:39           ` Dave Taht
2018-10-24 18:04             ` Mikael Abrahamsson
2018-10-23 23:28     ` Michael Richardson
2018-10-23 23:38       ` Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5asbkp2ZvAbOBNa-zOAq2aYf42CA=2gZ++5-gjJxhXow@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mellon@fugue.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